Merge pull request #5902 from segmentio/develop

Release 24.3.2

Author: pwseg

src/_data/catalog/beta_sources.yml

@@ -21,4 +21,5 @@
 - o9OyD6xsVJ
 - ODf0vA6dcH
 - YWOGVbyMVz
-- CwGEZ7eCcA
+- CwGEZ7eCcA
+- xeZMgSrtAQ

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2024-01-16 
+# destination categories last updated 2024-01-18 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-01-16 
+# destination data last updated 2024-01-18 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -3721,6 +3721,123 @@ items:
     label: API Key
   actions: []
   presets: []
+- id: 659eb601f8f615dac18db564
+  display_name: Aggregations.io (Actions)
+  name: Aggregations.io (Actions)
+  slug: aggregations-io-actions
+  hidden: false
+  endpoints:
+  - US
+  regions:
+  - us-west-2
+  - eu-west-1
+  url: connections/destinations/catalog/aggregations-io-actions
+  previous_names:
+  - Aggregations.io (Actions)
+  website: https://aggregations.io
+  status: PUBLIC_BETA
+  categories:
+  - Raw Data
+  - Analytics
+  logo:
+    url: https://cdn-devcenter.segment.com/886284de-022d-434b-8e45-b054964c7479.svg
+  mark:
+    url: https://cdn-devcenter.segment.com/b106e36f-d5e8-4307-8174-ac3c5ad432f5.svg
+  methods:
+    track: true
+    identify: true
+    group: true
+    alias: true
+    screen: false
+    page: true
+  platforms:
+    browser: true
+    mobile: false
+    server: true
+    warehouse: false
+    cloudAppObject: false
+  components: []
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: false
+  replay: false
+  connection_modes:
+    device:
+      web: false
+      mobile: false
+      server: false
+    cloud:
+      web: true
+      mobile: false
+      server: true
+  settings:
+  - name: api_key
+    type: password
+    defaultValue: ''
+    description: Your Aggregations.io API Key. This key requires Write permissions.
+    required: true
+    label: API Key
+  - name: ingest_id
+    type: string
+    defaultValue: ''
+    description: >-
+      The ID of the ingest you want to send data to. This ingest should be set
+      up as "Array of JSON Objects". Find your ID on the Aggregations.io
+      Organization page.
+    required: true
+    label: Ingest Id
+  actions:
+  - id: ibzRWPV7jdx3UvSqhDCWob
+    name: Send Events
+    slug: send
+    description: Send events to Aggregations.io.
+    platform: CLOUD
+    hidden: false
+    defaultTrigger: null
+    fields:
+    - id: pKS6wAoVMhgMKcGRtRyKPb
+      sortOrder: 0
+      fieldKey: data
+      label: Data
+      type: OBJECT
+      description: Payload to deliver (JSON-encoded).
+      placeholder: ''
+      defaultValue:
+        '@path': $.
+      required: false
+      multiple: false
+      choices: null
+      dynamic: false
+      allowNull: false
+    - id: bQA4z2u97zSZVXX16WtZvR
+      sortOrder: 1
+      fieldKey: enable_batching
+      label: Enable Batching
+      type: BOOLEAN
+      description: Enabling sending batches of events to Aggregations.io.
+      placeholder: ''
+      defaultValue: true
+      required: true
+      multiple: false
+      choices: null
+      dynamic: false
+      allowNull: false
+    - id: rF7Z7KScxWx34TEDnRmpHa
+      sortOrder: 2
+      fieldKey: batch_size
+      label: Batch Size
+      type: NUMBER
+      description: >-
+        Maximum number of events to include in each batch. Actual batch sizes
+        may be lower. If you know your events are large, you may want to tune
+        your batch size down to meet API requirements.
+      placeholder: ''
+      defaultValue: 300
+      required: false
+      multiple: false
+      choices: null
+      dynamic: false
+      allowNull: false
+  presets: []
 - id: 5d0ac1fbc12d700001651e34
   display_name: Airship
   name: Airship

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-01-16 
+# destination data last updated 2024-01-18 
 items:
   - id: 54521fd725e721e32a72eec6
     display_name: Intercom

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2024-01-16 
+# source categories last updated 2024-01-18 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2024-01-16 
+# sources last updated 2024-01-18 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET

src/connections/destinations/catalog/actions-aggregations-io/index.md

