Tokenizing links hurts interesting moments? | Community
Skip to main content
A
Anonymous
April 19, 2016
Question

Tokenizing links hurts interesting moments?

  • April 19, 2016
  • 2 replies
  • 2495 views

For all emails, my links are tokens set up so that in the email it shows "{{TOKEN}}" so that Marketo will register the click. For almost every email I only have one link, one CTA. But my newsletter has multiple links. I just noticed my interesting moments look odd because of this:

Marketo doesn't add in which link was clicked? Is this normal for tokenized links?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Josh_Hill13
Josh_Hill13
Level 10
April 19, 2016

Tokenized link to trigger flow and track?​

there are some other threads, but not sure if you are doing this specifically.

A
Anonymous
April 19, 2016

Hi Josh, yes that's exactly what I'm doing. My email has links that say "{{TOKEN}}" and so click links are working, but now in Interesting Moments the rest of the token is missing.

I'm guessing that either 1) it's not working as expected - the link URL should save in history, not the actual text from the email OR

2) this is working as expected because my interesting moments are under a different folder system than my programs so it can't read the tokens from another folder.

SanfordWhiteman
SanfordWhiteman
Level 10
April 20, 2016

Christina, yes, if the {{my.tokens}} are out of folder/program scope they will not work.  But you should use the {{trigger.tokens}} for IMs.

Nicholas_Manojl
Nicholas_Manojl
Level 8
April 19, 2016

I think I saw a thread the other week where someone had gone through and tested the placement of the token inside a URL.

From memory, {{my.token}} seemed to produce untrackable results (the token value being "www.xyz.com", whereas if you just put the entire value of the URL inside the token "www.xyz.com", then your links will resolve as trackable.

edit: actually I am saying the opposite to what everyone else is saying. Although personally I have never had an issue using the entire URL value inside the token.

Terms & ConditionsAccessibility statement

Loading footer...