DeepLink - Migrating From Other Links
You can continue using your UTM parameters or links for data collection you have created from other solutions to gather campaign data into Airbridge. You don't need to edit your existing links. Read on to learn how to migrate from links other than Airbridge tracking links to measure campaigns using Airbridge.
Through parsing URLs, the UTM parameters embedded in URLs can be automatically converted to Airbridge campaign parameters, allowing you to collect data and measure campaign performance using Airbridge.
The UTM parameter values are automatically collected as the campaign parameter values according to the mapping table below.
Airbridge Campaign Parameter | UTM Parameter |
|---|---|
channel | utm_source |
campaign | utm_campaign |
content | utm_content |
keyword | utm_term |
sub-publisher | utm_medium |
The utm_source parameter must be collected. If not, Airbridge cannot collect the UTM parameter values.
The campaign parameters that are mapped to the UTM parameters can also be found in the [Tracking Link]>[Link Generation] menu.
To utilize UTM parsing, the init function must be called. When calling the init function, you must set the utmParsing option to true.
The utm_source parameter is mandatory for UTM parsing. Without it, other UTM parameters will not be parsed. Performance data from campaigns with the same utm_source value will be aggregated together.
To measure the performance of web-to-web campaigns, additional UTM parameters must be appended to the tracking link. You can use the same format for the additional UTM parameters as the ones you already use. If you want to create additional UTM parameters, refer to the URL builder in the Google Analytics Help Center.
Through URL query parameter mapping, you can view the data collected by the query parameters of your existing URL in Airbridge reports.
By using urlQueryMapping, you can custom map other parameters to Airbridge campaign parameters to view the data in Airbridge reports. When calling the airbridge.init function, add urlQueryMapping and input key (Airbridge parameter) : value (Non-Airbridge parameter) pairs. The table below lists the Airbridge parameters that can be used as keys.
Parameter Name | Description |
|---|---|
channel | Channel |
campaign | Campaign |
ad_group | Advertising group |
ad_creative | Advertising creative |
content | Content |
term | Keyword |
sub_id | Sub publisher |
sub_id_1 | Sub sub publisher 1 |
sub_id_2 | Sub sub publisher 2 |
sub_id_3 | Sub sub publisher 3 |
campaign_id | Campaign ID |
ad_group_id | Advertising group ID |
ad_creative_id | Advertising creative ID |
term_id | Keyword ID |
Let's say the landing page of your ad looks like the following.
https://mybrand.com/?utm_source=google&utm_campaign=jan_ua_campaign&internal_code=ABC
The parameter values can be mapped to Airbridge parameters using urlQueryMapping so that the data can be viewed in the Airbridge reports, as shown in the example below.
airbridge.init({
app: '<YOUR_APP_NAME>',
webToken: '<YOUR_WEB_TOKEN>',
// ...
urlQueryMapping: {
channel: 'utm_source',
campaign: 'utm_campaign',
sub_id_1: 'my_sub_id',
},
})For example, if a conversion happens, the internal_code parameter value will be available in the Airbridge report by setting the GRoupBy as "Sub Sub Publisher 1."
Was this helpful?