Overview

This is a collection of uses of Context Data. This is not a step-by-step guide of setting up these configurations, but a breakdown of the different methods of approaching Context Data.

Table of Contents

Overview

Relational Data

Store Information

Coupon Data

HTML Data

Relational Data

The most common use of Context Data is using relational data. Relational Data uses Audience Data and combines it with Context Data with some form of shared information.

Store Information

City & Glory is a clothing retail store across the United States. All customer data is accessed through the Audience Data. Below is an example of the Audience Data:

The “preferred_store” column is the related column. This value is used to join information from the Context Data. City & Glory adds Context Data populated with store information. Below is an example of the Context Data:

Notice the correlation between the “preferred_store” of the Audience Data and the “store_id” of the Context Data. In this case, the address of the preferred store needs to be displayed in the  email Template.

The Audience and Context Data exist separately and must be joined together to dynamically populate the proper store address for each customer. FreeMarker is used to join the data.

In this example, the FreeMarker that combines the data is:

<#assign myData = ContextData['Entry[store_id="${Recipient.preferred_store}"]']>

This FreeMarker code creates a variable called myData. The value of myData is an object that stores all the returned information from the Context Data record where the store_id is the same value as the preferred_store from the Audience. To reference a value from the Context Data, the following FreeMarker is used:

${myData.address}

The data is now joined and can be referenced throughout the email/text/sms Template easily.

Coupon Data

The Weekly Sprout is a healthy living grocery store. Each week, a newsletter is sent out with coupon deals personalized to the customer. Customers that have a higher lifetime value receive better coupons. The Audience Data stores personalized data:

The Context Data contains the coupon data. The Context Data stores the details of the coupon:

Notice the coupon_id column in both the Audience and the Context Data. This is the value that will be used to join the data together. Using FreeMarker, this is how the relational data is combined:

<#assign myData = ContextData['Entry[coupon_id="${Recipient.coupon_id}"]']>

Now, within the Template, the relevant coupon data is rendered to the customer. In this case, the returned information would make up a large portion of the email/text/sms contact.

This example follows the same idea as the store information example. It’s a versatile approach to dynamic content.

HTML Data

Another interesting example of using Context Data is building the entire HTML Template through returned results from Context Data. It is possible to build the full email display through returned results from Context Data.

Newfound Apparel is a rising company that offers very personalized newsletters. Based on the Audience data, entire custom formatted HTML can be generated from the Context Data. Below is an example of the Audience Data:

The Context Data for this example only has two columns:

There is still an element of relational data within this example. Instead of using the relational data to select a coupon or store information, the actual HTML of the email is stored in the Context Data.

Using the data in this example takes more than just one line of code. Because there are two items that are needed (Recipient.template_id1 and Recipient.template_id2) from the context data, multiple FreeMarker statements are needed:

<#assign
html1 = ContextData['Entry[template_id="${Recipient.template_id1}"]']
html2 = ContextData['Entry[template_id="${Recipient.template_id2}"]']
>

Placing the HTML blocks into the Email Template uses the following variable:

${html1.code}
${html2.code}

This example can be expanded on even further with dozens of different templates. CSS styling can even be used within divs and elements to create a cohesive appearance to the HTML. This is a more advanced configuration as Web Design knowledge is needed to build the HTML code within the table. Testing is required to confirm everything is rendered correctly.