we have set up a couple of very simple conversion tags for Google Ads (for testing, we even chose one to fire on All Pages). One is based on the gtag.js version, the other one on the old Conversion Tag template.
The tags should fire in an app via a Tealium Web View (tealium.js) implementation.
We can see the tags firing (below an example request (to https://www.google.com/pagead/1p-conversion/942593865/? ). They look correct. But nothing gets to the Google Ads interface.
Could the reason be that Google does not accept Conversion Tags firing from domains other than the customer's normal domains? Here, they all fire from tags.tiqcdn.com (Tealium's domain), so I wonder if that could be the reason?
Is anyone else successfully getting their Google Ads Tags to run?
|tiba||Tealium Mobile Webview|
05-09-2019 02:59 AM - edited 05-09-2019 03:00 AM
No, we had to stop this after several tries.
The problem is that it does not seem possible (at least not without considerable extra engineering) to get the AdWords Cookie that is generated when clicking a link into Tealium's mobile app web view or the UDH-based library. So you can fire those Tags and they do send data to AdWords, but they will never show up as Conversions because AdWords cannot connect them with their "ad clicked" cookie.
If you have Adobe Analytics, they have a sensible In-App Conversion Tracking possibility (see the good description by Tealium here: https://community.tealiumiq.com/t5/Installation-Libraries/Mobile-App-Download-Tracking-with-Adobe-An... ), but with Google Analytics, you are really stuck with 2 options:
1) put the native Firebase framework into your app and use Firebase's built-in attribution stuff (does not cover all ad networks, eg no facebook) and their "Dynamic Links". You will have to live with Firebase's super-limited interface and even more limited e-commerce tracking framework, having to get any useful report data via BigQuery (quite a workaround, nothing for business people (they hate Firebase because they cannot do anything themselves and we have to now make Data Studio Reports for simple questions like "how many products X did campaign Y sell?"))
2) use a 3rd-party app attribution provider (adjust, appsflyer etc.). Here, instead of setting up an AdWords Conversion Tag in Tealium, you'd do the following:
1. Set up a 3rd party App Attribution provider that provides you with link URLs for your Ads.
2. Have your Ads link to those URLs (they then forward users into your app)
3. Inside the app, deploy the native 3rd-party Attribution provider's library. That library then does some "visitor stitching" and also informs AdWords etc. about your conversions via "postbacks".
hope that helps, @BretCamble .