Skip to content

Commit f6e988e

Browse files
Merge pull request #6899 from segmentio/thomas/action-slugs
Clean up for action destinations
2 parents ecbbf8e + 0197919 commit f6e988e

File tree

37 files changed

+295
-602
lines changed

37 files changed

+295
-602
lines changed

src/_data/catalog/slugs.yml

Lines changed: 81 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -232,4 +232,84 @@ destinations:
232232
- original: "usermaven-actions"
233233
override: "actions-usermaven"
234234
- original: "survicate-actions"
235-
override: "actions-survicate"
235+
override: "actions-survicate"
236+
- original: "customer-io-actions"
237+
override: "actions-customerio"
238+
- original: "braze-cloud-mode-actions"
239+
override: "actions-braze-cloud"
240+
- original: "braze-web-device-mode-actions"
241+
override: "actions-braze-web"
242+
- original: "talon-one-actions"
243+
override: "actions-talon-one"
244+
- original: "criteo-audiences"
245+
override: "actions-criteo-audiences"
246+
- original: "actable-predictive"
247+
override: "actions-actable-predictive"
248+
- original: "ripe-device-mode-actions"
249+
override: "actions-ripe"
250+
- original: "blackbaud-raisers-edge-nxt"
251+
override: "actions-blackbaud-raisers-edge-nxt"
252+
- original: "google-analytics-4-web"
253+
override: "actions-google-analytics-4-web"
254+
- original: "gwen-actions"
255+
override: "actions-cloud-gwen"
256+
- original: "blend-ai"
257+
override: "actions-blend-ai"
258+
- original: "tiktok-offline-conversions"
259+
override: "actions-tiktok-offline-conversions"
260+
- original: "userpilot-cloud-actions"
261+
override: "actions-userpilot-cloud"
262+
- original: "userpilot-web-actions"
263+
override: "actions-userpilot-web"
264+
- original: "screeb-web-actions"
265+
override: "actions-screeb-web"
266+
- original: "koala-cloud"
267+
override: "actions-koala-cloud"
268+
- original: "tiktok-pixel"
269+
override: "actions-tiktok-pixel"
270+
- original: "gameball-actions"
271+
override: "actions-gameball"
272+
- original: "pushwoosh"
273+
override: "actions-pushwoosh"
274+
- original: "acoustic-actions"
275+
override: "actions-acoustic"
276+
- original: "pendo-web-actions"
277+
override: "actions-pendo-web"
278+
- original: "delivr-ai-resolve"
279+
override: "actions-cdpresolution"
280+
- original: "optimizely-data-platform"
281+
override: "actions-optimizely-data-platform"
282+
- original: "hubble-actions"
283+
override: "hubble-web"
284+
- original: "jimo-actions"
285+
override: "actions-jimo"
286+
- original: "linkedin-conversions-api"
287+
override: "actions-linkedin-conversions"
288+
- original: "kameleoon-actions"
289+
override: "actions-kameleoon"
290+
- original: "marketo-static-lists-actions"
291+
override: "actions-marketo-static-lists"
292+
- original: "usermotion-actions"
293+
override: "actions-usermotion"
294+
- original: "1flow-web-actions"
295+
override: "actions-1flow"
296+
- original: "gleap-action"
297+
override: "gleap-cloud-actions"
298+
- original: "equals"
299+
override: "actions-equals"
300+
- original: "schematic"
301+
override: "actions-schematic"
302+
- original: "avo"
303+
override: "actions-avo"
304+
- original: "stackadapt"
305+
override: "actions-stackadapt-cloud"
306+
- original: "kafka"
307+
override: "actions-kafka"
308+
- original: "chartmogul"
309+
override: "actions-chartmogul"
310+
- original: "taboola-actions"
311+
override: "actions-taboola-actions"
312+
- original: "userguiding"
313+
override: "user_guiding"
314+
- original: "angler-ai"
315+
override: "actions-angler-ai"

src/connections/destinations/catalog/1flow-web-actions/index.md

Lines changed: 0 additions & 7 deletions
This file was deleted.

src/connections/destinations/catalog/avo/index.md renamed to src/connections/destinations/catalog/actions-avo/index.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: Avo Destination
33
id: 65c2465d0d7d550aa8e7e5c6
4-
redirect_from: "/connections/destinations/catalog/actions-avo/"
54
---
65

76
**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

Lines changed: 19 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,16 @@
22
title: Braze Cloud Mode (Actions) Destination
33
hide-boilerplate: true
44
hide-dossier: false
5-
hidden: true
5+
id: 60f9d0d048950c356be2e4da
6+
versions:
7+
- name: 'Braze Web Mode (Actions)'
8+
link: '/docs/connections/destinations/catalog/braze-web-device-mode-actions/'
9+
- name: 'Braze (Classic)'
10+
link: '/docs/connections/destinations/catalog/braze'
611
---
712
{% include content/plan-grid.md name="actions" %}
813

9-
[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.
14+
[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.
1015

1116
> success ""
1217
> **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:
2025
## Getting Started
2126

2227
1. From the Segment web app, click **Catalog**.
23-
2. Search for "Braze" in the Catalog, select **Braze**, and choose which of your sources to connect the destination to.
24-
3. Select "Actions" under the Destination framework options.
25-
4. Add the following Connection Settings:
28+
2. Search for "Braze" in the Catalog, select **Braze Cloud Mode (Actions)**, and choose which of your sources to connect the destination to.
29+
3. Add the following Connection Settings:
2630
- **API Key**: Created under Developer Console in the Braze Dashboard.
2731
- **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.
2832
- **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.
2933

30-
## Batching data to Braze
31-
32-
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.
33-
34-
{% include components/actions-fields.html %}
34+
> info ""
35+
> 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.
3536
37+
{% include components/actions-fields.html settings="true"%}
3638

3739
## Migration from Braze Classic
3840

3941
Keep the following in mind if you plan to move to Braze (Actions) from the classic Braze destination.
4042
{% include components/actions-map-table.html name="braze-cloud" %}
4143

44+
## Troubleshooting
45+
46+
### Missing required fields
47+
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.
48+
49+
### Missing events
50+
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: "[email protected]"), use "email:test@email.com" to search for the alias in Braze.

0 commit comments

Comments
 (0)