LiveIntent Audiences Destination

LiveIntent Audiences supports audiences generated by Engage as a user property.

If you don’t have Engage but still want to send data to LiveIntent, you can use the Page, Screen, Track, Identify, and Group calls. For more information about sending your data to LiveIntent through direct calls (to Page, Screen, Track, Identify, and Group), please reach out to your LiveIntent customer success representative.

LiveIntent maintains this destination. For more information about this destination, contact the LiveIntent Support team.

Getting Started

Before getting started, you need to request an API Key and AppId by sending an email to LiveIntent support at support@liveintent.com.

Once you have your API Key and APP ID:

1. Navigate to the Destinations catalog page in the Segment App and click Add Destination.
2. Search for LiveIntent in the Destinations Catalog, and select the LiveIntent Audiences destination.
3. Choose which Source should send data to the LiveIntent Audiences destination.
4. Enter the API Key and AppId that you received from LiveIntent in the LiveIntent Audiences destination settings page in Segment.

When you set up this destination for an Engage audience, provide the snake_cased version of the audience name in the Audience settings. You can send audiences generated using Engage to this destination as a user property. If no corresponding audience exists in LiveIntent’s platform, one will automatically create.

Settings

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.