From 721570b51e5f4ef778380ee399e2528f6ee351c7 Mon Sep 17 00:00:00 2001 From: CristhianMotoche Date: Wed, 15 Oct 2025 13:16:28 -0500 Subject: [PATCH 1/2] chore: Replace variable interpolation with Evergage --- src/connections/destinations/catalog/evergage/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/evergage/index.md b/src/connections/destinations/catalog/evergage/index.md index 54c1b045f5..bfd64c1059 100644 --- a/src/connections/destinations/catalog/evergage/index.md +++ b/src/connections/destinations/catalog/evergage/index.md @@ -18,7 +18,7 @@ analytics.identify('userId123', { }); ``` -A `userId` is required on all `identify` calls sent to Evergage. When you call `identify` Segment will call both `setUser` and `setUserField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `userId` and corresponding user traits into {{ integration.name}}. +A `userId` is required on all `identify` calls sent to Evergage. When you call `identify` Segment will call both `setUser` and `setUserField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `userId` and corresponding user traits into Evergage. ## Group If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: @@ -29,7 +29,7 @@ analytics.group('companyId123', { }); ``` -A `groupId` is required on all `group` calls sent to Evergage. When you call `group` Segment will call both `setCompany` and `setAccountField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `groupId` and corresponding group traits into {{ integration.name}}. +A `groupId` is required on all `group` calls sent to Evergage. When you call `group` Segment will call both `setCompany` and `setAccountField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `groupId` and corresponding group traits into Evergage. ## Track 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: From 0bc0bc6f36c009f49411ea1615d22df1e828f4be Mon Sep 17 00:00:00 2001 From: CristhianMotoche Date: Wed, 15 Oct 2025 15:11:00 -0500 Subject: [PATCH 2/2] chore: Modify to simplify migration --- src/connections/destinations/catalog/clicky/index.md | 4 ---- src/connections/destinations/catalog/clientsuccess/index.md | 2 -- src/connections/destinations/catalog/drip/index.md | 2 +- src/connections/destinations/catalog/eloqua/index.md | 2 +- 4 files changed, 2 insertions(+), 8 deletions(-) diff --git a/src/connections/destinations/catalog/clicky/index.md b/src/connections/destinations/catalog/clicky/index.md index 3fd88a575a..0587ea477e 100644 --- a/src/connections/destinations/catalog/clicky/index.md +++ b/src/connections/destinations/catalog/clicky/index.md @@ -15,8 +15,6 @@ Our Clicky destination code is open-source on GitHub. You can check out the code 3. In the destination settings, enter your Site ID in the settings. You can find your Site ID under the Preferences of your account. 4. Segment automatically initializes Clicky's script with your Site ID upon loading analytics.js. -- - - - ## Page 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 this: @@ -63,8 +61,6 @@ analytics.track("My Custom Event", { When you use our [`track`](/docs/connections/spec/track/) method, a goal is created in Clicky. Only the event name and the revenue of the event (if it exists) will be included in the call. Clicky doesn't support any other event properties. -- - - - ## Troubleshooting ### My visits aren't showing up in Clicky diff --git a/src/connections/destinations/catalog/clientsuccess/index.md b/src/connections/destinations/catalog/clientsuccess/index.md index 4844d55454..2fd4eda39f 100644 --- a/src/connections/destinations/catalog/clientsuccess/index.md +++ b/src/connections/destinations/catalog/clientsuccess/index.md @@ -17,8 +17,6 @@ To turn on the destination, do the following: **Note:** Because ClientSuccess focuses on group level events, you must pass group information before your events will show up. If you turn on the ClientSuccess destination in Segment and don't see events in ClientSuccess after 24 hours, it may be that your engineers need to send group information to Segment using Segment's `group` call. -- - - - ## Getting Started (for Developers) ClientSuccess supports the `identify`, `group`, `track`, and `page` methods of Segment. diff --git a/src/connections/destinations/catalog/drip/index.md b/src/connections/destinations/catalog/drip/index.md index 66a204d8e7..db9431d3d0 100644 --- a/src/connections/destinations/catalog/drip/index.md +++ b/src/connections/destinations/catalog/drip/index.md @@ -3,7 +3,7 @@ title: Drip Destination id: 54521fd525e721e32a72eeaa cmode-override: true --- -The Drip destination code is all open-source on GitHub if you want to check it out: [JavaScript](https://github.com/segment-integrations/analytics.js-integration-drip){:target="_blank"},(iOS and Android work using the server destination). +The Drip destination code is all open-source on GitHub if you want to check it out: [JavaScript](https://github.com/segment-integrations/analytics.js-integration-drip){:target="_blank"}, (iOS and Android work using the server destination). ## Getting Started diff --git a/src/connections/destinations/catalog/eloqua/index.md b/src/connections/destinations/catalog/eloqua/index.md index 96c94bb07f..5446b58161 100644 --- a/src/connections/destinations/catalog/eloqua/index.md +++ b/src/connections/destinations/catalog/eloqua/index.md @@ -44,7 +44,7 @@ Segment `identify` trait on the left to the Eloqua field on the right: | `title` | Title | Follow the Segment spec to ensure proper mapping of these fields from Segment -`identify` traits: /docs/connections/spec/identify/#traits. +`identify` traits: [/docs/connections/spec/identify/#traits](/docs/connections/spec/identify/#traits). In addition, Segment supports mapping custom `identify` traits to Eloqua custom object fields. To do so, you can set up mappings in the settings for your