Merge pull request #4465 from segmentio/develop

Release 23.12.2

Author: forstisabella

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2023-03-21 
+# destination categories last updated 2023-03-23 
 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 2023-03-21 
+# destination data last updated 2023-03-23 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -35372,7 +35372,7 @@ items:
   display_name: Innovid
   name: Innovid
   slug: innovid
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-03-21 
+# destination data last updated 2023-03-23 
 items:
   - id: 54521fd725e721e32a72eec1
     display_name: HubSpot

src/_data/catalog/regional-supported.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED LIST OF CONNECTIONS THAT SUPPORT REGIONAL
-# Last updated 2023-03-21 
+# Last updated 2023-03-23 
 warehouses:
   - id: WcjBCzUGff
     display_name: Azure SQL Data Warehouse
@@ -984,12 +984,11 @@ sources:
       - us
       - eu
   - id: lWMazCg4rS
-    display_name: Twilio Event Streams (Beta)
-    slug: twilio-event-streams-beta
-    url: connections/sources/catalog/cloud-apps/twilio-event-streams-beta
+    display_name: Twilio Event Streams
+    slug: twilio-event-streams
+    url: connections/sources/catalog/cloud-apps/twilio-event-streams
     regions:
       - us
-      - eu
     endpoints:
       - us
   - id: 4zkHfaSKI8

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2023-03-21 
+# source cateogries last updated 2023-03-23 
 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 2023-03-21 
+# sources last updated 2023-03-23 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
@@ -1220,7 +1220,7 @@ items:
     isCloudEventSource: true
     slug: name
     url: connections/sources/catalog/cloud-apps/name
-    hidden: false
+    hidden: true
     regions:
       - us
     endpoints:
@@ -2024,14 +2024,13 @@ items:
     categories:
       - SMS & Push Notifications
   - id: lWMazCg4rS
-    display_name: Twilio Event Streams (Beta)
+    display_name: Twilio Event Streams
     isCloudEventSource: true
-    slug: twilio-event-streams-beta
-    url: connections/sources/catalog/cloud-apps/twilio-event-streams-beta
-    hidden: true
+    slug: twilio-event-streams
+    url: connections/sources/catalog/cloud-apps/twilio-event-streams
+    hidden: false
     regions:
       - us
-      - eu
     endpoints:
       - us
     source_type: cloud-app

src/_redirects

@@ -0,0 +1,4 @@
+# Redirects file for Netlify
+
+# Redirect for Profiles -> Unify rename
+# /docs/profiles/*                        /docs/unify/:splat

src/connections/destinations/actions.md

@@ -65,7 +65,8 @@ To set up a new Actions-framework destination for the first time:
 7. Once you're satisfied with your mappings, click **Create Destination**.
 
 > info ""
-> At least one mapping to handle a connected source's event(s) must be configured and enabled in an Actions-framework destination in order for data to be sent downstream.
+> You must configure and enable at least one mapping to handle a connected source's event(s) in an Actions-framework destination in order for data to send downstream. 
+> Events send downstream in the order in which they appear in the mappings UI. There is no mechanism through which you can control the order of events that send to the downstream destinations outside of that. 
 
 ## Migrate a classic destination to an actions-based destination
 

src/connections/destinations/add-destination.md

@@ -132,6 +132,9 @@ You can add multiple instances of a destination using the Segment Public API. Se
     - **Warning**: If you bundle one instance of a destination in a mobile source but have other instances of that destination connected to that source you might see unexpected and inconsistent data.
 - **Non-mobile sources can only connect to one *device-mode* instance of a destination, in addition to up to 25 cloud-mode instances.** A web browser sending to a destination in device-mode sends data directly from the user's browser (instead of through the Segment servers), by bundling a copy of destination's code with the Segment SDK. Segment can't bundle multiple copies of the destination SDK and so it can't send data to multiple instances of the destination from the browser.
 - **You cannot connect a source to more than one instance of a destination that operates in device-mode only**. These destinations can only accept data from code directly on the user's device, and Segment cannot include duplicates of that code for a single source.
+- **Multi-instance support is not available for most hybrid Actions destinations, and will not support Web Mode Actions destinations**. Hybrid destinations are those that have some components that operate in device-mode and some that operate in cloud-mode. Actions destinations currently affected by this are Amplitude Actions and Braze Cloud Actions. 
+    - **Amplitude Actions** *does* have multi-instance support for Analytics.js and server sources, but *does not* have multi-instance support for mobile sources. 
+    - **Braze Cloud Actions** *does not* have multi-instance support because it includes a device-mode web plugin for the Debounce Middleware.
 
 
 ### Other multi-instance destination considerations

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

