Hi All,
I am in the process of setting up some API triggered sends in Marketing Cloud, and I would like to understand if we can use the same triggered send job, combined with dynamic content, to send out several different variations of the email. The emails will inform our users if they have moved up/down a level as part of our customer loyalty scheme. Data will be pushed from our partners into SFMC via API. As part of the advice I have already received from Salesforce, I will be undertaking the following (the API has already been installed on our SFMC environment):
1: Creating a list to hold the data - which will include all basics (subscriber key, email address), plus which level of loyalty scheme they previously and now currently are on
2: Creating a triggered send data extension - as above, however using the Triggered Send template, plus additional loyalty scheme variables listed above
3: Create and test the triggered send job - connecting the triggered send job to the data extension and email contenrt.
Is this simply a case of ensuring the dynamic content blocks within the email content point to the triggered send data extension?
Thanks
Sean
3 answers
Yep, you got it. That's about it. It sounds like you have a good grasp of the overall concept.
One thing to consider (likely not for right now but for down the road): triggered sends can be a little finicky if you're going to be updating them, because there's a specific order you have to disable a send, update content, and reenable. An alternate option would be to use Journey Builder for your triggered send. In that case, you would create a journey with an API entry event. You would make an API call to Marketing Cloud with the appropriate data, and the first step in the Journey would be an email. Emails in Journeys are technically triggered sends, so you'd really be accomplishing the same thing. I find a lot of clients find it easier to maintain their sends through a Journey versus a triggered send, however, and it would allow you to use additional Journey steps in the future to further edit data within Marketing Cloud or send follow up messages after the triggered send.
