Here's the token:Here's how the token is used in the email alert:And here's how it renders in an email (instead of pulling the history value from the lead record, it's including th...
We, too, have been experiencing some issues with how flow steps are supposed to function. For example, when we call (request) a smart campaign in the middle of the flow, we're find...
That doesn't seem to work. Here's the exact velocity token - called {{my.IM History}} that I'm using:${display.br(${lead.avanadeInterestingMomentHistory})}For your reference, the h...
Sanford Whiteman, your solution works great when the values need to be stored like this in a history field. The issue arises when we use that history field as a token in an email. ...
After doing some testing, the way around this is to place "NULL" in the "Default Value" field. This will then change the prior value (for the LT and MT/history fields) to NULL, ove...
I'm sure this is related to the DNS mess from yesterday. Considering the docs site is hosted on a Marketo.com sub-domain, I suspect it still needs time to resolve/propagate across ...
Adam raises a potential issue here. Not sure if this is what's causing his issue, but here goes:Lead converts on Marketo form using source URL:page.com?utm_campaign=cloud&utm_sourc...
Our security team created a new DKIM record for us to use with Marketo. But it was setup completely outside of Marketo (not using DKIM in the admin section - meaning I didn't provi...
I have this working using the following script:#set( $email = ${lead.Avanade_BD_Owner_EmailAddress} )#set( $domain = "@marketing.avanade.com" )#set( $final = $email.replace("@avana...