You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Aggregations.io](https://aggregations.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} enables you to use your existing analytics events and pipeline for real-time monitoring and alerting.
10
+
11
+
This destination is maintained by Aggregations.io. For any issues with the destination, [contact their Support team](mailto:[email protected]).
12
+
13
+
## Getting started
14
+
15
+
1. From the Segment web app, click **Catalog**, then click **Destinations**.
16
+
2. Find the Destinations Actions item in the left navigation, and click it.
17
+
3. Click **Configure Aggregations.io (Actions)**.
18
+
4. Select an existing Source to connect to Aggregations.io (Actions).
19
+
5. In the destination settings, enter your Aggregations.io API Key and Ingest ID. Your ingestion on the Aggregations.io dashboard should be set up using `Array of JSON Objects` and the API Key requires `Write` permission. For more information, see the [Aggregation.io docs](https://aggregations.io/docs/ingesting-data/create-an-ingest){:target="_blank"}.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-listrak/index.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,18 +42,19 @@ To sync an Engage audience with your Listrak (Actions) destination:
42
42
9. In the **Mappings** tab, click **New Mapping** and select **Update Email Contact Profile Fields**.
43
43
10. Under **Select events to map and send**, select **Track** for the **Event Type**.
44
44
11. Click **Add Condition** and add this condition: **Event Name** is `Audience Entered`.
45
-
12. Under **Select mappings**, enter the list ID and map the email address if `context.traits.email` is not desired.
46
-
13. Still under **Select mappings**, in the section for mapping the `Profile Field Values`, enter the profile field ID for the `Enter Key Name` textbox on the right and `on` in the textbox for its value to the left. Click **Save**.
47
-
14. Repeat steps 9 through 13 using `Audience Exited` instead of `Audience Entered` in step 11 and `off` instead of `on` in step 13.
48
-
15.**Enable** both mappings.
49
-
16. Go to the **Settings** tab for the destination and **Enable** the destination. Click **Save Changes**.
50
-
17. Select the Engage space and navigate to **Engage > Audiences**. Select the source audience to send to the Listrak destination.
51
-
18. Click **Add Destination** and select the Listrak Audience destination.
52
-
19. In the settings that appear on the right-hand side, toggle the **Send Track** option on and disable **Send Identify**.
53
-
20. Click **Save**.
54
-
21. 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){:target="_blank”}.
55
-
22. If you want to sync another audience, repeat steps 1 through 20.
45
+
12. Click **Add Condition** and add this condition: **Event Property**`audience_key` is `my_audience` (where `my_audience` is the Audience Key found on the Audience settings page).
46
+
13. Under **Select mappings**, enter the list ID and map the email address if `context.traits.email` is not desired.
47
+
14. Under **Select mappings**, in the section for mapping the `Profile Field Values`, enter the profile field ID for the `Enter Key Name` textbox on the right and `on` in the textbox for its value to the left. Click **Save**.
48
+
15. Repeat steps 9 through 14 using `Audience Exited` instead of `Audience Entered` in step 11 and `off` instead of `on` in step 14.
49
+
16.**Enable** both mappings.
50
+
17. Go to the **Settings** tab for the destination and **Enable** the destination. Click **Save Changes**.
51
+
18. Select the Engage space and navigate to **Engage > Audiences**. Select the source audience to send to the Listrak destination.
52
+
19. Click **Add Destination** and select the Listrak Audience destination.
53
+
20. In the settings that appear on the right-hand side, toggle the **Send Track** option on and disable **Send Identify**.
54
+
21. Click **Save**.
55
+
22. To filter email sends in Listrak using the new audience profile field, see the [help article](https://help.listrak.com/en/articles/3951597-introduction-to-building-filter-2-0-segments){:target="_blank”}.
56
+
23. Repeat steps 1 through 21, if you want to sync another audience.
[Pendo](http://www.pendo.io/){:target="_blank"} combines powerful software usage analytics with in-app guidance and user feedback capabilities, enabling even non-technical teams to deliver better product experiences to their customers or employees.
14
+
15
+
> success ""
16
+
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Pendo Web (Actions) Segment destination. There's also a page about the [non-Actions Pendo destination](/docs/connections/destinations/catalog/pendo/). Both of these destinations receives data from Segment.
17
+
18
+
## Benefits of Pendo Web (Actions) vs Pendo Classic
19
+
20
+
Pendo Web (Actions) provides the following benefits over the classic Pendo destination:
21
+
22
+
-**Support for Track, Identify, and Group calls**. The classic Pendo destination did not support Track calls and required users to configure an additional Webhook destination.
23
+
-**Full region support**. Setup allows the destination to be configured for US, EU, US restricted, or Japan.
24
+
-**Supports CNAME for Pendo**. Works with subscriptions using Pendo's custom CNAME feature.
25
+
26
+
## Getting started
27
+
28
+
1. From the Segment web app, click **Catalog**, then click **Destinations**.
29
+
2. Find the Destinations Actions item in the left navigation, and click it.
30
+
3. Click **Pendo Web (Actions)**.
31
+
4. Click **Add destination ->**.
32
+
5. Select an existing Source to connect to Pendo Web (Actions).
33
+
6. In the destination settings, enter your Pendo API Key which you can find in the Pendo UI under [Site Settings](https://app.pendo.io/admin){:target="_blank"} > Basic Information > API Key.
34
+
7. Select the correct region for your Pendo subscription.
35
+
36
+
{% include components/actions-fields.html %}
37
+
38
+
## Migration from the classic Pendo destination
39
+
40
+
Remove the classic Pendo destination and Webhook destination from your Segment workspace before adding the Pendo Web (Actions) destination.
0 commit comments