Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
@Chandana_kavuri please return to your thread and check responses.
@tomh2 please return to your thread and check responses.
There’s no better place than here. (And most of that is cross-posted to the official Products blog.) I’m really the only one in the world learning/writing at length about Velocity-in-Marketo specifically. The link you posted to Velocity 1.7 uses the same syntax as Marketo (and that’s the right versi...
You didn’t supply your full token code so I can’t show you where you introduced a syntax error. Under “Person”, fields like Sales Owner Email Address should be easily accessible.
Sent Email activities are only stored for 90 days. So it's not possible to create such a report.
No need for any kind of "nesting". Those Person fields are all available in Velocity already. Just choose them from the tree.Also, you shouldn't be using ${var} (formal references) here, just $var (simple refs). And don't use ==, use .equals().
Say you have an LP section like this:
tl;dr: if a URL’s query params all start with utm_, you do not need to separate them with &. Use the simple &. Using & when it’s not required is harmless. But it’s not really best practice, since it makes links harder to build by hand and harder to read. On the other hand, if you use params other th...
You must link to your page where this is happening. Can't repro in my labs. (We’ve got 2025-01-20 and 2025-03-26 versions only, perhaps something was patched today like what you’re mentioning.)