The purpose of this idea is to gather all requirements for the next level of program token management. Here they are :
New types of tokens required :
Furthermore, we should be able to access campaign/program member values as tokens, including SFDC custom fields on the campaign member object (see )
We should also be able to access all SFDC campaign fields as tokens in Marketo programs. See , , , and this one and this one: .
Of course, all these would be used in flow steps (such as change data values, interesting moments, SFDC task creation, etc...) and in assets
Token management also needs some significant improvement :
Finally, token usage should also be strengthened :
All these improvements, combined, would lead Program + tokens technology to a unmatched productivity tools for marketers in small to very large teams.
@robert: If I understood you correctly, I think you just want to look at the Used By tab of the form?
Yes, you're right. I didn't realize that trigger/filter usage was also
reflected there. Thanks for setting me straight.
On Fri, Apr 15, 2016 at 3:27 PM, Grant Booth <email@example.com>
Hi Grégoire Michel
My name is Joe Richardson and I have been tasked to rethink the Tokens experience. This is an amazing breakdown of asks and issues that you have compiled. Great job on that. Is it possible we can take this offline on a phone conversation? Contact me at if you are interested.
Also, from a global viewpoint, I would be interested about the top ten pain points in order of importance and why they hurt so bad (From this list). No worries if you are limited on time.
Great work here!
HI Joe Richardson,
It's not that easy to list the top pain points, excepted for a couple of limitations and bugs (mainly the issues related to token deletion and "used by" inaccurate information.
My take when writing this list is that tokens were initially designed as a set of potential loosely structured variables. But it proved over time to be an extremely powerful mechanism, with more potential that the initial design probably envisioned. It has become a most valuable feature of Marketo, one that makes a real difference with the other products on the market.
But to make this complete, as users and consultants, we really need the tokens to be moved to the next level, with asset token types (to references, images, files or forms), other token types (such as colors or URLs), security (so that some tasks such as defining or deleting tokens are left to experiences users), user friendliness and control (such as picklists)
Hey Grégoire Michel,
What do you think about the following?
- Writing to a token in a flow step
- Cross program tokens (which could actually be accomplished by writing to a global token)
Either of these would drastically improve the ability to centralize, automate and scale marketing programs
Would it be possible to have a " Token Display | Rendered-Token Display" boolean somewhere in the interface (much like the Desktop/Mobile view in the EMail 2.0 Editor) which would display tokenized values from within the editor experience without having to kick it into some kind of preview mode. I find myself wishing that I could
1) See tokenized values instead of the token in the asset preview
2) Edit those values from within the asset editor without having to leave the editor experience (maybe a "Token" pane in the Elements/ Variables Modules panel - with Local & Global tokens just like the Variables). It'd be nice to also be able to send those changes back 'upstream' rather than having to "walk-it back" to the top of the waterfall.
Nice one. Could you enter it as a separate idea so that I can reference it and we can vote?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.