Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
It's my experience that if you assign the Program ID to a Velocity variable in the email itself, it's not available in the context of Email Script Tokens and vice versa. However, as long as you don't need Custom Object or Opportunity Data, you can just write your entire Email Script in the Email Tem...
Thanks Jay, this worked for me. I also had to prefill a multi-select field with multiple checkboxes and found out that this can be handled as a regular field, since the data is stored as a semicolon separated string in a TextArea field.
Small correction: "30 form posts per minute per IP", not per second
How about setting disableClickDelay to True? Since it doesn't wait 350ms to track clicks, that should certainly help a bit.This is where this setting is documented: https://developers.marketo.com/javascript-api/lead-tracking/configuration/
Yun Bai no issues, other than that records without Company or Last Name will not sync and you'll need to create a Smart Campaign as Gregoire suggested to 're-sync' those records once the missing data is filled in. To make it more sophisticated, you could even exclude records with blank Company/Last...
As an alternative, consider adding a "clean Account name" custom field in SFDC, which is populated with a Workflow or Custom Trigger, then syncs to Marketo. Velocity scripting will cause your email to take at least 3 times longer to go out. Not a problem with 10k records, but starts being noticeable...
Aaron Startkston the lookupField should default to 'email' if not set. That should not be different across Marketo instances.
You cannot see them without linking to a Lead record.
This error wouldn't be related to the fields. Likely, there is an issue with the payload. Have you specified the lookupField? Is your action 'updateOnly'? In the payload, are there any leading or trailing spaces? Any special characters that could cause encoding issues (like '+')? I would also double...
Diego Lineros you can create a Token for each Language, then using dynamic content in the footer area to pull in the right Token.