Allow {{my.Tokens}} in visited web page triggers, filters, and choice steps

Allow {{my.Tokens}} in visited web page triggers, filters, and choice steps

It should be possible to place a {{my.Token}} in a trigger such as "Visited Web Page URL Contains" and have the token value resolve properly. Currently this isn't the case - Marketo appears to interpret the token name literally, rather than the value it represents, so using a token in a trigger like this won't allow the trigger to fire properly.

2015-06-03_09-29-28.png

Why does this matter?

The beauty of tokens is they allow you to make programs that are highly template based, with 95% of their appearance, content, and behavior set in one central place. But this sort of thing is weirdly not supported, and needs to be manually set. It's easy to forget when every other aspect of your program is token-based, and just creates extra work that really shouldn't be necessary.

Logically, tokens should work here, because we're talking about a local asset. They work great in most front-end assets,  and actually are supported in some cases in smart campaign flowsteps such as interesting moments or data value concatenation. But it's strange that they work in some situations, and not others. Allowing tokens to work here makes the functionality a lot more predictable and reliable to work with.

19 Comments
Level 6 - Champion Alumni

The work around I have found so far  is to use the token only for the final part of the link (www.pages.company.com/{{my.CTA_Link}} and to trigger on START WITH www.pages.company.com/. Of course this only works if you have one link only and I only used in in emails for CLICKS LINK IN EMAIL.

Completely agree with this.  Would be nice if you could do this for any trigger, especially the email ones.  Automate those email program progression steps. 

-Mike

I am going to try this workaround... I've used Contains with the /{{my.CTA_link}} trigger and couldn't get it to fire.  Thanks for the tip.

Level 10 - Champion Alumni

Tokens aren't supported at all within the Smart Lists of Smart Campaigns. So not sure how this would be a workaround.

Level 6 - Champion Alumni

Hi Dan, as I said, I used it only in emails and that left part of the link that was not tokenized (www.pages.company.com/) that I could use in a smart list.

Level 10 - Champion Alumni

That's interesting, Alex. Are you saying then that have been successful in using tokens in a trigger/filter within the smart list of a smart campaign?  My understanding was that they weren't supported at all in smart lists.

As I mentioned in another post, it would be helpful to have a comprehensive guide from Marleto that specific states where tokens can be used in smart campaigns. For example, there are some fields - like Acquisition Program Name - that won't accept a token, even in a flow step.

Level 10 - Community Moderator

The workaround I use is to append the token name as the hash of the URL. That is,

     http://{{my.videoURL}}#videoURL

     http://{{my.pdfURL}}#pdfURL

So the URL will always contain the literal string "#videoURL," "#pdfURL," etc.

Munchkin helpfully includes the hash in the Visit Web Page (it's debatable whether this should be the default behavior, but it helps us here!)

Level 6 - Champion Alumni

Somewhat - in that I did not use the token in the smart list. My token held only the second part of the URL and I triggered on clicks link in email, link contains "www.pages.company.com/". Of course that only works if you have only one link with that structure.

Level 10 - Champion Alumni

Ok, thanks for clarifying. So it sounds like there still is no way to use tokens in the smart list of a smart campaign. There are a bunch of related ideas to this already. I think we need a simple "allow tokens in smart lists of smart campaigns" idea. I'll create it next time I'm at my computer.

Level 10 - Champion Alumni

Here's a basic idea for allowing tokens within smart lists of smart campaigns: