Clean up for action destinations

src/_data/catalog/slugs.yml

@@ -232,4 +232,84 @@ destinations:
   - original: "usermaven-actions"
     override: "actions-usermaven"
   - original: "survicate-actions"
-    override: "actions-survicate"
+    override: "actions-survicate"
+  - original: "customer-io-actions"
+    override: "actions-customerio"
+  - original: "braze-cloud-mode-actions"
+    override: "actions-braze-cloud"
+  - original: "braze-web-device-mode-actions"
+    override: "actions-braze-web"
+  - original: "talon-one-actions"
+    override: "actions-talon-one"
+  - original: "criteo-audiences"
+    override: "actions-criteo-audiences"
+  - original: "actable-predictive"
+    override: "actions-actable-predictive"
+  - original: "ripe-device-mode-actions"
+    override: "actions-ripe"
+  - original: "blackbaud-raisers-edge-nxt"
+    override: "actions-blackbaud-raisers-edge-nxt"
+  - original: "google-analytics-4-web"
+    override: "actions-google-analytics-4-web"
+  - original: "gwen-actions"
+    override: "actions-cloud-gwen"
+  - original: "blend-ai"
+    override: "actions-blend-ai"
+  - original: "tiktok-offline-conversions"
+    override: "actions-tiktok-offline-conversions"
+  - original: "userpilot-cloud-actions"
+    override: "actions-userpilot-cloud"
+  - original: "userpilot-web-actions"
+    override: "actions-userpilot-web"
+  - original: "screeb-web-actions"
+    override: "actions-screeb-web"
+  - original: "koala-cloud"
+    override: "actions-koala-cloud"
+  - original: "tiktok-pixel"
+    override: "actions-tiktok-pixel"
+  - original: "gameball-actions"
+    override: "actions-gameball"
+  - original: "pushwoosh"
+    override: "actions-pushwoosh"
+  - original: "acoustic-actions"
+    override: "actions-acoustic"
+  - original: "pendo-web-actions"
+    override: "actions-pendo-web"
+  - original: "delivr-ai-resolve"
+    override: "actions-cdpresolution"
+  - original: "optimizely-data-platform"
+    override: "actions-optimizely-data-platform"
+  - original: "hubble-actions"
+    override: "hubble-web"
+  - original: "jimo-actions"
+    override: "actions-jimo"
+  - original: "linkedin-conversions-api"
+    override: "actions-linkedin-conversions"
+  - original: "kameleoon-actions"
+    override: "actions-kameleoon"
+  - original: "marketo-static-lists-actions"
+    override: "actions-marketo-static-lists"
+  - original: "usermotion-actions"
+    override: "actions-usermotion"
+  - original: "1flow-web-actions"
+    override: "actions-1flow"
+  - original: "gleap-action"
+    override: "gleap-cloud-actions"
+  - original: "equals"
+    override: "actions-equals"
+  - original: "schematic"
+    override: "actions-schematic"
+  - original: "avo"
+    override: "actions-avo"
+  - original: "stackadapt"
+    override: "actions-stackadapt-cloud"
+  - original: "kafka"
+    override: "actions-kafka"
+  - original: "chartmogul"
+    override: "actions-chartmogul"
+  - original: "taboola-actions"
+    override: "actions-taboola-actions"
+  - original: "userguiding"
+    override: "user_guiding"
+  - original: "angler-ai"
+    override: "actions-angler-ai"

src/connections/destinations/catalog/avo/index.md → src/connections/destinations/catalog/actions-avo/index.md

@@ -1,7 +1,6 @@
 ---
 title: Avo Destination
 id: 65c2465d0d7d550aa8e7e5c6
-redirect_from: "/connections/destinations/catalog/actions-avo/"
 ---
 
 **Avo lets you find, fix, and prevent data quality issues upstream.** World class data and product teams at companies like Fender, IKEA, and Wolt use Avo to guarantee event data quality upstream, so they can focus on building great user experiences. With Avo you get reliable data with less effort, by moving from reactive damage control to proactive data management and addressing your data quality issues at the source, where the data is created.

src/connections/destinations/catalog/actions-braze-cloud/index.md

@@ -2,11 +2,16 @@
 title: Braze Cloud Mode (Actions) Destination
 hide-boilerplate: true
 hide-dossier: false
-hidden: true
+id: 60f9d0d048950c356be2e4da
+versions:
+  - name: 'Braze Web Mode (Actions)'
+    link: '/docs/connections/destinations/catalog/braze-web-device-mode-actions/'
+  - name: 'Braze (Classic)'
+    link: '/docs/connections/destinations/catalog/braze'
 ---
 {% include content/plan-grid.md name="actions" %}
 
-[Braze](https://www.braze.com/){:target="_blank”}, formerly Appboy, is an engagement platform that empowers growth by helping marketing teams to build customer loyalty through mobile, omni-channel customer experiences.
+[Braze](https://www.braze.com/){:target="_blank"}, formerly Appboy, is an engagement platform that empowers growth by helping marketing teams to build customer loyalty through mobile, omni-channel customer experiences.
 
 > success ""
 > **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Braze Segment destination. There's also a page about the [non-Actions Braze destination](/docs/connections/destinations/catalog/braze/). Both of these destinations receives data _from_ Segment. There's also the [Braze source](/docs/connections/sources/catalog/cloud-apps/braze//), which sends data _to_ Segment!
@@ -20,22 +25,26 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic:
 ## Getting Started
 
 1. From the Segment web app, click **Catalog**.
-2. Search for "Braze" in the Catalog, select **Braze**, and choose which of your sources to connect the destination to.
-3. Select "Actions" under the Destination framework options.
-4. Add the following Connection Settings:
+2. Search for "Braze" in the Catalog, select **Braze Cloud Mode (Actions)**, and choose which of your sources to connect the destination to.
+3. Add the following Connection Settings:
    - **API Key**: Created under Developer Console in the Braze Dashboard.
    - **App ID**: The app identifier used to reference specific Apps in requests made to the Braze API. Created under Developer Console in the Braze Dashboard.
    - **REST Endpoint**: Your Braze REST Endpoint. For more information, see [API Overview](https://www.braze.com/docs/api/basics/){:target="_blank"} in the Braze documentation.
 
-## Batching data to Braze
-
-You can batch data sent to Braze within Cloud Mode Actions. Batch sizes are capped at 75 events, and these batches will accumulate over a 30-second period before being flushed. Request batching is done per-action mapping. For example, Identify calls (attributes) will be batched in a request, and Track calls (custom events) will be batched in a second request. Braze recommends enabling this feature as it reduces the number of requests being sent from Segment to Braze, reducing the risk of the destination hitting Braze rate limits and retrying requests.
-
-{% include components/actions-fields.html %}
+> info ""
+> Braze requires that you include a `userId` or `braze_id` for all calls made in cloud-mode. Segment sends a `braze_id` if the `userId` is missing. When you use a device-mode connection, Braze automatically tracks anonymous activity using the `braze_id` if a `userId` is missing.
 
+{% include components/actions-fields.html settings="true"%}
 
 ## Migration from Braze Classic
 
 Keep the following in mind if you plan to move to Braze (Actions) from the classic Braze destination.
 {% include components/actions-map-table.html name="braze-cloud" %}
 
+## Troubleshooting
+
+### Missing required fields
+Braze requires one of either `external_id`, `user_alias`, or `braze_id` to be present in all events sent. If events are failing to send, please check your event mappings to make sure these fields are resolving to valid values.
+
+### Missing events
+When an event is sent under an alias, the event may seem to be missing when the alias cannot be found in Braze. This may be due to incorrect search for the alias in Braze. To search for an alias in Braze, use the format "Alias Label:Alias Name". For example, if the "Alias Label" field is set as email and "Alias Name" field is set as email address (for example: "test@email.com"), use "email:test@email.com" to search for the alias in Braze.

src/connections/destinations/catalog/actions-braze-web/index.md

@@ -2,15 +2,19 @@
 title: Braze Web Mode (Actions) Destination
 hide-boilerplate: true
 hide-dossier: false
-hidden: true
+redirect_from:
+  - '/connections/destinations/catalog/vendor-braze/'
+id: 60fb01aec459242d3b6f20c1
+versions:
+  - name: 'Braze Cloud Mode (Actions)'
+    link: '/docs/connections/destinations/catalog/braze-cloud-mode-actions'
+  - name: 'Braze (Classic)'
+    link: '/docs/connections/destinations/catalog/braze'
 ---
 {% include content/plan-grid.md name="actions" %}
 
 [Braze](https://www.braze.com/){:target="_blank"}, formerly Appboy, is an engagement platform that empowers growth by helping marketing teams to build customer loyalty through mobile, omni-channel customer experiences.
 
-> success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Braze Segment destination. There's also a page about the [non-Actions Braze destination](/docs/connections/destinations/catalog/braze/). Both of these destinations receives data _from_ Segment. There's also the [Braze source](/docs/connections/sources/catalog/cloud-apps/braze/), which sends data _to_ Segment.
-
 ## Benefits of Braze Web Mode (Actions) vs Braze Classic
 
 Braze Web Mode (Actions) provides the following benefits over Braze Classic:
@@ -20,12 +24,14 @@ Braze Web Mode (Actions) provides the following benefits over Braze Classic:
 ## Getting Started
 
 1. From the Segment web app, click **Catalog**.
-2. Search for "Braze" in the Catalog, select **Braze**, and choose which of your sources to connect the destination to.
-  - Note that if you do not select a Javascript source, you will not see the option to select the Device mode version of the destination.
-3. Select "Actions" and "Device mode" under the Destination framework and Connection mode options.
-4. Configure the Connection Settings. **API Key** and **SDK Endpoint** are required settings.
+2. Search for "Braze" in the Catalog, select **Braze Web Mode (Actions)**, and choose which of your sources to connect the destination to.
+3. Configure the Connection Settings. **API Key** and **SDK Endpoint** are required settings.
+
+> info ""
+> If you're using a device-mode connection, Braze's SDK assigns a `device_id` and a backend identifier, `braze_id`, to every user. This allows Braze to capture anonymous activity from the device by matching on those identifiers instead of `userId`. This applies to _device-mode connections_.
+
 
-{% include components/actions-fields.html name="braze-web" connection="true" %}
+{% include components/actions-fields.html settings="true"%}
 
 ## Other features
 
@@ -159,11 +165,7 @@ For more details on this snippet, see Braze's documentation [here](https://www.b
 - Braze Web Mode (Actions) supports the Braze [Web](https://github.com/segment-integrations/analytics.js-integration-appboy){:target="_blank"} integration. [Braze Cloud Mode (Actions)](/docs/connections/destinations/catalog/actions-braze-cloud) supports server and mobile sources, but to use mobile sources in device-mode, use the Braze Classic destination.
 
 
-{% include components/actions-fields.html %}
-
-
 ## Migration from Braze Classic
 
 Keep the following in mind if you plan to move to Braze (Actions) from the classic Braze destination.
 {% include components/actions-map-table.html name="braze-web" %}
-

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

@@ -1,9 +1,77 @@
 ---
 title: Criteo Audiences Destination
 hide-personas-partial: true
-hide-boilerplate: false
-hide-dossier: true
-hidden: true
-published: false
+hide-boilerplate: true
+hide-dossier: false
 id: 6238cec53a46dd187d094eb7
----
+redirect_from:
+  - "/connections/destinations/catalog/actions-criteo-audiences" 
+---
+{% include content/plan-grid.md name="actions" %}
+
+Criteo Audiences (Actions) enables advertisers to send Segment Persona Audiences to Criteo using Criteo's Audience API.
+
+By using Segment's Persona Audiences with Criteo, you can increase traffic and drive conversions with hyper-relevant ads that promote product discovery.
+
+## Benefits of Criteo Audiences (Actions)
+
+Benefits of the Criteo Audiences (Actions) destination include:
+- **Improved email matching**: This integration creates a direct connection between Segment and Criteo for a higher match rate of email identifiers. 
+
+
+- **Fewer settings**: Unlike Criteo's Filter destination, this destination doesn't require any copy and paste code. You only need your Advertiser ID and Criteo API credentials.
+
+- **Criteo Audience**: You don't need a Criteo audience ID as the audience gets created on the fly using the Engage audience name. This enables the names of audience segments to be consistent across Segment and Criteo.
+
+- **Batching events and support for large audiences**: This destination supports batching which enables Criteo to receive large audiences without discrepancies.
+
+- **Near real time audience updates**: Actions destination helps Criteo receive real-time events and add or remove users from Criteo audiences appropriately.
+
+## Getting Started
+
+### Prerequisites:
+
+Before connecting to the Criteo Audiences (Actions) destination, you must create a Criteo API Marketing Solutions app to generate your app credentials (client ID and secret) as per the guidelines in [Criteo's Developer's Portal](https://developers.criteo.com/marketing-solutions/docs/onboarding-checklist){:target="_blank"}.
+
+You will also need your Criteo Advertiser ID. Please reach out to your Criteo Account Strategist to get this ID.
+
+### To Add the Criteo Audiences Destination:
+
+1. From your Segment workspace, go to **Connections > Catalog** and click **Destinations**.
+
+2. Search for **Criteo Audiences** in the Destinations Catalog and select the destination.
+
+3. Click **Configure Criteo Audiences**.
+
+4. Select the space in Engage to use as the Source as this destination only supports sending Engage Audiences to Criteo.
+
+5. On the **Settings** tab, name your destination. For example, `Criteo audiences – <audience name>`.
+
+6. Enter your Criteo Advertiser ID, API client ID and client secret.
+
+7. Click **Save Changes**.  
+
+8. In the **Mappings** tab, click **New Mapping** and select **Add Users to Audience**. To hash emails before you send them to Criteo, select **yes** in the **Hash Emails** dropdown. By default, emails are not hashed before you send them to Criteo; however, Criteo will hash the emails before storing them in our system. DO NOT change any other default settings. 
+
+9. Under the **Configure actions fields**, set **Enable Batching** to *Yes* and click **Save**.  
+
+7. Repeat steps 8 and 9 for **Remove Users from Audience**.
+
+8. **Enable** both mappings.
+
+9. Go to the **Settings** tab and **Enable** the destination.
+
+10. Select your space, and navigate to **Engage > Audiences**. Select the source audience that you want to send to your Criteo Audiences destination.
+
+11. Click **Add Destinations** and select the Criteo Audience destination you created. In the settings that appear on the right-hand side, toggle the **Send Track** option on and disable **Send Identify**. Click **Save**. 
+
+Your Criteo destination is now ready to receive audiences, and your Persona audiences now reflect in your Criteo Advertiser dashboard. Be aware, it takes 12-24 hours for the number of identifiers to populate in Criteo's Management Center.
+
+> warning ""
+> You can connect **ONE** Engage audience to a single instance of Criteo Audience destination. If you have multiple audiences, repeat the above process to create a new Criteo audience destination and connect the audience to new destination each time.
+
+{% include components/actions-fields.html %}
+
+## Legacy Destination
+
+Please discontinue use of the legacy Criteo destination. Follow the steps above to define your Segment Persona Audiences to be sent to Criteo.

src/connections/destinations/catalog/customer-io-actions/index.md → src/connections/destinations/catalog/actions-customerio/index.md

@@ -3,8 +3,6 @@ title: Customer.io (Actions) Destination
 hide-personas-partial: true
 hide-boilerplate: true
 redirect_from:
-- '/connections/destinations/catalog/actions-customerio/'
-- '/connections/destinations/catalog/actions-customer-io/'
 - '/connections/destinations/catalog/vendor-customerio'
 versions:
   - name: Customer.io (Classic)

src/connections/destinations/catalog/actions-gwen-cloud/index.md

@@ -3,8 +3,6 @@ title: GWEN (Actions) Destination
 hide-boilerplate: true
 hide-dossier: false
 id: 6411f979382d3759292d739f
-redirect_from:
-  - "/connections/destinations/catalog/actions-cloud-gwen"
 ---
 
 {% include content/plan-grid.md name="actions" %}