Braze Web SDK Tag Setup Guide
This article describes how to set up the Braze Web SDK tag in your Tealium iQ Tag Management account.
Supported Versions
- 3.5
- 4.0
The Braze Web SDK Tag supports tag template versions 3.3 and older. For best tag performance and functionality, we recommend updating to the most recent tag template.
Tag Tips
-
The Purchase Event fires when an Order ID is present.
-
Supports these E-Commerce extension parameters:
- Customer ID (Overrides
_ccustid
) - City (Overrides
_ccity
) - Country (Overrides
_ccountry
) - Order ID (Overrides
_corder
) - Sub Total (Overrides
_csubtotal
) - Currency (Overrides
_ccurrency
) - Product IDs (Overrides
_cprod
) - Product Quantities (Overrides
_cquan
)
- Customer ID (Overrides
-
Use mapping to dynamically override the standard configuration values.
Tag Configuration
First, go to the Tealium Tag Marketplace and add the Braze Web SDK tag to your profile (how to add a tag?).
After adding the tag, configure the following settings:
-
Code Version
- Enter the major.minor version of the Braze Web SDK version you want to use.
- For example, to deploy version 2.6.1, enter 2.6.
- To find the latest version of the Braze Web SDK, see the changelog.
-
API Key
- Your unique API key, available on your Braze dashboard in the Manage App Group settings.
-
Base URL
- The API endpoint pointing to the Braze Cluster you are assigned.
- Example for 4.0:
https://js.appboycdn.com/web-sdk/4.0/braze.no-amd.min.js
- Example for versions 3.5 and older:
https://js.appboycdn.com/web-sdk/3.5/appboy.no-amd.min.js
- For a list of options, see Braze SDK Endpoints.
-
Enable Logging
- When enabled, this will log debugging information in the web console.
Load Rules
Load Rules determine when and where to load an instance of this tag on your site.
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. (Learn more)
The destination variables for the Braze Web SDK tag are built into the Data Mapping tab for the tag. The following tables list the available destination categories and describe each destination name.
Standard
Destination Name | Description |
---|---|
initOpt.allow_crawler |
|
initOpt.app_ver |
|
initOpt.base_url |
|
initOpt.no_cookies |
|
initOpt.no_fntawsm |
|
initOpt.enable_htmlmsgs |
|
initOpt.enable_logging |
|
initOpt.localization |
|
initOpt.min_trggrinterval |
|
initOpt.msg_innewtab |
|
initOpt.card_innewtab |
|
initOpt.explicit_dissmisal |
|
initOpt.safari_pushid |
|
initOpt.srvcewrkr_location |
|
initOpt.session_timeout |
|
initOpt.enableSdkAuthentication |
|
E-Commerce
The Braze Web SDK tag is e-commerce enabled and will therefore automatically use the default E-Commerce extension mappings. Manually mapping in this category is generally not needed unless you want to override any extension mappings or your desired e-commerce variable is not offered in the extension.
Destination Name | Description |
---|---|
order_id |
|
order_subtotal |
|
order_currency |
|
customer_id |
|
customer_city |
|
customer_country |
|
product_id |
|
product_quantity |
|
Event
Map to these destinations for triggering specific events on a page.
Use the following steps to trigger an event:
- Select an event from the drop-down list.
- You can select from the predefined list or create a custom event.
- For a custom event, enter a name with which to identify it.
- In the Trigger field, enter the value of the variable being mapped.
- To map more events, click the + button and repeat Steps 1 and 2.
- Click Apply.
The following table lists the event triggers when the supplied value is found in the data layer.
Destination Name | Description |
---|---|
Purchase |
|
Alias |
|
addToSubscriptionGroup |
|
AddAtt |
|
IncAtt |
|
RmvAtt |
|
SetAtt |
|
SetAvatar |
|
SetLoc |
|
SetDOB |
|
SetEmail |
|
SetEmailSub |
|
SetPushSub |
|
SetFirst |
|
SetLast |
|
SetCity |
|
SetCountry |
|
SetLang |
|
SetPhone |
|
SetGender |
|
Custom |
|
Parameter
Map to these destinations to pass data to the events mapped earlier. Parameters are only used with predefined Events. See the Custom Event Data section below to learn how to pass a parameter with a custom event.
Use the following steps to pass a parameter to a predefined event:
- In the Event field, select an event from the drop-down list.
- In the Parameter field, select a parameter from the drop-down list.
- For a custom parameter, enter a name to identify the custom event.
- Click + Add.
Destination Name | Description |
---|---|
product_id |
|
product_quantity |
|
order_id |
|
order_subtotal |
|
order_currency |
|
purchase_properties |
|
alias |
|
label |
|
key |
|
value |
|
inc_value |
|
avatar_url |
|
longitude |
|
latitude |
|
accuracy |
|
altitude |
|
altitude_accuracy |
|
year |
|
month |
|
day |
|
email |
|
notification_type |
|
first_name |
|
subscriptionGroupId |
|
last_name |
|
gender |
|
customer_city |
|
customer_country |
|
localization |
|
phone_number |
|
Custom Event Data
Map to custom event data destinations if you want to pass a custom parameter with a custom event that you previously mapped in the Events tab.
Use the following steps to map a custom event data variable:
- For Event Name, enter the name of the custom event, exactly as specified in the Events tab.
- For Parameter, enter the name of the parameter you want to send.
- Click + Add.
Vendor Documentation
This page was last updated: September 12, 2022