Merge branch 'master' into update_docs_for_snippet_5.2.1

Author: stayseesong

src/_data/sidenav/main.yml

@@ -260,6 +260,8 @@ sections:
         title: Speeding Up Redshift Queries
       - path: /connections/storage/warehouses/redshift-useful-sql
         title: Useful SQL Queries for Redshift
+  - path: /connections/regional-segment
+    title: Regional Segment
   - path: /connections/test-connections
     title: Event Tester
   - path: /connections/data-export-options
@@ -276,18 +278,6 @@ sections:
     title: Integration Error Codes
   - path: /connections/rate-limits
     title: Rate Limits
-  - path: /connections/regional-segment
-    title: Regional Segment
-# - section_title: Reverse ETL
-#   section:
-#   - path: /reverse-etl
-#     title: Reverse ETL Overview
-#   - path: /reverse-etl/bigquery-setup
-#     title: BigQuery Reverse ETL Setup
-#   - path: /reverse-etl/redshift-setup
-#     title: Redshift Reverse ETL Setup
-#   - path: /reverse-etl/snowflake-setup
-#     title: Snowflake Reverse ETL Setup
 - section_title: Unify
   section:
   - path: /unify
@@ -324,9 +314,7 @@ sections:
       title: Tables & Materialized Views
   - section_title: Linked Profiles 
     slug: unify/linked-profiles
-    section: 
-    - path: /unify/linked-profiles/linked-events
-      title: Linked Events
+    section:
     - section_title: Setup Guides
       slug: unify/linked-profiles/setup-guides
       section: 
@@ -336,6 +324,9 @@ sections:
           title: Snowflake Setup
         - path: /unify/linked-profiles/setup-guides/redshift-setup
           title: Redshift Setup
+    - path: /unify/linked-profiles/linked-events
+      title: Linked Events
+ 
   - section_title: Traits
     slug: unify/traits
     section:
@@ -364,7 +355,7 @@ sections:
     title: Unify FAQs
   - path: /unify/product-limits
     title: Unify Limits
-
+ 
 - section_title: Engage
   section:
   - path: '/engage'
@@ -400,6 +391,8 @@ sections:
       title: Audiences Overview
     - path: '/engage/audiences/account-audiences'
       title: Account-level Audiences
+    - path: '/engage/audiences/generative-audiences'
+      title: Generative Audiences
     - path: '/engage/audiences/organization'
       title: Organize Audiences
 

src/api/public-api/index.md

