Upto 600 characters in a token - formatting issues - URGENT!!! | Community
Skip to main content
H
Hoppers13
New Participant
April 22, 2024
Question

Upto 600 characters in a token - formatting issues - URGENT!!!

  • April 22, 2024
  • 1 reply
  • 1993 views

hi all, we used an agency to develop an api sync and are now left in a situation where we're testing and some formatting components are going amiss.

we've a 'complaintscomments' token pulling in upto 600 characters in as token data, and its pulling in wildly on some clients' as you can imagine in testing. namely outlook. these emails are required to go live this week.

please does anyone know what might help with little/no IT dev work required please?

 

kr Mike

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

SanfordWhiteman
SanfordWhiteman
New Participant
April 22, 2024

Impossible to answer without more background. Are you talking about a Rich Text {{my.token}}? A Text {{my.token}}? A Person field or PMCF that you’re outputting using {{lead.token}} or {{member.token}}? Is the output actually different when you use the REST API-managed token vs. that exact same value entered in the Marketo UI?

 

There’s no inherent problem with 600 characters in a {{my.token}}. A String field on a Person or Program Member field is another story, since they’re limited to 255.

H
Hoppers13Author
New Participant
April 22, 2024

okay so the token causing issues is: {{my.TEComplaintDetails}}.

if people complain with minimal info there's no issues, but 600 characters, could be inputted and our paragraph text expands the width of the email container, the whole email view is zoomed in and its a mess!

SanfordWhiteman
SanfordWhiteman
New Participant
April 22, 2024

So this sounds like it has nothing to do with the token being updated via API vs. UI, nor with the value being truncated. It’s an email design issue.

 

Again though, there’s no way anyone could help here without seeing the source HTML of your template and screenshots at bare minimum. If you post code, remember to use the Syntax Highlighter so it’s readable:

 

 

    Terms & ConditionsAccessibility statement

    Loading footer...