David Emelianov
unread,Mar 22, 2023, 12:35:49 PM3/22/23Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Chromium Extensions, Zach Warneke, Oliver Dunk, Chromium Extensions, Harpaul Sambhi, Arnoud Kooi, Travel Arrow
Hello, it looks like we are still having issues tracking the track_install path. The install event itself is being captured in Analytics, but it seems that it can no longer differentiate between Paid and Non-Paid traffic. Our hunch is that the gclid inserted by auto-tagging is being lost by the Webstore.
Some context:
We added our Google Analytics UA property to our Webstore page 1-2 years ago. This has been extremely useful to track the performance of Google Search Ads, which we point directly to our Webstore landing page. Since our Google Analytics account is linked to our Google Ads account, we are able to ingest the "install" data from the Webstore into Google Ads and automatically optimize performance based on the conversion data. These ads have been running for about 8 months with this setup, and everything has been working perfectly.
Around March 2nd, the "install" conversion data from the Webstore stopped flowing into Google Ads. We didn't change our ad spend or our ad configuration, and the number of clicks on the ads remained the same. Without any changes on our side, it seems that Google Ads was no longer receiving any attributed "install" events from Analytics. Screenshot below:
Here's what we see in Google Analytics. It looks like the "visitors to the webstore landing page" is being reported as normal. There are some dips in overall volume (because ours Ads bidding strategy started getting mixed signals and then we turned off our ad campaigns for a while) but the data looks correct. As you can see, Analytics is able to correctly attribute traffic as "organic" vs "paid" (the green line vs the orange line).
However, if we drill down to our "install" conversions (which are tracked via the track_install path) then the problem becomes clear. Something changed on March 2nd which caused install events to stop being tracked entirely. And then shortly after that, the install events started getting tracked again, but Analytics was no longer able to differentiate between organic and paid conversions. The orange line and the green line completely inverted themselves.
Is it possible that this was due to a recent change in the webstore?
We are confident that this behavior is not due to any changes that we have made on our side. Here are some things that we have tried to verify this issue:
- We tried creating a new conversion event in Google Analytics and importing it into ads
- We tried unlinking and relinking our Google Analytics account from our Google Ads account
- We tried creating a brand new Google Analytics account and hooking it up to our Webstore page
- We audited our auto-tagging setup and verified that it was enabled in Google Analytics and in Google Ads. We also manually viewed one of our ads in Google Search and clicked on it to verify that the "gclid" URL param was getting appended property.
- We tried enabling manual auto-tagging overrides
Any assistance you would provide would be greatly appreciated. Currently, this issue is having a massive business impact for us because we are completely unable to run our ad campaigns effectively. If there's any additional details we can provide, we'd be happy to!
Thanks