Skip to content

Commit 65a9990

Browse files
committed
reset actions-stackadapt-cloud/index.md
1 parent 16f4240 commit 65a9990

File tree

1 file changed

+18
-17
lines changed
  • src/connections/destinations/catalog/actions-stackadapt-cloud

1 file changed

+18
-17
lines changed

src/connections/destinations/catalog/actions-stackadapt-cloud/index.md

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,15 @@ hide-dossier: true
55
beta: true
66
id: 61d8859be4f795335d5c677c
77
hidden: true
8-
redirect_from: "/connections/destinations/catalog/actions-stackadapt/"
8+
redirect_from: '/connections/destinations/catalog/actions-stackadapt/'
99
---
1010

1111
{% include content/plan-grid.md name="actions" %}
1212

13-
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.
13+
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+
15+
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"}.
1416

15-
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"}.
1617

1718
## Getting started
1819

@@ -21,7 +22,7 @@ This destination is maintained by StackAdapt. For any issues with the destinatio
2122
1. Log in to your StackAdapt account and navigate to the Pixels page.
2223
2. Above the list of pixels, click **Install StackAdapt Pixel**.
2324

24-
![Image showing location of link to install Pixel](images/install-pixel-link.png)
25+
![Image showing location of link to install Pixel](images/install-pixel-link.png)
2526

2627
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`.
2728

@@ -42,9 +43,9 @@ This destination is maintained by StackAdapt. For any issues with the destinatio
4243

4344
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:
4445

45-
- [Creating Conversion Events](https://support.stackadapt.com/hc/en-us/articles/360005859214-Creating-Conversion-Events){:target="\_blank"}
46-
- [Creating Retargeting Audiences](https://support.stackadapt.com/hc/en-us/articles/360005939153-Creating-Retargeting-Audiences){:target="\_blank"}
47-
- [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"}
46+
- [Creating Conversion Events](https://support.stackadapt.com/hc/en-us/articles/360005859214-Creating-Conversion-Events){:target="_blank"}
47+
- [Creating Retargeting Audiences](https://support.stackadapt.com/hc/en-us/articles/360005939153-Creating-Retargeting-Audiences){:target="_blank"}
48+
- [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"}
4849

4950
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:
5051

@@ -65,7 +66,7 @@ A Segment event fired with the code `analytics.track("User Registered")` can be
6566
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:
6667

6768
| Segment Ecommerce Event Property | StackAdapt Event Key |
68-
| -------------------------------- | -------------------- |
69+
|----------------------------------|----------------------|
6970
| `order_id` | `order_id` |
7071
| `revenue` | `revenue` |
7172
| `product_id` | `product_id` |
@@ -77,7 +78,7 @@ The StackAdapt destination also supports forwarding ecommerce fields for the pur
7778
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:
7879

7980
| Segment Ecommerce Event Property | StackAdapt Product Object Key |
80-
| -------------------------------- | ----------------------------- |
81+
|----------------------------------|-------------------------------|
8182
| `products.$.product_id` | `product_id` |
8283
| `products.$.category` | `product_category` |
8384
| `products.$.name` | `product_name` |
@@ -111,7 +112,7 @@ analytics.track('Order Completed', {
111112
Although trait fields are not frequently used in event rules, the StackAdapt destination forwards them and they can be used if desired.
112113

113114
| Segment Trait Property | StackAdapt Event Key |
114-
| ---------------------- | -------------------- |
115+
|------------------------|----------------------|
115116
| `traits.email` | `email` |
116117
| `traits.first_name` | `first_name` |
117118
| `traits.last_name` | `last_name` |
@@ -124,13 +125,13 @@ For example, to create a conversion event when a user with the domain `example.c
124125
This rule would match a Segment event fired with code such as:
125126

126127
```javascript
127-
analytics.track("Order Completed", {
128-
order_id: "50314b8e9bcf000000000000",
128+
analytics.track('Order Completed', {
129+
order_id: '50314b8e9bcf000000000000',
129130
traits: {
130-
131-
first_name: "John",
132-
last_name: "Smith",
133-
phone: "+180055501000"
131+
132+
first_name: 'John',
133+
last_name: 'Smith',
134+
phone: '+180055501000'
134135
}
135136
});
136137
```
@@ -168,4 +169,4 @@ When forwarding past events using Reverse ETL, only users who have interacted wi
168169

169170
## Data and privacy
170171

171-
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.
172+
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

Comments
 (0)