diff --git a/src/connections/destinations/catalog/castle/index.md b/src/connections/destinations/catalog/castle/index.md index 72c64075a1..5ad01766c9 100644 --- a/src/connections/destinations/catalog/castle/index.md +++ b/src/connections/destinations/catalog/castle/index.md @@ -47,12 +47,12 @@ Calls are now visible in Castle dashboards in real-time. 2. Next, add the Castle destination to your analytics instance: - ```swift - let analytics = Analytics(configuration: Configuration(writeKey: "")) - - let castleDestination = CastleDestination(userJwt: "") - analytics.add(plugin: castleDestination) - ``` + ```swift + let analytics = Analytics(configuration: Configuration(writeKey: "")) + + let castleDestination = CastleDestination(userJwt: "") + analytics.add(plugin: castleDestination) + ``` ### Android @@ -73,10 +73,10 @@ Calls are now visible in Castle dashboards in real-time. 2. Next, add the Castle destination to your analytics instance: - ```kotlin - analytics = Analytics("", applicationContext) - analytics.add(plugin = CastleDestination(userJwt = "")) - ``` + ```kotlin + analytics = Analytics("", applicationContext) + analytics.add(plugin = CastleDestination(userJwt = "")) + ``` ## Page @@ -102,7 +102,6 @@ analytics.track('Added to Cart') Segment sends Track calls to Castle as a `$custom` events. -*** diff --git a/src/connections/destinations/catalog/doubleclick-floodlight/index.md b/src/connections/destinations/catalog/doubleclick-floodlight/index.md index f8669d8c5b..25d2ba37e6 100644 --- a/src/connections/destinations/catalog/doubleclick-floodlight/index.md +++ b/src/connections/destinations/catalog/doubleclick-floodlight/index.md @@ -27,7 +27,11 @@ After you finish configuring Doubleclick Floodlight, Segment maps the following - `u` values (if any) are pulled from your property mapping setting. - `dc_lat` is set to `0` or `1` depending on whether the device has **Limit Ad Tracking** enabled (for mobile data only). -**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`. However you 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. +**Important:** Floodlight requires that you set a `User-Agent` header with that of the app where the track event took place. + +![User-Agent header.](images/cDlD6KmuuOK.png) + +The Segment Android and Analytics.js (JavaScript) library automatically collect the `userAgent`. However you 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. A generated user agent string might look something like the following: diff --git a/src/connections/destinations/catalog/engage-messaging/index.md b/src/connections/destinations/catalog/engage-messaging/index.md index 771a6c17ac..6101c582d1 100644 --- a/src/connections/destinations/catalog/engage-messaging/index.md +++ b/src/connections/destinations/catalog/engage-messaging/index.md @@ -44,5 +44,3 @@ analytics.track('Login Button Clicked') ``` Segment sends Track calls to Engage Messaging as a `track` event. - ---- diff --git a/src/connections/destinations/catalog/optimizely-full-stack/index.md b/src/connections/destinations/catalog/optimizely-full-stack/index.md index 2171659fe6..0961698f28 100644 --- a/src/connections/destinations/catalog/optimizely-full-stack/index.md +++ b/src/connections/destinations/catalog/optimizely-full-stack/index.md @@ -34,7 +34,7 @@ This requires that customers include a native Optimizely implementation before t 3. Create a native Optimizely instance in your server environment so you can access Optimizely decisioning methods like `activate`, `isFeatureEnabled`. 4. Finally, define any [`events`](https://docs.developers.optimizely.com/full-stack/docs/create-events){:target="_blank"} and [`attributes`](https://docs.developers.optimizely.com/full-stack/docs/define-attributes){:target="_blank"} in your Optimizely dashboard, and to associate `metrics` with the appropriate Optimizely Experiments. Segment maps Track event names to Optimizely `eventName` - the `eventName` corresponds to an experiment `metric`. In addition, Segment maps Track event `context.traits` to Optimizely `attributes`. -> warning "Optimizely SDKs v1.x or v2.x require matching `attributes` objects for correct attribution" +> warning "Optimizely SDKs v1.x or v2.x require matching attributes objects for correct attribution" > If you use Optimizely SDKs v1.x or v2.x and use any `activate` or `isFeatureEnabled` calls, the `attributes` object for each user must match the `attributes` object passed to any Track calls for that user ID so that it can be correctly attributed on the Optimizely results page. If you are using Optimizely SDKs v3+, [Easy Event Tracking](https://blog.optimizely.com/2019/02/26/introducing-easy-event-tracking-the-easier-way-to-understand-and-optimize-the-customer-journey/){:target="_blank"} is enabled by default for decision events. Set up does not require maintaining the attributes of a user as long as the user ID stays the same between Optimizely `activate` and `isFeatureEnabled` calls and Segment Track calls to have Optimizely `metrics` populated in the Optimizely results page. If you would like to segment your Optimizely results by user `attribute`, then make sure the `attributes` passed in for the `activate` and `isFeatureEnabled` calls match the `attributes` passed in for the Track calls for that user id.