From 738862034d70726ed9a7bf25e7a4207b1ce48346 Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Mon, 6 Oct 2025 12:54:14 -0500 Subject: [PATCH 1/7] Add code fence language --- .../mobile/apple/destination-plugins/1flow-swift.md | 6 +++--- .../mobile/apple/destination-plugins/adjust-swift.md | 8 ++++---- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/1flow-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/1flow-swift.md index 8932c44aea..b77a0bf8a7 100644 --- a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/1flow-swift.md +++ b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/1flow-swift.md @@ -30,7 +30,7 @@ You'll then have the option to pin to a version, or specific branch, as well as Open your Package.swift file and add the following to the `dependencies` section: -``` +```swift .package( name: "Segment", url: "https://github.com/1Flow-Inc/segment-1flow-ios.git", @@ -42,14 +42,14 @@ Open your Package.swift file and add the following to the `dependencies` section Open the file where you set up and configure the Analytics-Swift library. Add this plugin to the list of imports. -``` +```swift import Segment import SegmentOneFlow // <-- Add this line ``` Just under your Analytics-Swift library setup, call `analytics.add(plugin: ...)` to add an instance of the plugin to the Analytics timeline. -``` +```swift let analytics = Analytics(configuration: Configuration(writeKey: "") .flushAt(3) .trackApplicationLifecycleEvents(true)) diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adjust-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adjust-swift.md index 2ecb072e10..810eab998d 100644 --- a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adjust-swift.md +++ b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adjust-swift.md @@ -30,7 +30,7 @@ You'll then have the option to pin to a version, or specific branch, as well as Open your Package.swift file and add the following do your the `dependencies` section: -``` +```swift .package( name: "Segment", url: "https://github.com/segment-integrations/analytics-swift-integration-adjust.git", @@ -41,14 +41,14 @@ Open your Package.swift file and add the following do your the `dependencies` se Open the file where you setup and configure the Analytics-Swift library. Add this plugin to the list of imports. -``` +```swift import Segment import SegmentAdjust // <-- Add this line ``` Just under your Analytics-Swift library setup, call `analytics.add(plugin: ...)` to add an instance of the plugin to the Analytics timeline. -``` +```swift let analytics = Analytics(configuration: Configuration(writeKey: "") .flushAt(3) .trackApplicationLifecycleEvents(true)) @@ -133,4 +133,4 @@ The destination automatically forwards push notification tokens through to Adjus ### Event buffering -By default, our destination enables event buffering for Adjust. This saves your customers' battery life. However, you can disable this in the options on the Adjust destination settings on Segment. \ No newline at end of file +By default, our destination enables event buffering for Adjust. This saves your customers' battery life. However, you can disable this in the options on the Adjust destination settings on Segment. From b2a11a69f0980b41a306449a7c28717f22699ace Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Mon, 6 Oct 2025 12:54:25 -0500 Subject: [PATCH 2/7] Fix heading --- .../mobile/apple/destination-plugins/nielsen-dtvr-swift.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/nielsen-dtvr-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/nielsen-dtvr-swift.md index 5bc1ccbbb3..b5d8c9ef5e 100644 --- a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/nielsen-dtvr-swift.md +++ b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/nielsen-dtvr-swift.md @@ -15,7 +15,7 @@ To get started with Nielsen-DTVR and retrieve an `appid` to configure this integ - Reach out to your Segment customer service representative to enable the Nielsen-DTVR plugin, as this destination is in private beta. -### Adding the dependency +## Adding the dependency ### via Xcode In the Xcode `File` menu, click `Add Packages`. You'll see a dialog where you can search for Swift packages. In the search field, enter the URL to this repo. From fd0425afcaf65262776d4fb64aca8359b6e73614 Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Mon, 6 Oct 2025 13:08:48 -0500 Subject: [PATCH 3/7] Fix link def --- .../libraries/mobile/apple/destination-plugins/adobe-swift.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md index a8718848a8..a9653c540e 100644 --- a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md +++ b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md @@ -12,7 +12,7 @@ Adobe Analytics uses a slightly different approach to tracking than Segment, and For example, if one of your end users dismissed a welcome dialog in your app, Segment would generate a `Welcome Dialog Dismissed` event with properties that contain the user ID (`user123`) and the dialog name (`welcome-dialog`), while Adobe Analytics would model the same action as a pageView with variables that represent the dialog name, visitorID, and the event name, and an eVar ("dismissed"). -Both Segment and Adobe Analytics have recommended standard data for tracking events. Segment has [the Spec](/docs/connections/spec/), and Adobe uses predefined events. Segment automatically maps incoming event data and some product level properties to Adobe's predefined events, when the event data is in the correct Segment Ecommerce Spec](/docs/connections/spec/ecommerce/v2/) format. Video calls using the format described in [this document](/docs/connections/spec/video) are also automatically mapped. If you're using the Mobile SDKs, mobile lifecycle events are also automatically mapped. If you need to create Page and Track events that are outside the scope of the Ecommerce Spec, you need to map those in your Segment destinations settings UI. +Both Segment and Adobe Analytics have recommended standard data for tracking events. Segment has [the Spec](/docs/connections/spec/), and Adobe uses predefined events. Segment automatically maps incoming event data and some product level properties to Adobe's predefined events, when the event data is in the correct [Segment Ecommerce Spec](/docs/connections/spec/ecommerce/v2/) format. Video calls using the format described in [this document](/docs/connections/spec/video) are also automatically mapped. If you're using the Mobile SDKs, mobile lifecycle events are also automatically mapped. If you need to create Page and Track events that are outside the scope of the Ecommerce Spec, you need to map those in your Segment destinations settings UI. Segment strongly recommends that you create a [Tracking Plan](/docs/protocols) for both your Segment and Adobe Analytics events before you send any events or properties to Adobe. This helps you map your Segment events to Adobe `events` and Segment properties to Adobe variables. If you decide to set up Adobe Analytics for mobile, you must set up this mapping in both the Segment settings and the Adobe Mobile Services dashboard, so it's good to stay consistent. From f8d21597605aff2b2ba516cf7fef9b39e94b5a4d Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Mon, 6 Oct 2025 23:09:22 -0500 Subject: [PATCH 4/7] Fixes --- .../mobile/apple/destination-plugins/adobe-swift.md | 6 +++--- .../mobile/apple/destination-plugins/mixpanel-swift.md | 8 +++++++- 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md index a9653c540e..a1b61d11f5 100644 --- a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md +++ b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md @@ -44,7 +44,7 @@ You then have the option to pin to a version or specific branch and select which Open your Package.swift file and add the following to the `dependencies` section: -``` +```swift .package( name: "Segment", url: "https://github.com/segment-integrations/analytics-swift-adobe-analytics.git", @@ -56,14 +56,14 @@ Open your Package.swift file and add the following to the `dependencies` section Open the file where you set up and configured the Analytics-Swift library. Add this plugin to the list of imports. -``` +```swift import Segment import SegmentAdobe // <-- Add this line ``` Just under your Analytics-Swift library setup, call `analytics.add(plugin: ...)` to add an instance of the plugin to the Analytics timeline. -``` +```swift let analytics = Analytics(configuration: Configuration(writeKey: "") .flushAt(3) .trackApplicationLifecycleEvents(true)) diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md index cfce2c663f..19a64ffc6f 100644 --- a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md +++ b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md @@ -82,9 +82,15 @@ The first thing you'll want to do is to identify your users so Mixpanel knows wh As soon as you have a `userId` for a visitor that was previously anonymous you'll need to [`alias`](/docs/connections/spec/alias/) their old anonymous `id` to the new `userId`. In Mixpanel only **one** anonymous user history can be merged to **one** identified user. For that reason you should only call `alias` once, right after a user registered, but before the first `identify`. - When you call the Identify method from the client in either a browser using Analytics.js or one a mobile SDKs, several things occur: Segment recognizes and translates the [special traits](/docs/connections/spec/identify/#traits) so that they fit the expectations of Mixpanel's API. The table below shows the mappings. Pass the key on the left and Segment transforms it to the key on the right before sending to Mixpanel. + When you call the Identify method from the client in either a browser using Analytics.js or one a mobile SDKs, several things occur: + Segment recognizes and translates the [special traits](/docs/connections/spec/identify/#traits) so that they fit the expectations of Mixpanel's API. + The table below shows the mappings. Pass the key on the left and Segment transforms it to the key on the right before sending to Mixpanel. + + + + From 6f729dc5aff5f32586384b05040e59c0139f4107 Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Tue, 7 Oct 2025 15:26:35 -0500 Subject: [PATCH 5/7] Fix table --- .../catalog/libraries/mobile/android/wear.md | 29 +++++++++++++++---- 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/src/connections/sources/catalog/libraries/mobile/android/wear.md b/src/connections/sources/catalog/libraries/mobile/android/wear.md index e9ec90f0ee..737ee13db5 100644 --- a/src/connections/sources/catalog/libraries/mobile/android/wear.md +++ b/src/connections/sources/catalog/libraries/mobile/android/wear.md @@ -82,12 +82,21 @@ analytics.track("Purchased Item", new Properties().putValue("sku", "13d31").putR ```
KeySegment transformation
`created` `$created`
+ + + + + + + - + + - + +
FieldTypeDescription
`name` _String,required_`name`_String,required_ A name for the tracked action.
`properties` _Properties,optional_`properties`_Properties,optional_ A map of properties for this action, e.g. revenue if the action was a purchase.
@@ -106,16 +115,26 @@ analytics.screen("Purchase Screen", "Smartwatches", new Properties().putValue("s ``` + + + + + + + - + + - + + - + +
FieldTypeDescription
`name` _String,optional*_`name`_String,optional*_ A name for the screen. Optional if category is provided.
`category` _String,optional*_`category`_String,optional*_ A category for the screen. Optional if name is provided.
`properties` _Properties,optional_`properties`_Properties,optional_ A map of properties for this screen.
From ea5e564b1397647058360e70c4fe440473625fbd Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Tue, 7 Oct 2025 22:56:59 -0500 Subject: [PATCH 6/7] Update mixpanel-swift.md --- .../mobile/apple/destination-plugins/mixpanel-swift.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md index 19a64ffc6f..71d4f68739 100644 --- a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md +++ b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md @@ -82,9 +82,7 @@ The first thing you'll want to do is to identify your users so Mixpanel knows wh As soon as you have a `userId` for a visitor that was previously anonymous you'll need to [`alias`](/docs/connections/spec/alias/) their old anonymous `id` to the new `userId`. In Mixpanel only **one** anonymous user history can be merged to **one** identified user. For that reason you should only call `alias` once, right after a user registered, but before the first `identify`. - When you call the Identify method from the client in either a browser using Analytics.js or one a mobile SDKs, several things occur: - Segment recognizes and translates the [special traits](/docs/connections/spec/identify/#traits) so that they fit the expectations of Mixpanel's API. - The table below shows the mappings. Pass the key on the left and Segment transforms it to the key on the right before sending to Mixpanel. +When you call the Identify method from the client in either a browser using Analytics.js or one a mobile SDKs, several things occur: Segment recognizes and translates the [special traits](/docs/connections/spec/identify/#traits) so that they fit the expectations of Mixpanel's API. The table below shows the mappings. Pass the key on the left and Segment transforms it to the key on the right before sending to Mixpanel. From 7bafafaf1b6f1c0b8b5541637fac786962d62c12 Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Wed, 8 Oct 2025 09:08:53 -0500 Subject: [PATCH 7/7] Fix identation of code blocks --- .../catalog/cloud-apps/wootric/index.md | 4 +-- .../catalog/libraries/mobile/amp/index.md | 29 +++++++++---------- 2 files changed, 16 insertions(+), 17 deletions(-) diff --git a/src/connections/sources/catalog/cloud-apps/wootric/index.md b/src/connections/sources/catalog/cloud-apps/wootric/index.md index 0faeef284b..adbf507493 100644 --- a/src/connections/sources/catalog/cloud-apps/wootric/index.md +++ b/src/connections/sources/catalog/cloud-apps/wootric/index.md @@ -24,7 +24,7 @@ Below is a table of events that InMoment sends to Segment. These events will sho | Event Name | Description | -| ------------------------------- | --------------------------------------- | | +| ------------------------------- | --------------------------------------- | | Wootric survey response created | A survey response was created | | Wootric survey response updated | An existing survey response was updated | @@ -33,7 +33,7 @@ Below is a table of events that InMoment sends to Segment. These events will sho Below are tables outlining the properties included in the events listed above. | Property Name | Description | -| ------------- | --------------------------------------------------------------------- | | +| ------------- | --------------------------------------------------------------------- | | channel | The channel from which the survey was responded like ‘web' or ‘email' | | created_at | The timestamp of when the response was created | | metric_type | The mode of the survey like "NPS" or “CSAT” | diff --git a/src/connections/sources/catalog/libraries/mobile/amp/index.md b/src/connections/sources/catalog/libraries/mobile/amp/index.md index 3f972d78f6..4faa5a1071 100644 --- a/src/connections/sources/catalog/libraries/mobile/amp/index.md +++ b/src/connections/sources/catalog/libraries/mobile/amp/index.md @@ -17,14 +17,14 @@ If you're new to [AMP](https://www.ampproject.org){:target="_blank"}, go through ### Step 1: Include AMP component Before the closing `` tag, include the [`amp-analytics` component](https://www.ampproject.org/docs/reference/components/amp-analytics){:target="_blank"}: - ```js +```js - ``` +``` ### Step 2: Include Segment analytics Within your `` tags, include the following Segment analytics snippet: - ```html +```html - ``` +``` Replace `WRITE_KEY` with the write key you obtain from the AMP Source you've set up within the Segment UI. For sources in [EU workspaces](/docs/guides/regional-segment/), use the following snippet: - ```html +```html - ``` +``` By default, the snippet will automatically fire a page event which you can read more about [in the Page section of this documentation](/docs/connections/sources/catalog/libraries/mobile/amp/#page). @@ -66,7 +66,7 @@ The Page method lets you record page views on your website, along with your choi A `page` call is included by default when you include Segment Analytics into your code with the ability to customize the `name` of your page: - ```html +```html - ``` +``` ## Track @@ -85,7 +85,7 @@ The Track method (referred to as `click` in AMP) lets you record any actions you In order to track these `click` events simply add a trigger with a `selector`, which behaves the same way as [CSS Selectors](https://www.w3schools.com/cssref/css_selectors.asp){:target="_blank"}, which will send that event once the user clicks: - ```html +```html - ``` +``` ### UTM parameters @@ -226,4 +226,3 @@ For further details refer to the various `Client ID` scenarios in relation to AM See a live AMP with Segment analytics -