From 8db07f57f191aeacff06a80adaf2e7b370985298 Mon Sep 17 00:00:00 2001 From: Thomas Gilbert Date: Mon, 5 Aug 2024 12:24:10 -0400 Subject: [PATCH 1/3] correct all actions destinations to use the correct slugs --- src/_data/catalog/slugs.yml | 78 +++++++- .../catalog/1flow-web-actions/index.md | 7 - .../index.md | 0 .../{avo => actions-avo}/images/api-key.png | Bin .../images/avo-destination.png | Bin .../images/issue-sidebar.png | Bin .../images/select-source.png | Bin .../catalog/{avo => actions-avo}/index.md | 1 - .../index.md | 0 .../catalog/actions-braze-cloud/index.md | 29 ++- .../catalog/actions-braze-web/index.md | 28 +-- .../catalog/actions-criteo-audiences/index.md | 78 +++++++- .../catalog/actions-customer-io/index.md | 7 - .../index.md | 2 - .../catalog/actions-gwen-cloud/index.md | 2 - .../index.md | 0 .../index.md | 0 .../catalog/actions-talon-one/index.md | 110 ++++++++++- .../index.md | 2 +- .../index.md | 0 .../destinations/catalog/blend-ai/index.md | 9 - .../catalog/braze-cloud-mode-actions/index.md | 52 ------ .../braze-web-device-mode-actions/index.md | 172 ------------------ .../catalog/criteo-audiences/index.md | 77 -------- .../destinations/catalog/equals/index.md | 7 - .../catalog/gleap-action/index.md | 7 - .../catalog/google-analytics-4-web/index.md | 7 - .../catalog/gwen-actions/index.md | 9 - .../catalog/hubble-actions/index.md | 7 - .../catalog/linkedin-conversion-tag/index.md | 12 -- .../catalog/pendo-web-actions/index.md | 7 - .../catalog/ripe-cloud-mode-actions/index.md | 7 - .../catalog/screeb-web-actions/index.md | 7 - .../destinations/catalog/stackadapt/index.md | 43 ----- .../catalog/talon-one-actions/index.md | 112 ------------ .../tiktok-offline-conversions/index.md | 7 - .../catalog/tiktok-pixel/index.md | 7 - 37 files changed, 291 insertions(+), 602 deletions(-) delete mode 100644 src/connections/destinations/catalog/1flow-web-actions/index.md rename src/connections/destinations/catalog/{actable-predictive => actions-actable-predictive}/index.md (100%) rename src/connections/destinations/catalog/{avo => actions-avo}/images/api-key.png (100%) rename src/connections/destinations/catalog/{avo => actions-avo}/images/avo-destination.png (100%) rename src/connections/destinations/catalog/{avo => actions-avo}/images/issue-sidebar.png (100%) rename src/connections/destinations/catalog/{avo => actions-avo}/images/select-source.png (100%) rename src/connections/destinations/catalog/{avo => actions-avo}/index.md (98%) rename src/connections/destinations/catalog/{blackbaud-raisers-edge-nxt => actions-blackbaud-raisers-edge-nxt}/index.md (100%) delete mode 100644 src/connections/destinations/catalog/actions-customer-io/index.md rename src/connections/destinations/catalog/{customer-io-actions => actions-customerio}/index.md (96%) rename src/connections/destinations/catalog/{optimizely-data-platform => actions-optimizely-data-platform}/index.md (100%) rename src/connections/destinations/catalog/{actions-ripe-web => actions-ripe}/index.md (100%) rename src/connections/destinations/catalog/{userpilot-cloud-actions => actions-userpilot-cloud}/index.md (99%) rename src/connections/destinations/catalog/{userpilot-web-actions => actions-userpilot-web}/index.md (100%) delete mode 100644 src/connections/destinations/catalog/blend-ai/index.md delete mode 100644 src/connections/destinations/catalog/braze-cloud-mode-actions/index.md delete mode 100644 src/connections/destinations/catalog/braze-web-device-mode-actions/index.md delete mode 100644 src/connections/destinations/catalog/criteo-audiences/index.md delete mode 100644 src/connections/destinations/catalog/equals/index.md delete mode 100644 src/connections/destinations/catalog/gleap-action/index.md delete mode 100644 src/connections/destinations/catalog/google-analytics-4-web/index.md delete mode 100644 src/connections/destinations/catalog/gwen-actions/index.md delete mode 100644 src/connections/destinations/catalog/hubble-actions/index.md delete mode 100644 src/connections/destinations/catalog/linkedin-conversion-tag/index.md delete mode 100644 src/connections/destinations/catalog/pendo-web-actions/index.md delete mode 100644 src/connections/destinations/catalog/ripe-cloud-mode-actions/index.md delete mode 100644 src/connections/destinations/catalog/screeb-web-actions/index.md delete mode 100644 src/connections/destinations/catalog/stackadapt/index.md delete mode 100644 src/connections/destinations/catalog/talon-one-actions/index.md delete mode 100644 src/connections/destinations/catalog/tiktok-offline-conversions/index.md delete mode 100644 src/connections/destinations/catalog/tiktok-pixel/index.md diff --git a/src/_data/catalog/slugs.yml b/src/_data/catalog/slugs.yml index ad61a11647..f7201dcf7d 100644 --- a/src/_data/catalog/slugs.yml +++ b/src/_data/catalog/slugs.yml @@ -232,4 +232,80 @@ destinations: - original: "usermaven-actions" override: "actions-usermaven" - original: "survicate-actions" - override: "actions-survicate" \ No newline at end of file + 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" diff --git a/src/connections/destinations/catalog/1flow-web-actions/index.md b/src/connections/destinations/catalog/1flow-web-actions/index.md deleted file mode 100644 index 3d8000dd5e..0000000000 --- a/src/connections/destinations/catalog/1flow-web-actions/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: '1Flow Web (Actions) Destination' -hidden: true -id: 656773f0bd79a3676ab2733d -published: false -beta: true ---- diff --git a/src/connections/destinations/catalog/actable-predictive/index.md b/src/connections/destinations/catalog/actions-actable-predictive/index.md similarity index 100% rename from src/connections/destinations/catalog/actable-predictive/index.md rename to src/connections/destinations/catalog/actions-actable-predictive/index.md diff --git a/src/connections/destinations/catalog/avo/images/api-key.png b/src/connections/destinations/catalog/actions-avo/images/api-key.png similarity index 100% rename from src/connections/destinations/catalog/avo/images/api-key.png rename to src/connections/destinations/catalog/actions-avo/images/api-key.png diff --git a/src/connections/destinations/catalog/avo/images/avo-destination.png b/src/connections/destinations/catalog/actions-avo/images/avo-destination.png similarity index 100% rename from src/connections/destinations/catalog/avo/images/avo-destination.png rename to src/connections/destinations/catalog/actions-avo/images/avo-destination.png diff --git a/src/connections/destinations/catalog/avo/images/issue-sidebar.png b/src/connections/destinations/catalog/actions-avo/images/issue-sidebar.png similarity index 100% rename from src/connections/destinations/catalog/avo/images/issue-sidebar.png rename to src/connections/destinations/catalog/actions-avo/images/issue-sidebar.png diff --git a/src/connections/destinations/catalog/avo/images/select-source.png b/src/connections/destinations/catalog/actions-avo/images/select-source.png similarity index 100% rename from src/connections/destinations/catalog/avo/images/select-source.png rename to src/connections/destinations/catalog/actions-avo/images/select-source.png diff --git a/src/connections/destinations/catalog/avo/index.md b/src/connections/destinations/catalog/actions-avo/index.md similarity index 98% rename from src/connections/destinations/catalog/avo/index.md rename to src/connections/destinations/catalog/actions-avo/index.md index 2afc044138..95d8878de4 100644 --- a/src/connections/destinations/catalog/avo/index.md +++ b/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. diff --git a/src/connections/destinations/catalog/blackbaud-raisers-edge-nxt/index.md b/src/connections/destinations/catalog/actions-blackbaud-raisers-edge-nxt/index.md similarity index 100% rename from src/connections/destinations/catalog/blackbaud-raisers-edge-nxt/index.md rename to src/connections/destinations/catalog/actions-blackbaud-raisers-edge-nxt/index.md diff --git a/src/connections/destinations/catalog/actions-braze-cloud/index.md b/src/connections/destinations/catalog/actions-braze-cloud/index.md index 29ef730c8f..e9cf33ac82 100644 --- a/src/connections/destinations/catalog/actions-braze-cloud/index.md +++ b/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. diff --git a/src/connections/destinations/catalog/actions-braze-web/index.md b/src/connections/destinations/catalog/actions-braze-web/index.md index a1e3f46a3f..e4422499d0 100644 --- a/src/connections/destinations/catalog/actions-braze-web/index.md +++ b/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" %} - diff --git a/src/connections/destinations/catalog/actions-criteo-audiences/index.md b/src/connections/destinations/catalog/actions-criteo-audiences/index.md index 2142cc9629..d149042adc 100644 --- a/src/connections/destinations/catalog/actions-criteo-audiences/index.md +++ b/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 ---- \ No newline at end of file +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 – `. + +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. diff --git a/src/connections/destinations/catalog/actions-customer-io/index.md b/src/connections/destinations/catalog/actions-customer-io/index.md deleted file mode 100644 index 2ef7806761..0000000000 --- a/src/connections/destinations/catalog/actions-customer-io/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: Customer.io (Actions) Destination -hide-personas-partial: true -hide-boilerplate: false -hide-dossier: true -published: false ---- diff --git a/src/connections/destinations/catalog/customer-io-actions/index.md b/src/connections/destinations/catalog/actions-customerio/index.md similarity index 96% rename from src/connections/destinations/catalog/customer-io-actions/index.md rename to src/connections/destinations/catalog/actions-customerio/index.md index 15a9f54114..46dffe8120 100644 --- a/src/connections/destinations/catalog/customer-io-actions/index.md +++ b/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) diff --git a/src/connections/destinations/catalog/actions-gwen-cloud/index.md b/src/connections/destinations/catalog/actions-gwen-cloud/index.md index 3b79f288af..40c9e636e1 100644 --- a/src/connections/destinations/catalog/actions-gwen-cloud/index.md +++ b/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" %} diff --git a/src/connections/destinations/catalog/optimizely-data-platform/index.md b/src/connections/destinations/catalog/actions-optimizely-data-platform/index.md similarity index 100% rename from src/connections/destinations/catalog/optimizely-data-platform/index.md rename to src/connections/destinations/catalog/actions-optimizely-data-platform/index.md diff --git a/src/connections/destinations/catalog/actions-ripe-web/index.md b/src/connections/destinations/catalog/actions-ripe/index.md similarity index 100% rename from src/connections/destinations/catalog/actions-ripe-web/index.md rename to src/connections/destinations/catalog/actions-ripe/index.md diff --git a/src/connections/destinations/catalog/actions-talon-one/index.md b/src/connections/destinations/catalog/actions-talon-one/index.md index 99dc5e243e..1c1f950059 100644 --- a/src/connections/destinations/catalog/actions-talon-one/index.md +++ b/src/connections/destinations/catalog/actions-talon-one/index.md @@ -1,8 +1,110 @@ --- -title: Talon.One (Action) Destination +title: 'Talon.One (Actions) Destination' hide-boilerplate: true hide-dossier: false -published: false -id: +id: 6234b137d3b6404a64f2a0f0 --- -content moved to `/talon-one-actions` \ No newline at end of file + + + +{% include content/plan-grid.md name="actions" %} + +Create flexible and targeted promotional and loyalty campaigns with [Talon.One](https://www.talon.one/){:target="_blank"}. +Campaigns can be created and managed by non-technical users like marketers. There is no need to +get your development team involved. Features include coupons, discounts, loyalty +programs, referral tracking, geofencing, and bundling. + +This destination is maintained by Talon.One. For any issues with the destination, [contact the Talon.One Support team](mailto:support@talon.one) or refer to [Talon.One's documentation](https://docs.talon.one/docs/dev/technology-partners/segment){:target="_blank"}. + + +> success "" +> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Talon.One Segment destination. There's also a page about the [non-Actions Talon.One destination](/docs/connections/destinations/catalog/talonone/). Both of these destinations receive data from Segment. + +## Benefits of Talon.One (Actions) vs Talon.One Classic + +Talon.One (Actions) allows you to share more data than the classic destination. +The classic version only shares customer profile data. The Action version supports sharing the following data: + +- Customer profile data +- Audience data +- Tracking events + + + +## Getting started + +### Creating an API key in Talon.One + +Segment needs a Talon.One-generated API key to be able to send data to your Talon.One Application. To generate an API key specific to Segment: + +1. Open your Talon.One Application in the Campaign Manager and click **Settings > Developer settings**. +1. Click **Create API Key**. +1. For **Do you want to use this API Key with a 3rd party service**, select **Yes**. +1. Select **Segment** from the dropdown. +1. Select an expiry date and click **Create API Key**. +1. Copy it for later use. + +> info "Talon.One API Rate Limit" +> Talon.One limits integrations with Segment to 60 requests per second for any given client, regardless of the endpoint. To increase this limit, contact Talon.One. + +### Adding a Talon.One destination + +To start sending data to Talon.One from Segment, create a Talon.One +[destination](/docs/connections/destinations/) in Segment. + +1. In Segment, click **Destinations** > **Add Destination**. The **Destination catalog** opens. +1. Search for **Talon.one** and configure the destination. +1. Enter the details: + - In **Name**, type a name, for example `Talon.One destination`. + - In **API key**, paste the API key generated in the previous section. + - In **Deployment**, type the URI of your Talon.One deployment, for example + `https://mycompany.europe-west1.talon.one/`. +1. (Optional) Set up your filters. +1. Configure the mapping: + 1. Click **New Mapping** and select the type of action to perform in Talon.One. + For example _When a new audience is created in Segment, also create it in Talon.One._ + 1. Configure the trigger and action fields. +1. Click **Event Tester** and test if you received the data in Talon.One. + +Once you receive data, you can start creating rules that rely on that data. + +> warning "" +> **Important**: You might need to create custom attributes in Talon.One to be able to map the data from Segment in Talon.One. See the [Talon.One docs](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#creating-custom-attributes){:target="_blank"}. + +### Testing the integration + +You can use the following payloads to test and fine-tune your requests. + +```json +{ + "messageId": "segment-test-message-t1kx8e", + "timestamp": "2022-03-22T12:41:20.918Z", + "type": "track", // or any other type in Segment + "userId": "test-user-z65zqk", + "event": "track-event", // or any other event in Segment + "email": "test@example.org", + "projectId": "qR6APLKpCBB3ue8pHkBLpo", + "properties": { + "eventType": "mySegmentEvent", + "type": "boolean", + "customerProfileId": "a_customer_id", + "attributes": { + "language": "English" // depends your custom attributes in Talon.One + } + } +} +``` + +### Next steps + +Once you receive data from Segment inside Talon.One, start creating your rules in the Campaign Manager. See the [Talon.One documentation](https://docs.talon.one/docs/product/rules/overview){:target="_blank"}. + + +{% include components/actions-fields.html %} + + +## Migration from the classic Talon.One destination + +To prevent duplicate events being created in Talon.One, ensure that for each Segment source, this destination and the classic Talon.One destination are not both enabled at the same time. + + diff --git a/src/connections/destinations/catalog/userpilot-cloud-actions/index.md b/src/connections/destinations/catalog/actions-userpilot-cloud/index.md similarity index 99% rename from src/connections/destinations/catalog/userpilot-cloud-actions/index.md rename to src/connections/destinations/catalog/actions-userpilot-cloud/index.md index cf95931350..4e8ad75ee9 100644 --- a/src/connections/destinations/catalog/userpilot-cloud-actions/index.md +++ b/src/connections/destinations/catalog/actions-userpilot-cloud/index.md @@ -41,4 +41,4 @@ If you experience any issues while setting up Userpilot as a destination, follow - Check your Userpilot API Key. Make sure it's correctly entered in Segment. - Verify that you've enabled Userpilot as a destination in Segment. -- If you're still having trouble, [contact Segment's support team](https://segment.com/help/contact/){:target="_blank"} for further assistance. \ No newline at end of file +- If you're still having trouble, [contact Segment's support team](https://segment.com/help/contact/){:target="_blank"} for further assistance. diff --git a/src/connections/destinations/catalog/userpilot-web-actions/index.md b/src/connections/destinations/catalog/actions-userpilot-web/index.md similarity index 100% rename from src/connections/destinations/catalog/userpilot-web-actions/index.md rename to src/connections/destinations/catalog/actions-userpilot-web/index.md diff --git a/src/connections/destinations/catalog/blend-ai/index.md b/src/connections/destinations/catalog/blend-ai/index.md deleted file mode 100644 index ea67fb3b9d..0000000000 --- a/src/connections/destinations/catalog/blend-ai/index.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Blend Ai Destination -hidden: false -id: 64244158b33d1380a79dc85c -published: false -beta: true -private: false - ---- diff --git a/src/connections/destinations/catalog/braze-cloud-mode-actions/index.md b/src/connections/destinations/catalog/braze-cloud-mode-actions/index.md deleted file mode 100644 index 0cd30764e2..0000000000 --- a/src/connections/destinations/catalog/braze-cloud-mode-actions/index.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Braze Cloud Mode (Actions) Destination -hide-boilerplate: true -hide-dossier: false -redirect_from: - - '/connections/destinations/catalog/actions-braze-cloud/' -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. - -> 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 Cloud Mode (Actions) vs Braze Classic - -Braze Cloud Mode (Actions) provides the following benefit over Braze Classic: - -- **E-commerce mappings**. Segment implementations that don't follow the e-commerce spec due to incompatible event names (for example, Trip Booked vs Order Completed) can use Event Triggers to log purchases in Braze Cloud Mode (Actions). - -## Getting Started - -1. From the Segment web app, click **Catalog**. -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. - -> 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. diff --git a/src/connections/destinations/catalog/braze-web-device-mode-actions/index.md b/src/connections/destinations/catalog/braze-web-device-mode-actions/index.md deleted file mode 100644 index 921224d8a7..0000000000 --- a/src/connections/destinations/catalog/braze-web-device-mode-actions/index.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -title: Braze Web Mode (Actions) Destination -hide-boilerplate: true -hide-dossier: false -redirect_from: - - '/connections/destinations/catalog/actions-braze-web/' - - '/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. - -## Benefits of Braze Web Mode (Actions) vs Braze Classic - -Braze Web Mode (Actions) provides the following benefits over Braze Classic: - -- **E-commerce mappings**. Users who can't follow the e-commerce spec due to incompatible event names (for example, Trip Booked vs Order Completed) can log purchases in Braze Web Mode (Actions). - -## Getting Started - -1. From the Segment web app, click **Catalog**. -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 settings="true"%} - -## Other features - -Braze Web Mode (Actions) can use the following features of Braze. - -### In-app Messaging - -Once configured, you can trigger in-app message display as a result of several different event types. By default, all In-App Messages that a user is eligible for are automatically delivered to the user upon a session start event. A new session automatically starts when a user loads your site. If you'd like to force a new session for a user, make an Identify call with the corresponding [userId](/docs/connections/spec/identify/#user-id) for that user. - -If you don't want your site to display new In-App Messages as they're received, disable automatic display and register your own display subscribers. To do this: - -Create your subscriber by calling: - -```js -analytics.ready(function() { - window.appboy.subscribeToNewInAppMessages(function(inAppMessages) { - // Display the first in-app message. You could defer display here by pushing this message to code within in your own application. - // If you don't want to use Appboy's built-in display capabilities, you could alternatively pass the in-app message to your own display code here. - window.appboy.display.showInAppMessage(inAppMessages[0]); - - // Return an array with any remaining, unhandled messages to appboy's internal queue. - // These will be part of the inAppMessages param the next time this subscriber is invoked. - return inAppMessages.slice(1); - }); -}); -``` - -The `inAppMessages` parameter will be an array of [`appboy.ab.InAppMessage`](https://js.appboycdn.com/web-sdk/latest/doc/ab.InAppMessage.html){:target="_blank"} subclass or [`appboy.ab.ControlMessage`](https://js.appboycdn.com/web-sdk/latest/doc/ab.ControlMessage.html){:target="_blank"} objects, each of which has various lifecycle event subscription methods. - - - -### Push Notifications - -1. To support push notifications on Chrome, you'll need to enable FCM/GCM as well as configure your site. Check out steps [one and two here for detailed instructions on both](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/initial_sdk_setup#step-1-to-support-chrome-enable-fcmgcm){:target="_blank"}. - -2. Browser Registration. In order for a browser to receive push notifications, you must register it for push by calling: - - ```js - analytics.ready(function() { - window.appboy.registerAppboyPushMessages(); - }); - ``` - - **Note:** Place this snippet outside of your [Segment Snippet](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-copy-the-segment-snippet) within your `script` tag. - - **Note:** This requests push permission from the user. - -To show your own push-related UI to the user before requesting push permission (known as a soft push prompt), you can test to see if the user's browser supports push by calling: - -```js -analytics.ready(function() { - if (window.appboy.isPushSupported()) { - // Add your push logic - } - }); -``` - -Braze recommends checking to see if this returns `true` since not all browsers can receive push notifications. See [Soft Push Prompts](#soft-push-prompts) for instructions on setting up a soft push prompt using Braze In-App Messages. - -To unsubscribe a user, call: - -```js -analytics.ready(function() { - window.appboy.unregisterAppboyPushMessages(); -}); -``` - -1. Set your GCM/FCM server API key and SenderID on the Braze dashboard. You can find more details for this [here](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/initial_sdk_setup#step-4-set-your-gcmfcm-server-api-key-and-senderid-on-the-Braze-dashboard){:target="_blank"}. - -2. To support push notifications on Safari, add your Website Push ID into your Segment Settings UI and Segment sends it when the Braze Web SDK initializes. To get your Website Push ID, follow the first two bullet points in [these instructions](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/initial_sdk_setup#step-5-configure-safari-push){:target="_blank"}. - -### Soft Push Prompts - -1. Follow [step one](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/initial_sdk_setup#soft-push-prompts){:target="_blank"} to create a "Prime for Push" in-app messaging Campaign on the Braze dashboard. - -2. Add the following snippet to your site: - -```js -analytics.ready(function() { - window.appboy.subscribeToNewInAppMessages(function(inAppMessages) { - var message = inAppMessages[0]; - if (message != null) { - var shouldDisplay = true; - - if (message instanceof appboy.ab.inAppMessage) { - // Read the key/value pair for msg-id - var msgId = message.extras["msg-id"]; - - // If this is our push primer message - if (msgId == "push-primer") { - // We don't want to display the soft push prompt to users on browsers that don't support push, or if the user - // has already granted/blocked permission - if (!appboy.isPushSupported() || appboy.isPushPermissionGranted() || appboy.isPushBlocked()) { - shouldDisplay = false; - } - // Prompt the user when the first button is clicked - message.buttons[0].subscribeToClickedEvent(function() { - appboy.registerAppboyPushMessages(); - }); - } - } - - // Display the message - if (shouldDisplay) { - appboy.display.showInAppMessage(message); - } - } - - // Remove this message from the array of IAMs and return whatever's left - return inAppMessages.slice(1); - }); - }); -``` - -For more details on this snippet, see Braze's documentation [here](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/initial_sdk_setup#soft-push-prompts){:target="_blank"}. - -> info "" -> Place this snippet outside of your [Segment Snippet](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-copy-the-segment-snippet) within your `script` tag. - -1. When you'd like to display the Soft Push to a user, call: - -```js - analytics.ready(function() { - window.appboy.logCustomEvent("prime-for-push") - }); -``` - - - -## Important differences from the classic Braze destination -- 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. - - -## 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" %} diff --git a/src/connections/destinations/catalog/criteo-audiences/index.md b/src/connections/destinations/catalog/criteo-audiences/index.md deleted file mode 100644 index d149042adc..0000000000 --- a/src/connections/destinations/catalog/criteo-audiences/index.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Criteo Audiences Destination -hide-personas-partial: true -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 – `. - -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. diff --git a/src/connections/destinations/catalog/equals/index.md b/src/connections/destinations/catalog/equals/index.md deleted file mode 100644 index 51de0ce704..0000000000 --- a/src/connections/destinations/catalog/equals/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'Equals Destination' -hidden: true -id: 659eb6903c4d201ebd9e2f5c -published: false -beta: true ---- diff --git a/src/connections/destinations/catalog/gleap-action/index.md b/src/connections/destinations/catalog/gleap-action/index.md deleted file mode 100644 index 64a001993e..0000000000 --- a/src/connections/destinations/catalog/gleap-action/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'Gleap (Action) Destination' -hidden: true -id: 656f2474a919b7e6e4900265 -published: false -beta: true ---- diff --git a/src/connections/destinations/catalog/google-analytics-4-web/index.md b/src/connections/destinations/catalog/google-analytics-4-web/index.md deleted file mode 100644 index 0baa123cad..0000000000 --- a/src/connections/destinations/catalog/google-analytics-4-web/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'Google Analytics 4 Web Destination' -hidden: true -id: 63ed446fe60a1b56c5e6f130 -published: false -beta: true ---- diff --git a/src/connections/destinations/catalog/gwen-actions/index.md b/src/connections/destinations/catalog/gwen-actions/index.md deleted file mode 100644 index 170cf7a545..0000000000 --- a/src/connections/destinations/catalog/gwen-actions/index.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: GWEN (Actions) Destination -hidden: false -id: 6411f979382d3759292d739f -published: false -beta: true -private: false - ---- diff --git a/src/connections/destinations/catalog/hubble-actions/index.md b/src/connections/destinations/catalog/hubble-actions/index.md deleted file mode 100644 index 8fed5c1b80..0000000000 --- a/src/connections/destinations/catalog/hubble-actions/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'Hubble (Actions) Destination' -hidden: true -id: 651aac880f2c3b5a8736e0cc -published: false -beta: true ---- diff --git a/src/connections/destinations/catalog/linkedin-conversion-tag/index.md b/src/connections/destinations/catalog/linkedin-conversion-tag/index.md deleted file mode 100644 index ea1007f261..0000000000 --- a/src/connections/destinations/catalog/linkedin-conversion-tag/index.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: LinkedIn Conversion Tag Destination ---- -## Getting Started - -When you enable the LinkedIn Insight Tag in the Segment web app, your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading LinkedIn Insight Tag's tracking snippet onto your page. - -This means you should remove LinkedIn Insight Tag's snippet from your page. - -The LinkedIn Insight Tag automatically starts loading the pixel on sites which you load Analytics.js on. - -LinkedIn Insight Tag doesn't track any other forms of data through Segment, so none of the rest of our API is supported. diff --git a/src/connections/destinations/catalog/pendo-web-actions/index.md b/src/connections/destinations/catalog/pendo-web-actions/index.md deleted file mode 100644 index 3921e4e611..0000000000 --- a/src/connections/destinations/catalog/pendo-web-actions/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'Pendo Web (Actions) Destination' -hidden: true -id: 6501a4325a8a629197cdd691 -published: false -beta: true ---- diff --git a/src/connections/destinations/catalog/ripe-cloud-mode-actions/index.md b/src/connections/destinations/catalog/ripe-cloud-mode-actions/index.md deleted file mode 100644 index 807616114e..0000000000 --- a/src/connections/destinations/catalog/ripe-cloud-mode-actions/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'Ripe Cloud Mode (Actions) Destination' -hidden: true -id: 63cade592992cf7052ce2e3e -published: false -beta: true ---- diff --git a/src/connections/destinations/catalog/screeb-web-actions/index.md b/src/connections/destinations/catalog/screeb-web-actions/index.md deleted file mode 100644 index 7995ccc398..0000000000 --- a/src/connections/destinations/catalog/screeb-web-actions/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'Screeb Web (Actions) Destination' -hidden: true -id: 64820d8030d09e775fbac372 -published: false -beta: true ---- diff --git a/src/connections/destinations/catalog/stackadapt/index.md b/src/connections/destinations/catalog/stackadapt/index.md deleted file mode 100644 index 0160a9b2e9..0000000000 --- a/src/connections/destinations/catalog/stackadapt/index.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -# The end name should be similar to `Slack Destination` -title: StackAdapt Destination -hide-boilerplate: true -hide-dossier: true -hidden: true ---- - - - -{% include content/plan-grid.md name="actions" %} - - - - -[StackAdapt](https://www.stackadapt.com){:target="_blank"} is a self-serve programmatic advertising platform for by digital marketers. Ad buyers can plan, execute and manage data-driven digital advertising campaigns across all devices, inventory, and publisher partners. - -## Benefits of StackAdapt (Actions) - -StackAdapt (Actions) provides the following benefits: - -- **Event & Page View Tracking**: Leverage the StackAdapt Pixel for event and page view tracking -- **Audience Retargeting**: Use pixel data to create lookalike audiences -- **Reporting**: Consolidate all conversion and other media metrics into one platform, for a robust reporting solution - - - -## Getting started - -1. From the Segment web app, click **Catalog**, then click **Destinations**. -2. Find the Destinations Actions item in the left navigation, and click it. -3. Click **Configure StackAdapt**. -4. Select an existing Source to connect to StackAdapt (Actions). - - - -{% include components/actions-fields.html %} - - diff --git a/src/connections/destinations/catalog/talon-one-actions/index.md b/src/connections/destinations/catalog/talon-one-actions/index.md deleted file mode 100644 index 2a48c055f1..0000000000 --- a/src/connections/destinations/catalog/talon-one-actions/index.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -title: 'Talon.One (Actions) Destination' -hide-boilerplate: true -hide-dossier: false -id: 6234b137d3b6404a64f2a0f0 -redirect_from: - - '/connections/destinations/catalog/actions-talon-one' ---- - - - -{% include content/plan-grid.md name="actions" %} - -Create flexible and targeted promotional and loyalty campaigns with [Talon.One](https://www.talon.one/){:target="_blank"}. -Campaigns can be created and managed by non-technical users like marketers. There is no need to -get your development team involved. Features include coupons, discounts, loyalty -programs, referral tracking, geofencing, and bundling. - -This destination is maintained by Talon.One. For any issues with the destination, [contact the Talon.One Support team](mailto:support@talon.one) or refer to [Talon.One's documentation](https://docs.talon.one/docs/dev/technology-partners/segment){:target="_blank"}. - - -> success "" -> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Talon.One Segment destination. There's also a page about the [non-Actions Talon.One destination](/docs/connections/destinations/catalog/talonone/). Both of these destinations receive data from Segment. - -## Benefits of Talon.One (Actions) vs Talon.One Classic - -Talon.One (Actions) allows you to share more data than the classic destination. -The classic version only shares customer profile data. The Action version supports sharing the following data: - -- Customer profile data -- Audience data -- Tracking events - - - -## Getting started - -### Creating an API key in Talon.One - -Segment needs a Talon.One-generated API key to be able to send data to your Talon.One Application. To generate an API key specific to Segment: - -1. Open your Talon.One Application in the Campaign Manager and click **Settings > Developer settings**. -1. Click **Create API Key**. -1. For **Do you want to use this API Key with a 3rd party service**, select **Yes**. -1. Select **Segment** from the dropdown. -1. Select an expiry date and click **Create API Key**. -1. Copy it for later use. - -> info "Talon.One API Rate Limit" -> Talon.One limits integrations with Segment to 60 requests per second for any given client, regardless of the endpoint. To increase this limit, contact Talon.One. - -### Adding a Talon.One destination - -To start sending data to Talon.One from Segment, create a Talon.One -[destination](/docs/connections/destinations/) in Segment. - -1. In Segment, click **Destinations** > **Add Destination**. The **Destination catalog** opens. -1. Search for **Talon.one** and configure the destination. -1. Enter the details: - - In **Name**, type a name, for example `Talon.One destination`. - - In **API key**, paste the API key generated in the previous section. - - In **Deployment**, type the URI of your Talon.One deployment, for example - `https://mycompany.europe-west1.talon.one/`. -1. (Optional) Set up your filters. -1. Configure the mapping: - 1. Click **New Mapping** and select the type of action to perform in Talon.One. - For example _When a new audience is created in Segment, also create it in Talon.One._ - 1. Configure the trigger and action fields. -1. Click **Event Tester** and test if you received the data in Talon.One. - -Once you receive data, you can start creating rules that rely on that data. - -> warning "" -> **Important**: You might need to create custom attributes in Talon.One to be able to map the data from Segment in Talon.One. See the [Talon.One docs](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#creating-custom-attributes){:target="_blank"}. - -### Testing the integration - -You can use the following payloads to test and fine-tune your requests. - -```json -{ - "messageId": "segment-test-message-t1kx8e", - "timestamp": "2022-03-22T12:41:20.918Z", - "type": "track", // or any other type in Segment - "userId": "test-user-z65zqk", - "event": "track-event", // or any other event in Segment - "email": "test@example.org", - "projectId": "qR6APLKpCBB3ue8pHkBLpo", - "properties": { - "eventType": "mySegmentEvent", - "type": "boolean", - "customerProfileId": "a_customer_id", - "attributes": { - "language": "English" // depends your custom attributes in Talon.One - } - } -} -``` - -### Next steps - -Once you receive data from Segment inside Talon.One, start creating your rules in the Campaign Manager. See the [Talon.One documentation](https://docs.talon.one/docs/product/rules/overview){:target="_blank"}. - - -{% include components/actions-fields.html %} - - -## Migration from the classic Talon.One destination - -To prevent duplicate events being created in Talon.One, ensure that for each Segment source, this destination and the classic Talon.One destination are not both enabled at the same time. - - diff --git a/src/connections/destinations/catalog/tiktok-offline-conversions/index.md b/src/connections/destinations/catalog/tiktok-offline-conversions/index.md deleted file mode 100644 index 8949f7fa75..0000000000 --- a/src/connections/destinations/catalog/tiktok-offline-conversions/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'Tiktok Offline Conversions Destination' -hidden: true -id: 6447ca8bfaa773a2ba0777a0 -published: false -beta: true ---- diff --git a/src/connections/destinations/catalog/tiktok-pixel/index.md b/src/connections/destinations/catalog/tiktok-pixel/index.md deleted file mode 100644 index 8dcf9ac554..0000000000 --- a/src/connections/destinations/catalog/tiktok-pixel/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'TikTok Pixel Destination' -hidden: true -id: 64c1690a9f08c84a420aba78 -published: false -beta: true ---- From c6fd0ea6ab03690462a277a261ef7295ec725b5d Mon Sep 17 00:00:00 2001 From: Thomas Gilbert Date: Mon, 5 Aug 2024 12:29:30 -0400 Subject: [PATCH 2/3] add userguiding slug override --- src/_data/catalog/slugs.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/_data/catalog/slugs.yml b/src/_data/catalog/slugs.yml index f7201dcf7d..6928337792 100644 --- a/src/_data/catalog/slugs.yml +++ b/src/_data/catalog/slugs.yml @@ -309,3 +309,5 @@ destinations: override: "actions-chartmogul" - original: "taboola-actions" override: "actions-taboola-actions" + - original: "userguiding" + override: "user_guiding" From 01979195789e81c9cf9e9dd1ac9d21e05908cadf Mon Sep 17 00:00:00 2001 From: Thomas Gilbert Date: Tue, 6 Aug 2024 09:44:56 -0400 Subject: [PATCH 3/3] add angler ai --- src/_data/catalog/slugs.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/_data/catalog/slugs.yml b/src/_data/catalog/slugs.yml index 6928337792..0843a6e8ac 100644 --- a/src/_data/catalog/slugs.yml +++ b/src/_data/catalog/slugs.yml @@ -311,3 +311,5 @@ destinations: override: "actions-taboola-actions" - original: "userguiding" override: "user_guiding" + - original: "angler-ai" + override: "actions-angler-ai"