Merge pull request #2974 from segmentio/develop

Release 22.22.2

Author: rchinn1

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

@@ -81,7 +81,7 @@ The Google Analytics 4 reports only display active users who engage with your si
 
 If you choose to integrate with Google Analytics 4 client-side (using Gtag outside of Segment) _and_ also use Segment's Google Analytics 4 destination to send events through the API, you can track sessions server-side. When using Gtag, [Google generates a `session_id` and `session_number` when a session begins](https://support.google.com/analytics/answer/9191807?hl=en){:target='_blank'}. The `session_id` and `session_number` generated on the client can be passed as Event Parameters to stitch events sent through the API with the same session that was collected client-side.
 
-You can double-check your session_id and session_number with the [Google Site Tag function](https://developers.google.com/tag-platform/gtagjs/reference){:target='_blank'} or by running this script in your JavaScript console and replacing `G-xxxxxxxxxx` with your GA4 measurement ID:
+You can check your `session_id` and `session_number` with the [Google Site Tag function](https://developers.google.com/tag-platform/gtagjs/reference){:target='_blank'} or by running this script in your JavaScript console and replacing `G-xxxxxxxxxx` with your Google Analytics 4 Measurement ID:
 
 ```java
 const sessionIdPromise = new Promise(resolve => {

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

@@ -500,5 +500,11 @@ Segment supports these destinations for Analytics React Native 2.0 in device-mod
 - [Facebook App Events](https://www.npmjs.com/package/@segment/analytics-react-native-plugin-facebook-app-events){:target="_blank"}
 - [Firebase](https://www.npmjs.com/package/@segment/analytics-react-native-plugin-firebase){:target="_blank"}
 
+## FAQs
+### Can I use the catalog of device-mode destinations from Segment's 1.X.X React-Native release?
+No, only the plugins listed above are supported in device-mode for Analytics React Native 2.0.
+### Will I still see device-mode integrations listed as `false` in the integrations object?
+When you successfully package a plugin in device-mode, you won't see the integration listed as `false` in the integrations object for a Segment event. This logic is packaged in the event metadata, and isn't surfaced in the Segment debugger.
+
 ## Changelog
 [View the Analytics React Native 2.0 changelog on GitHub](https://github.com/segmentio/analytics-react-native/releases){:target="_blank"}.

src/connections/sources/catalog/libraries/mobile/swift-ios/index.md

@@ -407,6 +407,11 @@ Segment supports these destinations for Analytics Swift, with more to come:
 * [Firebase](https://github.com/segment-integrations/analytics-swift-firebase)
 * [Mixpanel](https://github.com/segment-integrations/analytics-swift-mixpanel)
 
+## FAQs
+### Can I use the catalog of device-mode destinations from Analytics-iOS?
+No, only the plugins listed above are supported in device-mode for Analytics-Swift.
+### Will I still see device-mode integrations listed as `false` in the integrations object?
+When you successfully package a plugin in device-mode, you will no longer see the integration listed as `false` in the integrations object for a Segment event. This logic is now packaged in the event metadata, and is not surfaced in the Segment debugger.
 
 ## Changelog
 [View the Analytics-Swift changelog on GitHub](https://github.com/segmentio/analytics-swift/releases).  

src/connections/storage/catalog/bigquery/index.md

@@ -176,7 +176,7 @@ Start by creating your Twilio account and getting an API key for Engage:
 2. In your Twilio console, select the **Account** dropdown menu, then **API keys & tokens**.
 3. On the Auth Tokens & API Keys page, click **Create API key**.
 4. Enter a name for the API key in the **Friendly name** field.
-5. Set the region to **United States (US1) - Default** and key type to **Standard**.
+5. Set the region to **United States (US1) - Default** and key type to **Main**.
 6. Click **Create API Key**.
 7. Copy both the **SID** and **Secret** field contents.
 
@@ -192,7 +192,7 @@ Start by creating your Twilio account and getting an API key for Engage:
 11. Under **Enter your Twilio API Key information** (shown below), paste the Account SID, API Key SID, and API Key Secret you copied above into their respective fields.
 12. Click **Verify**, then click **Save Twilio Account.**
 
-<!--    ![Entering Twilio API key into Engage](images/engageapifields.png "Entering Twilio API key into Engage") -->
+  ![Entering Twilio API key into Engage](images/engageapifields.png "Entering Twilio API key into Engage")
 
 > info ""
 > If you’re unable to verify your Account SID, SID, or API Key secret, you may have copied an extra space at the end of one or the other. Verify that you’ve not added any extra characters or spaces, then try to verify again.

src/engage/overview/images/apikeys.png

@@ -53,6 +53,17 @@ Use Segment’s APIs to manage user subscriptions programmatically on an ongoing
 
 Managing subscriptions with Segment's APIs allows you to handle continuous updates of subscription statuses, like when users subscribe to your marketing campaigns on a website form or modify their subscription from within a notification center.
 
+### Receive subscription confirmation with the Public API
+
+To receive an API response that confirms Segment has both received and processed subscription status requests, use Segment's [Public API](https://api.segmentapis.com/docs/spaces/#replace-messaging-subscriptions-in-spaces){:target="_blank"}.
+
+For example, if a user updates their subscription state in your notification center:
+
+1. Use the [Public API](https://api.segmentapis.com/docs/spaces/#replace-messaging-subscriptions-in-spaces){:target="_blank"} synchronous call to update their subscription state.
+2. The API returns an immediate success or failure response.
+3. For successful requests, Segment instantly updates subscription states in your workspace. `Subscribed` email and phone numbers will receive messages from Engage campaigns that they are a part of.
+4. You can then display successful updates or error messages with users in your notification center.
+
 ## The `track` call versus using the Public API
 
 When you use the `track` call, Segment replies with a standard HTTP `200 OK` status response code if it successfully received the request. Because the `track` call updates user traits asynchronously, though, the `200 OK` code indicates that Segment has received, but not yet processed, the request. As a result, use the `track` call for non-critical subscription updates, like form signups on your website or adding a subscription from within the user's notification center.