@@ -42,7 +42,7 @@ Learn more about [GitHub's secret scanning program](https://docs.github.com/en/d
 ## OAuth 2.0
 
 > info ""
-> This feature is currently in pilot and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. 
+> OAuth 2.0 is currently in private beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
 
 ## FAQs
 #### What should I do if I see a notification that my token was exposed?

src/connections/destinations/actions.md

@@ -75,6 +75,55 @@ Moving from a classic destination to an actions-based destination is a manual pr
 5. Verify that data is flowing from the development or test source to the partner tool.
 6. Repeat the steps above with your production source.
 
+### Migrate to an actions-based destination using Destination Filters
+For a more comprehensive migration from a classic destination to an actions-based destination, follow the steps outlined below. This implementation strategy is only available for customers on a Segment Business Tier plan with access to [Destination Filters](/docs/connections/destinations/destination-filters/). By adding additional line of defense with Destination Filters, you remove the possibility of duplicate events or dropped events and ensure that events sent before/after a specified `received_at` timestamp are sent to each destination.
+
+This migration strategy involves configuring a destination filter on both the Classic destination and the Actions destination. Configure the classic destination filter to block events by the `received_at` field with a certain value, and the Actions destination to drop events until the `received_at` timestamp field reaches that same value. Destination Filters within the UI have a limitation where they cannot access any top-level fields, but this is not a limitation for [Destination Filters](https://docs.segmentapis.com/tag/Destination-Filters/){:target="_blank”} created by the [Public API](https://segment.com/docs/api/public-api/){:target="_blank”} using [FQL](https://segment.com/docs/api/public-api/fql/){:target="_blank”}. Because the `received_at` is a top-level field in the payload, you'll need to create a destination filter with the Public API and submit the request with that FQL information described below.
+
+By combining these Filters, Segment sends events through the Classic integration up until a specified time and then blocks events after that time. Then the Actions integration blocks events until that specified time, and only allows events beginning at that specified time.
+
+The following code samples show you how you can create filters for your destinations using the [Create Filter for Destination](https://docs.segmentapis.com/tag/Destination-Filters#operation/createFilterForDestination){:target="_blank”} Public API operation.
+
+#### Classic destination
+_Endpoint_: `POST` `https://api.segmentapis.com/destination/classic_destination_id_from_url/filters`
+``` 
+// JSON BODY : 
+{
+  "sourceId": "add_source_id_here",
+  "destinationId": "classic_destination_id_from_url",
+  "title": "drop event after (timestamp) received_at > value April 4, 2023 19:55pm",
+  "description": "drop event after (timestamp) received_at > value April 4, 2023 19:55pm",
+  "if": "(received_at >= '2023-04-21T19:55:00.933Z')",
+  "actions": [
+    {
+      "type":"DROP"
+    }
+  ],
+  "enabled": true
+}
+```
+
+#### Actions destination
+_Endpoint_: `POST` `https://api.segmentapis.com/destination/actions_destination_id_from_url/filters`
+```
+// JSON BODY :
+{
+  "sourceId": "add_source_id_here",
+  "destinationId": "actions_destination_id_from_url",
+  "title": "drop event before (timestamp) received_at < value April 4, 2023 19:55pm",
+  "description": "drop event before (timestamp) received_at < value April 4, 2023 19:55pm",
+  "if": "(received_at < '2023-04-21T19:55:00.933Z')",
+  "actions": [
+    {
+      "type":"DROP"
+    }
+  ],
+  "enabled": true
+}
+```
+
+After configuring the Destination Filter on both the Classic and Actions destination, see each destination's Filters tab and enable the filters. After completing the migration, you can disable the Classic destination on the Settings page, and remove each of the filters from both destinations.
+
 ## Edit a destination action
 You can add or remove, disable and re-enable, and rename individual actions from the Actions tab on the destination's information page in the Segment app. Click an individual action to edit it.
 

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

@@ -54,7 +54,7 @@ To manually add the Log Purchases Action:
 The Amplitude (actions) destination does not offer a device-mode connection mode. If you're using one of Segment's new libraries ([Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift){:target="_blank”} or [Kotlin](https://github.com/segmentio/analytics-kotlin){:target="_blank”}) with the Actions-framework version of the destination, you do not need the device-mode connection.
 
 
-Most previous deployments of the Amplitude Segment destination used the device-mode connection to use the `session_id` tracking feature. The new Actions-framework Amplitude destination, includes session ID tracking by default. When connected to the Analytics.js 2.0 source, Segment automatically loads a plugin on your website for session tracking and enrichment as an alternative to the Amplitude SDK. This means you don't need to bundle any software to run on the user's device, or write any code. It also means that you can use more of the Segment platform features on data going to Amplitude, such as Protocols filtering and transformations, and Profiles Identity Resolution.
+Most previous deployments of the Amplitude Segment destination used the device-mode connection to use the `session_id` tracking feature. The new Actions-framework Amplitude destination includes session ID tracking by default. When connected to the Analytics.js 2.0 source, Segment automatically loads a plugin on your website for session tracking and enrichment as an alternative to the Amplitude SDK. This means you don't need to bundle any software to run on the user's device, or write any code. It also means that you can use more of the Segment platform features on data going to Amplitude, such as Protocols filtering and transformations, and Profiles Identity Resolution.
 
 Session tracking is available with Segment's new libraries: [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift){:target="_blank”} or [Kotlin](https://github.com/segmentio/analytics-kotlin){:target="_blank”}. 
 

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

@@ -81,7 +81,7 @@ Conversions tracked by other means, such as importing goals from Google Analytic
 
 ### Enhanced conversions for leads
 
-[Enhanced conversions for leads](https://developers.google.com/google-ads/api/docs/conversions/upload-identifiers){:target="_blank"} allows you to use hashed, first-party user-provided data from your website lead forms for offline lead measurement. When you upload your leads, the provided hashed information is used to attribute back to the Google Ad campaign. In order to send enhanced conversions for leads, you can use the "Upload Click Conversion" action. Instead of sending GCLID, send an email address or phone number of the user for Segment to hash and send to Google Ads. 
+[Enhanced conversions for leads](https://developers.google.com/google-ads/api/docs/conversions/upload-identifiers){:target="_blank"} allows you to use hashed, first-party user-provided data from your website lead forms for offline lead measurement. When you upload your leads, the provided hashed information is used to attribute back to the Google Ad campaign. In order to send enhanced conversions for leads, you can use the "Upload Click Conversion" action. If available, include both GCLID and send an email address and phone number of the user for Segment to hash and send to Google Ads. 
 
 ### Refreshing access tokens
 

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

@@ -14,7 +14,7 @@ This destination is maintained by Insider. For any issues with the destination,
 ## Getting started
 
 > info "Prerequisites"
-> Before connecting to the Insider Audiences (Actions) destination, you must have an Insider Account, Account Name, and a [Unified Customer Database API Key](https://academy.useinsider.com/docs/api-authentication-tokens){:target="_blank"}.
+> Before connecting to the [Insider Audiences (Actions) destination](/docs/connections/destinations/catalog/actions-insider-audiences/), you must have an Insider Account, Account Name, and a [Unified Customer Database API Key](https://academy.useinsider.com/docs/api-authentication-tokens){:target="_blank"}.
 
 To add the Insider Audiences Destination:
 

src/connections/destinations/catalog/bing-ads/index.md

@@ -3,24 +3,26 @@ title: Bing Ads Destination
 rewrite: true
 id: 54521fd525e721e32a72ee97
 ---
- [Bing Ads](https://bingads.microsoft.com){:target="_blank"} enables marketers to track and monitor campaigns, clicks, CTRs, spend, and budget. Bing Ads lets you place cross-device product ads in front of Bing, Yahoo, and MSN customers and support imported pay-per-click ad campaigns from third-party platforms like Google AdWords. With Bing Ads you can also re-target ads to customers after they complete an action like leaving a shopping cart or viewing a product without purchasing. Learn more about all you can do with [Bing Ads](https://advertise.bingads.microsoft.com/en-us/resources/training/what-is-bing-ads){:target="_blank"}. You can also [browse the code on GitHub](https://github.com/segment-integrations/analytics.js-integration-bing-ads){:target="_blank"}.
+
+[Bing Ads](https://bingads.microsoft.com){:target="_blank"} enables Marketers to track and monitor campaigns, clicks, CTRs, spend and budget. Bing Ads lets you place cross-device product ads in front of Bing, Yahoo, and MSN customers and support imported pay-per-click ad campaigns from third-party platforms like Google AdWords. With Bing Ads you can also retarget ads to customers after they complete an action like leaving a shopping cart or viewing a product without purchasing. To learn more, see [Bing Ads](https://advertise.bingads.microsoft.com/en-us/resources/training/what-is-bing-ads){:target="_blank"}. You can also browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-bing-ads){:target="_blank"}.
 
 ## Getting started
 
-Before you can track conversions or target audiences, you need to create a UET tag in Bing Ads and then add it to the destination settings. Follow the steps within [the Bing Ads documentation to create a UET tag](https://advertise.bingads.microsoft.com/en-us/resources/training/universal-event-tracking){:target="_blank"}.
+Before you can track conversions or target audiences, create a UET tag in Bing Ads and then add it to the destination settings. Follow the steps within [the Bing Ads documentation to create a UET tag](https://advertise.bingads.microsoft.com/en-us/resources/training/universal-event-tracking){:target="_blank"}.
 
-Once you have created the Tag ID, you can follow the steps below:
+After you have created the Tag ID, follow the steps below:
 
 1. From the Segment web app, click **Catalog**.
-2. Search for "Bing Ads" in the Catalog, select it, and choose which of your sources to connect the destination to. Note the source must be sending events using Segment's JavaScript library Analytics.js.
-3. In the destination settings, enter your Tag Id
+2. Search for "Bing Ads" in the Catalog, select it, and choose which of your sources to connect to the destination. Note that the source must be sending events using Segment's JavaScript library Analytics.js.
+3. In the destination settings, enter your Tag Id.
+
+Your changes will appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Bing Ads snippets on your page and sending data.
 
-> info ""
-> Bing Ads supports one Tag ID per source. Be sure to associate conversion goals to the correct Tag ID in settings.
+_**Note:** You'll only be able to include one Tag ID per source so make sure to associate the conversion goals to the correct Tag ID that is included in your settings._
 
 ## 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:
+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 looks like:
 
 ```javascript
 // name and properties are optional
@@ -33,6 +35,47 @@ Page events will be sent to Bing Ads as a `Page Load` event where name and prope
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does.
 
+For Segment to map your track events to a Conversion Goal, first create the goal on your Bing Ads account:
+
+1. Click the **Campaigns** tab, and then on the left pane, click **Conversion Tracking**.
+2. Under **Conversion Tracking**, click **Conversion Goals**.
+3. On the conversion goals page, click **Create conversion goal**.
+4. Enter a name for your goal in the **Goal name** box. When naming your goal, use a descriptive name that makes sense to you. (For example, "Checkout page")
+5. Choose the `Event` type of conversion and click **Next**.
+6. Fill in the appropriate values. Make sure to add the Segment event name as the **label** field and to associate the goal to the correct Tag (**UET Tag**) that is set up in your Segment source.
+
+## Setting up Custom Events:
+
+### Step 1: Add the UET Tag Tracking Code to Your Website
+
+1. Copy the UET tag from Microsoft Advertising.
+2. Paste the tag into the head or body section of your website's code.
+
+### Step 2: Create a Conversion Goal or Remarketing List
+
+Creating a conversion goal for a custom event:
+
+1. From the top menu, select **Tools > Conversion goals.**
+2. Select the type of conversion you want to track.
+3. Enter a descriptive name for your goal.
+4. Fill in the appropriate values for your selected goal type.
+5. Fine-tune your conversion goal with advanced settings.
+6. Associate the UET tag with the conversion goal.
+
+Creating a remarketing list for a custom event:
+
+In Microsoft Advertising, click **Shared Library > Audiences.**
+Click **Create audience > Remarketing list.**
+For Whom to add to your audience, select **Custom events.**
+Choose the parameters to report when logging custom events.
+Set the membership duration.
+Associate the UET tag with the remarketing list.
+
+### Step 3: Modify the UET Tag Tracking Code in Your Website
+
+1. Add the code for the custom event to the UET tag tracking code.
+2. Follow the instructions provided to set up the event tag on your website.
+
 For Segment to map your track events to a Conversion Goal, create the goal in your Bing Ads account:
 
 For information about tracking custom events, see Microsoft's article [How to track custom events with UET](https://help.ads.microsoft.com/#apex/ads/en/56684/2-500){:target="_blank"}
@@ -56,7 +99,6 @@ analytics.track('Order Completed', {
 | Action   | Always set to `track`                         |
 
 
-
 ## Troubleshooting
 
 {% include content/client-side-script-unverified.md %}

src/connections/destinations/destination-filters.md

@@ -31,7 +31,9 @@ Keep the following limitations in mind when you use destination filters:
 - *(For device-mode)* Destination filters don't filter some fields that are collected by the destination SDK outside of Segment such as `page.url` and `page.referrer`.
 - *(For web device-mode)* Destination filters for web device-mode only supports the Analytics.js 2.0 source. You need to enable device mode destination filters for your Analytics.js source. To do this, go to your Javascript source and navigate to **Settings > Analytics.js** and turn the toggle on for **Destination Filters**.
 - *(For web device-mode)* Destination filters for device-mode only supports the Analytics.js 2.0 source.
-- *(For mobile device-mode)* Destination filters for mobile device-mode doesn't support iOS and Android libraries.
+- *(For mobile device-mode)* Destination filters for mobile device-mode is currenlty not supported.
+- Destination Filters don't apply to events that send through the destination Event Tester.
+- Destination Filters within the UI and [FQL]([url](https://segment.com/docs/api/public-api/fql/)) do not currently support matching on event fields containing '.$' or '.$.', which references fields with an array type. 
 
 [Contact Segment](https://segment.com/help/contact/){:target="_blank"} if these limitations impact your use case.
 

src/connections/functions/source-functions.md

@@ -390,7 +390,7 @@ Copy and paste this URL into the upstream tool or service to send data to this s
 ## OAuth 2.0
 
 > info ""
-> OAuth 2.0 is currently in pilot and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. 
+> OAuth 2.0 is currently in private beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
 
 ## Source function FAQs