I wanted to create a message where we acknowledge the amount of time someone has been engaging with our organization, specifically, how long they have been a member. Using two date contact properties (let’s call them “membership join date” and “Today’s date”, a fancy property I set up following what I learned at https://community.hubspot.com/t5/CRM/How-to-create-a-Today-s-date-date-property/m-p/389836), I successfully created a Calculated contact property “years since membership join”. When viewing the property in a contact record or contact list, values displayed as 7 months, 1 year, 4 years, etc. I was thrilled (and proud)!
Then, I added that property as a personalization token to a marketing email. Thank goodness I sent myself a test message, because it--and every attempt after, using any contact’s information--displays the correct value, just represented in MILLISECONDS. So, rather than saying something like “George, you’ve been a loyal member for 17 years”, as the value appears on George’s record, it would have said “George, you’ve been a loyal member for 536,479,200,000”.
Someone helpful from Hubspot created an additional calculation property that referenced that value, and rounded off to the nearest year. That solution only got me partway, though, because I can’t use that property as a personalization token and easily add the proper time word (eg. month, months, year, years). That would take creating several contact lists and apply smart content groupings to any message in which I plan to reference “years since membership join”.
For now, I have altered our messaging to say “you’ve been a loyal member since (insert membership join year, a different property)”. But I’d prefer to use the Time Between calculated property that Hubspot [almost completely] set up for this purpose.
Would anyone find value in Hubspot updating their time between calculated property to show values in terms of weeks/years in both contact records, lists, AND personalization tokens? Or does anyone have other ideas for how to accomplish this?
Thanks,
Pete

