Nesting Tokens

Question

I have a paragraph inside an email that needs to be altered depending on certain lead attributes. I created the following token that successfully changes which paragraph is displayed, however it doesn't fully work.#if( ${lead.Layer__c}== "Base")

Reach out to your recruiter {{lead.Lead Owner First Name:default=}} @ {{lead.Lead Owner Email Address:default=}}

#else

Nothing catching your eye? Click Here

#end The problem is that the paragraph prints into the email like this:"Reach out to your recruiter {{lead.Lead Owner First Name:default=}} @ {{lead.Lead Owner Email Address:default=}}" How would I go about making those two bolded tokens actually print their respective values? I thought I could use the #set command at the start of the script token, but that doesn't work.#set( $firstName== ${lead.Lead Owner First Name}) #set( $email== ${lead.Lead Owner Email Address}) #if( ${lead.Layer__c}== "Base")

Reach out to your recruiter $firstName @ $email

#else

Nothing catching your eye? Click Here

#end Trying to preview my email with this token inside of it just breaks the preview window. Velocity Script is fairly new to me, so it's entirely possible I just didn't use the right syntax. Is it possible to do what I'm trying to do here?

SanfordWhiteman · Accepted Answer

Aaah, thanks for clarifying. That part of my code works now. I really wish there was more documentation about Velocity scripting inside of Marketo. I tried emailing Marketo Support for help and they basically told me they couldn't troubleshoot Velocity script tokens because it's just something they provide access to and not something they are trained on.

Can you point me towards any good sources of how to use Velocity, specifically as it works in Marketo? I tried looking at this guide from the creators, but it doesn't seem to use the same syntax. It doesn't even mention the ".equals()" notation that you suggested.

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 version), not sure exactly what you mean there?

There reason you shouldn’t use == is it coerces the types of its operands to strings if the types don’t otherwise match. This can lead to wildly strange outcomes (in both directions, false negative and false positive). In contrast .equals() is strongly typed and doesn’t do anything magical.

SanfordWhiteman · Answer

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

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded