Fail to send an email with tokenized link

[SESA598759]

I would like to use an external link with Marketo id being tracked in my email.

The token: {{my.Marketoid}} is as follows,

#set ( $mylink = "www.wjx.cn/vj/hDlbBiY.aspx?sojumpparm=${lead.Marketo_ID}" )
<a href="http://${mylink}" style="color: #FFFFFF">Survey</a>

It works well in the preview and sample email, but I cannot send a real one via a smart campaign.

[Phillip_Wild]

Hi there

When you say "you cannot send a real one", what is the exact error you are seeing? Is the email failing to send, and you receive an error? Or is the link not output correctly?

Thanks!

[SESA598759]

There isn't an error notification at all. I just cannot receive the email finally.

I can run the "send email" batch campaign, but Marketo even has no record of sending that email.

[Katja_Keesom]

Did you add your personal record to the database? Make the email operational? Have you set your smart campaign to allow for your database record to flow through every time?

Sounds like the issue may not be with the script so much, but with your sending process.

[SESA598759]

The sending failure only happens to the email with a tokenized link. If I switch to sending another normal email, it is OK.

I ignore the communication limit, btw.

[Michael_Florin]

Did you get a notification on your batch send failing? I'm asking because we got this note from Support one month ago:

"We introduced a new validation (without a formal notice) that was supposed to fail email script tokens being put in the URL because the link was showing the script and Eng says we don't support script tokens in links.

This breaks a number of Batch Campaigns because customers are relying on this functionality and we made no announcement about a change to this behavior. We've gotten Eng to roll back to the change so that campaigns stop failing but we'll need to have a conversation with Eng on what the expected functionality going forward is and make sure that any behavior changes are documented and announced in advance. Failed Campaigns can be found in your Notifications section."

[SanfordWhiteman]

I believe that note relates to Velocity tokens erroneously included within links in the email asset, i.e. as part of a link, the rest of which isn't coming from Velocity. That's never been supported officially but sometimes worked.

That's different from outputting the entire link from Velocity, which has always been the supported method (and is what @SESA598759 is doing).

[SESA598759]

Thanks for your reply.

I didn't receive any notifications. But when I look at the "Results" of the batch campaign, it shows nothing. I suppose this time we have to find another way out. 

If you have other methods to track users' responses to a survey, please kindly share them with me. Appreciate it a lot!

[SanfordWhiteman · Accepted solution]

Take out the Send Email step and replace it and replace it with something easy to trace like a Change Data Value that sets a Datetime field to {{system.datetime}}. Don't make any other changes and run it for the exact same lead you were just testing with. What happens?

If you have other methods to track users' responses to a survey, please kindly share them with me. Appreciate it a lot!

---

I don't actually understand why you've chosen to use Velocity in this case. It's a lead field, and it presumably doesn't require encoding (you aren't running it through $esc.url()), so the link can be right in the email content with a {{lead.token}} in the query string.

[NCHAN]

"Change Data Value" was run normally.

We have tried to directly use {{lead.ID}} in the link in that email, and it works well now. Many thanks!