Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents:

Table of Contents
minLevel2

The Transactional Injection Feed

While the feeds in the previous section: Ongage Feeds: HTML, RSS, XML and JSON use a URL to retrieve dynamic content from an external content/web server to populate outgoing email messagemessages, with this feature you can specify the dynamic feed directly within the Transactional API call. 

Use Cases

A powerful feature for eCommerce and travel

This is a powerful feature for eCommerce and travel sites. With it one can send transactional emails of purchase summaries (e.g., purchase line items) or reservations details (e.g., hotel, room, itinerary line items, etc.).

The feature enables marketers to use the same email message, yet each recipient will get a tailor message of their reservation details, or purchase summaries, based on the dynamic content values in the feed. These API calls with their tailor feeds are generated from data in a back-end CRM/Accounting/Reservation platform. 

Setup Required to send Transactional emails using an API Injection Feed

Email Message

Your email message needs to include List Dynamic as well Feed Dynamic field which you are going to populate through the Transactional API Request.

...

For the above setup, the transactional Email received in Inbox will look similar to screenshot shared below.

Use Cases

A powerful feature for eCommerce and Travel

This is a very powerful feature for eCommerce and travel sites. With it you can send transactional emails of purchase summaries or reservations. A summary of your purchase items, hotel reservations etc. With the feed for example, you could have a single email that has all the reservation information using dynamic fields as place holders. And then use the same email message to send a Transactional API request to each user with their reservation details populated through an XML feed. 

Additional Notes

  1. The List Field value added in API request above under "message_dynamic_fields" will overwrite the value stored in List field of any contact while sending the Transactional Emails only. The original value stored in list field will still remain as it is after the API request.
  2. You can also use IF-THEN-ELSE conditions in the email message and send dynamic content to end users based on the List field value either populated in API request or already stored in List.

...