Merge pull request #3186 from segmentio/develop

Release 22.27.3

Author: rchinn1

.github/styles/Vocab/Docs/accept.txt

@@ -22,13 +22,15 @@ Amberflo
 Appboy
 Appsflyer
 async
+background(?:ed|ing)
 Blitzllama
 blocklist
 boolean
 Breyta
 Chargebee
 CloudFront
 Cocoapods
+Contentful
 Criteo
 csv
 deeplink
@@ -73,6 +75,7 @@ middleware
 Middleware
 Mixpanel
 namespace
+Ninetailed
 Okta
 Omnichannel
 onboarding
@@ -84,6 +87,7 @@ Shopify
 Skalin
 Smartly
 Snapchat
+Spideo
 Subnet
 svg
 Totango
@@ -97,4 +101,5 @@ viewability
 waitlist
 WebKit
 Wootric
+Xcode
 Zendesk

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2022-07-05 
+# destination categories last updated 2022-07-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 2022-07-05 
+# destination data last updated 2022-07-07 
 items:
 - id: 60b5d0a01f3726b85dc05aab
   display_name: 2mee
@@ -22700,16 +22700,20 @@ items:
     server: true
   components:
   - code: >-
-      https://github.com/segment-integrations/analytics.js-integration-google-analytics
+      https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/google-analytics
+    owner: SEGMENT
     type: BROWSER
   - code: >-
       https://github.com/segment-integrations/analytics-ios-integration-google-analytics
+    owner: SEGMENT
     type: IOS
   - code: >-
       https://github.com/segment-integrations/analytics-android-integration-google-analytics
+    owner: SEGMENT
     type: ANDROID
   - code: >-
       https://github.com/segmentio/integrations/tree/master/integrations/google-analytics
+    owner: SEGMENT
     type: SERVER
   browserUnbundlingSupported: true
   browserUnbundlingPublic: true
@@ -28527,7 +28531,7 @@ items:
   display_name: Mixpanel (Actions)
   name: Mixpanel (Actions)
   slug: mixpanel-actions
-  hidden: false
+  hidden: true
   endpoints:
   - us
   regions:
@@ -30665,6 +30669,65 @@ items:
     label: Subbrand Property Name
   actions: []
   presets: []
+- id: 60635bda625d1d13b153c8ca
+  display_name: Ninetailed
+  name: Ninetailed
+  slug: ninetailed
+  hidden: false
+  endpoints:
+  - us
+  regions:
+  - us
+  url: connections/destinations/catalog/ninetailed
+  previous_names:
+  - Ninetailed
+  website: https://ninetailed.io
+  status: PUBLIC_BETA
+  categories:
+  - A/B Testing
+  - Analytics
+  - Marketing Automation
+  - Personalization
+  logo:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/40210039-b8fc-4a7f-a04b-657153890b17.svg
+  mark:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/cbed56fc-e143-49ae-96eb-e4847cde8f5f.svg
+  methods:
+    track: true
+    identify: true
+    group: false
+    alias: false
+    page: false
+  platforms:
+    browser: true
+    mobile: true
+    server: true
+  components: []
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: false
+  replay: false
+  connection_modes:
+    device:
+      web: false
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: false
+      server: false
+  settings:
+  - name: apiKey
+    type: string
+    defaultValue: ''
+    description: >-
+      Go to the Ninetailed dashboard or your CMS App Dashboard, find and copy
+      the “API key”.
+    required: true
+    label: API Key
+  actions: []
+  presets: []
 - id: 5fd719e85f1569d6af775ec1
   display_name: Noora
   name: Noora
@@ -39523,6 +39586,16 @@ items:
     description: "Please set a Startdeliver user custom field to match a Segment event on. You can find your custom fields here –\_https://app.startdeliver.com/settings/fields."
     required: true
     label: Startdeliver user custom field to match on
+  - name: syncUsingEmailInsteadOfCustomField
+    type: boolean
+    defaultValue: false
+    description: >-
+      Override the use of Custom Field to match usage. Custom Field still has to
+      be filled in, however this toggle will override the use of Custom Field.
+      If there's no email in the root object or in the objects' traits, the
+      Custom Field will be used as a fallback.
+    required: true
+    label: Sync using Email instead of custom field
   actions: []
   presets: []
 - id: 613ba8c0114797213a8eff94

src/_data/catalog/regional-supported.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED LIST OF CONNECTIONS THAT SUPPORT REGIONAL
-# Last updated 2022-07-05 
+# Last updated 2022-07-07 
 warehouses:
   - id: WcjBCzUGff
     display_name: Azure SQL Data Warehouse
@@ -2785,6 +2785,14 @@ destinations:
       - eu
     endpoints:
       - us
