Merge pull request #2245 from segmentio/12-3-silent-deploy

12 3 silent deploy

Author: markzegarelli

src/connections/destinations/catalog/actions-facebook-conversions-api/index.md

@@ -5,17 +5,17 @@ hide-boilerplate: true
 hide-dossier: true
 ---
 
-Facebook Conversions API (Actions) enables advertisers to send events from their servers directly to Facebook. Server-side events link to Facebook Pixel events, and process like browser pixel events. This means that serve-side events are used in measurement, reporting, and optimization, just like browser pixel events.
+Facebook Conversions API (Actions) enables advertisers to send events from their servers directly to Facebook. Server-side events link to Facebook Pixel events, and process like browser pixel events. This means that server-side events are used in measurement, reporting, and optimization, just like browser pixel events.
 
 > info ""
 > This document is about a feature which is in beta. This means that the Facebook Conversions API (Actions) destination is in active development, and some functionality may change before it becomes generally available.
 
 > success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Customer.io Segment destination. There's also a page about the [non-Actions Facebook Conversions API destination](/docs/connections/destinations/catalog/facebook-pixel-server-side/). Both of these destinations receives data _from_ Segment.
+> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Facebook Conversions API Segment destination. There's also a page about the [non-Actions Facebook Conversions API destination](/docs/connections/destinations/catalog/facebook-pixel-server-side/). Both of these destinations receive data _from_ Segment.
 
 ## Benefits of Facebook Conversions API (Actions) vs Facebook Conversions API Classic
 
-Segment’s Facebook Conversions API (Actions) destination provides the following benefits over the classic Facebook Conversions API destination:
+The Facebook Conversions API (Actions) destination provides the following benefits over the classic Facebook Conversions API destination:
 - **Fewer settings**. Data mapping for actions-based destinations happens during configuration, which eliminates the need for most settings.
 - **Clearer mapping of data**. Actions-based destinations enable you to define the mapping between the data Segment receives from your source, and the data Segment sends to Facebook Conversions API.
 - **Support for page calls**. Page calls can be sent to Facebook as a standard Page View.
@@ -50,14 +50,14 @@ The Facebook Conversions API (Actions) destination is in Private Beta, and does
 1. To access the destination, navigate to this URL: `https://app.segment.com/<workspace_slug>/destinations/catalog/actions-facebook-conversions-api`. Replace `<workspace_slug>` with your workspace slug.
 2. Click **Configure Facebook Conversions API (Actions)** in the top-right corner of the screen.
 3. Choose which of your sources to connect the destination to. (You can connect more sources to the destination later.)
-4. Click **Configure Actions** and follow the set up steps to** Create Destination**.
+4. Click **Configure Actions** and follow the set up steps to **Create Destination**.
 5. On the Settings tab, enter in your Pixel ID and click **Save**.
 6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
 
 ## Configuration options
 
 
