From 2ba7c83dcb39271110f796ea61338023c85c1963 Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Tue, 14 Oct 2025 17:25:49 -0500 Subject: [PATCH 1/7] Fixes for batch 7.4 --- .../catalog/freshsales-suite-crm/index.md | 17 ++++---- .../destinations/catalog/ibm-ubx/index.md | 2 +- .../sources/catalog/cloud-apps/vero/index.md | 40 +++++++++---------- src/connections/spec/ecommerce/index.md | 2 +- 4 files changed, 31 insertions(+), 30 deletions(-) diff --git a/src/connections/destinations/catalog/freshsales-suite-crm/index.md b/src/connections/destinations/catalog/freshsales-suite-crm/index.md index 3d8916680b..a85e2a463a 100644 --- a/src/connections/destinations/catalog/freshsales-suite-crm/index.md +++ b/src/connections/destinations/catalog/freshsales-suite-crm/index.md @@ -36,7 +36,7 @@ You can use identify to create a contact when a website visitor fills a webform. userId is a mandatory field which is used to identify the contact in Freshsales. If your user identifier is not email, then email has to be a part of traits. -```json= +```json { "userId": "97980cfea0067", "type": "identify", @@ -78,7 +78,7 @@ Custom fields won't automatically create. You have to create them in Freshsales You can also update Accounts and Deals associated with a contact in Freshsales. The company and deal objects in the identify payload correspond to the Accounts and Deals objects in Freshsales. When you use the identify method to create a contact, it's possible to also create the corresponding Account and Deal and Freshsales. To do this, pass the company or the deal objects within traits in the identify call. -```json= +```json { "userId" : "97980cfea0067", "type": "identify", @@ -101,7 +101,7 @@ You can also update Accounts and Deals associated with a contact in Freshsales. You can track activities of your website visitors. If a user is subscribing to a newsletter and you want to track it, use the track method. -```json= +```json { "userId" : "john.doe@example.com", "event": "Email Bounced", @@ -121,15 +121,16 @@ Segment standardized a series of reserved event names that have special semantic If you want to track users visiting your sites, you can use the page method. When you call a page event, Segment sends a pageview to Freshsales. You can send extra data parameters within properties in the event payload. [See the reserved properties for more details](/docs/connections/spec/page/#properties). -```json= +```json { - "userId" : "john.doe@example.com", + "userId": "john.doe@example.com", "name": "Page view", - “type”: ”page”, - "properties" : { + "type": "page", + "properties": { "title": "Welcome to pricing page | Example.com", - "url" : "http://example.com/pricing" + "url": "http://example.com/pricing" } +} ``` ## FAQs diff --git a/src/connections/destinations/catalog/ibm-ubx/index.md b/src/connections/destinations/catalog/ibm-ubx/index.md index f0c1608f6b..791511b767 100644 --- a/src/connections/destinations/catalog/ibm-ubx/index.md +++ b/src/connections/destinations/catalog/ibm-ubx/index.md @@ -82,7 +82,7 @@ mappings may apply: `name` `siteID` - + _**Note:** As with `track` events, all properties sent by the user that aren't diff --git a/src/connections/sources/catalog/cloud-apps/vero/index.md b/src/connections/sources/catalog/cloud-apps/vero/index.md index c87d01f364..5a7ffe74ca 100644 --- a/src/connections/sources/catalog/cloud-apps/vero/index.md +++ b/src/connections/sources/catalog/cloud-apps/vero/index.md @@ -63,26 +63,26 @@ Collections are the groupings of data we pull from your Source. In your warehous Event Recipient has opened the HTML message. You need to enable Open Tracking for getting this type of event - - Email Link Clicked - Event - Recipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event - - - Email Unsubscribed - Event - Recipient clicked on message's subscription management link - - - Email Bounced - Event - Receiving server could not or would not accept message - - - Email Marked as Spam - Event - Recipient marked message as spam - + + Email Link Clicked + Event + Recipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event + + + Email Unsubscribed + Event + Recipient clicked on message's subscription management link + + + Email Bounced + Event + Receiving server could not or would not accept message + + + Email Marked as Spam + Event + Recipient marked message as spam + -- - - ## Identify diff --git a/src/connections/destinations/catalog/keen/index.md b/src/connections/destinations/catalog/keen/index.md index 57b9507edc..b0b9e97d3e 100644 --- a/src/connections/destinations/catalog/keen/index.md +++ b/src/connections/destinations/catalog/keen/index.md @@ -9,7 +9,6 @@ When you enable Keen in the Segment web app, your changes appear in the Segment Keen is supported on the client side and server side. -- - - ## Identify diff --git a/src/connections/destinations/catalog/librato/index.md b/src/connections/destinations/catalog/librato/index.md index 0c10df41a1..940024517e 100644 --- a/src/connections/destinations/catalog/librato/index.md +++ b/src/connections/destinations/catalog/librato/index.md @@ -9,7 +9,6 @@ When you enable Librato in the Segment web app, your changes appear in the Segme Librato supports the Segment `track` method for both client-side and server-side. -- - - ## Track diff --git a/src/connections/destinations/catalog/livechat/index.md b/src/connections/destinations/catalog/livechat/index.md index 748df4af30..97db17014a 100644 --- a/src/connections/destinations/catalog/livechat/index.md +++ b/src/connections/destinations/catalog/livechat/index.md @@ -9,7 +9,6 @@ When you enable LiveChat in the Segment web app, your changes appear in the Segm LiveChat is only supported on the client-side. -- - - ## Identify diff --git a/src/connections/destinations/catalog/localytics/index.md b/src/connections/destinations/catalog/localytics/index.md index b47fd6e190..04901b71e8 100644 --- a/src/connections/destinations/catalog/localytics/index.md +++ b/src/connections/destinations/catalog/localytics/index.md @@ -43,7 +43,6 @@ Whenever you call [`track`](/docs/connections/spec/track/), we'll log an event w Localytics. [`track`](/docs/connections/spec/track/) takes the name of the event and any optional properties you want to associate with the event. -- - - ## Push Notifications diff --git a/src/connections/destinations/catalog/marketo/index.md b/src/connections/destinations/catalog/marketo/index.md index 0012bc552e..5771c4461a 100644 --- a/src/connections/destinations/catalog/marketo/index.md +++ b/src/connections/destinations/catalog/marketo/index.md @@ -11,7 +11,6 @@ When you enable Marketo in the Segment web app, your changes appear in the Segme ### Important Note: Our client-side and server-side destinations each require **different** credentials for authentication. Read through the information below on `identify` calls for further information. -- - - ## Page and Track diff --git a/src/connections/destinations/catalog/mixpanel/index.md b/src/connections/destinations/catalog/mixpanel/index.md index 05fe21e16c..2ec9b89a3b 100644 --- a/src/connections/destinations/catalog/mixpanel/index.md +++ b/src/connections/destinations/catalog/mixpanel/index.md @@ -337,7 +337,6 @@ analytics.track({ Segment doesn't map `$library_version` since that is reserved for Mixpanel's library version, not Segment's. Segment doesn't map to `$brand`. -- - - ## Features diff --git a/src/connections/destinations/catalog/olark/index.md b/src/connections/destinations/catalog/olark/index.md index 0fa22b794a..cdc9587194 100644 --- a/src/connections/destinations/catalog/olark/index.md +++ b/src/connections/destinations/catalog/olark/index.md @@ -9,7 +9,6 @@ When you enable Olark in the Segment web app, your changes appear in the Segment Olark is only supported in device mode (on the client). -- - - ## Page @@ -32,7 +31,6 @@ More documentation on the Olark API can be found [in Olark's docs](https://www.o When you call [`track`](/docs/connections/spec/track/) or one of its helpers on analytics.js, we call Olark's `sendNotificationToOperator` function as `visitor triggered *eventName*`. You must enable this option with the *track* flag, because it can sometimes be bothersome. -- - - ## Features @@ -52,7 +50,6 @@ analytics.ready(function(){ [Read the ready docs for more details](/docs/connections/sources/catalog/libraries/website/javascript/#ready) -- - - ## Record Live Chat Events diff --git a/src/connections/destinations/catalog/onesignal/index.md b/src/connections/destinations/catalog/onesignal/index.md index 0dff3e8658..d1b084568f 100644 --- a/src/connections/destinations/catalog/onesignal/index.md +++ b/src/connections/destinations/catalog/onesignal/index.md @@ -11,7 +11,6 @@ OneSignal will only track new users. If you have existing push notification data OneSignal supports the `identify` and `track` methods and is currently only available on iOS using Segment. -- - - ## Identify & Track diff --git a/src/connections/destinations/catalog/planhat/index.md b/src/connections/destinations/catalog/planhat/index.md index 15f4744cb9..6bb2324655 100644 --- a/src/connections/destinations/catalog/planhat/index.md +++ b/src/connections/destinations/catalog/planhat/index.md @@ -12,7 +12,6 @@ The Segment Planhat destination is 100% handled through our servers, so you don' The Segment Planhat destination supports Identify, Page, Track, and Group calls. For more information, see the [Segment Spec documentation](/docs/connections/spec/). -- - - ## Identify diff --git a/src/connections/destinations/catalog/preact/index.md b/src/connections/destinations/catalog/preact/index.md index 42e22ca178..d14b58d3eb 100644 --- a/src/connections/destinations/catalog/preact/index.md +++ b/src/connections/destinations/catalog/preact/index.md @@ -17,7 +17,6 @@ To group users into accounts in preact you'll use our [`group`](/docs/connection Our [`track`](/docs/connections/spec/track) method will record events in Preact. Users must be identified on the client side for events to appear in Preact. -- - - ## Features diff --git a/src/connections/destinations/catalog/sailthru/index.md b/src/connections/destinations/catalog/sailthru/index.md index 717c8b0629..32500155f2 100644 --- a/src/connections/destinations/catalog/sailthru/index.md +++ b/src/connections/destinations/catalog/sailthru/index.md @@ -18,7 +18,6 @@ The Sailthru server-side destination will allow you to add users, send custom ev - The template passed through as `reminder_template` must match the public name configured in Sailthru's UI. - We recommend appending `traits.email` whenever possible in your `identify` calls. If you send an `identify` call without a `traits.email` and only a `userId`, the profile will be created in Sailthru but you would not be able to find that user using their **User Look Up** feature. -- - - ### Page You must configure a `customerId` in your integration settings in order to use the `page` functionality. This value is only required for `page` calls and can be found in your Sailthru Dashboard under **App Settings** @@ -41,7 +40,6 @@ analytics.page('Page Name', { See our [documentation](/docs/connections/spec/page/#properties) for more info on the `keywords` property. -- - - ### Identify From 2c24d3b8a1101664e8aa58d6ba01744fb3a90494 Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Wed, 15 Oct 2025 15:03:09 -0500 Subject: [PATCH 3/7] Fixes --- .../destinations/catalog/hotjar/index.md | 29 ++++++++++--------- .../destinations/catalog/hydra/index.md | 4 +-- .../catalog/cloud-apps/marketo/index.md | 8 ++--- 3 files changed, 21 insertions(+), 20 deletions(-) diff --git a/src/connections/destinations/catalog/hotjar/index.md b/src/connections/destinations/catalog/hotjar/index.md index a2698cbc26..35374deb7d 100644 --- a/src/connections/destinations/catalog/hotjar/index.md +++ b/src/connections/destinations/catalog/hotjar/index.md @@ -34,19 +34,20 @@ Identify calls that do not have a User ID value will not be sent to Hotjar. Currently, the Hotjar Identify API **does not** support ingesting values passed as nested objects or lists over your identify Spec: -```js +```json "traits": { - "name": "Peter Gibbons", - "email": "peter@example.com", - "plan": "premium", - "logins": 5, - "address": { - "street": "6th St", - "city": "San Francisco", - "state": "CA", - "postalCode": "94103", - "country": "USA" - } + "name": "Peter Gibbons", + "email": "peter@example.com", + "plan": "premium", + "logins": 5, + "address": { + "street": "6th St", + "city": "San Francisco", + "state": "CA", + "postalCode": "94103", + "country": "USA" + } +} ``` In the example above, Hotjar rejects all the values in the `address` field. @@ -62,8 +63,8 @@ Currently, the Hotjar Events API **does not** support ingesting event properties ```js analytics.track("Experiment Viewed", { experiment_id: "1234", - experiment_name: "new_upsell_UX" - variation_id: "1234b" + experiment_name: "new_upsell_UX", + variation_id: "1234b", variation_name: "variant" }); ``` diff --git a/src/connections/destinations/catalog/hydra/index.md b/src/connections/destinations/catalog/hydra/index.md index 655adfdf82..38df66ad93 100644 --- a/src/connections/destinations/catalog/hydra/index.md +++ b/src/connections/destinations/catalog/hydra/index.md @@ -23,7 +23,7 @@ If you would like to use `track` event data, create a `Segment Product Usage Sca 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: -``` +```js analytics.identify('userId123', { email: 'john.doe@example.com', firstName: 'John', @@ -45,7 +45,7 @@ Identify calls will be sent to Hydra as an `identify` event. Upon receiving an I 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: -``` +```js analytics.track('Device deploy started', "properties": { "feature": "Device management", diff --git a/src/connections/sources/catalog/cloud-apps/marketo/index.md b/src/connections/sources/catalog/cloud-apps/marketo/index.md index 547770af8f..17a83e9485 100644 --- a/src/connections/sources/catalog/cloud-apps/marketo/index.md +++ b/src/connections/sources/catalog/cloud-apps/marketo/index.md @@ -36,10 +36,10 @@ You will need Admin permissions to your Marketo account. 2. Go to **Admin > Munchkin** to find your Munchkin Account ID. ![Screenshot of the Tracking Code section of Marketo's Munchkin page.](images/Image2018-04-30at5.28.54PM.png) 3. Go to Admin > LaunchPoint - 1. If you don't already have a REST service setup, follow [these steps](http://developers.marketo.com/rest-api/custom-services/){:target="_blank"}. - 2. Then, copy the "Client ID" and "Client Secret" parameters. - ![Screenshot of the Details section of the LaunchPoint page.](images/Image2018-04-30at5.29.32PM.png) - 3. Paste the "Client ID" and "Client Secret" into the Segment Marketo source settings. + 1. If you don't already have a REST service setup, follow [these steps](http://developers.marketo.com/rest-api/custom-services/){:target="_blank"}. + 2. Then, copy the "Client ID" and "Client Secret" parameters. + ![Screenshot of the Details section of the LaunchPoint page.](images/Image2018-04-30at5.29.32PM.png) + 3. Paste the "Client ID" and "Client Secret" into the Segment Marketo source settings. Data should start flowing into your warehouse in the next few hours. From 6f12ad8fdfcd4770dd0237ae4d2bfcc373eec347 Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Wed, 15 Oct 2025 15:49:59 -0500 Subject: [PATCH 4/7] fix header --- src/connections/destinations/catalog/hawkei/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/hawkei/index.md b/src/connections/destinations/catalog/hawkei/index.md index 246e1bbe1c..b98c509eee 100644 --- a/src/connections/destinations/catalog/hawkei/index.md +++ b/src/connections/destinations/catalog/hawkei/index.md @@ -70,6 +70,6 @@ You'll want to create events that are part of critical paths in your application ## Troubleshooting -## AnonymousId +### AnonymousId All requests to Hawkei require an `anonymousId` to be set. Segment sets this automatically on client-side libraries, but for server side libraries (php, Ruby etc) this needs to be explicitly set. From 6c624e093746662d55c492fe083ba42a64afb513 Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Wed, 15 Oct 2025 16:35:47 -0500 Subject: [PATCH 5/7] Fixes --- src/connections/destinations/catalog/google-ads-gtag/index.md | 4 ++-- src/connections/destinations/catalog/gtag/index.md | 4 ++++ 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/google-ads-gtag/index.md b/src/connections/destinations/catalog/google-ads-gtag/index.md index 3ce0ef820d..f2f4780e80 100644 --- a/src/connections/destinations/catalog/google-ads-gtag/index.md +++ b/src/connections/destinations/catalog/google-ads-gtag/index.md @@ -47,7 +47,7 @@ To enable consent mode for your Google Ads (Gtag) destination, you can choose fr * **Option 1:** 1. Set the consent defaults by implementing the `ready()` method to set consent defaults. - ``` + ```js analytics.ready(function() { window.gtag('consent', 'default', { 'ad_storage': 'granted', @@ -62,7 +62,7 @@ To enable consent mode for your Google Ads (Gtag) destination, you can choose fr 3. Pass the information to Gtag.js by calling `gtag` inside the Segment `ready`() method. - ``` + ```js analytics.ready(function() { window.gtag('consent', 'update', { 'ad_storage': 'denied', diff --git a/src/connections/destinations/catalog/gtag/index.md b/src/connections/destinations/catalog/gtag/index.md index dcc0ff705f..e66fa2c11f 100644 --- a/src/connections/destinations/catalog/gtag/index.md +++ b/src/connections/destinations/catalog/gtag/index.md @@ -130,6 +130,8 @@ analytics.track('Logged In'); Segment sends these event attributes to Google Analytics: +| Event Attributes | Info | +| ------------------ | --------- | | **Event Category** | All | | **Event Action** | Logged In | @@ -150,6 +152,8 @@ In this example, Segment sends all Google Analytics event parameters: Segment sends these event attributes to Google Analytics: +| Event Attributes | Info | +| ------------------ | --------- | | **Event Category** | Account | | **Event Action** | Logged In | | **Event Label** | Premium | From bf9e50d79a142c6a981ed0ba023bc482434797ff Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Wed, 15 Oct 2025 19:41:24 -0500 Subject: [PATCH 6/7] Add languages in codefence --- .../destinations/catalog/freshsales/index.md | 14 +++++++------- .../destinations/catalog/fullstory/index.md | 6 +++--- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/src/connections/destinations/catalog/freshsales/index.md b/src/connections/destinations/catalog/freshsales/index.md index b2477e6372..b85d5e8947 100644 --- a/src/connections/destinations/catalog/freshsales/index.md +++ b/src/connections/destinations/catalog/freshsales/index.md @@ -19,7 +19,7 @@ You can use `identify` to create a lead or a contact when a website visitor fill ### User ID `userId` is a mandatory field which is used to identify the lead or contact in Freshsales. If your user identifier is not email, then email has to be a part of traits. -
+```json
 {
   "userId": "97980cfea0067",
   "traits": {
@@ -32,11 +32,11 @@ You can use `identify` to create a lead or a contact when a website visitor fill
     }
   }
 }
-
+``` By default, every `identity` is created as a lead. If you'd like an identity to be a contact, you'd need to pass `fs_contact` as `true` as a part of traits. -
+```json
 {
   "userId" : "97980cfea0067",
   "traits" : {
@@ -50,7 +50,7 @@ By default, every `identity` is created as a lead. If you'd like an identity to
     }
   }
 }
-
+``` ### Traits `traits` are pieces of information you know about a user that are included in an `identify` method. @@ -72,7 +72,7 @@ As part of traits, you can send custom fields created in Freshsales by using the ### Objects: Accounts and Deals associated to a contact or lead can also be updated in Freshsales. The objects company and deal in the identity correspond to the Accounts and Deals in Freshsales. You can pass the `traits` of the company or the deal along with the respective objects in the identity. -``` +```json { "userId" : "97980cfea0067", "traits" : { @@ -98,7 +98,7 @@ You can track activities of your website visitors. If a user is subscribing to a ### Track request payload -``` +```json { "userId" : "john.doe@example.com", "event": "Email Bounced", @@ -120,7 +120,7 @@ When you call a `page` event, we send a pageview to Freshsales. You can send ext ### Sample Page request payload -``` +```json { "userId" : "john.doe@example.com", "name": "Page view", diff --git a/src/connections/destinations/catalog/fullstory/index.md b/src/connections/destinations/catalog/fullstory/index.md index ff78b4c9b4..1e248fd05d 100644 --- a/src/connections/destinations/catalog/fullstory/index.md +++ b/src/connections/destinations/catalog/fullstory/index.md @@ -39,7 +39,7 @@ analytics.identify("userId"); In addition, Segment will send over along any traits included in the `identify` call. The example call below would send over both `plan` and `logins`. -``` +```js analytics.identify("userId123", { plan: "premium", logins: 5 @@ -50,7 +50,7 @@ analytics.identify("userId123", { Both `email` and `displayName` are special traits that will be passed to FullStory to be used in their interface as explained in [FullStory's docs](https://help.fullstory.com/hc/en-us/articles/360020828113){:target="_blank"}. These traits are optional. -``` +```js analytics.identify("userId123", { email: "john.doe@example.com", displayName: "John Doe" @@ -63,7 +63,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th An example call would look like: -``` +```js analytics.track('Product Purchased', { order_ID: '2969302398', category: 'boots', From ff7e6f66c9350d6c0b44a7f99fe4ab150f02c8b9 Mon Sep 17 00:00:00 2001 From: Carolina Lopez Date: Thu, 16 Oct 2025 00:10:59 -0500 Subject: [PATCH 7/7] Remove backquotes, not allowed in callouts title --- src/connections/destinations/catalog/firebase/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/firebase/index.md b/src/connections/destinations/catalog/firebase/index.md index 0d0c6f5f73..8d7c6e4731 100644 --- a/src/connections/destinations/catalog/firebase/index.md +++ b/src/connections/destinations/catalog/firebase/index.md @@ -44,7 +44,7 @@ buildscript { apply plugin: 'com.google.gms.google-services' ``` -> warning "Use the `aar` package when adding the Segment-Firebase SDK" +> warning "Use the aar package when adding the Segment-Firebase SDK" > The Firebase SDK requires Android resources which are available on `aar` packages.