Using Linked Audiences with Iterable

The following engagement tools are available for use with Linked Audiences in Segment:

Segment sends data from your Linked Audiences to actions-based destinations. For example, you could send account information for the audience profiles with past due accounts to an email platform.

You can configure multiple triggers per audience (for example, one for account entry, and one for account exit).

Iterable Journey Campaigns store the entity personalization payload as event properties in custom events.

Note: Using custom events can impact your Iterable billing.

In Segment, make sure you have:

• Set up your Linked Audience.
• A copy of your Linked Audience event name and Iterable user id.
• Set up Iterable as an actions destination.
• Set up a Custom Event destination action and the relevant trigger using the Linked Audiences workflow.

In Iterable, make sure you have:

• Permissions to access the application, or access to someone who has permissions.
• Created all Segment profiles as Iterables profiles using the Upsert User destination action through Connections or Reverse ETL. This is a requirement for them to receive a campaign triggered by a custom event.
• Review the custom event payload schema from your Segment Linked Audiences test event so you know what properties to include in your message personalization. You can do this by accessing the user's profile and clicking into their event history to see the specific properties.
• Created an Iterable profile, for campaign testing, with an email address you can access.
• Familiarity with the Handlebars templating syntax to manually type out the code using dot notation.

To use Linked Audiences you must set up a Journey campaign in Iterable.

In Iterable, do the following:

1. Create a Journey and in the Start tile select the Entry source as Event Occurs, then choose Entry type = Custom event. Search and choose the name of the Segment custom event you previously set up and tested in Segment.
2. Add an Email Message tile, create your campaign, and connect it to your Start Tile.
3. Edit the content in your email:
   1. Under Design, choose either the WYSIWYG Editor or the Side by Side Editor.
   2. Reference your Segment custom event payload schema in Iterable to determine what properties to include in your message. You can do this by accessing the user's profile and clicking into their event history (Events > History > Details).
   3. Translate the event properties in the payload schema into Handlebars syntax for custom events, and enter it in the HTML editor in Iterable. See the personalization examples below for more specific details.
4. Choose any additional settings that apply and review and publish your journey. Then continue on to Test your campaign flow in Segment.

1. Open the Segment app and send yourself a test email for review. Add your Iterable user id and click Send test event to destination. Review the email you received, and make sure it is formatted properly.

Expand image

If the event is sent successfully to Iterable, you will see a "message": "success" response in Segment.

2. Open Iterable and check the Campaign tab in Messaging Insights (Insights > Messaging Insights > Campaigns > [Your Unique Campaign]) to confirm that Iterable has sent the message.
3. If your email doesn't look the way you want it to, adjust the Handlebars syntax in Iterable, and send another test event. See the following personalization examples for more specific details.
4. When you're finished testing your campaign, proceed to Enable your Linked Audience.

Use the following examples as context and information to experiment with setting up your campaign in Iterable.

The following is an example of what your payload data might look like with nested payload properties:

1
{
2
   "event": "abandoned_carts_linked_audience",
3
   "properties": {
4
      "first_name": "Andrew",
5
      "last_name": "Shopper",
6
      "shopping_cart__id": "123",
7
      "shopping_cart__products": [
8
         {
9
            "id": "324",
10
            "product_name": "Premium Tennis Shoes",
11
            "product_price": "$140",
12
            "__entity": "product"
13
         },
14
         {
15
             "id": "489",
16
             "product_name": "Premium Jacket",
17
             "product_price": "$200",
18
            "__entity": "product"
19
          }
20
       ],
21
       "__entity": "cart"
22
     }
23
 }

The following helps translate your payload data into Handlebars syntax:

• To reference a specific event property:
  • Use the following Handelbars syntax: {{event_property_name}}
  • An example of this property might look like: {{first_name}}
• To reference nested event properties within an Array:
  • Use the following Handlebars syntax: {{event_property_name.[#_that_represents_specific_entry_in_array].nested_event_property_name}}
  • An example of this property might look like: {{shopping_cart__products[0].product_name}}

You can read more on how to reference event properties and nested properties in Handlebars.

Use the Segment custom event payload schema to build an abandoned cart email campaign that includes specific information for the product in a customer's shopping cart.

When an email is sent, it lists the specific product and its related price in your customer's shopping cart. It might look like the following screenshot:

Expand image

This is an example of what your email using HTML and Handlebars syntax might look like in Iterable:

1
Hi {{first_name}},
2
<br />
3
<br />
4
Did you forget to checkout?<br />
5
<br />
6
We noticed you added some items to your shopping cart including this item: <br />
7
<br />
8
<b>Product Name: </b>
9
{{shopping_cart__products.[0].product_name}}
10
<br />
11
<b>Product Price: </b>
12
{{shopping_cart__products.[0].product_price}} USD
13
<br />
14
<br />
15

16
Quick, now is your chance to own this item before it sells out!
17

Use the Segment custom event payload schema to build an abandoned cart email campaign where you can use the #each block helper to run a block of code repeatedly. In this example, you can list all of the products and their related prices in a customer's shopping cart.

When an email is sent, it lists all of the products and their related prices in your customer's shopping cart. It might look like the following screenshot:

Expand image

This is an example of what your email using HTML and Handlebars syntax might look like in Iterable:

1
Hi {{first_name}},
2
<br />
3
<br />
4
Did you forget to checkout?<br />
5
<br />
6
We noticed you added some items to your shopping cart. Here's what you left: <br />
7
<br />
8

9
{{#each shopping_cart__products}}
10
<b>Product Name: </b>
11
{{product_name}}
12
<br />
13
<b>Product Price: </b>
14
{{product_price}} USD
15
<br />
16
<br />
17

18
{{/each}}
19

20
Quick, now is your chance to own these items before they sell out!