-The Segment Facebook Conversions API destination gives you several ways to implement your conversion tracking. You can use it with [Facebook Pixel](/docs/connections/destinations/catalog/facebook-pixel/), or as a stand-alone alternative. You can read more about implementation options below and in [Facebook documentation](https://developers.facebook.com/docs/marketing-api/conversions-api/guides/end-to-end-implementation#pick-your-integration-type){:target="_blank"}.
+The Facebook Conversions API (Actions) destination gives you several ways to implement your conversion tracking. You can use it with [Facebook Pixel](/docs/connections/destinations/catalog/facebook-pixel/), or as a stand-alone alternative. You can read more about implementation options below and in [Facebook documentation](https://developers.facebook.com/docs/marketing-api/conversions-api/guides/end-to-end-implementation#pick-your-integration-type){:target="_blank"}.
 
 
 ### Send events from both the browser and the server
@@ -94,6 +94,12 @@ For this option to work best, the same External ID needs to be passed from the b
 
 With the Facebook Conversions API (Actions) destination, you can choose any field in your event to map to External ID. By default, Segment uses the userId (or anonymousId if userId is not present) to set the External ID, but you can change this in the User Data object mapping of your Action.
 
+![the coalesce function](images/image1.png)
+
+You can send additional User Data to increase the match rate for events from a server source. Collect other fields from the browser, like User Agent, IP Address, and [Facebook's cookie parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc){:target="_blank"}, pass them to the server, and map them in the User Data object.
+
+![the user data object](images/image2.png)
+
 #### Deduplication considerations
 
 If you choose this option, each source sends different events, and deduplication is not necessary.
@@ -102,7 +108,6 @@ If you choose this option, each source sends different events, and deduplication
 
 Use this approach if you don’t want to track users from the browser with Facebook Pixel. By default, Facebook Pixel collects cookie data, as well as browser data such as the IP Address and the User Agent, some of which you might not want to collect. By sending from a Segment server source to Facebook’s Conversions API, you can control which identifiers you pass to Facebook.
 
-
 #### Match rate considerations
 
 If you use Facebook Conversions API as a stand-alone without certain data fields collected from the browser, the match rate might not be as high as if you included them. You can increase the match rate for events from a server source by including User Data, such as Zip Code, Country and State.
@@ -131,4 +136,4 @@ After you start sending events, you should start seeing them in twenty minutes.
 
 1. Go to the Events Manager.
 2. Click on the corresponding pixel.
-3. In the Overview tab, look for events where the “Connection Method” is Server.
+3. In the Overview tab, look for events where the “Connection Method” is Server.

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

@@ -12,15 +12,15 @@ hidden: true
 
 
 > success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Google Analytics destination. There's also a page about the [non-Actions Google Analytics destination](/docs/connections/destinations/catalog/google-analytics/). Both of these destinations receives data _from_ Segment.
+> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Google Analytics 4 destination. There's also a page about the [non-Actions Google Universal Analytics destination](/docs/connections/destinations/catalog/google-analytics/). Both of these destinations receive data _from_ Segment.
 
 ## Benefits of Google Analytics 4
 
 The Google Analytics 4 destination provides the following benefits:
 
 - **Fewer settings**. Data mapping for actions-based destinations happens during configuration, which eliminates the need for most settings.
 - **Clearer mapping of data**. Actions-based destinations enable you to define the mapping between the data Segment receives from your source and the data Segment sends to Google Analytics 4.
-- **Support for multi-product arrays**. Products nested within arrays, like the products array in the [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed) event, can be sent to Google Analytics 4.
+- **Support for multi-product arrays**. Products nested within arrays, like the `products` array in the [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed) event, can be sent to Google Analytics 4.
 - **Multi-platform support**. You can use a Google Analytics 4 property for a website, an app, or both a website and app together.
 
 ## Getting started
@@ -32,8 +32,8 @@ The Google Analytics 4 destination is in Private Beta and does not appear in the
 1. To access the destination, navigate to this URL: `https://app.segment.com/<workspace_slug>/destinations/catalog/actions-google-analytics-4`. Replace `<workspace_slug>` with your workspace slug.
 2. Click **Configure Google Analytics 4** in the top-right corner of the screen.
 3. Choose which of your sources to connect the destination to. (You can connect more sources to the destination later.)
-4. Click **Configure Actions** and follow the set up steps to** Create Destination**.
-5. On the Settings tab, enter in the [Measurement ID](https://support.google.com/analytics/answer/9539598){:target='_blank'} and API Secret associated with your GA4 stream and click **Save**._ Note: to create a new API Secret, navigate in the Google Analytics UI to Admin > Data Streams > choose your stream > Measurement Protocol > Create. _
+4. Click **Configure Actions** and follow the set up steps to **Create Destination**.
+5. On the Settings tab, enter in the [Measurement ID](https://support.google.com/analytics/answer/9539598){:target='_blank'} and API Secret associated with your GA4 stream and click **Save**. _Note: To create a new API Secret, navigate in the Google Analytics UI to Admin > Data Streams > choose your stream > Measurement Protocol > Create._
 6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
 
 ## Available Google Analytics 4 actions
@@ -58,4 +58,4 @@ Combine the supported [triggers](docs/connections/destinations/actions/#componen
 * Generate Lead
 * Sign Up
 * Login
-* Custom Event
+* Custom Event

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

@@ -3,39 +3,37 @@ rewrite: true
 title: Appcues Destination
 hide-cmodes: true
 ---
-[Appcues](https://www.appcues.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) adds an experience layer to your product, so you can build user onboarding, NPS surveys, or feature announcements in minutes instead of in weeks. The Appcues JavaScript Destination is open-source. You can browse the code [on GitHub](https://github.com/appcues/analytics.js-integration-appcues).
-
-If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact)!
+[Appcues](https://www.appcues.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) adds an experience layer to your product so you can build user onboarding, NPS surveys, or feature announcements in minutes instead of weeks. The Appcues JavaScript Destination is open-source. You can browse the code [on GitHub](https://github.com/appcues/analytics.js-integration-appcues).
 
 
 ## Getting Started
 
 1. From the Segment web app, click **Catalog**.
-2. Search for "Appcues" in the Catalog, select it, and choose which of your sources to connect the destination to.
+2. Search for "Appcues" in the Catalog, select it, and choose the source you'll connect to the destination.
 3. In the destination settings, enter your `Appcues Id` (for client-side integration functionality) and/or your `API Key` (for server-side integration functionality) from the [Appcues account page](https://my.appcues.com/account).
 
 ### Server
 
-Although our JavaScript destination is the traditional way to use Appcues as part of the Segment platform, Appcues also offers a server-side destination with Segment, which is useful if you'd like to send user profile or event data to Appcues from another Segment partner service. The server-side destination may be used simultaneously with the JS destination. In many cases, this is preferable to routing all data through the JS destination.
+As an alternative to a traditional JavaScript implementation, Appcues offers a server-side destination with Segment.
+
+You may find the server-side destination useful if you'd like to send user profile or event data to Appcues from another Segment partner service. You can use the server-side destination alongside the JavaScript destination, which you may find preferable to routing all data through the JavaScript destination.
 
-The user profile and event data received through Appcues' server-side Segment destination can be used to segment
-and target Appcues flows, just like data received from the JS destination.
+As with the JavaScript destination, you can segment and target user profile and event data received through the Appcues server-side Segment destination.
 
-For example, using the server-side destination, customer profile and event data could be directed from a CRM tool into the Appcues platform. This data could then be used for content targeting and user segmentation in the Appcues content editor, alongside data from our `analytics.js` destination.
+For example, using the server-side destination, you can direct customer profile and event data from a CRM tool into Appcues. You can then use the directed data for content targeting and user segmentation in the Appcues content editor, alongside data from Segment's `analytics.js` destination.
 
 ## Page
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
+Refer to the Segment Spec for information about the [Page method](/docs/connections/spec/page/). The following represents an example `page` call:
 
 ```javascript
 analytics.page();
 ```
-
-Appcues will check to see if a user qualifies for an experience every time the page changes. When you first call `page` using `analytics.js`, `Appcues.start` checks if there are any current flows for the user and loads them if necessary.
+Each time the page changes, Appcues checks to see if a user qualifies for an experience. When you first call `page` using Analytics.js, `Appcues.start` checks if there are any current flows for the user and loads them, if necessary.
 
 ## Identify
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
+Refer to the Segment Spec for information about the [Identify method](/docs/connections/spec/identify/). The following represents an example `identify` call:
 
 ```javascript
 analytics.identify('12091906-01011992', {
@@ -44,28 +42,30 @@ analytics.identify('12091906-01011992', {
 });
 ```
 
-When you `identify` on `analytics.js`, we call `Appcues.identify`. This is the preferred method of using and targeting on user properties.
+When you call `identify` with Analytics.js, Segment calls `Appcues.identify`. This is the preferred method of using and targeting on user properties.
 
-To get the most out of Appcues, you should send as much user data as possible in the `identify` call. Properties are used to target experiences to specific users and personalize content. Most Appcues customers send properties that fall into a few groups:
-  * Properties to target based on broad classifications such as `role` or `userType`
-  * Properties to personalize Appcues content such as `name`, `firstName` or `company`
-  * Properties to target based on user lifecycle such as `createdAt` (date) or usage metrics such as `numTasksComplete`
+To get the most out of Appcues, you should send as much user data as possible in the `identify` call. Properties personalize content and target experiences to specific users. Most Appcues customers send properties that fall into one of the following groups:
+  * Properties to target based on broad classifications, such as `role` or `userType`
+  * Properties to personalize Appcues content, such as `name`, `firstName`, or `company`
+  * Properties to target based on user lifecycle, such as `createdAt` (date), or usage metrics, such as `numTasksComplete`
 
 ## Track
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
+Refer to the Segment Spec for information about the [Track method](/docs/connections/spec/track/). The following represents an example `track` call:
 
 ```javascript
 analytics.track("step_activated", {
   property: "test"
 });
 ```
 
-Calls to `analytics.track` invoke `Appcues.track` as well. This will send event data to the Appcues platform, where it can be used for future content triggering.
+Calls to `analytics.track` also invoke `Appcues.track`. As a result, the call sends event data to Appcues, where you can use it for future content triggering.
 
 ### Sending Appcues events to other Segment partner services
 
-Want to read Appcues events in your 3rd party analytics or marketing automation tool? Appcues supports sending events to other tools on the Segment platform. These events will be sent as track calls to the other destinations you've turned on. A partial list of Appcues content lifecycle events that can be tracked:
+Appcues supports sending events to other tools on the Segment platform. This capability allows you to read Appcues events in your third-party analytics or marketing automation tools.
+
+These events are sent as track calls to the other destinations you've turned on. The following shows a partial list of trackable Appcues content lifecycle events:
   * `flow_shown`
   * `flow_skipped`
   * `flow_finished`
@@ -81,11 +81,17 @@ Want to read Appcues events in your 3rd party analytics or marketing automation
 
 To enable this feature, go to the Integrations Settings in Appcues and click "Activate" under the Segment integration.
 
+After you activate the Segment integration, Appcues forwards these events to your Segment workspace. The events will appear in the same [Source Debugger](/docs/connections/sources/debugger/).
+
 ### Whitelisted Domains
 
-By default, Appcues will target based on the path of the URL. So if we created an Appcues experience and targeted it to `/integrations`, it would appear wherever the embed script is installed with that URL path, like appcues.com/integrations and my.appcues.com/integrations. If your `analytics.js` script is installed on multiple domains (e.g. your marketing site and your web app), you should use Appcues whitelisted domains when targeting your experience.
+By default, Appcues targets based on the URL's path.
+
+For example, if you create an Appcues experience and target it to `/integrations`, it appears wherever the embed script is installed with that URL path, like `appcues.com/integrations` and `my.appcues.com/integrations`.
+
+If you've installed the Analytics.js script on multiple domains (like a marketing site and your web app), you should use Appcues-whitelisted domains when targeting your experience.
 
 
 ## Delete
 
-When you trigger a user deletion using our [Privacy features](/docs/privacy/user-deletion-and-suppression/), we will forward a delete notification to Appcues, who will act on the notification. You can read more about how Appcues handles deletion requests [in their docs here.](https://docs.appcues.com/article/443-gdpr-deletion-api)
+When you trigger a user deletion using [Segment's Privacy features](/docs/privacy/user-deletion-and-suppression/), Segment forwards an actionable delete notification to Appcues. Refer to the Appcues documentation for information on [how Appcues handles deletion requests](https://docs.appcues.com/article/443-gdpr-deletion-api){:target="_blank"}.