Skip to content

Commit ee87f67

Browse files
finish destination documentation
1 parent b5fec80 commit ee87f67

File tree

1 file changed

+29
-39
lines changed
  • src/connections/destinations/catalog/actions-listrak

1 file changed

+29
-39
lines changed

src/connections/destinations/catalog/actions-listrak/index.md

Lines changed: 29 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -15,49 +15,39 @@ This destination is maintained by Listrak. For any issues with the destination,
1515
## Getting started
1616

1717
1. Before connecting to the Listrak Destination, set up the [Listrak Source](/docs/connections/sources/catalog/cloud-apps/listrak/). Note the API client ID and client secret after creating the integration in Listrak.
18-
1. From your Segment workspace, go to **Connections > Catalog** and click **Destinations**.
19-
1. Search for **Listrak** in the Destinations Catalog and select the destination.
20-
1. Click **Add destination**.
21-
1. Select an existing Source to connect to Listrak.
22-
1. On the **Setup** tab, name your destination. For example, `Listrak`.
23-
1. Enter your Listrak API client ID and client secret.
24-
1. Click **Save Changes**.
25-
1. Follow the steps in the Destinations Actions documentation on [Customize mappings](/docs/connections/destinations/actions/#customize-mappings).
26-
1. Enable the destination and configured mappings.
18+
2. From your Segment workspace, go to **Connections > Catalog** and click **Destinations**.
19+
3. Search for **Listrak** in the Destinations Catalog and select the destination.
20+
4. Click **Add destination**.
21+
5. Select an existing Source to connect to Listrak.
22+
6. On the **Setup** tab, name your destination. For example, `Listrak`.
23+
7. Enter your Listrak API client ID and client secret.
24+
8. Click **Save Changes**.
25+
9. Follow the steps in the Destinations Actions documentation on [Customize mappings](/docs/connections/destinations/actions/#customize-mappings) or follow the steps below to Sync an Engage Audience.
26+
10. Enable the destination and configured mappings.
2727

2828
### Sync an Engage Audience
2929

3030
1. Each Engage audience to be synced to Listrak must only include email addresses subscribed to the list. To do this, add a condition to the Engage audience that ensures the custom trait for the list exists (eg. have a Custom Trait listrak_list_12345 exists, where 12345 is the list ID).
31-
1. In Listrak, go to **Contacts > Profile Fields** and click **Create Field Group**.
32-
1. Enter `Engage Audiences` for the name and Click **Save**.
33-
1. Enter a name for the audience for the **Field Name**.
34-
1. Select **Check Box** for the **Data Type**.
35-
1. Click the **Update** button.
36-
1. Go to **Help & Support > API ID Information** and note the list ID and field ID.
37-
1. In Segment, open the previously created Listrak destination.
38-
39-
1. In the **Mappings** tab, click **New Mapping** and select **Update Email Contact Profile Fields**.
40-
41-
1. Under **Select events to map and send**, select **Track** for the **Event Type**.
42-
43-
1. Click **Add Condition** and create a condition **Event Name** is **Audience Entered**.
44-
45-
1. Under **Select mappings**, enter the list ID, map the email address,
46-
47-
1. Repeat steps 2 through 4 for **Event Name** is **Audience Exited**.
48-
49-
8. **Enable** both mappings.
50-
51-
9. Go to the **Settings** tab and **Enable** the destination.
52-
53-
10. Select your space, and navigate to **Engage > Audiences**. Select the source audience that you want to send to your Criteo Audiences destination.
54-
55-
11. Click **Add Destinations** and select the Criteo Audience destination you created. In the settings that appear on the right-hand side, toggle the **Send Track** option on and disable **Send Identify**. Click **Save**.
56-
57-
Your Criteo destination is now ready to receive audiences, and your Persona audiences now reflect in your Criteo Advertiser dashboard. Be aware, it takes 12-24 hours for the number of identifiers to populate in Criteo's Management Center.
58-
59-
> warning ""
60-
> You can connect **ONE** Engage audience to a single instance of Criteo Audience destination. If you have multiple audiences, repeat the above process to create a new Criteo audience destination and connect the audience to new destination each time.
31+
2. In Listrak, go to **Contacts > Profile Fields** and click **Create Field Group**.
32+
3. Enter `Engage Audiences` for the name and Click **Save**.
33+
4. Enter a name for the audience for the **Field Name**.
34+
5. Select **Check Box** for the **Data Type**.
35+
6. Click the **Update** button.
36+
7. Go to **Help & Support > API ID Information** and note the list ID and profile field ID.
37+
8. In Segment, open the previously created Listrak destination.
38+
9. In the **Mappings** tab, click **New Mapping** and select **Update Email Contact Profile Fields**.
39+
10. Under **Select events to map and send**, select **Track** for the **Event Type**.
40+
11. Click **Add Condition** and create a condition **Event Name** is `Audience Entered`.
41+
12. Under **Select mappings**, enter the list ID, map the email address, enter the profile field ID for the key and `on` for the value
42+
13. Repeat steps 9 through 12 using `Audience Exited` for the **Event Name** and `off` for the profile field value
43+
14. **Enable** both mappings.
44+
15. Go to the **Settings** tab and **Enable** the destination.
45+
16. Select the Engage space and navigate to **Engage > Audiences**. Select the source audience to send to the Listrak destination.
46+
17. Click **Add Destination** and select the Listrak Audience destination.
47+
18. In the settings that appear on the right-hand side, toggle the **Send Track** option on and disable **Send Identify**.
48+
19. Click **Save**.
49+
20. To filter email sends in Listrak using the new audience profile field, see this [help article](https://help.listrak.com/en/articles/3951597-introduction-to-building-filter-2-0-segments)
50+
21. If you want to sync another audience, repeat steps 1 through 20.
6151

6252
{% include components/actions-fields.html %}
6353

0 commit comments

Comments
 (0)