Hi there!
We are building an integration with the Hubspot Email tool for the Passendo ad server. For this, we need macros for merging of the email of the email receipient, as well as a timestamp variable.
The timestamp variable works fine with this:
{{ content.publish_date }}
However, we cant seem to find a variable that correctly merges the email. For example, if I were to receive an email sent via Hubspot, I’d like my email to be merged in the tag below as ‘dl@passendo.com’.
We have already confirmed that ‘{{ content.author_email }}’ works in our tag by inserting the email from the SENDER of the email. So we really just need the correct variable for use the other way around. Example with Mailchimp as the ESP, the macro is simply “*|EMAIL|*”
Hope to hear from you soon!
Kind Regards, Dexter Landau, Client Success Manager
Example tag (contains macro for the author of the email, where we need instead the macro for the receipient of the email, as defined in the list of subscribers receiving the sendout:
<table border=‘0’ cellpadding=‘0’ cellspacing=‘0’><tr><td style=‘font-size: 0px;’><a href=‘http://images.passendo.com/click/2/4418/{{ content.author_email }}/{{ content.publish_date }}’><img src=‘https://images.passendo.com/view/2/4418/{{ content.author_email }}/{{ content.publish_date }}’></a><img width=‘1’ height=‘1’ style=‘display:none;border-style:none;’ alt=‘’ src=‘https://images.passendo.com/t/2/4418/{{ contact.email }}/{{ content.publish_date }}/0/0’><img width=‘1’ height=‘1’ style=‘display:none;border-style:none;’ alt=‘’ src=‘https://images.passendo.com/extt/2/4418/{{ contact.email }}/{{ content.publish_date }}?pid=1’><img width=‘1’ height=‘1’ style=‘display:none;border-style:none;’ alt=‘’ src=‘https://images.passendo.com/extt/2/4418/{{ contact.email }}/{{ content.publish_date }}?pid=2’><img width=‘1’ height=‘1’ style=‘display:none;border-style:none;’ alt=‘’ src=‘https://images.passendo.com/extt/2/4418/{{ contact.email }}/{{ content.publish_date }}?pid=3’><img width=‘1’ height=‘1’ style=‘display:none;border-style:none;’ alt=‘’ src=‘https://images.passendo.com/extt/2/4418/{{ contact.email }}/{{ content.publish_date }}?pid=4’></td></tr><tr><td style=‘font-size: 0px;’><a title=‘Privacy Info’ target=‘_blank’ href=‘Passendo Privacy{{ contact.email }}/{{ content.publish_date }}’><img src=‘https://images.passendo.com/ppv/2/4418/{{ contact.email }}/{{ content.publish_date }}’></a></td></tr></table>
Hi, @Passendo.
Happy to help.
It sounds like you’re describing the HubL variable {{ contact.email }}, which will pull in the contact — or recipient’s — email address. I see this token several times in your template, though, so perhaps I’ve misunderstood you.
If this isn’t what you’re looking for, could you describe what you mean by “merging” an email address in more detail?
Hi Isaac
Thanks for reaching out.
Although we couldnt find {{ contact.email }} on the list of variables, we actually assumed that that would be the correct variable. We also tried in the test tag. But the problem was that the following was merged on the URL’s using this variable:
%3Cimg%20data-mce-placeholder=%22true%22%20data-mce-resize=%22false%22%20class=%22mce-token%20sorbet%22%20style=%22width:%2058px;%20height:%2020px;%20background:%20
So basically a completely messy encoding instead of replacing the variables with the email address and timestamp. Whereas this string: {{ content.author_email }}/{{ content.publish_date }} correctly merged as the author’s email address and the timestamp.
So basically, what we are looking for, is a variable that when inserted in the tag will replace itself with the raw email address of the recipient so the output ends up being “/dl@passendo.com/2019-02-07%2009:03:19/”
Hope this clarifies!
Hey, @Passendo.
Could you share a link to an email draft where you’re experimenting with these variables?
I just sent myself an email with links containing the {{ contact.email }} token and it worked perfectly. If anything, the spaces in the {{ content.publish_date }} value caused issues. See the screenshot below for how I formatted my links and the results.
Hi Isaac
I have inserted the tag in this draft:
As you might see, we don’t need the macros to be formatted in the mail itself, but rather be passed on on links and view requests coming into our server via the tag:
<table border=‘0’ cellpadding=‘0’ cellspacing=‘0’><tr><td style=‘font-size: 0px;’><a href=‘http://images.passendo.com/click/2/4418/{{ contact.email }}/{{ content.publish_date }}’><img src=‘https://images.passendo.com/view/2/4418/{{ contact.email }}/{{ content.publish_date }}’></a><img width=‘1’ height=‘1’ style=‘display:none;border-style:none;’ alt=‘’ src=‘https://images.passendo.com/t/2/4418/{{ contact.email }}/{{ content.publish_date }}/0/0’><img width=‘1’ height=‘1’ style=‘display:none;border-style:none;’ alt=‘’ src=‘https://images.passendo.com/extt/2/4418/{{ contact.email }}/{{ content.publish_date }}?pid=1’><img width=‘1’ height=‘1’ style=‘display:none;border-style:none;’ alt=‘’ src=‘https://images.passendo.com/extt/2/4418/{{ contact.email }}/{{ content.publish_date }}?pid=2’><img width=‘1’ height=‘1’ style=‘display:none;border-style:none;’ alt=‘’ src=‘https://images.passendo.com/extt/2/4418/{{ contact.email }}/{{ content.publish_date }}?pid=3’><img width=‘1’ height=‘1’ style=‘display:none;border-style:none;’ alt=‘’ src=‘https://images.passendo.com/extt/2/4418/{{ contact.email }}/{{ content.publish_date }}?pid=4’></td></tr><tr><td style=‘font-size: 0px;’><a title=‘Privacy Info’ target=‘_blank’ href=‘Passendo Privacy{{ contact.email }}/{{ content.publish_date }}’><img src=‘https://images.passendo.com/ppv/2/4418/{{ contact.email }}/{{ content.publish_date }}’></a></td></tr></table>
But if these macros should work, we’ll definitely have your client make a test sendout with them and see if it works 
We might have done something wrong on our end when testing it via our own account.
Regards, Dexter
Hey, @Passendo.
Just to make sure we’re on the same page, you’re referring to the source code in that email’s Main Email Body module, right?
If so, I count the same nine {{ content.publish_date }} variables in that table, but the {{ contact.email }} variables you cite are nowhere to be found.
Instead, it looks like the variable may have been split and/or improperly encoded as data-mce-property-category="contact" data-mce-property-name="email" data-mce-property-label="Email">, per the screenshot below. Am I looking in the right place? If I am, the recipients’ email addresses aren’t being pulled in because the {{ contact.email }} HubL token is unrecognizable.
If you add {{ contact.email }} directly into the source code of this table, I would expect the token to work.
Hi Isaac
You may just have solved our problem.
We were probably inserting the tags via copy and paste based on the impressions we could add html straight from the frontend UI, we didn’t recognize we actually had the ability to edit the source code, which is much preferred. This also explains why the variable was replaced with random formatting.
When looking at a second glance, we found the button for editing the source code, and this should give the result we hope for.
Thank you for your help, we’ll do some testing with our (mutual) client from here and cross our fingers that the integration works!
Kind regards, Dexter
