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
[StackAdapt](https://www.stackadapt.com/){:target="_blank"} is a programmatic advertising platform specializing in audience engagement. StackAdapt enables marketers to deliver high-performing advertising campaigns across channels through real-time bidding, detailed audience targeting, and data-driven insights. StackAdapt’s integration with Twilio Engage helps you sync user data to optimize targeting and improve your campaign outcomes.
14
+
15
+
This destination is maintained by StackAdapt. For any issues with the destination, please [submit a ticket to StackFAdapt's support team](https://support.stackadapt.com/hc/en-us/requests/new?ticket_form_id=360006572593){:target="_blank"}.
16
+
17
+
## Getting started
18
+
19
+
### Getting your StackAdapt GraphQL Token
20
+
21
+
If you do not have an existing StackAdapt API key, [reach out to the StackAdapt team for help](https://support.stackadapt.com/hc/en-us/requests/new?ticket_form_id=360006572593){:target="_blank"}.
22
+
23
+
### Setting up the StackAdapt Audience destination in Segment Engage
24
+
25
+
1. From the Segment web app, navigate to **Connections > Catalog > Destinations**.
26
+
2. Search for and select the "StackAdapt Audience" destination.
27
+
3. Click **Add Destination**.
28
+
4. Select an existing source that is Engage Space to connect to the StackAdapt Audience destination.
29
+
5. Enter a name for your destination.
30
+
6. On the Settings screen, provide your StackAdapt GraphQL API token.
31
+
7. Toggle on the destination using the **Enable Destination** toggle.
32
+
8. Click **Save Changes**.
33
+
9. Follow the steps in the Destinations Actions documentation to [customize mappings](/docs/connections/destinations/actions/#customize-mappings) or use the documentation to [sync an Engage Audience](#sync-an-engage-audience).
34
+
10. Enable the destination and click **Save Changes**.
35
+
36
+
### Sync an Engage Audience
37
+
38
+
To sync an Engage audience with StackAdapt:
39
+
40
+
1. Each Engage audience should only contain profiles that have a valid email address. Profiles missing an email address are not valid on StackAdapt's platform.
41
+
2. Add a condition to the Engage audience to ensure the required email trait is included.
42
+
3. Open the previously created StackAdapt Audience destination.
43
+
4. On the Mappings tab, click **New Mapping** and select **Forward Audience Event**.
44
+
5. Under Define event trigger, click **Add Condition** and add this condition: Event Type is `Track` or `Identify`.
45
+
6. Under **Map fields**, select the advertiser you want to sync the audience with. You can identify a specific advertiser by finding its ID in StackAdapt.
To verify that your audience is syncing with StackAdapt, open StackAdapt and navigate to **Audience & Attribution** > **Customer Data** > **Profiles**. On the Profiles tab, you should be able to see a list of profiles being synced to StackAdapt platform.
51
+
52
+
> info "Syncs can take up to 4 hours"
53
+
> It can take up to 4 hours from the time you initiate a sync for profiles to show up in StackAdapt.
54
+
55
+
If you want to create a StackAdapt Audience from your Twilio Engage Audience:
56
+
57
+
1. Open StackAdapt and navigate to **Audience & Attribution** > **Customer Data** > **Segments**, then click **Create Segment**.
58
+
2. Choose **Segment Engage Audience ID** or **Segment Engage Audience Name** as the rule.
59
+
3. Select the value for the corresponding filter.
60
+
4. Click **Submit** to create the segment.
61
+
62
+
### Sending an Audience to StackAdapt
63
+
64
+
1. In Segment, go to Engage > Audiences and select the audience to sync with StackAdapt.
65
+
2. Click **Add Destination** and select **StackAdapt Audience**.
66
+
3. Toggle **Send Track** and **Send Identify** on.
67
+
4. Click **Save**.
68
+
69
+
## Data and privacy
70
+
71
+
Review [StackAdapt's Data Processing Agreement](https://www.stackadapt.com/data-processing-agreement){:target="_blank"} to learn more about StackAdapt's privacy and data terms.
By setting up StackAdapt as a Segment destination, your Segment events will be forwarded to [StackAdapt](https://www.stackadapt.com/){:target="_blank"}. This allows you to generate retargeting and lookalike audiences, track conversions, and measure return on ad spend using your Segment events - bypassing the need to install the StackAdapt pixel on your website and write code to send events to StackAdapt.
12
-
13
-
This destination is maintained by StackAdapt. For any issues with the destination, please [submit a ticket to StackAdapt's support team](https://support.stackadapt.com/hc/en-us/requests/new?ticket_form_id=360006572593){:target="_blank"}.
11
+
By setting up StackAdapt as a Segment destination, your Segment events will be forwarded to [StackAdapt](https://www.stackadapt.com/){:target="\_blank"}. This allows you to generate retargeting and lookalike audiences, track conversions, and measure return on ad spend using your Segment events - bypassing the need to install the StackAdapt pixel on your website and write code to send events to StackAdapt.
14
12
13
+
This destination is maintained by StackAdapt. For any issues with the destination, please [submit a ticket to StackAdapt's support team](https://support.stackadapt.com/hc/en-us/requests/new?ticket_form_id=360006572593){:target="\_blank"}.
15
14
16
15
## Getting started
17
16
@@ -20,7 +19,7 @@ This destination is maintained by StackAdapt. For any issues with the destinatio
20
19
1. Log in to your StackAdapt account and navigate to the Pixels page.
21
20
2. Above the list of pixels, click **Install StackAdapt Pixel**.
22
21
23
-
22
+
24
23
25
24
3. In the instructions that appear, copy the universal pixel ID from the code snippet. Below is an example of a code snippet where the universal pixel ID is `sqQHa3Ob1hFi__2EcYYVZg1`.
26
25
@@ -41,9 +40,9 @@ This destination is maintained by StackAdapt. For any issues with the destinatio
41
40
42
41
Segment events that are forwarded to StackAdapt can be used to track ad conversions, and to generate retargeting and lookalike audiences. Please review the StackAdapt documentation for the general setup of these if you are not already familiar:
-[How to Generate and Target a Lookalike Audience](https://support.stackadapt.com/hc/en-us/articles/360023738733-How-to-Generate-and-Target-a-Lookalike-Audience){:target="_blank"}
-[How to Generate and Target a Lookalike Audience](https://support.stackadapt.com/hc/en-us/articles/360023738733-How-to-Generate-and-Target-a-Lookalike-Audience){:target="\_blank"}
47
46
48
47
Setup of conversion events, retargeting audiences, and lookalike audiences that fire on Segment events is largely the same as the setup in the StackAdapt documentation, with a few caveats:
49
48
@@ -64,7 +63,7 @@ A Segment event fired with the code `analytics.track("User Registered")` can be
64
63
The StackAdapt destination also supports forwarding ecommerce fields for the purpose of creating event rules that match ecommerce events, with default mappings to properties specified in the [Segment V2 Ecommerce Event Spec](/docs/connections/spec/ecommerce/v2/) as described in the below table:
@@ -76,7 +75,7 @@ The StackAdapt destination also supports forwarding ecommerce fields for the pur
76
75
For events that can involve multiple products, such as checkout events, StackAdapt forwards a JSON array of product objects with a `products` key and fields that map by default to following Segment product array fields:
Although trait fields are not frequently used in event rules, the StackAdapt destination forwards them and they can be used if desired.
111
110
112
111
| Segment Trait Property | StackAdapt Event Key |
113
-
|------------------------|----------------------|
112
+
|----------------------|--------------------|
114
113
|`traits.email`|`email`|
115
114
|`traits.first_name`|`first_name`|
116
115
|`traits.last_name`|`last_name`|
@@ -123,13 +122,13 @@ For example, to create a conversion event when a user with the domain `example.c
123
122
This rule would match a Segment event fired with code such as:
124
123
125
124
```javascript
126
-
analytics.track('Order Completed', {
127
-
order_id:'50314b8e9bcf000000000000',
125
+
analytics.track("Order Completed", {
126
+
order_id:"50314b8e9bcf000000000000",
128
127
traits: {
129
-
email:'john.smith@example.com',
130
-
first_name:'John',
131
-
last_name:'Smith',
132
-
phone:'+180055501000'
128
+
email:"john.smith@example.com",
129
+
first_name:"John",
130
+
last_name:"Smith",
131
+
phone:"+180055501000"
133
132
}
134
133
});
135
134
```
@@ -167,4 +166,4 @@ When forwarding past events using Reverse ETL, only users who have interacted wi
167
166
168
167
## Data and privacy
169
168
170
-
Review [StackAdapt's Data Processing Agreement](https://www.stackadapt.com/data-processing-agreement){:target="_blank"} to learn more about StackAdapt's privacy and data terms.
169
+
Review [StackAdapt's Data Processing Agreement](https://www.stackadapt.com/data-processing-agreement){:target="\_blank"} to learn more about StackAdapt's privacy and data terms.
0 commit comments