+  - id: 60635bda625d1d13b153c8ca
+    display_name: Ninetailed
+    slug: ninetailed
+    url: connections/destinations/catalog/ninetailed
+    regions:
+      - us
+    endpoints:
+      - us
   - id: 5fd719e85f1569d6af775ec1
     display_name: Noora
     slug: noora

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2022-07-05 
+# source cateogries last updated 2022-07-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 2022-07-05 
+# sources last updated 2022-07-07 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
@@ -535,7 +535,7 @@ items:
     isCloudEventSource: true
     slug: ibm-watson-assistant
     url: connections/sources/catalog/cloud-apps/ibm-watson-assistant
-    hidden: false
+    hidden: true
     regions:
       - us
     endpoints:

src/connections/destinations/catalog/actions-criteo-audiences/index.md

@@ -1,76 +1,9 @@
 ---
-title: Criteo Audiences (Actions) Destination
-hidden: true
+title: Criteo Audiences Destination
 hide-personas-partial: true
 hide-boilerplate: false
 hide-dossier: true
-id:
----
-{% include content/plan-grid.md name="actions" %}
-
-Criteo Audiences (Actions) enables advertisers to send Segment Persona Audiences to Criteo using Criteo's Audience API.
-
-By using Segment's Persona Audiences with Criteo, you can increase traffic and drive conversions with hyper-relevant ads that promote product discovery.
-
-## Benefits of Criteo Audiences (Actions)
-
-Benefits of the Critero Audiences (Actions) destination include:
-- **Improved email matching**: This integration creates a direct connection between Segment and Criteo for a higher match rate of email identifiers. 
-
-
-- **Fewer settings**: Unlike Criteo's Filter destination, this destination doesn't require any copy and paste code. You only need your Advertiser ID and Criteo API credentials.
-
-- **Criteo Audience**: You don't need a Criteo audience ID as the audience gets created on the fly using the Personas audience name. This enables the names of audience segments to be consistent across Segment and Criteo.
-
-- **Batching events and support for large audiences**: This destination supports batching which enables Criteo to receive large audiences without discrepancies.
-
-- **Near real time audience updates**: Actions destination helps Criteo receive real-time events and add or remove users from Criteo audiences appropriately.
-
-## Getting Started
-
-### Prerequisites:
-
-Before connecting to the Criteo Audiences (Actions) destination, you must create a Criteo API Marketing Solutions app to generate your app credentials (client ID and secret) as per the guidelines in [Criteo's Developer's Portal](https://developers.criteo.com/marketing-solutions/docs/onboarding-checklist){:target="_blank"}.
-
-You will also need your Criteo Advertiser ID. Please reach out to your Criteo Account Strategist to get this ID.
-
-### To Add the Criteo Audiences Destination:
-
-1. From your Segment workspace, go to **Connections > Catalog** and click **Destinations**.
-
-2. Search for **Criteo Audiences** in the Destinations Catalog and select the destination.
-
-3. Click **Configure Criteo Audiences**.
-
-4. Choose your **Personas** space for the Source as this destination only supports sending Personas Audiences to Criteo.
-
-On the **Settings** tab, name your destination. For example, Criteo audiences – <audience name>.
-
-6. Enter your Criteo Advertiser ID, API client ID and client secret.
-
-7. Click **Save Changes**.  
-
-8. In the **Mappings** tab, click **New Mapping** and select **Add Users to Audience**. Don't change any defaults.
-
-9. Under the **Configure actions fields**, set **Enable Batching** to *Yes* and click **Save**.  
-
-7. Repeat steps 8 and 9 for **Remove Users from Audience**.
-
-8. **Enable** both mappings.
-
-9. Go to the **Settings** tab and **Enable** the destination.
-
-10. Go to your **Personas** space and click the **Audiences** tab. Select the source audience that you want to send to your Criteo Audiences destination.
-
-11. Click **Add Destinations** and select the Criteo Audience destination you created. In the settings that appear on the right-hand side, toggle the **Send Track** option on and disable **Send Identify**. Click **Save**. 
-
-Your Criteo destination is now ready to receive audiences, and your Persona audiences now reflect in your Criteo Advertiser dashboard. Please note that it takes approximately 12-24 hours for the number of identifiers to populate in Criteo's Management Center.
-
-> warning ""
-> **NOTE**: Currently, you can only connect **ONE** personas audience to a single instance of Criteo Audience destination. If you have multiple audiences, repeat the above process to create a new Criteo audience destination and connect the audience to new destination each time.
-
-{% include components/actions-fields.html %}
-
-## Legacy Destination
-
-Please discontinue use of the legacy Criteo destination. Follow the steps above to define your Segment Persona Audiences to be sent to Criteo.
+hidden: true
+published: false
+id: 6238cec53a46dd187d094eb7
+---

src/connections/destinations/catalog/actions-google-analytics-4/index.md

@@ -121,6 +121,10 @@ For a complete map of Universal Analytics functionality to corresponding Google
 
 ## FAQ & Troubleshooting
 
+### Attribution Reporting
+
+Google doesn't currently support passing certain reserved fields to the Google Analytics 4 Measurement Protocol API. This includes attribution data, like UTM parameters. If you rely on attribution reporting, you can either send this data as [custom dimensions](/docs/connections/destinations/catalog/actions-google-analytics-4/#custom-dimensions-and-metrics) or implement a parallel client-side integration to collect this data with gtag.js.
+
 ### Debug Mode
 
 The Google Analytics 4 [debug mode](https://support.google.com/analytics/answer/7201382?hl=en){:target="_blank"} only works with a client-side implementation through gtag.js, Google Tag Manager, or Firebase. Because Segment's Google Analytics 4 integration is server-side and uses the Measurement Protocol API, debug mode is not supported.

src/connections/destinations/catalog/criteo-audiences/index.md

@@ -1,6 +1,77 @@
 ---
-title: 'Criteo Audiences Destination'
-hidden: true
+title: Criteo Audiences Destination
+hide-personas-partial: true
+hide-boilerplate: true
+hide-dossier: false
 id: 6238cec53a46dd187d094eb7
-published: false
+redirect_from:
+  - "/connections/destinations/catalog/actions-criteo-audiences" 
 ---
+{% include content/plan-grid.md name="actions" %}
+
+Criteo Audiences (Actions) enables advertisers to send Segment Persona Audiences to Criteo using Criteo's Audience API.
+
+By using Segment's Persona Audiences with Criteo, you can increase traffic and drive conversions with hyper-relevant ads that promote product discovery.
+
+## Benefits of Criteo Audiences (Actions)
+
+Benefits of the Criteo Audiences (Actions) destination include:
+- **Improved email matching**: This integration creates a direct connection between Segment and Criteo for a higher match rate of email identifiers. 
+
+
+- **Fewer settings**: Unlike Criteo's Filter destination, this destination doesn't require any copy and paste code. You only need your Advertiser ID and Criteo API credentials.
+
+- **Criteo Audience**: You don't need a Criteo audience ID as the audience gets created on the fly using the Personas audience name. This enables the names of audience segments to be consistent across Segment and Criteo.
+
+- **Batching events and support for large audiences**: This destination supports batching which enables Criteo to receive large audiences without discrepancies.
+
+- **Near real time audience updates**: Actions destination helps Criteo receive real-time events and add or remove users from Criteo audiences appropriately.
+
+## Getting Started
+
+### Prerequisites:
+
+Before connecting to the Criteo Audiences (Actions) destination, you must create a Criteo API Marketing Solutions app to generate your app credentials (client ID and secret) as per the guidelines in [Criteo's Developer's Portal](https://developers.criteo.com/marketing-solutions/docs/onboarding-checklist){:target="_blank"}.
+
+You will also need your Criteo Advertiser ID. Please reach out to your Criteo Account Strategist to get this ID.
+
+### To Add the Criteo Audiences Destination:
+
+1. From your Segment workspace, go to **Connections > Catalog** and click **Destinations**.
+
+2. Search for **Criteo Audiences** in the Destinations Catalog and select the destination.
+
+3. Click **Configure Criteo Audiences**.
+
+4. Choose your **Personas** space for the Source as this destination only supports sending Personas Audiences to Criteo.
+
+5. On the **Settings** tab, name your destination. For example, `Criteo audiences – <audience name>`.
+
+6. Enter your Criteo Advertiser ID, API client ID and client secret.
+
+7. Click **Save Changes**.  
+
+8. In the **Mappings** tab, click **New Mapping** and select **Add Users to Audience**. Don't change any defaults.
+
+9. Under the **Configure actions fields**, set **Enable Batching** to *Yes* and click **Save**.  
+
+7. Repeat steps 8 and 9 for **Remove Users from Audience**.
+
+8. **Enable** both mappings.
+
+9. Go to the **Settings** tab and **Enable** the destination.
+
+10. Go to your **Personas** space and click the **Audiences** tab. Select the source audience that you want to send to your Criteo Audiences destination.
+
+11. Click **Add Destinations** and select the Criteo Audience destination you created. In the settings that appear on the right-hand side, toggle the **Send Track** option on and disable **Send Identify**. Click **Save**. 
+
+Your Criteo destination is now ready to receive audiences, and your Persona audiences now reflect in your Criteo Advertiser dashboard. Be aware, it takes 12-24 hours for the number of identifiers to populate in Criteo's Management Center.
+
+> warning ""
+> **NOTE**: You can connect **ONE** personas audience to a single instance of Criteo Audience destination. If you have multiple audiences, repeat the above process to create a new Criteo audience destination and connect the audience to new destination each time.
+
+{% include components/actions-fields.html %}
+
+## Legacy Destination
+
+Please discontinue use of the legacy Criteo destination. Follow the steps above to define your Segment Persona Audiences to be sent to Criteo.