From c96e874636d2e0da360aff0a77cdeb84be9ce394 Mon Sep 17 00:00:00 2001 From: Sina Jamshidi Date: Thu, 7 Sep 2023 10:18:54 -0700 Subject: [PATCH 1/6] AMP-84095 add description of Braze User Alias Label --- docs/data/destinations/braze.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/data/destinations/braze.md b/docs/data/destinations/braze.md index b8cfea6aa..e266e44ee 100644 --- a/docs/data/destinations/braze.md +++ b/docs/data/destinations/braze.md @@ -33,7 +33,8 @@ To configure streaming from Amplitude to Braze, you need the following informati 1. Select your **Braze API Endpoint**. 2. Enter your **Braze API Key**. 3. Enter your **Braze App ID**. -4. Check **Update Users Only** to only update users that exist in Braze, and not create new ones. If you're sending alias-only user profiles, don't check this field. If you check **Update Users Only**, your alias-only user profiles aren't created in Braze. More information available in the [Braze documentation](https://www.braze.com/docs/api/objects_filters/user_attributes_object). +4. If you are using [Braze User Alias](https://www.braze.com/docs/api/objects_filters/user_alias_object) to identify your users on Braze, enter the **Braze User Alias Label** you plan on using. Otherwise this field can be safely ignored. +5. Check **Update Users Only** to only update users that exist in Braze, and not create new ones. If you're sending alias-only user profiles, don't check this field. If you check **Update Users Only**, your alias-only user profiles aren't created in Braze. More information available in the [Braze documentation](https://www.braze.com/docs/api/objects_filters/user_attributes_object). ### Configure mappings From 77eae97b8ed5f73cdbf12a70ce6f7be9d9003dbc Mon Sep 17 00:00:00 2001 From: Sina Jamshidi Date: Thu, 7 Sep 2023 10:28:51 -0700 Subject: [PATCH 2/6] Update docs/data/destinations/braze.md Co-authored-by: markzegarelli --- docs/data/destinations/braze.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/data/destinations/braze.md b/docs/data/destinations/braze.md index e266e44ee..10280c6ae 100644 --- a/docs/data/destinations/braze.md +++ b/docs/data/destinations/braze.md @@ -34,7 +34,7 @@ To configure streaming from Amplitude to Braze, you need the following informati 2. Enter your **Braze API Key**. 3. Enter your **Braze App ID**. 4. If you are using [Braze User Alias](https://www.braze.com/docs/api/objects_filters/user_alias_object) to identify your users on Braze, enter the **Braze User Alias Label** you plan on using. Otherwise this field can be safely ignored. -5. Check **Update Users Only** to only update users that exist in Braze, and not create new ones. If you're sending alias-only user profiles, don't check this field. If you check **Update Users Only**, your alias-only user profiles aren't created in Braze. More information available in the [Braze documentation](https://www.braze.com/docs/api/objects_filters/user_attributes_object). +5. Check the **Update Users Only** option to update users that exist in Braze, not create new users. If you send alias-only user profiles, don't check this field. If you check **Update Users Only**, your alias-only user profiles aren't created in Braze. More information available in the [Braze documentation](https://www.braze.com/docs/api/objects_filters/user_attributes_object). ### Configure mappings From f300cd066aaad559368df9a11ed524e5e304705c Mon Sep 17 00:00:00 2001 From: Sina Jamshidi Date: Thu, 7 Sep 2023 10:29:11 -0700 Subject: [PATCH 3/6] Update docs/data/destinations/braze.md Co-authored-by: markzegarelli --- docs/data/destinations/braze.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/data/destinations/braze.md b/docs/data/destinations/braze.md index 10280c6ae..e26dd3c14 100644 --- a/docs/data/destinations/braze.md +++ b/docs/data/destinations/braze.md @@ -33,7 +33,7 @@ To configure streaming from Amplitude to Braze, you need the following informati 1. Select your **Braze API Endpoint**. 2. Enter your **Braze API Key**. 3. Enter your **Braze App ID**. -4. If you are using [Braze User Alias](https://www.braze.com/docs/api/objects_filters/user_alias_object) to identify your users on Braze, enter the **Braze User Alias Label** you plan on using. Otherwise this field can be safely ignored. +4. If you use the [Braze User Alias](https://www.braze.com/docs/api/objects_filters/user_alias_object) to identify your users on Braze, enter the **Braze User Alias Label** you plan to use. Otherwise, you can ignore this field. 5. Check the **Update Users Only** option to update users that exist in Braze, not create new users. If you send alias-only user profiles, don't check this field. If you check **Update Users Only**, your alias-only user profiles aren't created in Braze. More information available in the [Braze documentation](https://www.braze.com/docs/api/objects_filters/user_attributes_object). ### Configure mappings From 13501a1f374cb4fd814476bc0834c337230d908d Mon Sep 17 00:00:00 2001 From: Mark Zegarelli Date: Thu, 7 Sep 2023 12:52:16 -0700 Subject: [PATCH 4/6] Disable linting in formatguide --- docs/utils/formatguide.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/utils/formatguide.md b/docs/utils/formatguide.md index a6368e3e6..f4c286b13 100644 --- a/docs/utils/formatguide.md +++ b/docs/utils/formatguide.md @@ -2,6 +2,12 @@ title: Format Guide description: See how different formatting options render --- + + + + + + This cheatsheet covers the most used formatting features like admonitions and code blocks. From d63f29c7481b9f9029ab688282a9512e35d70b21 Mon Sep 17 00:00:00 2001 From: Mark Zegarelli Date: Thu, 7 Sep 2023 13:37:17 -0700 Subject: [PATCH 5/6] further cleanup and rerun jobs --- docs/data/destinations/braze.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/data/destinations/braze.md b/docs/data/destinations/braze.md index e26dd3c14..2ad5d3d8b 100644 --- a/docs/data/destinations/braze.md +++ b/docs/data/destinations/braze.md @@ -3,7 +3,7 @@ title: Braze Event Streaming description: Amplitude CDP's Braze streaming integration enables you to forward your Amplitude events and users straight to Braze with just a few clicks. --- -Amplitude CDP's Braze streaming integration enables you to forward your Amplitude events and users straight to [Braze](https://www.braze.com/) with just a few clicks. +The Amplitude CDP Braze streaming integration enables you to forward your Amplitude events and users straight to [Braze](https://www.braze.com/) with just a few clicks. !!!note "Other Amplitude CDP + Braze integrations" @@ -61,8 +61,9 @@ Under **Send Events**, make sure the toggle is enabled ("Events are sent to Braz 2. (optional) In **Select additional properties**, select any more event and user properties you want to send to Braze. If you don't select any properties here, Amplitude doesn't send any. These properties are sent to Braze as [Braze custom event properties](https://www.braze.com/docs/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-properties). _Transformed event properties and transformed user properties aren't supported._ ### Configure user forwarding + !!!warning "Temporarily Disabled" - We're actively working on improving the experience of user forwarding to Braze, including addressing concerns around high call volumes which can incur additional costs in Braze. All enabled user forwarding syncs will continue to run. Temporarily, no new user forwarding syncs can be enabled. If an enabled user forwarding sync is disabled, it can not be re-enabled at this time. Event forwarding to Braze is unaffected by this and can still be configured as normal. User forwarding destinations other than Braze are also unaffected and can still be configured as normal. + Amplitude is working to improve the experience of user forwarding to Braze, including addressing concerns around high call volumes which can incur additional costs in Braze. All enabled user forwarding syncs will continue to run. Temporarily, no new user forwarding syncs can be enabled. If an enabled user forwarding sync is disabled, it can not be re-enabled at this time. Event forwarding to Braze is unaffected by this and can still be configured as normal. User forwarding destinations other than Braze are also unaffected and can still be configured as normal. Under **Send Users**, make sure the toggle is enabled ("Users are sent to Braze") if you want to stream users and their properties to Braze. When enabled, users are automatically created or updated in Braze when an event is sent to Amplitude. [Amplitude Identify API](https://www.docs.developers.amplitude.com/analytics/apis/identify-api/) calls are also forwarded to Braze. Users aren't sent on a schedule or on-demand using this integration. From ff5cbe86952e63a1bac6cf711431e7507f12ca1c Mon Sep 17 00:00:00 2001 From: Mark Zegarelli Date: Thu, 7 Sep 2023 13:46:46 -0700 Subject: [PATCH 6/6] suppress the spelling errors --- docs/data/sources/tealium.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/data/sources/tealium.md b/docs/data/sources/tealium.md index c5c2fca0e..112b822af 100644 --- a/docs/data/sources/tealium.md +++ b/docs/data/sources/tealium.md @@ -80,7 +80,7 @@ In the data layer, you can define the following variable types: };   ``` - + * **Querystring Parameters:** This captures parameters from the URL. For example, if the URL is `http://example.com/path/file.html?sortOrder=price`, the variable name in Tealium is `sortOrder`. * **First-Party Cookies:** Reference value in a cookie being set on your domain. When creating a cookie variable, you can either specify Tealium cookie, `utag_main`, or standard cookie. You can also add your own custom values to the `utag_main cookie`. The `utag.js` library creates and maintains a single cookie called `utag_main`; within it are several built-in values that keep track of the visitor session. * `ses_id`: Unique identifier for the session. @@ -92,7 +92,7 @@ In the data layer, you can define the following variable types: * **JavaScript Variables:** Select this to reference a JavaScript variable on the web page other than the `utag_data` object. * **Meta Data Elements:** Reference content of a meta tag in the page. * **AudienceStream Attributes:** Attributes such as badges, metrics, and properties that are defined in AudienceStream, which takes data that flows into Tealium's other product (Universal Data Hub) and creates visitor profiles representing the most important attributes of user engagement. - + ### Load rules Load rules are conditions that define when and where to load a tag. They consist of logical conditions that must pass before Amplitude loads a tag. For example, you can set it up so that only certain tags load on certain domains. You can use AND/OR logic or time/date-based conditions to load tags.