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
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/amazon-lambda/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Amazon Lambda Destination
3
3
rewrite: true
4
4
---
5
5
6
-
Segment makes it easy to send your data to AWS Lambda (and lots of other destinations). Once you've tracked your data using our open source [libraries](https://segment.com/libraries) we'll translate and route your data to AWS Lambda in the format they understand.
6
+
Segment makes it easy to send your data to AWS Lambda (and lots of other destinations). Once you've tracked your data using our open source [libraries](/docs/connections/sources/catalog/) we'll translate and route your data to AWS Lambda in the format they understand.
7
7
8
8
[AWS Lambda](https://aws.amazon.com/lambda/) lets you run code without provisioning or managing servers. You pay only for the compute time you consume - there is no charge when your code is not running.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/amazon-personalize/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ rewrite: true
3
3
title: Amazon Personalize Destination
4
4
---
5
5
6
-
Segment makes it easy to send your data to Amazon Personalize (and lots of other destinations). Once you've tracked your data through our opensource [libraries](https://segment.com/libraries) we'll translate and route your data to Amazon Personalize in the format they understand. [Learn more about how to use Amazon Personalize with Segment.](/docs/connections/destinations/catalog/amazon-personalize)
6
+
Segment makes it easy to send your data to Amazon Personalize (and lots of other destinations). Once you track your data using our open-source [libraries](/docs/connections/sources/catalog/) we'll translate and route your data to Amazon Personalize in the format they understand. [Learn more about how to use Amazon Personalize with Segment.](/docs/connections/destinations/catalog/amazon-personalize)
7
7
8
8
[Amazon Personalize](https://aws.amazon.com/personalize/) is a machine learning service that makes it easy for developers to create individualized recommendations for customers using their applications. AWS Personalize enables…
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/azure-function/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ beta: true
4
4
title: Azure Function Destination
5
5
---
6
6
7
-
Segment makes it easy to send your data to Azure Function (and lots of other destinations). Once you've tracked your data through our opensource [libraries](https://segment.com/libraries) we'll translate and route your data to Azure Function in the format they understand. [Learn more about how to use Azure Function with Segment.](/docs/connections/destinations/catalog/azure-function)
7
+
Segment makes it easy to send your data to Azure Function (and lots of other destinations). Once you track your data using our open-source [libraries](/docs/connections/sources/catalog/) we'll translate and route your data to Azure Function in the format they understand. [Learn more about how to use Azure Function with Segment.](/docs/connections/destinations/catalog/azure-function)
8
8
9
9
[Azure Function](https://azure.microsoft.com/en-us/services/functions) is a serverless compute service that enables you to run code on-demand without having to explicitly provision or manage infrastructure. Use Azure Functions to run a script or piece of code in response to a variety of events.
The [DoubleClick Floodlight](https://support.google.com/searchads/answer/7298761?hl=en) destination allows you to make calls directly to Floodlight based on your mapped events. All you have to do is enter your **DoubleClick Advertiser ID** in the Doubleclick Floodlight destinations settings in the Segment App, then map the Segment `track` events to their corresponding Floodlight tags.
6
7
7
-
The DoubleClick Floodlight destination allows you to make calls directly to Floodlight based on your mapped events. All you have to do is drop in your **DoubleClick Advertiser ID** into your settings and map the Segment `track` events to their corresponding Floodlight tags.
8
-
9
-
If you'd like to send mobile data, this destination _requires_ you to send device specific information such as the `IDFA` or the `AdvertisingId` and thus you should send events using our **mobile** libraries. You can also send data from `analytics.js` and we will make direct HTTP requests to Doubleclick Floodlight from your browser.
8
+
This destination _requires_ that mobile implementations send device-specific information such as the `IDFA` or the `AdvertisingId`, so you should send events using [one of the Segment mobile libraries](/docs/connections/sources/catalog/#mobile). You can also send data from [Analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/) and Segment makes direct HTTP requests to Doubleclick Floodlight from your browser.
10
9
11
10
## Track
12
11
13
-
In order to send `track` events to DoubleClick Floodlight, you **must** first create the Floodlight tags (**Sales** or **Counter**) inside your DoubleClick Campaign Manager and then map the Segment events to those tags inside Segment settings.
12
+
Before you send `track` events to DoubleClick Floodlight, you **must** first go to the DoubleClick Campaign Manager and create the Floodlight tags (**Sales** or **Counter**). Once you do that, you can map the Segment events to those tags from in the destination's settings in the Segment App.
14
13
15
-
If you want to track custom properties, be sure to create [custom variables](https://segment.com/docs/connections/destinations/catalog/doubleclick-floodlight/#setting-up-custom-variables) inside DoubleClick Campaign Manager.
14
+
To track custom properties first create [custom variables](#setting-up-custom-variables) inside DoubleClick Campaign Manager.
16
15
17
-
Once all the configurations are finished, whenever we receive a mapped Segment event, we will map the following properties and settings:
16
+
After you finish configuring Doubleclick Floodlight, Segment maps the following properties and settings when it receives a mapped event:
18
17
19
-
-`dc_rdid`will be set as `IDFA` or `AdvertisingId` (for mobile data only)
20
-
-`src`will be pulled from your destination settings
21
-
-`cat` and `type`will be pulled from your event mappings from the settings OR your top level **Activity Tag** and **Group Tag** settings
22
-
-`ord` for **counter** tags will be a random number to prevent browser caching
23
-
-`ord` for **sales** tags will be your whatever you define in your settings! (ie. `properties.order_id`) Include the `properties.` prefix to the key to ensure we can find the associated value in your `properties` object.
24
-
-`qty` for **sales** tags only we will sum the quantity of products in your `products` array property or fallback on top level `properties.quantity`
25
-
-`cost` for **sales** tags only we will send the `revenue`
26
-
-`u$` (if any) will be pulled from your property mapping setting
27
-
-`dc_lat`will be set to `0` or `1` depending on whether the device has **Limit Ad Tracking** enabled (for mobile data only)
18
+
-`dc_rdid`is set as `IDFA` or `AdvertisingId` (for mobile data only)
19
+
-`src`is pulled from your destination settings
20
+
-`cat` and `type`are pulled from your event mappings from the settings OR your top level **Activity Tag** and **Group Tag** settings
21
+
-`ord` for **counter** tags are a random number to prevent browser caching
22
+
-`ord` for **sales** tags are set to whatever you define in your settings! (ie. `properties.order_id`) Include the `properties.` prefix to the key to ensure Segment finds the associated value in your `properties` object.
23
+
-`qty` for **sales** tags only, Segment sums the quantity of products in your `products` array property or falls back on top level `properties.quantity`
24
+
-`cost` for **sales** tags only Segment sends the `revenue`
25
+
-`u$` (if any) is pulled from your property mapping setting
26
+
-`dc_lat`is set to `0` or `1` depending on whether the device has **Limit Ad Tracking** enabled (for mobile data only)
28
27
29
-
**Important:** Floodlight requires that you [set a `User-Agent` header](https://cloudup.com/cDlD6KmuuOK) with that of the app where the track event took place. Our Android or analytics.js library automatically collects the `userAgent`. However, for iOS library you must manually send the user agent string inside the `context` object. If `context.userAgent` is not provided, we will try to generate a user agent string based on some device and operating system information that we *do*already collect.
28
+
**Important:** Floodlight requires that you [set a `User-Agent` header](images/cDlD6KmuuOK.png) with that of the app where the track event took place. The Segment Android and Analytics.js (javascript) library automatically collect the `userAgent`. Howeveryou must manually send the user agent string inside the `context` object if you are using the iOS library. If `context.userAgent` is not provided, Segment tries to generate a user agent string based on some device and operating system information that is already has.
30
29
31
-
Such generated user agent string might look something like this:
30
+
A generated user agent string might look something like the following:
32
31
33
32
`Segment/1.0 (iPhone OS; CPU iPhone7,2; en-US) Apple; Version 8.1.3`
By default, the Segment event property you define for each custom variable mapping will be matched against the property values found in the `properties` object of a `track` event. You can, however, use JSON style dot-notation-accessors wrapped in double curly brackets to map to **any** property in the event's raw payload to your custom variables. For example, some acceptable values could be `context.campaign.name`, `context.userAgent`, or `anonymousId` (inside of the double curly brackets). You can find the complete structure of a standard Segment event payload [here](/docs/connections/spec/common/#structure).
57
56
58
-
**Note:** `dc_rdid` and `dc_lat` will be automatically collected by our mobile libraries and `ord` will be uniquely generated for each event.
57
+
**Note:** `dc_rdid` and `dc_lat` are automatically collected by our mobile libraries and `ord` is uniquely generated for each event.
59
58
60
59
## Page
61
60
62
-
Our DoubleClick Floodlight destination also supports tracking named `page` events as conversions. In order to enable this functionality, follow the same steps laid out above for `track` events however, in the destination settings, input the conversion "event" name following this structure (where \[PAGE NAME\] is the `name` parameter you are passing to the Segment `page` event):
61
+
The Segment DoubleClick Floodlight destination also supports tracking named `page` events as conversions. To enable this feature, follow the same steps explained above for `track` events but in the destination settings, enter the conversion "event" name. Use the structure in the example below, replacing `PAGE NAME` with the `name` parameter you pass to the Segment `page` event:
63
62
64
-
**Viewed** \[PAGE NAME\] **Page**
63
+
**Viewed `PAGE NAME` Page**
65
64
66
65
Here's an example for tracking a `page` event with the name **Confirmation**:
67
66
68
67
69
68
70
-
Make sure you enter the name case sensitively.
69
+
The name is case sensitive.
71
70
72
-
Reference our [docs](/docs/connections/sources/catalog/libraries/website/javascript/#page) for more on the `name` parameter.
71
+
See the [Analytics.js documentation](/docs/connections/sources/catalog/libraries/website/javascript/#page) for more on the `name` parameter.
73
72
74
73
### Pages with categories
75
74
76
-
If you are passing category names to `page` events you would like to track as conversions, you will need to slightly modify the event name you input into your destination settings. As opposed to **Viewed** \[PAGE NAME\] **Page**, you will need to input it as:
If you are passing category names to `page` events you would like to track as conversions, you must slightly modify the event name you input into your destination settings. Instead of **Viewed `PAGE NAME` Page**, enter it as: **Viewed `CATEGORY NAME` `PAGE NAME` **Page**
79
76
80
-
For example, if you had a `page` event with the name as **Confirmation** that was being categorized as part of a group of **Checkout** pages, you would input:
77
+
For example, if you had a `page` event with the name as **Confirmation** that was being categorized as part of a group of **Checkout** pages, you would enter:
81
78
82
79
**Viewed Checkout Confirmation Page**
83
80
84
-
Reference our [docs](/docs/connections/sources/catalog/libraries/website/javascript/#page) for more on the `category` paramter.
81
+
See the [Analytics.js documentation](/docs/connections/sources/catalog/libraries/website/javascript/#page) for more on the `category` paramter.
85
82
86
83
## Setting up Custom Variables
87
84
@@ -95,25 +92,25 @@ For each custom variable you want to create or edit, enter a Friendly Name, whic
95
92
96
93
Choose the Type of custom variable you're creating. Choose string if you want the variable to include alphanumeric characters or special characters. The only characters you can't use are ", < and >. Choose number if you want to pass numeric values.
97
94
98
-
If you add Custom Floodlight Variables to a report as metrics, note that they will be summed in the report as if they are numeric values, even if the variables are actually strings. The string variables will display a value of 0.
95
+
If you add Custom Floodlight Variables to a report as metrics, they are summed in the report as if they are numeric values, even if the variables are actually strings. The string variables will display a value of 0.
99
96
100
-
Click Save.
97
+
Click **Save**.
101
98
102
99
## COPPA Compliance
103
100
104
-
DoubleClick Floodlight lets you set a parameter called `tag_for_child_directed_treatment` as either `0` or `1` if you want to mark a particular tag as coming from a user under the age of 13, under the [COPPA](https://www.ftc.gov/news-events/media-resources/protecting-consumer-privacy/kids-privacy-coppa) compliance.
101
+
DoubleClick Floodlight lets you set a parameter called `tag_for_child_directed_treatment` as either `0`, or `1` to mark a specific tag as coming from a user under the age of 13, under the [COPPA compliance privacy law](https://www.ftc.gov/news-events/media-resources/protecting-consumer-privacy/kids-privacy-coppa).
105
102
106
103
If you want to set this flag, you can send an integration option namespaced as `coppaCompliant` with `true` or `false` (default):
107
104
108
105
```java
109
-
110
106
Analytics.with(context).track("Free El", new Properties().putValue("show", "Stranger Things").putValue("source", "Netflix").putValue("greatestShowEver", true), new Options().setIntegrationOptions("DoubleClick Floodlight", new ValueMap().putValue("coppaCompliant", true)));
111
107
```
112
108
113
-
> Note: This flag was previously called "copaCompliant" instead of "coppaCompliant". The method has been aliased to preserve the old functionality, and you do not need to update it if you used the old spelling.
109
+
> success ""
110
+
> **Tip**: This flag was previously called `copaCompliant` (a typo) instead of `coppaCompliant`. The method has been aliased to preserve the old functionality, and you do not need to update it if you used the old spelling.
114
111
115
112
## Sending Personally Identifiable Information (PII)
116
113
117
-
Do not map custom variables that are PII. Refer to the [warning](https://support.google.com/dfa/partner/answer/2548879?hl=en) by DoubleClick:
114
+
Do not map custom variables that contain Personally Identifying Information (PII). Refer to [this warning by DoubleClick](https://support.google.com/dfa/partner/answer/2548879?hl=en):
118
115
119
116
The terms of your DoubleClick contract prohibit passing any information to us that we could use or recognize as personally identifiable information (PII). If you enter certain key-values into a field in a DoubleClick product, you may see a warning that reminds you that you must not use key-values to pass data that we would recognize as PII. Key-values that trigger this warning include, for example, email and username. Note that it is okay to use these key-values if your purpose is not to collect information that DoubleClick could use or recognize as PII. (For example, email=weekly is fine, but passing a user's email address is not.) If you do choose one of these key-values, DoubleClick may contact you in the future to confirm that you are not using them in a way that is prohibited.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/facebook-pixel/index.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,6 +120,8 @@ Here is how you'd specify standard events in the settings view:
120
120
121
121
122
122
123
+
You can map more than one Track event to the same Facebook standard event.
124
+
123
125
### Legacy Events
124
126
125
127
To send *Legacy Conversion* events, use the Segment setting called "Legacy Conversion Pixel IDs". Any events that appear in that mapping will be sent to Facebook with the specified Pixel ID used as the Facebook Pixel `eventName`. Conversion events only support `currency` and `value` as event properties, so only these will be associated with the event. `currency` will default to "USD" if left out.
***Project-level build.gradle***: Add Google Services dependency and their Maven repo location to repositories:
34
33
35
-
```
34
+
```js
36
35
buildscript {
37
36
dependencies {
38
37
// Add this line
@@ -68,7 +67,7 @@ Analytics analytics = new Analytics.Builder(context, writeKey)
68
67
69
68
By default, we bundle only `Firebase/Core` which is [Firebase's Analytics offering](https://firebase.google.com/docs/analytics/). You can see the other available [Firebase dependencies and features here](https://firebase.google.com/docs/android/setup).
70
69
71
-
###iOS
70
+
##Getting Started on iOS
72
71
73
72
1. Register your app in the [Firebase console](https://console.firebase.google.com/) and add the `GoogleService-Info.plist` to the root of your Xcode project.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/freshmarketer/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Freshmarketer Destination
3
3
rewrite: true
4
4
---
5
5
6
-
Segment makes it easy to send your data to [Freshmarketer](https://www.freshmarketer.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) (and lots of other destinations). Once you've tracked your data through our opensource [libraries](https://segment.com/libraries) we'll translate and route your data to Freshmarketer in the format they understand. Learn more about how to use Freshmarketer with Segment.
6
+
Segment makes it easy to send your data to [Freshmarketer](https://www.freshmarketer.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) (and lots of other destinations). Once you track your data using our open-source [libraries](/docs/connections/sources/catalog/) we'll translate and route your data to Freshmarketer in the format they understand. Learn more about how to use Freshmarketer with Segment.
7
7
8
8
This destination is maintained by Freshmarketer. For any issues with the destination, [contact their team](mailto:[email protected]).
0 commit comments