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
<divclass="premonition success"><divclass="fa fa-check-square"></div><divclass="content"><pclass="header">Upgrade to Analytics.js 2.0</p>
2
+
<pmarkdown=1>Actions-based destinations require features found in [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/). [Upgrade your Analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2/) source to take advantage of Actions-based destinations, performance improvements, and more.</p>
{% capture blurb %}A new version of this destination is available. See [{{name}} (Actions)]({{link}}) {% endcapture %}
7
+
{% endif %}
8
+
9
+
<divclass="premonition warning"><divclass="fa fa-check-square"></div><divclass="content"><pclass="header">{{page.title | replace: 'Destination', ''}} (Classic) is in Maintenance mode</p>
10
+
<pmarkdown=1>The {{name}} (Classic) Destination has entered maintenance mode. Future updates are limited to security updates and bug fixes. {{blurb}}</p>
Copy file name to clipboardExpand all lines: src/connections/destinations/actions.md
+6
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,9 @@ You can also choose which event types, event names, or event property values tri
14
14
15
15
Each Actions-framework Destination you see in the Segment catalog represents a feature or capability of the destination which can consume data from your Segment source. The Action clearly lists which data from the events it requires, and which data is optional. For example, Amplitude requires that you always send a `LogEvent` , or Slack always requires a `PostMessage`. Each Action also includes a default mapping which you can modify.
16
16
17
+
{% include content/ajs-upgrade.md %}
18
+
19
+
17
20
## Benefits of Destination Actions
18
21
19
22
-**Easier setup**: Users see fewer initial settings which can decrease the time spent configuring the destination.
@@ -76,6 +79,9 @@ To set up a new Actions-framework destination for the first time:
76
79
77
80
## Migrate a classic destination to an actions-based destination
78
81
82
+
{% include content/ajs-upgrade.md %}
83
+
84
+
79
85
Moving from a classic destination to an actions-based destination is a manual process. Segment recommends that you follow the procedure below:
80
86
81
87
1. Create the actions-based destination with your development or test source.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/activecampaign/index.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ This destination is maintained by ActiveCampaign. For any issues with the destin
19
19
20
20
## Page
21
21
22
-
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
22
+
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
23
23
24
24
```js
25
25
analytics.page();
@@ -32,7 +32,7 @@ When you call `page`, we will send that event to ActiveCampaign as a `site track
32
32
33
33
## Identify
34
34
35
-
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:
35
+
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
122
+
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/adquick/index.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ This destination is maintained by AdQuick. For any issues with the destination,
21
21
22
22
## Page
23
23
24
-
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
24
+
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
25
25
26
26
```
27
27
analytics.page()
@@ -32,7 +32,7 @@ Page calls will be sent to AdQuick as a `pageview`.
32
32
33
33
## Screen
34
34
35
-
If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like:
35
+
If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like:
36
36
37
37
```
38
38
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
@@ -43,7 +43,7 @@ Screen calls will be sent to AdQuick as a `screenview`.
43
43
44
44
## Identify
45
45
46
-
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:
46
+
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
47
47
48
48
```
49
49
analytics.identify('userId123', {
@@ -56,7 +56,7 @@ Identify calls will be sent to AdQuick as an `identify` event.
56
56
57
57
## Track
58
58
59
-
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
59
+
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/adroll/index.md
+6-8
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,7 @@ rewrite: true
3
3
title: AdRoll Destination
4
4
---
5
5
6
-
[AdRoll](https://developers.adroll.com/) is a retargeting network that allows you to show ads to visitors who've landed on your site while browsing the web. The AdRoll Destination is open-source. You can browse the code on [GitHub](https://github.com/segment-integrations/analytics.js-integration-adroll).
7
-
8
-
This document was last updated on January 26, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact)!
6
+
[AdRoll](https://adroll.com/) is a retargeting network that allows you to show ads to visitors who've landed on your site while browsing the web. The AdRoll Destination is open-source. You can browse the code on [GitHub](https://github.com/segment-integrations/analytics.js-integration-adroll).
9
7
10
8
## Getting Started
11
9
@@ -21,26 +19,26 @@ This document was last updated on January 26, 2018. If you notice any gaps, outd
21
19
22
20
## Page
23
21
24
-
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
22
+
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
25
23
```javascript
26
24
analytics.page()
27
25
```
28
26
_**NOTE:** The `page` call **must** be made on a page for any `identify` or `track` events to be sent to AdRoll. Our Analytics.js snippet includes a `page` call by default so you should be fine, unless you've manually removed the page call from your Analytics.js snippet._
29
27
30
28
## Identify
31
29
32
-
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:
30
+
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
Set a `userId` using the `identify` call which will then be passed it to AdRoll each time a [`track`](https://segment.com/docs/connections/destinations/catalog/adroll/#track) call is made. If you pass an `email` trait, we'll send that to AdRoll by setting `window.adroll_email` to that value.
36
+
Set a `userId` using the `identify` call which will then be passed it to AdRoll each time a [`track`](/docs/connections/destinations/catalog/adroll/#track) call is made. If you pass an `email` trait, we'll send that to AdRoll by setting `window.adroll_email` to that value.
39
37
40
38
41
39
## Track
42
40
43
-
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
41
+
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
Prior to rolling out Segment ID's, AdRoll allowed "named segments". If your account was created prior to 2015, then the track events you send from the browser using our [`analytics.track`](https://segment.com/docs/connections/destinations/catalog/adroll/#track) method will be passed on to AdRoll as `adroll_segments` with the segment being the snake-cased event name.
91
+
Prior to rolling out Segment ID's, AdRoll allowed "named segments". If your account was created prior to 2015, then the track events you send from the browser using our [`analytics.track`](/docs/connections/destinations/catalog/adroll/#track) method will be passed on to AdRoll as `adroll_segments` with the segment being the snake-cased event name.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/adtriba/index.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -17,12 +17,12 @@ This destination is maintained by Adtriba. For any issues with the destination,
17
17
18
18
1. From the Segment web app, click **Catalog**.
19
19
2. Search for "Adtriba" in the Catalog, select it, and choose which of your sources to connect the destination to.
20
-
3. Enter the "Project Tracker ID / API Key" into your Segment Settings UI which you can find from your [Adtriba dashboard](https://console.adtriba.com).
20
+
3. Enter the "Project Tracker ID / API Key" into your Segment Settings UI which you can find on the Adtriba dashboard.
21
21
4. Validate the forwarded events by checking the Tracking Report under the "Tracking" tab.
22
22
23
23
## Page
24
24
25
-
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
25
+
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
26
26
27
27
```
28
28
analytics.page()
@@ -33,7 +33,7 @@ Page calls will be sent to Adtriba as a `pageview`.
33
33
34
34
## Identify
35
35
36
-
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:
36
+
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
37
37
38
38
```
39
39
analytics.identify('userId123', {
@@ -46,7 +46,7 @@ Identify calls will be sent to Adtriba as an `identify` event.
46
46
47
47
## Track
48
48
49
-
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
49
+
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
50
50
51
51
```
52
52
analytics.track('Conversion', {
@@ -58,4 +58,4 @@ analytics.track('Conversion', {
58
58
59
59
Track calls will be sent to Adtriba as a `track` event.
60
60
61
-
Trigger additional events by using [Semantic Events](https://segment.com/docs/connections/spec/semantic/) in order to enrich the Adtriba machine learning process.
61
+
Trigger additional events by using [Semantic Events](/docs/connections/spec/semantic/) in order to enrich the Adtriba machine learning process.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/algolia-insights/index.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ This destination is maintained by [Algolia](https://www.algolia.com/). For any i
22
22
23
23
1. From the Segment web app, click **Catalog**.
24
24
2. Search for "Algolia" in the Catalog, select it, and choose which of your sources to connect the destination to.
25
-
3. Enter the "App ID" & "API Key" into your Segment Settings UI which you can find from your [Algolia Dashboard](https://www.algolia.com/apps/), under API Keys menu.
25
+
3. Enter the "App ID" & "API Key" into your Segment Settings UI which you can find on the Algolia Dashboard, under API Keys menu.
26
26
27
27
_**NOTE:** The Algolia Insights Destination is not a plug-and-play integration. It requires you to modify your frontend code to send additional Algolia-related data like index name, queryID, etc._
28
28
@@ -32,9 +32,9 @@ You can read more about how to send Algolia-related data to Segment from [the do
32
32
33
33
## Track
34
34
35
-
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does.
35
+
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does.
36
36
37
-
Algolia supports the following six events from Segment's [Ecommerce Spec](https://segment.com/docs/connections/spec/ecommerce/v2/).
37
+
Algolia supports the following six events from Segment's [Ecommerce Spec](/docs/connections/spec/ecommerce/v2/).
0 commit comments