Hello All,
I need to add multiple tokens in the Change Data value flow step to accomplish one requirement: Need to stamp the last suppression reason of a lead and the updated one in a single field attribute "Suppression Reason" as highlighted below (this screenshot is for a single case only as I have added multiple other CDV's for the same):
As per the Marketo documentation, multiple tokens can be used in Interesting Moment, Create Task, and Send Alert flow steps. So just wanted to check if there is any way to do it for CDV too ?
Solved! Go to Solution.
Agreed with Katja, given that the field type can accept the size and type of data you have in the tokens and want to stamp in the field, you should be good at using multiple tokens. For e.g., String/Text area fields are open text fields, whereas an integer field is not. String fields are limited to holding 255 chars (data gets truncated in case of overflow), whereas text fields can hold up to 30k chars.
Yes, you can. You can type normal text and insert tokens in any combination (of course respecting the overall length of the field).
Thank you @Katja_Keesom and @Darshil_Shah1 for confirming. However, while trying to add {{lead.Suppression Reason}} token after the {{lead.Email Invalid Cause}} using the semicolon (;) into the New Value field, it's was not popping up in the suggestd values below which lead to doubt in my head whether Marketo would respect it if I hard code it or wouldn't work (considering the field length as you mentioned).
Auto-suggest directly references and looks for any matching data in the respective field in your DB. If you're using tokens in the CDV flow step, then there is a high chance that Marketo would not find any relevant matches in the DB. FYR - the auto-suggest doesn't replace the tokens with values while searching the database for any matches as you're typing up in the CDV step.
Agreed with Katja, given that the field type can accept the size and type of data you have in the tokens and want to stamp in the field, you should be good at using multiple tokens. For e.g., String/Text area fields are open text fields, whereas an integer field is not. String fields are limited to holding 255 chars (data gets truncated in case of overflow), whereas text fields can hold up to 30k chars.