Merge pull request #6512 from segmentio/develop

Release 24.19.1

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2024-05-02 
+# destination categories last updated 2024-05-07 
 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-05-02 
+# destination data last updated 2024-05-07 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -3280,6 +3280,18 @@ items:
       This is currently in Beta Testing and not generally available. 
     required: false
     label: 'Merchandising Events '
+  - name: oAuthClientId
+    type: string
+    defaultValue: ''
+    description: Client ID for your OAuth Server-to-Server Credential
+    required: false
+    label: OAuth Client ID
+  - name: oAuthClientSecret
+    type: password
+    defaultValue: ''
+    description: Client Secret for your OAuth Server-to-Server Credential
+    required: false
+    label: OAuth Client Secret
   - name: pageNameFallbackToScreen
     type: boolean
     defaultValue: false
@@ -27371,6 +27383,64 @@ items:
   actions: []
   presets: []
   partnerOwned: false
+- id: 662d3328d029f89724a0c294
+  display_name: events.win
+  name: events.win
+  slug: events-win
+  hidden: false
+  endpoints:
+  - US
+  regions:
+  - us-west-2
+  - eu-west-1
+  url: connections/destinations/catalog/events-win
+  previous_names:
+  - events.win
+  website: http://www.events.win
+  status: PUBLIC_BETA
+  categories:
+  - Analytics
+  - Customer Success
+  logo:
+    url: https://cdn-devcenter.segment.com/79396f25-00b5-4364-8f84-3461e63880ca.svg
+  mark:
+    url: https://cdn-devcenter.segment.com/c2a3d938-1db7-4b72-a9d0-8af638830182.svg
+  methods:
+    track: false
+    identify: false
+    group: false
+    alias: false
+    screen: false
+    page: false
+  platforms:
+    browser: true
+    mobile: true
+    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: true
+      server: true
+  settings:
+  - name: apiKey
+    type: string
+    defaultValue: ''
+    description: Your events.win developer key
+    required: true
+    label: Developer Key
+  actions: []
+  presets: []
+  partnerOwned: true
 - id: 5fdce712dc1fbc625ebd13b8
   display_name: Everflow
   name: Everflow
@@ -62021,7 +62091,7 @@ items:
   previous_names:
   - Listrak (Actions)
   website: https://www.listrak.com/
-  status: PUBLIC_BETA
+  status: PUBLIC
   categories:
   - Marketing Automation
   - Email Marketing
@@ -81825,8 +81895,6 @@ items:
   categories:
   - CRM
   - Analytics
-  - Marketing Automation
-  - Personalization
   logo:
     url: https://cdn.filepicker.io/api/file/Gs7h3XjXTAW94s1zQbNJ
   mark:

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-05-02 
+# destination data last updated 2024-05-07 
 items:
   - id: 54521fd925e721e32a72eee1
     display_name: Pardot

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2024-05-02 
+# source categories last updated 2024-05-07 
 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-05-02 
+# sources last updated 2024-05-07 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
@@ -1776,14 +1776,16 @@ items:
     description: >-
       When you enter your Salesforce credentials and hit save, we will sync
       Salesforce standard objects (and their corresponding properties) to any
-      databases you have turned on. 
+      databases you have turned on. Salesforce data will reflect the state of
+      the object at the time of the sync. We will run an update every ~3 hours.
+      | Sync Salesforce standard objects and their corresponding properties to
+      any of your databases every ~ 3 hours.
 
+      Salesforce data reflects the state of the obiect at the time of the svnc.
 
-      Salesforce data will reflect the state of the object at the time of the
-      sync.
-
-
-      We will run an update every ~3 hours.
+      To create and update Profiles with Salesforce data, use the Segment
+      Profiles destination. This destination lets you send your Salesforce data
+      to Segment as Identify calls.
     logo:
       url: https://d3hotuclm6if1r.cloudfront.net/logos/salesforce-default.svg
     categories:

src/_data/sidenav/main.yml

@@ -515,6 +515,8 @@ sections:
       title: Configure Consent Management
     - path: /privacy/consent-management/consent-in-unify/
       title: Consent in Unify
+    - path: /privacy/consent-management/consent-faq/
+      title: Consent FAQs
   - path: /privacy/account-deletion
     title: Account & Data Deletion
   - path: /privacy/hipaa-eligible-segment

