Send Email with dynamic content using API | Community
Skip to main content
Level 3
February 11, 2020
Question

Send Email with dynamic content using API

  • February 11, 2020
  • 1 reply
  • 3734 views

Hi,

We have a gaming app and API connects the app with Marketo. We need to set up trigger based email campaigns for different criteria using smart list as Requested Campaign Source = Web Service API and Flow as Send Email.

 

I have created dynamic email fields using lead tokens in the emails(and have added them to field management under admin). For example: s_clan_leaderboardinfo, s_clan_clanname. s_clan_season# etc.

 

I will be sharing the dynamic tokens with backend team and they said they will be running triggers based on my smart campaigns.

Please let me know if you have any idea/suggestions to follow here? Or if I can add anything else to improve my program.

 

Thanks.

 

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
Level 10
February 11, 2020

{{lead.tokens}} aren't dynamic content. They're static values - mutable values to be sure, but they are permanent changes and only output one value for a lead at a given point in time.

 

"Dynamic" in Marketo-speak means that either the lead's segment (within a certain segmentation) switches content blocks automatically, or Velocity code is used to generate content based on any number of point-in-time characteristics, or that you're passing {{my.tokens}} as ephemeral content within a single API call. It doesn't sound like you're doing any of these, you're just setting a lead field.

 

I'm not sure what you're asking exactly. Is setting lead fields the best way to send ephemeral data? Not really, but it's not a tragically bad idea. Depends on your volume and how you're throttling requests to your app (which consume API calls in turn).

Lopa1408Author
Level 3
February 11, 2020

Let me give you one example of an email with dynamic field that I am working on. It looks like this:

 

 
 

we have to set up the email for different seasons(dynamic field) of Clan and different missions(dynamic field) of the game. Shall I use {{my.tokens}} here instead of the lead tokens?

 

SanfordWhiteman
Level 10
February 11, 2020

Right now you're using static tokens. It isn't "dynamic" now, it's merely personalized. Let's not change established definitions as it makes it  harder to communicate.

 

I would advise using text {{my.tokens}} in this case and passing the values in the Request call.