Step 1: Connect your Google Analytics Account in Brax
Access the Integrations page by clicking on your email in the top right corner, and selecting Integrations:
On the top right corner of the Integrations page, Click the Edit Button to enter Edit mode. Then, click on the Connect button and select Google Analytics from the drop down list.
A pop-up window will appear asking you to connect to your Google Analytics Account. Click Connect
Sign into your Google Analytics account via oAuth. You will then be prompted to give Brax access to your GA account. Click on the Agree button to give access to Brax.
Step 2: Add a Traffic Source Mapping Setting
Under Integrations, click Connect and look for "Google Analytics Traffic source". This is where you'll see the "Add Traffic Source" button.
You will see a powerful wizard that will help you set everything up. Here you will choose which site and source you want to pull data for and the tracking string you are using.
First select the Google Analytics Account, Property, and View.
Next select the traffic source this mapping setting is for and name this setting.
Click next and paste in your tracking string. If you don't have one, you can generate one here. Scroll below for more details on the tracking strings.
After that, we will show you how your data in the string will be translated into Brax.
If everything looks good, it's time to update your campaigns with your new tracking code.
Once you're done, hit "Finish" and you're ready to go!
You will need to add a traffic source mapping setting for each website and traffic source.
Tracking String Details: Which Variables are Supported Per Network
Each network has different variables that are need to be passed into Google Analytics UTM parameters. These variables can all be passed in one UTM parameter or many. Here are the different variables by network and examples of passing them in one UTM or many UTMs.
All networks require that you pass in an identifier for the source. This can be passed in as utm_source alone or simply added to the beginning of the single UTM to differentiate each network. See examples for more details.
Outbrain
{{CAMPAIGN}} - Brax variable - used to map campaign data.
{{campaign_id}} - Outbrain variable - Used to map campaign data.
{{publisher_id}} - Outbrain variable - used to map publisher data.
{{section_id}} - Outbrain variable - used to map section data.
{{promoted_link_id}} - Outbrain variable - used to map ad data.
{{AD_ID}} - Brax variable - used to map ad data.
EXAMPLE 1: Multi-UTM tracking code
utm_source=outbrain&utm_campaign={{campaign_id}}&utm_medium={{publisher_id}}&utm_term={{section_id}}&utm_content={{promoted_link_id}}
EXAMPLE 2: Single UTM tracking code
utm_campaign=OB_{{campaign_id}}_{{publisher_id}}_{{section_id}}_{{promoted_link_id}}
Note: {{CAMPAIGN}} and {{campaign_id}} are interchangeable. {{promoted_link_id}} and {{AD_ID}} are interchangeable.
Taboola
{{CAMPAIGN}} - Brax variable - used to map campaign data.
{campaign_id} - Taboola variable - Used to map campaign data.
{site} - Taboola variable - used to map site data.
{campaign_item_id} - Taboola variable - used to map ad data.
{{AD_ID}} - Brax variable - used to map ad data.
EXAMPLE 1: Multi-UTM tracking code
utm_source=taboola&utm_campaign={campaign_id}&utm_medium={site}&utm_content={campaign_item_id}
EXAMPLE 2: Single UTM tracking code
utm_campaign=TB_{campaign_id}_{site}_{campaign_item_id}
Note: {{CAMPAIGN}} and {campaign_id} are interchangeable. {{AD_ID}} and {campaign_item_id} are interchangeable.
Revcontent
{{CAMPAIGN}} - Brax variable - used to map campaign data.
{boost_id} - Revcontent variable - Used to map campaign data.
{widget_id} - Revcontent variable - used to map widget data.
{adv_targets} - Revcontent variable - used to map targets data.
{content_id} - Revcontent variable - used to map ad data.
{{AD_ID}} - Brax variable - used to map ad data.
EXAMPLE 1: Multi-UTM tracking code
utm_source=revcontent&utm_campaign={boost_id}&utm_medium={widget_id}&utm_term={adv_targets}&utm_content={content_id}
EXAMPLE 2: Single UTM tracking code
utm_campaign=RC_{boost_id}_{widget_id}_{adv_targets}_{content_id}
Note: {{CAMPAIGN}} and {boost_id} are interchangeable. {{AD_ID}} and {content_id} are interchangeable.
Yahoo Gemini
{{CAMPAIGN}} - Brax variable - used to map campaign data.
{campaignid} - Gemini variable - Used to map campaign data.
${pubid} - Gemini variable - used to map publisher & device data.
{device} - Gemini variable - used to map publisher & device data.
{adgroupid} - Gemini variable - used to map ad group data.
{adid} - Gemini variable - used to map ad data.
{{AD_ID}} - Brax variable - used to map ad data.
EXAMPLE 1: Multi-UTM tracking code
utm_source=yahoo&utm_campaign={campaignid}&utm_medium=${pubid}|{device}&utm_term={adgroupid}&utm_content={adid}
EXAMPLE 2: Single UTM tracking code
utm_campaign=YG_{campaignid}_${pubid}|{device}_{adgroupid}_{adid}
Note: {{CAMPAIGN}} and {campaignid} are interchangeable. {{AD_ID}} and {adid} are interchangeable.
{{CAMPAIGN}} - Brax variable - used to map campaign data.
[cid] - ContentAd variable - Used to map campaign data.
[did] - ConentAd variable - used to map publisher data.
{{AD_ID}} - Brax variable - used to map ad data.
EXAMPLE 1: Multi-UTM tracking code
utm_source=contentad&utm_campaign=[cid]&utm_medium=[did]&utm_content={{AD_ID}}
EXAMPLE 2: Single UTM tracking code
utm_campaign=contentad_[cid]_[did]_{{AD_ID}}
Note: {{CAMPAIGN}} and [cid] are interchangeable.
HELP ME!!
You're probably a "Do-it-yourself" kind of person, but if you need some help, reach out to us at Love@Brax.io
Comments
0 comments
Article is closed for comments.