src/connections/destinations/actions.md

@@ -181,7 +181,7 @@ If necessary, click **New Mapping** to create a new, blank action.
 4. Set up the data mapping from the Segment format to the destination tool format.
 - You can click the Source field, then select the **Enrichments** tab to view and select Enrichments to use.
 5. Test the mapping with data from a sample event.
-    The edit panel shows you the mapping output in the format for the destination tool. You can change your mapping as needed and re-test.
+    The edit panel shows you the mapping output in the format for the destination tool. The **Select Object** option sends the entire object from the event, while the **Edit Object** option lets you map each individual property. You can change your mapping as needed and re-test.
 6. When you're satisfied with the mapping, click **Save**. Segment returns you to the Mappings table.
 7. In the Mappings table **Status** column, verify that the **Enabled** toggle is on for the mapping you just customized.
 

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

@@ -0,0 +1,38 @@
+---
+title: ChartMogul (Actions) Destination
+id: 65f9888628c310646331738a
+beta: true
+hidden: true
+private: true
+---
+
+
+{% include content/plan-grid.md name="actions" %}
+
+[ChartMogul](https://chartmogul.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} is a subscription analytics platform and CRM used by thousands of businesses to measure, understand, and grow their recurring revenue businesses.
+
+This destination is maintained by ChartMogul. For any issues with the destination, [contact their Support team](https://help.chartmogul.com/hc/en-us/requests/new){:target="_blank"}.
+
+## Getting started
+
+1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"} search for "ChartMogul".
+2. Select ChartMogul and click **Add Destination**.
+3. Select an existing Source to connect to ChartMogul (Actions).
+4. [Create a source](https://app.chartmogul.com/#/data-platform/sources/add-source){:target="_blank"} in ChartMogul.
+5. Make sure the **Account / Contact / Enrichment data** tab is selected and click **Twilio Segment**.
+6. Enter the **Name** for your source.
+7. Under **Create a company in ChartMogul when** select:
+   - **the email or UserID is created** — if you recognize any individual who interacts with your organization as a lead and want to create a [customer record](https://help.chartmogul.com/hc/en-us/articles/214085765){:target="_blank"} for them
+   - **user is added to a company** — if you recognize an individual who interacts with your organization as a lead only if they're part of an organization
+8. Copy the **Webhook URL**.
+9. Click **SAVE AND CONTINUE CONFIGURATION IN SEGMENT**.
+10. Paste the **Webhook URL** in the ChartMogul destination settings in Segment.
+
+{% include components/actions-fields.html %}
+
+## Supported event calls
+ChartMogul (Actions) accepts two types of event calls:
+- [Track](https://segment.com/docs/connections/spec/track/){:target="_blank"} — used for contact details and custom attributes
+- [Group](https://segment.com/docs/connections/spec/group/){:target="_blank"} — used for customer details and custom attributes
+
+ChartMogul uses attributes from these calls to create new or update existing [custom attributes](https://help.chartmogul.com/hc/en-us/articles/206120219){:target="_blank"} for contacts or customers, or to update customers' select [standard attributes](https://help.chartmogul.com/hc/en-us/articles/5321255006364#standard-attributes){:target="_blank"}.

src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md

@@ -127,3 +127,6 @@ This error indicates that the conversion action specified in the upload request
 
 To resolve this, ensure that the ConversionActionType value in Google Ads is correctly configured.
 
+### `The required field was not present., at conversions[0].gclid` Error
+
+Events going to Google for this integration require a `GCLID` field, an `email`, or a `phone_number`. If one of those identifiers isn't being sent properly, then you may see the `The required field was not present., at conversions[0].gclid` error. To fix this, please double check that at least one of those fields is being passed to Google on each payload.

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

@@ -10,10 +10,6 @@ id: 652ea51a327a62b351aa12c0
 
 This destination is maintained by Kameleoon. For any issues with the destination, [contact the Kameleoon Support team](mailto:[email protected]).
 
-> success ""
-> This page is about the [Actions-framework](/docs/connections/destinations/actions/) Kameleoon Segment destination. There's also a page about the [non-Actions Kameleoon destination](/docs/connections/destinations/catalog/kameleoon/). Both of these destinations receive data from Segment.
-
-
 ## Benefits of Kameleoon (Actions) vs Kameleoon Classic
 
 Kameleoon (Actions) provides the following benefits over the classic Kameleoon destination:

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

@@ -4,7 +4,6 @@ id: 650bdf1a62fb34ef0a8058e1
 beta: true
 ---
 
-
 {% include content/plan-grid.md name="actions" %}
 
 [Klaviyo](https://www.klaviyo.com){:target="_blank"} is a powerful email platform focused on ecommerce that helps companies make more money. It supports segmentation based on category and event triggers like product bought, page viewed, email engagement, or amount spent.
@@ -21,61 +20,66 @@ Klaviyo (Actions) provides the following benefits:
 - **More control** - Actions-based destinations enable you to define the mapping between the data Segment receives from your sources, and the data Segment sends to Klaviyo.
 - **Default property mappings** - Default mappings from the Segment like event, timestamp, and more, allow data to be mapped correctly without any setup required.
 
-
 ## Getting started
 
 1. From the Segment web app, click **Catalog**.
-2. Search for *Klaviyo (Actions)* in the Catalog, select it, and choose which of your sources to connect the destination to.
+2. Search for **Klaviyo (Actions)** in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. Navigate to [Account > Settings > API Keys](https://www.klaviyo.com/account#api-keys-tab){:target="_blank"} in Klaviyo's UI and copy your API Key into the Segment Settings UI.
 
 > info ""
-> Klaviyo requires the Private API Key to use the List API. You can find this by going to Klaviyo's UI and clicking [Account > Settings > API Keys > Create API Key](https://www.klaviyo.com/account#api-keys-tab){:target="_blank"}  to generate a Private API Key and copy it into the Segment Settings UI.
-
+> Klaviyo requires the Private API Key to use the List API. You can find this by going to Klaviyo's UI and clicking [Account > Settings > API Keys > Create API Key](https://www.klaviyo.com/account#api-keys-tab){:target="_blank"} to generate a Private API Key and copy it into the Segment Settings UI.
 
 {% include components/actions-fields.html %}
 
-## Using Klaviyo with RETL 
+## Using Klaviyo with RETL
 
-Klaviyo (Actions) Destination can accept [RETL](/docs/connections/reverse-etl/) data. You can send the models you created in your data warehouse source. Follow [the steps](/docs/connections/reverse-etl/#step-1-add-a-source) to create your data warehouse source and set up models. 
+Klaviyo (Actions) Destination can accept [RETL](/docs/connections/reverse-etl/) data. You can send the models you created in your data warehouse source. Follow [the steps](/docs/connections/reverse-etl/#step-1-add-a-source) to create your data warehouse source and set up models.
 
+| Action              | Added                                                   | Updated                                                   | Deleted                                                        |
+| ------------------- | ------------------------------------------------------- | --------------------------------------------------------- | -------------------------------------------------------------- |
+| Order Completed     | <img class="inline" src="/docs/images/supported.svg" /> | <img class="inline" src="/docs/images/unsupported.svg" /> | <img class="inline" src="/docs/images/unsupported.svg" />      |
+| Track Event         | <img class="inline" src="/docs/images/supported.svg" /> | <img class="inline" src="/docs/images/unsupported.svg" /> | <img class="inline" src="/docs/images/unsupported.svg" />      |
+| Upsert Profile      | <img class="inline" src="/docs/images/supported.svg" /> | <img class="inline" src="/docs/images/supported.svg" />   | <img class="inline" src="/docs/images/unsupported.svg" />      |
+| Remove Profile      | <img class="inline" src="/docs/images/supported.svg" /> | <img class="inline" src="/docs/images/unsupported.svg" /> | <img class="inline" src="/docs/images/supported.svg" />        |
+| Subscribe Profile   | <img class="inline" src="/docs/images/supported.svg" /> | <img class="inline" src="/docs/images/unsupported.svg" /> | <img class="inline" src="/docs/images/supported.svg" /> **\*** |
+| Unsubscribe Profile | <img class="inline" src="/docs/images/supported.svg" /> | <img class="inline" src="/docs/images/unsupported.svg" /> | <img class="inline" src="/docs/images/supported.svg" />        |
 
-| Action          | Added           | Updated        | Deleted         |
-| --------------  | --------------- | -------------- | --------------- | 
-| Order Completed | <img class="inline" src="/docs/images/supported.svg" /> | <img class="inline" src="/docs/images/unsupported.svg" />        | <img class="inline" src="/docs/images/unsupported.svg" />       |
-| Track Event     | <img class="inline" src="/docs/images/supported.svg" />         | <img class="inline" src="/docs/images/unsupported.svg" />       | <img class="inline" src="/docs/images/unsupported.svg" />        |
-| Upsert Profile  | <img class="inline" src="/docs/images/supported.svg" />         | <img class="inline" src="/docs/images/supported.svg" />        | <img class="inline" src="/docs/images/unsupported.svg" />        |
+> info ""
+> **\*** Though technically possible, it may not be the most intuitive approach to using RETL.
+>
+> **e.g.,** Triggering a **Subscribe Profile** action when a user is **deleted** from a Model that queries unsubscribed users.
 
 In order to add users to a list, use the **Upsert Profile** Action and fill out the **List** field with the Klaviyo list to add the profile to.
 
-Follow these steps to create a list in Klaviyo: 
+Follow these steps to create a list in Klaviyo:
 
 1. Navigate to **Audience > Lists & Segments**.
 2. Click **Create List/Segment**.
 3. Choose **List**.
 4. Give your list a name and add any applicable tags.
 5. Click **Create List**.
 
-
 ## Using Klaviyo with Engage
 
-Klaviyo (Actions) Destination can accept your [Engage](/docs/engage/) data. You **don't** need to create a list in Klaviyo. During the first sync, Segment creates a list with the same name as your audience. 
+Klaviyo (Actions) Destination can accept your [Engage](/docs/engage/) data. If you wish to add a profile to a list associated with the Engage audienceId, you **don't** need to create a list in Klaviyo. During the first sync with the **Add Profile To List (Engage)** Mapping, Segment creates a list with the same ID as your audience.
+
+To add and remove profiles in Klaviyo with Engage Audience data:
 
-To use Klaviyo with Engage:
 1. Create and configure your Engage Audience.
 2. Navigate to **Engage > Engage Settings > Destinations** and click **Add Destination**.
 3. Select **Klaviyo (Actions) Audiences**.
 4. Select your Audience Space as the source, and name your destination.
-5. On the **Mappings** tab, click **Add Mapping** and select **Add Profile To List**. 
-6. Click **Save** and make sure to enable the mapping. 
-7. On the **Mappings** tab, click **Add Mapping** and select **Remove Profile from list**. 
-8. Click **Save** and make sure you enable the mapping. 
-9. Enable the destination. 
+5. On the **Mappings** tab, click **Add Mapping** and select **Add Profile To List (Engage)**.
+6. Click **Save** and make sure to enable the mapping.
+7. On the **Mappings** tab, click **Add Mapping** and select **Remove Profile from List (Engage)**.
+8. Click **Save** and make sure you enable the mapping.
+9. Enable the destination.
 10. On the **Engage > Audiences > (your audience)** page, click **Add Destination** and select the destination created.
 11. In the settings that appear in the side panel, toggle the **Send Track** option on, and don't change the **Audience Entered/Audience Exited** event names.
 12. Click **Save Settings**.
 
-## FAQ 
+## FAQ
 
-### Dealing with 429 Responses from Klaviyo's API 
+### Dealing with 429 Responses from Klaviyo's API
 
 If you're encountering rate limiting issues, consider enabling batching for the Action receiving these errors. Ensure that within the mapping configuration, "Batch data to Klaviyo" is set to "Yes". This adjustment can help alleviate the rate limiting problem.

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

@@ -5,9 +5,6 @@ id: 64b6a221baf168a989be641a
 
 {% include content/plan-grid.md name="actions" %}
 
-> info ""
-> The Listrak Destination is in beta, and Listrak is still developing the destination. To join Listrak's beta program or to give any feedback to help improve the Listrak Destination and its documentation, [let Listrak know](mailto:[email protected]).
-
 [Listrak](https://www.listrak.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is the retail industry’s leading customer engagement platform. Listrak delivers results for more than 1,000 retailers by providing best-in-class email, text message marketing, identity resolution marketing and push notifications through seamless cross-channel orchestration. Listrak’s data-first approach delivers 1:1 personalization at scale so you can send messages at precisely the right time across the right combination of channels and devices to maximize customer engagement, revenue, and lifetime value.
 
 Listrak maintains this destination. For any issues with the destination, [contact the Listrak Support team](mailto:[email protected]).