Using events in event triggered campaigns

There are a few important things to know about the events which trigger your campaigns to make sure those campaigns work as you expect.

1. Event attributes can be used in action content

You can use all of the data you send with an event in action content. For example, if you send us a purchase event with the following data:

{"name":"purchase","data":{"price": "9.99", "product": "socks", "color":"blue"}}

You can send a receipt email (or push notification, or SMS, or any other action) with the product’s name, price, and color in it. Whatever you send in the event attributes is available to you; you can learn more about using event data here.

2. Event attributes can be used to refine campaign recipients

When setting up your event triggered campaign, you can use also event attributes to allow only a subset of the users who have performed that event to match. For example, if you’re sending the purchase event with the following data:

{"name":"purchase","data":{"price": "9.99", "product": "socks", "color":"blue"}}

…and you want to send an event triggered campaign only to those who bought socks, you can add an event data filter to your campaign trigger:

You can also do this when you create segments based on events:

3. Event attributes can override certain email headers

If you send any of these attributes as part of your event, they will override your campaign settings:

  1. from_address
  2. recipient
  3. reply_to

For example: If a purchase event triggers an email to send, but that purchase event contains recipient = wile.e.coyote@example.com as an attribute then all emails triggered by that campaign will go to wile.e.coyote@example.com, no matter the settings in the campaign itself.

4. Event attributes can include attachments

If your event includes an attachment, it will be attached to any emails which go out as part of that event. Here’s an example using an .ics file.