Inserting Personalization Tokens in Follow-up Emails Created in Form EditorSOLVE
Jan 21, 2020 5:43 AM
Hi HubSpot Community!
I have created this post in response to customer inquiries regarding the use of personalization tokens in follow-up emails created in the HubSpot Forms tool.
Currently, the use of personalization tokens within these follow-up emails is not available. I have found a workaround that gives you the ability to insert the tokens within the simple follow-up email editor in the Forms tool.
If we use the HubL code that inserts the internal value of a property as a personalization tokens, we are able to successfully pull in the data from respective property. The HubL code used for these looks like this:
In the tests that I have ran, the HubL code inserted the value from the property in the contact record.
You would need to structure the HubL code for the internal value as follows:
If the property is two or more words (e.g. "first name") these will need to be written as one word (e.g. firstname). It is also required to include the double curly bracket at the beginning and end of the token.
There are two different ways that you can go about accessing the internal value for the property you would like to insert as a personalization token.
1. Accessing the internal value within the portal's property settings.
When you navigate to Settings > Properties and click into a property to edit, you will see the symbol for source code ("</>") listed next to the property name. By clicking onto the source code symbol, you will see what the corresponding internal name is for the property. The video below shows you what steps to take:
2. Accessing the internal value within the Email Editor
If you have access to the HubSpot Email tool, you are able to access the internal value of the personalization token within the source code of the email. You will first need to insert a personalization token in the email and then you can access the source code which will show you the internal value of the token. The video below shows you what steps to take:
I have tested this in a few follow-up emails and have always seen the value correctly pulled into the follow-up email. I would recommend testing this in your portal to ensure that this workaround is functional.
Please let me know if you have any additional questions!
Solved! Go to Solution.