@@ -49,6 +49,10 @@ With Google Analytics 4, you must create custom dimensions and metrics within th
 
 The Google Analytics 4 [debug mode](https://support.google.com/analytics/answer/7201382?hl=en){:target="_blank"} is supported with the Google Analytics 4 Web destination. DebugView displays the events and user properties that Analytics collects from a user in real-time. This can be helpful in troubleshooting your implementation.
 
+### Send events from both the browser and the server 
+
+With Google Analytics 4 Web, events are sent from the browser to GA4. If you use Segment’s [Google Analytics 4 Cloud destination](/docs/connections/destinations/catalog/actions-google-analytics-4/#benefits-of-google-analytics-4-cloud) to send events through the API and tie data between client-side and server-side, you need to pass the same Client ID from the browser and the server. To do this, fetch the Gtag-generated **clientId** on the web client and pass it to Segment as a property. For more information, see [Google Analytics 4 destination: User Identification](/docs/connections/destinations/catalog/actions-google-analytics-4/#user-identification) on the next steps.
+
 ### Additional (unmapped) events are sent to GA4
 
 Google Analytics 4 collects events triggered by basic interactions with your site. For more information, see [Google Analytics 4 Automatically collected events](https://support.google.com/analytics/answer/9234069?hl=en){:target="_blank"}
@@ -61,4 +65,3 @@ Google may take [24-48 hours](https://support.google.com/analytics/answer/933379
 ### Data is not sent to Google
 
 Ensure that at least one mapping has been configured and enabled in the destination mappings for an event you want to send to Google Analytics. If no mappings are enabled, the destination does not send events.
-

src/connections/destinations/catalog/iterable/index.md

@@ -24,6 +24,9 @@ When you call `identify` with one of Segment's sources, Segment calls Iterable's
 
 Iterable keys users by `email` or a user ID. This user ID will be the Segment `userId` if sent. To use a Segment `userId` for identify calls, first call identify with both a `userId` and `email`. Iterable won't accept the request and throws an error if you fail to send one of either the `userId` or `email`.
 
+> info ""
+> You must send the `email` parameter to Segment as `email`. The `email` value can't be passed in with any other key name in the payload. Sending `email` in with a different key name (for example, `customer_email`, `mail`) will not allow Iterable's processes to understand that key holds the `email` value you want to use. The same condition applies to the `userId` field. Using keys other than `email` and `userId` cause payloads to be silently rejected by Iterable.
+
 <!-- commented out because this functionality isn't currently working ZD#355518
 ### Merge Nested Objects
 
@@ -58,12 +61,18 @@ When you call `track` with one of Segment's sources, Segment calls Iterable's [t
 
 If a user does not already exist in Iterable, calling `track` for a user event will add that user into the system. You can track with either an `email` or userId (if a `userId` exists for that email).
 
+> info ""
+> You must send the `email` parameter to Segment as `email`. The `email` value can't be passed in with any other key name in the payload. Sending `email` in with a different key name (for example, `customer_email`, `mail`) will not allow Iterable's processes to understand that key holds the `email` value you want to use. The same condition applies to the `userId` field. Using keys other than `email` and `userId` cause payloads to be silently rejected by Iterable.
+
 ### Example steps:
 
 First `track` event with `userId` and `email`; user will be created
 
 Subsequent `track` with `userId`
 
+> info ""
+> If you send an ISO formatted date field in your events, Segment converts it into UTC to conform to standard Iterable format: `yyyy-MM-dd HH:mm:ss ZZ` (for example, `2023-02-05 20:42:10 +00:00`). Iterable has a specific date format that must be used to segment a field by date. Read more about Iterable date field [here](https://support.iterable.com/hc/en-us/articles/208183076-Data-Field-Types-in-Iterable#date){:target="_blank"}.
+
 ### Ecommerce
 
 Iterable also supports Segment's [ecommerce events](/docs/connections/spec/ecommerce/v2/). This works just as you would expect, using the `track` method.

src/connections/sources/catalog/cloud-apps/twilio-event-streams/index.md

@@ -0,0 +1,4 @@
+---
+title: 'Twilio Event Streams Source'
+hidden: true
+---

src/connections/sources/catalog/libraries/mobile/react-native/index.md

@@ -610,5 +610,7 @@ const segmentClient = createClient({
   writeKey: segmentWriteKey
 });
 ```
+### What is the instanceId set in context?
+The instanceId was introduced in [V 2.10.1](https://github.com/segmentio/analytics-react-native/releases/tag/%40segment%2Fanalytics-react-native-v2.10.1) and correlates events to a particular instance of the client in a scenario when you might have multiple instances on a single app. 
 ## Changelog
 [View the Analytics React Native 2.0 changelog on GitHub](https://github.com/segmentio/analytics-react-native/releases){:target="_blank"}.

src/protocols/apis-and-extensions/typewriter.md

@@ -543,7 +543,7 @@ typewriter.setTypewriterOptions({
 
 Typewriter only supports `track` calls. However, you can continue to use the underlying (untyped) analytics instance to perform `identify`, `group`, `page`, `screen`, and `alias` calls.
 
-Not all languages support run-time validation. Currently, `analytics.js` and `analytics-node` support it using [AJV](https://github.com/epoberezkin/ajv){:target="_blank"} (both for JavaScript and TypeScript projects) while `analytics-swift` and `analytics-kotlin` don't support run-time validation. Typewriter also doesn't support run-time validation using Common JSON Schema.
+Not all languages support run-time validation. Currently, `analytics.js` and `analytics-node` support it using [AJV](https://github.com/epoberezkin/ajv){:target="_blank"} (both for JavaScript and TypeScript projects) while `analytics-swift` and `analytics-kotlin` don't support run-time validation. Typewriter also does not support event validation using the Common JSON Schema.
 
 ## Contributing
 

src/protocols/faq.md

@@ -72,6 +72,10 @@ Yes. Using the [Public API](/docs/protocols/apis-and-extensions/), you can copy
 
 If you [discarded events](/docs/protocols/enforce/schema-configuration) as a part of your original Tracking Plan, you must connect to the same Source and configure identical Schema Controls in your other Workspace so that blocked events behave as expected.
 
+### Can I connect a Source to more than one Tracking Plan?
+
+Unfortunately, Sources cannot be connected to more than one Tracking Plan. If you were able to connect more than one Tracking Plan to a Source, it could create conflict if events overlapped. 
+
 ## Protocols Validation
 
 ### What is the difference between Violations Emails and the Violations page in the Segment UI?