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.
Related
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.
A site I work with recently saw a doubling of it's direct traffic as recorded in Google Analytics. There doesn't seem to be a obvious external reason for the increase (like some promotion or something) so I'm looking into a possible technical reason.
When loading the homepage and monitoring Real Time Traffic Sources, I see two hits in rapid succession each time I reload the page.
However I'm using the GA debugger extension in Chrome and it's only showing the two expected function calls: ga('create') and ga('send', 'pageview').
The site has other event tracking set up but each event is wrapped in an event listener in JS so they aren't firing automatically. And if they were they should show up in the GA debugger anyway
So I'm at a loss. I can't think of why this is happening, let alone just for direct traffic as opposed to other sources. Anyone have any ideas?
Thanks!
I had set up my Google Tag to track clicks on spans with certain IDs, the events are firing according to WASP extension, but they are not showing up in my Google Analytics account.
Here is my trigger:
My Tag:
WASP in action:
GA displays pageview only:
Code is installed properly
Sorry if this seems pretty obvious, but in Real Time you should be on the Events tab, and it seems you are looking in the Content tab. Events are never displayed there.
While the configuration looks to be correct, remember that events won't show up in your standard reports until the data is processed, which takes about 24 hours. As long as the hit is showing up in your Real-Time reports, then you shouldn't have any issues.
Can you please post full HTTP request? For instance from Charles Web Debugging Proxy of Live HTTP Headers extension or anything simillar.
What you post seems to be correct as #nyuen says!
When I access the page of certain communities of Stackoverflow, it often occurs that for about a minute my computer gets a very high loading and I can't even scroll the page with the mouse. Recently I read at the bottom of the screen that it was waiting for google.analytics.com in that time period.
Is this a normal phenomenon to be expected or could I do something to avoid
that inconvenience?
You can opt out of being tracked by Google Analytics or download a number of add-ons that block network requests for the script, but I highly doubt that would solve your problem.
Google Analytics is loaded asynchronously, so it doesn't block other scripts or affect the performance of anything else on the page while it's being downloaded.
There may be times where the connection is slow or for whatever reason it takes a while for your browser to download the script from google-analytics.com, but if you page is responding slowly and you happen to see that it's waiting for google-analytics.com at the bottom, those two things are likely not related.
What's far more likely is that whatever is causing the request for the Google Analytics script to be slow is also causing the rest of the page to be slow. In other words Google Analytics is not the root of your problem, it's another symptom.
In either case, you can try blocking it just to be sure. Sometimes web developers implement Google Analytics incorrectly...
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).