In case of IOS trafficking due to Apple’s iOS14.5 changes if the click occurs from an iOS device and the user has opted out of tracking, RedTrack can get WBRAID and GBRAID parameters:

•WBRAID is used for web-to-app measurement;

•GBRAID is used for app-to-app measurement.

After the Apple’s iOS14.5 update, instead of the GCLID parameter on iOS surfaces, WBRAID parameter exists in places for clicks associated with web conversion and GBRAID parameter is for clicks associated with app conversions. The new parameters work in tandem with the modeled online conversion that does not attribute conversions to an individual user but rather offers a holistic report on conversions in compliance with user privacy. These parameters use aggregation and de-identification techniques that ensure cross-site behavior cannot be tied back to an individual user.

These parameters are already embedded in the Google Ads traffic channel template as of January 11, 2022, as for the templates added before that date, you may add the parameters manually in the very template in the section Additional parameters:

Pay attention to the following important details:

•if you do conversions in app, you need to remove the {wbraid} parameter from the Google Ads Traffic channel template in RT;

•one-per-click counting setting may block creation of conversions with such parameters as GBRAID/WBRAID in which case an error when sending such conversions will pop up.

To resolve this issue you need to change the one-per-click setting in your Google Ads account:

Check out this article for more details on changing the one-per-click setting in Google Ads.

Check out our RT↔Google Ads integration guide for more information.

Important!

It takes about 48 hours for Google to process IOS conversions without clickid and appear in the Google Ads dashboard. However, there is a chance that Google will not attribute 100% of postbacks due to its logic or additional user settings.