The most frequently asked questions about Google Ads.
Why am I unable to see Google Ad Set and Ad Set ID in Analytics?
The ad dimensions, for example, ad name and ad set name are not supported for the Google AdWords UAC campaigns.
This is since Ad Set Name is not among the supported variables passed to Branch via Google AdWords for such campaigns. You can only see the ad group ID for non-UAC campaigns on conversions.
Branch doc - Common Sources of SAN Reporting Discrepancies
Why do Google Ads get disapproved destination mismatch using Branch Links?
Google has a destination mismatch policy, which indicates that the final URL should not have any redirect when a user clicks on a Google ad. You can refer to a Google doc here: https://support.google.com/adspolicy/answer/6368661?hl=en
While Branch Links will always redirect user before taking them to the destination, they get disapproved if used in the final URL section of their ads, hence it is recommended to use the Branch Link in the tracking template URL instead which allows for parallel tracking and does not break attribution for web based campaigns.
More on parallel tracking and general FAQ related to Google ads can be found here: Google Ads
Will adding custom parameter ~customer_ad_set_name or ~customer_ad_name to the Branch Ad Link result in including the ad group name in Branch Dashboard?
For data coming through our SAN connector, this is a limitation based on what Google provides--you can find the full mapping here, but Branch only showing ‘ad set id’ is due to Google only providing the ‘ad set id’ to us for this value. For this SAN-based data, there’s no way to tweak what reporting labels are being used.
However, for any activity that is coming through Branch Links instead of using the SAN connector (as some search traffic may be), you can also opt to use ‘~ad_set_name’ rather than a ‘~customer_x value’. If ‘~ad_set_name’ is not already in use by your team, there would be no conflict presented from this solution, and it would keep your data values more closely paired with the ~ad_set_id value Branch is already getting.