Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
One option I considered was manually overriding the token at the campaign levelNot sure I understand how you’d have different values without overriding for each campaign? However, you should use a Velocity {{my.token}} for it to make things easier, not a Text {{my.token}}.
Indeed, I call it the Fieldset-at-a-Time (FsaaT) method and there’s a blog post and some demos out there. The JS can be even tighter now than a few years ago due to browser built-ins, it’s really quite easy. If you don’t care about giving somebody a Back button, just use multiple forms. The user doe...
I would have those tokens be Velocity {{my.tokens}}. Then each can access any $variables set in earlier tokens.
Well, using Velocity output as part of links isn’t generally supported. Instead, output the whole link including the and from Velocity,
Is it a Velocity {{my.token}}? I don't understand any other way that what you're saying could be true -- that the {{my.token}} reflects lead-level values.
There's no reason a {{my.token}} won't be sent with a webhook, as long as the Call Webhook step is inside/inherits from the place the {{my.token}} is defined. is it really a {{my.token}} though? A person-specific history field would be a {{lead.token}} (which also will be sent in a webhook).
Sure, that would be interesting, although the thing is it totally changes the idea of where Dynamic Content can go.
Something like a country-specific footer can be easily done in Velocity (which can be on the template).
Couldn’t you use the id of the to simulate this?