I am successfully tracking traffic on a site (so far over 150 hits), however the Site Speed is still showing all zeroes. I know that the default is to only calculate speed for 1% of the requests, but it seems that nothing is getting tracked at all for Site Speed. I'm using the newest version of Chrome.
Any ideas? Thanks!
Site speed sample rate sets the percentage of users to be tracked not the percentage of requests. Here's what the docs say:
This setting determines how often site speed tracking beacons will be sent. By default, 1% of users will be automatically be tracked. Note: Analytics restricts Site Speed collection hits for a single property to the greater of 1% of users or 10K hits per day in order to ensure an equitable distribution of system resources for this feature.
In your case, if you don't expect to have more than 10K hits to your property in a single day, you can safely set the sample rate to 100%. Note: this has to be done in the create method:
ga('create', 'UA-XXXX-Y', {'siteSpeedSampleRate': 100});
Have you called the _setSightSpeedSampleRate() method? That would be my best guess. According to the Google docs:
The _setSiteSpeedSampleRate() method must be called prior to _trackPageview() in order to be effective.
Related
We have updated Google Analytics sampling rate to 100% for many partners.
ga('create', 'UA-xxxxxxxxx-x', {'siteSpeedSampleRate': 100});
However, for some partners, we observed that all pageviews are not set for page load sampling. In some cases, it is around 80%.
Is there any exact reason for this? Doesn't {'siteSpeedSampleRate': 100} means all pageviews should be sent for page load sampling?
Thanks!
Even if you put the sampling rate to 100 you can still hit quota limits here (Site Speed processing quota limit).
https://developers.google.com/analytics/devguides/collection/analyticsjs/user-timings#sampling_considerations
To measure all the site speed hits you can extract the values (different load times) via GTM and some custom javascript and send the values as dimensions or events.
We are using Google Analytics on a webshop. Recently we have added enhanced ecommerce to measure more events so we can optimize the webshop. But now we are experiencing less pageviews and other data is missing.
I don't know what it is, but on a specific page we are nog measuring anymore, I removed some items from the ga:addImpression data, and now the pageview is measured again.
I can find limits for GA, but I can't find anything for the amount of data that can be send to GA. Because is this seems to be related to the amount of data that is send to GA. If I shorten the name of a product, the pageview is also measured again. GA is practically broken now for us because we are missing huge numbers of pageviews.
Where can I find these limits, or how will I ever know when I'm running into these limits?
In one hand, im not sure how are you building your hits but maybe you should keep in mind the payload limits to send information to GA. (The limit is 8Kb)
In the other hand there is a limit in fact that you should consider (Docs)
This applies to analytics.js, Android iOS SDK, and the Measurement Protocol.
200,000 hits per user per day
500 hits per session
If you go over either of these limits, additional hits will not be processed for that session / day, respectively. These limits apply to Analytics 360 as well.
My best advise is to regulate the amount of events you send really considering which information has value. No doubt EE data is really important so you should partition productImpression hits in multiple ones of the problem is the size. (As shown in the screenshot)
And finally, migrate to GTM.
EDIT: Steps to see what the dataLayer has in it (in a given moment)
A Google Analytics request can send max about 8KB of data:
POST:
payload_data – The BODY of the post request. The body must include
exactly 1 URI encoded payload and must be no longer than 8192 bytes.
URL Endpoint
The length of the entire encoded URL must be no longer than 8000
Bytes.
If your hit exceeds that limit (happens e.g. with large product lists in EEC tracking) it is not (as far as I can tell) processed.
There are also restrictions to field length for some fields (e.g. custom dimension with max 150 bytes, others are detailed in the parameter reference ).
In some cases the data type is relevant, e.g. if in your event tracking the event value is set to a string the call might fail.
I think this is the page you are looking for Quota and limits page can help
These limits apply to the Web Property / Property / Tracking ID.
10 million hits per month per property
If you go over this limit, the Google Analytics team might contact you and ask you upgrade to Analytics 360 or implement client sampling to reduce the amount of data being sent to Google Analytics.
I defined a Site Speed Sample Rate of 100% (via the Google Tag Manager). It's definitely more than 1% now but far from 100%. In fact a comparison of the speed samples and real pageviews in GA shows, that the rate is at constant 25% now. Our page has about 10,0000 users per day. Every page includes the same simple tag.
Any ideas what could be wrong? Thanks!
Site speed hits are sampled on the server as well as the client. You may be running into the limits outlined here:
https://developers.google.com/analytics/devguides/collection/analyticsjs/user-timings#sampling
In fact a comparison of the speed samples and real pageviews in GA shows, that the rate is at constant 25% now.
I'm not sure how you're coming to this conclusion. I don't think there's any reliable way to know what percentage of hits were sent from looking at reports.
The best way to test whether 100% of hits are being sent is to inspect the network tab in your browser's developer tools. If you set siteSpeedSampleRate to 100, you should be able to clear your cookies, refresh the page, and see timing hits being sent. If you repeat this (making sure to clear cookies), you should see hits being sent 100% of the time.
Although setting siteSpeedSampleRate to 100 will indeed send speed data every time, you might be hitting one of the site speed processing quotas:
https://developers.google.com/analytics/devguides/collection/analyticsjs/limits-quotas#timing_hits
https://developers.google.com/analytics/devguides/collection/analyticsjs/user-timings#sampling_considerations
I am using Google Web Analytics Online Tool to monitor visits on my site.
What bugs me is that often I see that records contain the folloowing entries:
Page Visits: 1.00
Average Visit Duration: 00:00:00
Bounce Rate: 100%
What does that mean?
If the visitor comes to my site it should stay at least couple of seconds until he leaves?
Could that mean that something is wrong with accessing my site (I had similar problems before, but I am convinced I fixed them since I am not getting any errors when I try to access my site from different computers.)
When a visitor comes to your page google analytics sets a cookie where a timestamp is stored. When the user visits a second page in your site Google compares the stored timestamp to the actual time and calculates visits duration from the difference between the two. If all your visitors have bounced there is no second data point to compare the stored value to and google is unable to compute a duration.
A common workaround is to set a javascript timeout and trigger an event after ten seconds or so (with the "interaction" flag in the event set to true, see Google Analytics event tracking docs for details). The assumption is that somebody who looks for more than ten seconds at you page is not actually a bounce (I think that since "bounce rate" has so hugely negative connotations people try to avoid high bounce rates even at the price of introducing bad data; you should realize that "bounce rate" simply means that there are not enough data points to say anything meaningful about those particular visitors).
Personally I do not like that approach because it means to redefine inaction of a visitor as action. A better idea (IMO) is to implement a meaningful interaction point - like a "read more" link that loads content via ajax or something like it - and track that via event tracking or virtual page view.
Event tracking guide:
https://developers.google.com/analytics/devguides/collection/gajs/eventTrackerGuide
Short Update: With Universal Analytics the technical details have changed (i.e. there are no longer cookies with timestamps, all information is processed on the GA servers). So the first paragraph is no longer up to date, however the rest of the answer is still valid.
I'm having a similar issue, i monitor those placements and recently found out the traffic is hardly getting to my site, recent experiment showed that those are placements triggered via clicks from GDN, but people have not even reached my page, were blocked by pop-up blocker or other similar software
I have a website which has around 500-600 vists per week. I would like to increase the sampling size to 100% in the google analytics tracking code.
I would like to know if this has eny effect on the performance of my website
Contrary to the comment above Google has an option to set sample sizes:
https://developers.google.com/analytics/devguides/collection/gajs/methods/gaJSApiBasicConfiguration#_gat.GA_Tracker_._setSampleRate
This will not affect you visitors (since the pixel is sent anyway, sampling happens during data processing).
I don't think it will make any difference if you have only a few hundred visitors, though (I'm guessing that Google is smart enough not to use sampling unless necessary, and in any case you should use setSampleRate to make your samples smaller, not bigger).
2016 answer
According to the official doc, the default sampling rate is 1%. If your site has little traffic, you can increase this rate with setSiteSpeedSampleRate()