Merge remote-tracking branch 'upstream/develop' into develop

Author: lopenchi

src/_includes/content/reset-mobile.md

@@ -1,6 +1,2 @@
-<div class="premonition info">
-  <div class="fa fa-info-circle"></div>
-  <div class="content">
-    <p>The reset method doesn't clear the `userId` from connected client-side integrations. If you want to clear the `userId` from connected client-side destination plugins, you'll need to call the equivalent reset method for that library.</p>
-  </div>
-</div>
+> info ""
+> The reset method doesn't clear the `userId` from connected client-side integrations. If you want to clear the `userId` from connected client-side destination plugins, you'll need to call the equivalent reset method for that library.

src/_includes/content/syntax-note.md

@@ -1 +1,2 @@
-<div class="premonition info"><div class="fa fa-info-circle"></div><div class="content"> <p markdown=1>Based on the library you use, the syntax in the examples might be different. You can find library-specific documentation on the [Sources Overview](/docs/connections/sources/) page.</p></div></div>
+> info ""
+> Based on the library you use, the syntax in the examples might be different. You can find library-specific documentation on the [Sources Overview](/docs/connections/sources/) page.

src/connections/destinations/catalog/actions-ms-bing-ads-audiences/index.md

@@ -0,0 +1,23 @@
+---
+title: Microsoft Bing Ads Audiences Destination
+id: 68bff47aa7bba4dd200b450a
+beta: true
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Microsoft Bing Ads Audiences](https://ui.ads.microsoft.com//?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} lets you sync Segment audience data to Microsoft Advertising's Customer match lists. This enables real-time or batch audience updates using Microsoft Advertising's Customer Management and Bulk APIs. You can use this destination to keep your audience targeting lists up to date across Microsoft platforms.
+
+## Getting started
+
+1. From your workspace's [destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Ms Bing Ads Audiences".
+2. Select Ms Bing Ads Audiences and click **Add destination**.
+3. Select an existing source to connect to the destination.
+4. Give the destination a name and click **Create destination**.
+5. Connect your Microsoft account. Grant Segment permissions to access your Microsoft account (you can disconnect this later). 
+6. In **Basic Settings**, enter the **Customer Account ID** and **Customer ID**.
+7. Go to the **Mappings** tab to configure the mappings settings.
+8. Toggle **Enable Destination** on to activate the integration. 
+
+{% include components/actions-fields.html %}
+

src/connections/destinations/catalog/actions-ms-bing-capi/index.md

@@ -0,0 +1,23 @@
+---
+title: Microsoft Bing CAPI Destination
+id: 68b82be249b48bae343517c7a
+beta: true
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Microsoft Bing Conversions API (CAPI)](https://ui.ads.microsoft.com//?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} lets you send offline conversion data from Segment to Microsoft Advertising. This enables enhanced customer attribution data and supports cross-device and cross-platform conversion attribution. You can use this destination to track offline actions, such as in-store purchases driven by ad clicks, and attribute them to your Microsoft Ads campaigns. 
+
+## Getting started
+
+1. From your workspace's [destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Microsoft Bing CAPI".
+2. Select Microsoft Bing CAPI and click **Add destination**.
+3. Select an existing source to connect to the destination.
+4. Give the destination a name and click **Create destination**.
+5. In **Basic Settings**, enter the Bing **UetTag** and **ApiToken**.
+    > * To find the UET tag, see Microsoft's steps on [how to create a UET tag](https://help.ads.microsoft.com/#apex/3/en/56682/2-500){:target="_blank"}. 
+    > * To generate the API token, contact [Microsoft support](https://about.ads.microsoft.com/en/support){:target="_blank"} or fill out a [request form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbRwMZAe0PcMxHmZ0AjDaNRmxUM0o5UURRVktCRkxHNEFLTVNYQjI3NDNBUS4u){:target="_blank"}.
+6. Toggle **Enable Destination** on to start sending data to Microsoft Bing CAPI from Segment.
+
+{% include components/actions-fields.html %}
+

src/connections/functions/insert-functions.md

@@ -563,6 +563,10 @@ async function onGroup(event, settings) {
 ```
 By including handlers for all the major event types, you ensure that all supported events are processed correctly, preventing the "Unsupported Event Type" error. Always test your updated code before implementing it in production.
 
+##### What destination types support Insert Functions?
+
+Only cloud-mode [event destinations](/docs/engage/using-engage-data/#engage-destination-types-event-vs-list) support destination Insert Functions. [List destinations](/docs/engage/using-engage-data/#list-destinations) aren't compatible. 
+
 {% comment %}
 
 ## Using Segment's Public API

src/connections/sources/catalog/libraries/mobile/apple/implementation.md

@@ -373,4 +373,4 @@ let analytics = Analytics(configuration: config)
 ```
 
 ## Changelog
-[View the Analytics Swift changelog on GitHub](https://github.com/segmentio/analytics-swift/releases){:target="_blank"}.   -->
+[View the Analytics Swift changelog on GitHub](https://github.com/segmentio/analytics-swift/releases){:target="_blank"}.  ->

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

@@ -461,7 +461,7 @@ To set up automatic screen tracking with React Navigation:
       }
     }}
     >
-  ```
+    ```
 
 ### React Native Navigation
 To set up automatic screen tracking while using [React Native Navigation](https://wix.github.io/react-native-navigation/docs/before-you-start/){:target="_blank"}:
@@ -653,7 +653,7 @@ To get started with destination filters on mobile device-mode destinations using
 
     segmentClient.add({ plugin: new DestinationFiltersPlugin() });
     segment.add({ plugin: new FirebasePlugin() })
-    ``` -->
+    ```
 
 ## Supported destinations
 Segment supports a large number of [cloud-mode](/docs/connections/destinations/#connection-modes) destinations. Segment also supports the following destinations for Analytics React Native 2.0 in device-mode:

src/connections/sources/catalog/libraries/server/node/index.md

@@ -404,7 +404,7 @@ const onExit = async () => {
 ```
 
 ### Collect unflushed events 
-If you need to preserve all of your events in the instance of a forced timeout, even ones that came in after analytics.flush({ close: true }) was called, you can still collect those events by using:
+If you need to preserve all of your events in the instance of a forced timeout, even ones that came in after `analytics.flush({ close: true })` was called, you can still collect those events by using:
 
 ```javascript
 const unflushedEvents = []

src/connections/sources/catalog/libraries/website/javascript/quickstart.md

@@ -111,12 +111,10 @@ To do that, Segment recommends that you use a backend template to inject an Iden
 Depending on your templating language, your actual Identify call might look something like this:
 
 ```js
-{% raw %}
 analytics.identify(' {{user.id}} ', {
   name: '{{user.fullname}}',
   email: '{{user.email}}'
 });
-{% endraw %}
 ```
 
 With that call in your page footer, you successfully identify every user that visits your site.

src/connections/sources/custom-domain.md

@@ -15,10 +15,10 @@ Custom Domain is a fully-managed service that enables you to configure a first-p
 
 {% include content/domain-delegation-solutions.md %}
 
-### How DNS subdomain delegation works
+## How DNS subdomain delegation works
 DNS subdomain delegation is a process where the control of a specific subdomain is assigned to another DNS server, allowing that server to manage the DNS records for the subdomain. This delegation is useful for distributing the management of DNS records and enables specialized handling of subdomain traffic.
 
-### How CNAME records work
+## How CNAME records work
 When a user tries to access the alias domain, the DNS resolver looks up the CNAME record, finds the canonical name, and resolves it to the IP address of the target. For example, you could alias your subdomain to point to the Segment domain. If a user accesses your site, they are redirected to the Segment domain, but their browser's address bar still shows the alias domain.
 
 CNAME records provide flexibility and centralized management, making it easier to handle domain redirections and subdomain configurations.