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.
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
.png)