Google Conversion Tag on our website keeps in "Still Running" mode. We have been searching the net for a solution and everywhere the Google Consent Mode is given as a possible cause.
Checking in on this, this should not be the problem.. The consent management system sets the default values and also correctly updates the tag when the user changes his settings.
When checking my tag in the Tag Assistant window , I can see that when the tag is fired, the consent is granted (in the consent tab). When I deny consent on ad_storage for testing purposes, the tag isn't triggered at all, which is the way it should be.
So something else must cause this to happen. Any suggestions?
Seems that the problem was the Ads ID itself.. It used to work with a numeric value for a year until suddenly the tag got a 400 response. By adding a prefix "AW-" in front of the ID the tag suddenly started working again. Strange behaviour and even stranger I couldn't find anything online about this change..
After trying this the calls didn't come in..
I'm starting to believe that this has something to do with some parts of the website not being GDPR compliant, but Ads should mention this much more clearly.
Related
we have recently implemented cookies consent mode in Google tag manager. Pageviews in google analytics (both universal and GA 4) dropped to about 4 % of the original page views.
When I visit the web page without giving any consent some requests to google-analytics.com still appears in network tab. This tells me something is still tracked. No cookies are saved as expected.
Do you have a different experience? Should GA track pageviews anonymously even without consent or it this a correct behavior? Why would analytics script send any requests if it not appears in GA?
It is expected that you see requests to Google Analytics. However in consent mode you should not see _ga cookies being set (or existing _ga cookies being used). That's basically what consent mode is, cookie-free tracking. You should also see a parameter gcs=100 in the GA request to confirm that consent mode is indeed active.
However these requests are not surfaced in the reports (there would be no point, since without user identifier you cannot create sessions). Apparently they are being used for some sort of Machine Learning thing in the background, but I don't think this has much effect on the analytics part of GA (afaik this is more for Google Ads and GA audiences).
So yes, seeing requests in consent mode is normal (if this helps in any way with GDPR compliance etc. in entirely another matter). If you do not run campaigns and do not hope for an uplift via ML models applied to consent mode data, then you probably do not need to bother and can just disable the tags if no consent is given.
It happens because you have to set ad_storage and analytics_storage as denied by default in initialization code, like described in the documentation (in the example only ad_storage is denied, just add analytics_storage too): https://developers.google.com/tag-platform/devguides/consent#implementation_example
I started to notice that my Google Ads clicks wasnt 100% counting by google analytics (For exemple, during a certain period I had 300 clicks and only 100 sessions were counted as Paid Search on analytics). So I contacted Google Ads Support, they investigated and came to me with this:
Actually, your site is losing the attribution of Google Ads because of an automatic redirection of the structure in which it was developed.
When we have Google Ads linked with Google Analytics, they are talked through a parameter called GCLID. To verify this loss, follow the path I made (in several products, here is an example):
1- I accessed the link https://mywebsite.com/products/running-shoes?variant=15320930779194
2- After full site loading, I added the & gclid = Tester123 parameter to the URL (in the browser, so the final URL was https://mywebsite.com/products/running-shoes?variant=15320930779194&gclid=Tester123) and hit Enter
3- To understand if there is a redirect, the normal behavior would be for the URL to remain the same (with & gclid = Tester123 at the end), but in this case, the parameter some (and hence the assignment)
So, the campaign actually appeared (not set) in Analytics, and could be assigned to any of the other channels (Direct, Organic, ...) For this to be resolved, the site structure must stop causing this automatic redirection in the final URL of each product. With this, the results will be effectively assigned to Google Ads.
They also said that if even if I want to use manual tracking (UTMs) I would still have that problem, since the redirections would keep spoiling it.
As I use Shopify as my website platform, I checked with them and I have no redirections that are causing this problem, at least not created by me nor that their support know.
So I am lost over all this. I dont know where to start solving this problem. Google doesnt tell me what kind of redirections may cause this, I dont use any kind of redirections, and Shopify cant tell me if their code causes this problem (what I dont believe, because other shopify websites would also been suffering from this).
So can anyone give me any direction about this? What redirections may be causing this lost of data?
Thanks for your time!
One thing to note, Google Ads might have a different way of counting, there is the possibility of multiple clicks per session.
That said, you can try Google Tag Assistant, start your recording, click on one of your ads, follow that through and see the parameters being passed.
Unfortunately, it is hard to debug with limited information. The more details you can provide the better.
Check where your GA code is placed in the page code. If GA script is at the bottom of page or there are some heavy scripts above GA tracker, losses of bounced sessions can be large. I.e. user enters the page and immediately closes it. GA script doesn't have time to download.
Why user closes the page immediately?
Сlick by mistake
Slow site
And check that all your landing pages are OK and have 200 server response.
I have to debug the following message which I get in google analytics:
The data view XY was configured for e-commerce, but no data is transmitted.
This is the site.
As you can see in the source code, the tag manager is implemented properly, and a network analysis shows that data is transmitted, I get status code 200.
I used the extension "Google Tag Assistant", it showed that everything works fine (go to the site and click on something, then you will get this:)
As you can see it works. So why do I get this message?
Could you show us a little bit more what you have setup in GTM? As far as i can see i assume you should be getting pageviews since the beacons are correct:
But im also seeing you have some kind of event that wont work cause your Action and Category are undefined and Analytics says this fields are mandatory.
If you are not even seeing the pageviews you may have your UA-45904794-4 wrong (Or not well configured on GTM) or a filter on Google Analytics that shouldnt be there.
If you have any further questions just ask and i ll edit this and add more information.
Hope it helps!
You can check that you don't have ecommerce tracking in the container:
Since you do not, you should disable it in analytics on the property:
This warning means that according to the Analytics property settings you intend to track ecommerce data, but you are not sending any.
Or you can finish setting up ecommerce and publish the resulting container. For example, by following that section in the quick start guide:
When I go to my site on mobile it almost instantly shows up as an active user on google analytics. But when I do so on PC it never shows up as an active user. Even tried going to the site through Rabb.it
Also it shows active users 1 but "no data has been received the last 48 hours", does it just take time to update?
Have you looked at the JS debugger on your PC browser? Maybe there is an error that is causing the script to load incorrectly?
I've seen Firefox block the actual HTTP request to the analytics tracker, for example if you have private browsing turned on. I would start with using either Chrome's Developer tools or Firefox in conjunction with Firebug to try to take a peek under the covers as to what is occurring, i.e.
Verify that the JS actually loads correctly
Check for debug errors on the JS console
Check to see if the HTTP request is actually going through.
If your browser is blocking it you will see something like the image below.
I am facing really weird problem related to event tracking. We have implemented google analytics standard code and event tracking for one website and that site is uploaded on online version of test staging sever (not live yet for public).
Google Analytics shows data for pageviews but not showing for event tracking. I looked at code and seems that its working fine.
Anybody has clue what is happening ? Please advise me
I'd check to make sure the __utm.gif tracking pixel request for the event is being made. Things to check:
Javascript errors when the event is triggered.
Verify __utm.gif via the network tab in Firebug or Chrome Dev tools, or Fiddler, or ga_debug.js
If your'e following a link right after the event is triggered, you may have to add a delay to allow time for the image request to be processed.
A code snippet showing your _trackEvent code might be helpful.
Looking at your comments, it is difficult for us to review and answer. Is it possible for your ti share the URL in which you have incorporated the event tracking.
However, possible reasons could be:
* a silly error in JS.
* proper closer of tags.
* need to set up goals as well (not mandatory though).