Using 40+ Custom Tokens in Velocity Script: Risks and Considerations

[GowthamNataraj1]

I understand that there's a limit of 40 custom field tokens that can be used directly in a Marketo email. If this limit is exceeded, Marketo throws an error indicating that the token limit has been crossed.

I'm curious whether using more than 40 custom tokens in a Velocity Script could cause any issues, such as dynamic content not displaying correctly or email delivery failures.

In my specific use case, I'm currently using 42 custom consent field tokens within if-elseif statements to conditionally show or hide the unsubscribe link in the email footer.

Has anyone had experience working with Velocity Scripts in Marketo and encountered issues when using more than 40 custom tokens? I'd appreciate any insights or best practices.

[SanfordWhiteman · Accepted solution]

The limit doesn't apply to $variables (which are not tokens) in Velocity.