@@ -0,0 +1,21 @@
+---
+title: Aggregations.io (Actions) Destination
+id: 659eb601f8f615dac18db564
+beta: true
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Aggregations.io](https://aggregations.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} enables you to use your existing analytics events and pipeline for real-time monitoring and alerting.
+
+This destination is maintained by Aggregations.io. For any issues with the destination, [contact their Support team](mailto:[email protected]).
+
+## Getting started
+
+1. From the Segment web app, click **Catalog**, then click **Destinations**.
+2. Find the Destinations Actions item in the left navigation, and click it.
+3. Click **Configure Aggregations.io (Actions)**.
+4. Select an existing Source to connect to Aggregations.io (Actions).
+5. In the destination settings, enter your Aggregations.io API Key and Ingest ID. Your ingestion on the Aggregations.io dashboard should be set up using `Array of JSON Objects` and the API Key requires `Write` permission.  For more information, see the [Aggregation.io docs](https://aggregations.io/docs/ingesting-data/create-an-ingest){:target="_blank"}.
+
+{% include components/actions-fields.html %}

src/connections/destinations/catalog/actions-klaviyo/index.md

@@ -1,8 +1,5 @@
 ---
 title: Klaviyo (Actions) Destination
-hide-boilerplate: true
-hide-dossier: true
-hidden: true
 id: 650bdf1a62fb34ef0a8058e1
 beta: true
 ---

src/connections/destinations/catalog/actions-listrak/index.md

@@ -42,18 +42,19 @@ To sync an Engage audience with your Listrak (Actions) destination:
 9. In the **Mappings** tab, click **New Mapping** and select **Update Email Contact Profile Fields**.
 10. Under **Select events to map and send**, select **Track** for the **Event Type**.  
 11. Click **Add Condition** and add this condition: **Event Name** is `Audience Entered`.
-12. Under **Select mappings**, enter the list ID and map the email address if `context.traits.email` is not desired.
-13. Still under **Select mappings**, in the section for mapping the `Profile Field Values`, enter the profile field ID for the `Enter Key Name` textbox on the right and `on` in the textbox for its value to the left. Click **Save**.
-14. Repeat steps 9 through 13 using `Audience Exited` instead of `Audience Entered` in step 11 and `off` instead of `on` in step 13.
-15. **Enable** both mappings.
-16. Go to the **Settings** tab for the destination and **Enable** the destination. Click **Save Changes**.
-17. Select the Engage space and navigate to **Engage > Audiences**. Select the source audience to send to the Listrak destination.
-18. Click **Add Destination** and select the Listrak Audience destination. 
-19. In the settings that appear on the right-hand side, toggle the **Send Track** option on and disable **Send Identify**.
-20. Click **Save**.
-21. To filter email sends in Listrak using the new audience profile field, see this [help article](https://help.listrak.com/en/articles/3951597-introduction-to-building-filter-2-0-segments){:target="_blank”}.
-22. If you want to sync another audience, repeat steps 1 through 20.
+12. Click **Add Condition** and add this condition: **Event Property** `audience_key` is `my_audience` (where `my_audience` is the Audience Key found on the Audience settings page).
+13. Under **Select mappings**, enter the list ID and map the email address if `context.traits.email` is not desired.
+14. Under **Select mappings**, in the section for mapping the `Profile Field Values`, enter the profile field ID for the `Enter Key Name` textbox on the right and `on` in the textbox for its value to the left. Click **Save**.
+15. Repeat steps 9 through 14 using `Audience Exited` instead of `Audience Entered` in step 11 and `off` instead of `on` in step 14.
+16. **Enable** both mappings.
+17. Go to the **Settings** tab for the destination and **Enable** the destination. Click **Save Changes**.
+18. Select the Engage space and navigate to **Engage > Audiences**. Select the source audience to send to the Listrak destination.
+19. Click **Add Destination** and select the Listrak Audience destination. 
+20. In the settings that appear on the right-hand side, toggle the **Send Track** option on and disable **Send Identify**.
+21. Click **Save**.
+22. To filter email sends in Listrak using the new audience profile field, see the [help article](https://help.listrak.com/en/articles/3951597-introduction-to-building-filter-2-0-segments){:target="_blank”}.
+23. Repeat steps 1 through 21, if you want to sync another audience.
 
 {% include components/actions-fields.html %}
 
----
+---

src/connections/destinations/catalog/actions-pendo-web/index.md

@@ -0,0 +1,40 @@
+---
+title: Pendo Web (Actions) Destination
+id: 6501a4325a8a629197cdd691
+hidden: true
+beta: true
+hide-boilerplate: true
+hide-dossier: true
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+
+[Pendo](http://www.pendo.io/){:target="_blank"} combines powerful software usage analytics with in-app guidance and user feedback capabilities, enabling even non-technical teams to deliver better product experiences to their customers or employees.
+
+> success ""
+> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Pendo Web (Actions) Segment destination. There's also a page about the [non-Actions Pendo destination](/docs/connections/destinations/catalog/pendo/). Both of these destinations receives data from Segment.
+
+## Benefits of Pendo Web (Actions) vs Pendo Classic
+
+Pendo Web (Actions) provides the following benefits over the classic Pendo destination:
+
+- **Support for Track, Identify, and Group calls**. The classic Pendo destination did not support Track calls and required users to configure an additional Webhook destination.
+- **Full region support**. Setup allows the destination to be configured for US, EU, US restricted, or Japan.
+- **Supports CNAME for Pendo**. Works with subscriptions using Pendo's custom CNAME feature.
+
+## Getting started
+
+1. From the Segment web app, click **Catalog**, then click **Destinations**.
+2. Find the Destinations Actions item in the left navigation, and click it.
+3. Click **Pendo Web (Actions)**.
+4. Click **Add destination ->**.
+5. Select an existing Source to connect to Pendo Web (Actions).
+6. In the destination settings, enter your Pendo API Key which you can find in the Pendo UI under [Site Settings](https://app.pendo.io/admin){:target="_blank"} > Basic Information > API Key.
+7. Select the correct region for your Pendo subscription.
+
+{% include components/actions-fields.html %}
+
+## Migration from the classic Pendo destination
+
+Remove the classic Pendo destination and Webhook destination from your Segment workspace before adding the Pendo Web (Actions) destination.

src/connections/destinations/catalog/aggregations-io-actions/index.md

@@ -0,0 +1,7 @@
+---
+title: 'Aggregations.io (Actions) Destination'
+hidden: true
+id: 659eb601f8f615dac18db564
+published: false
+beta: true
+---

src/connections/destinations/catalog/gleap-cloud-actions/index.md

@@ -0,0 +1,25 @@
+---
+title: Gleap (Actions) Destination
+id: 656f2474a919b7e6e4900265
+beta: true
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Gleap](https://gleap.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a customer feedback platform designed for apps and websites. It offers a suite of tools including visual bug reporting, live chat, AI customer support, public roadmaps, marketing automation, and more, aimed at enhancing customer success and product improvement.
+
+
+This destination is maintained by Gleap. For any issues with the destination, [contact their Support team](mailto:[email protected]).
+
+
+## Getting started
+
+1. From the Segment web app, click **Catalog**, then click **Destinations**.
+2. Find the Destinations Actions item in the left navigation, and click it.
+3. Click **Configure Gleap**.
+4. Select an existing Source to connect to Gleap (Actions).
+5. To use the Gleap destination, obtain an API key by signing up at [app.gleap.io](https://app.gleap.io){:target="_blank”}.
+6. Once registered, navigate to **Project > Settings > Security** in the Gleap dashboard.
+7. Copy the API key and paste it into the Segment Gleap destination settings.
+
+{% include components/actions-fields.html %}

src/connections/functions/insert-functions.md

@@ -57,7 +57,7 @@ Segment invokes a separate part of the function (called a "handler") for each ev
 The default source code template includes handlers for all event types. You don't need to implement all of them - just use the ones you need, and skip the ones you don't.
 
 > info ""
-> Removing the handler for a specific event type results in blocking the events of that type from arriving at their destination. 
+> Removing the handler for a specific event type results in blocking the events of that type from arriving at their destination. To keep an event type as is but still send it downstream, add a `return event` inside the event type handler statement.
 
 Insert functions can define handlers for each message type in the [Segment spec](/docs/connections/spec/):
 

src/connections/sources/catalog/cloud-apps/cdpresolution/index.md renamed to src/connections/sources/catalog/cloud-apps/cdp-resolution-enrichment/index.md

@@ -1,13 +1,15 @@
 ---
-title: CDP Resolution Source
+title: CDP Resolution Enrichment Source
+id: HoFsjsDOW2
+beta: true
 hidden: true
 ---
 
 [CDP Resolution](https://cdpresolution.com?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} helps customers identify their target audience for the purpose of activation, ongoing engagement, and conversion.  You can find a [list of the different attributes](https://www.cdpresolution.com/resources/UPID?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} you can collect with CDP Resolution Enrichment.
 
 This source is maintained by CDP Resolution. For any issues with the destination, [contact the CDP Resolution support team](mailto:[email protected]).
 
-How this works: A user is logged into CDP Resolution UI application.  They are performing a segmentation operation of identifying their total addressable market and enriching their Segment workspace with data from CDP Resolution.
+Here's how it works: When a user logs into the CDP Resolution UI application, they engage in a segmentation operation to identify their total addressable market. Concurrently, they enhance their Segment workspace by incorporating data sourced from CDP Resolution.
 
 ## Getting started
 
@@ -24,4 +26,6 @@ To set up your CDP Resolution Enrichment source:
 
 Further documentation can be found on the [CDP documentation site](https://docs.cdpresolution.com?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"}.
 
-If you configured your CDP Resolution Source correctly, and if you also configured CDP Resolution to send user profile data to a Segment Source, you should start to see user profile data shown in the Segment Source debugger as Identify and Group calls.
+## Events 
+
+If you've correctly set up your CDP Resolution Source and configured CDP Resolution to transmit user profile data to a Segment source, user profile data will begin to populate in the Segment Source debugger as Identify and Group calls.

src/connections/sources/catalog/libraries/website/javascript/index.md

@@ -903,20 +903,23 @@ For more information, visit the [Segment localstorage-retry library](https://git
 
 You can set the `debug` cookie to `analytics.js` to log debug messages from Analytics.js to the console.
 
-## Ad Blocking
-Segment doesn't endorse bypassing ad blockers for client-side tracking. Your users have control as to what gets loaded on the page, because they can add a plugin to block third party scripts from loading, which includes Segment. As you can expect some data loss in client-side tracking, there are three routes Segment recommends you to choose from:
+## Tracking Blockers and Browser Privacy Settings
 
-1. Honor the decision of the user to implement the ad blocker knowing that unfortunately, some data will be lost.
-2. Ask the customer to remove the ad blocker (for example, in the case of large, corporate customers).
-3. Move as many events and tracking over to a server-side library as possible, which won't run into the same limitations.
+Segment does not endorse bypassing tracking blockers or browser privacy settings for client-side tracking. Your users have control over what gets loaded on their pages and can use plugins or browser settings to block third-party scripts, including Segment. To minimize client-side data loss, Segment recommends you choose from the following routes:
 
-If the above routes don't work, Segment provides these workarounds to help with tracking and to mitigate data loss:
+1. Respect the user's decision to implement tracking blockers or use privacy settings, knowing that, unfortunately, some data will be lost.
+2. Ask the customer to disable the tracking blockers or adjust their privacy settings (for example, in the case of large, corporate customers).
+3. Move as many events and tracking actions as possible to a server-side library, which won't encounter the same limitations.
+
+To minimize client-side data loss, Segment provides a few workarounds. However, it's important to note that Segment cannot guarantee their effectiveness.
 
 * Use the [bundle obfuscation](#bundle-obfuscation) feature. You can add an obfuscate property to the object in the second parameter, which obscures the URL from which your integrations and destination actions are loaded. This helps prevent words that are flagged by ad blockers to not be detected in your URL, enabling the integration to properly load.
 
-* Create a [custom proxy](/docs/connections/sources/catalog/libraries/website/javascript/custom-proxy/). This changes the URL that Segment loads from (cdn.segment.com), as well as the outgoing requests generated when events are triggered (api.segment.io). By setting up proxies for these URLs, some ad blockers won't prevent Segment from loading, which means your events send downstream to your destinations. 
+* Create a [custom proxy](/docs/connections/sources/catalog/libraries/website/javascript/custom-proxy/). This changes the URL that Segment loads from (cdn.segment.com) and the outgoing requests generated when events are triggered (api.segment.io).
+
+* Consider implementing the [Segment Edge SDK](https://segment.com/blog/twilio-segment-edge-sdk/){:target="_blank”}. The Segment Edge SDK leverages Cloudflare Workers to facilitate first-party data collection and real-time user profiling for app personalization. It integrates Segment's library into web apps, manages user identity via HttpOnly cookies, and employs an internal router for efficient data processing and user experience customization. This innovative approach simplifies tracking and personalization for Segment customers. More information is available in the [Edge SDK README](https://github.com/segmentio/analytics-edge/blob/main/packages/edge-sdk/README.md){:target="_blank”}.
 
-* Consider tracking data using one of Segment's [server-side libraries](/docs/connections/sources/#server). By using a server-side library, you no longer have to worry about ad blockers and privacy browsers preventing Segment from loading. This option may require more code to track something like a `.page()` call, since now you have to manually pass contextual information that otherwise would've been collected automatically by Analytics.js, such as `url`, `path`, `referrer`. Note that some destinations are device-mode only.
+* Consider using one of Segment’s [server-side libraries](/docs/connections/sources/#server). Using a server-side library eliminates concerns about tracking blockers and privacy browsers that can prevent Segment from loading. This option may require additional code to track actions like a Page call, as you now need to manually pass contextual information that would have been automatically collected by Analytics.js, like `url`, `path`, and `referrer`. Note that some destinations are device-mode only.
 
 ## Add destinations from npm