According to what I can tell from Google's documentation, discreet hitTypes like pageview, event, and social all count against your "hit" budget. But with eCommerce, it looks like a hitType called "transaction" is sent first, followed by a number of "item" hitTypes. Do each one of these "item" hitTypes count against the budget, or are they included with the single "transaction" hitType.
If anyone knows for absolute certain, I would be most appreciative. Thanks!
https://support.google.com/analytics/answer/1070983?hl=en specifies 10 mio hits as data limit. The Google TOS in their first paragraph specify that an item is a hit ("A Hit may currently be a[n] page view, a transaction, item, or event"). So they count towards the limit.
Related
Does Google Analytics have enough information to answer the question of how much time have my top 100 users spent on my site? I don't need their user information, I don't care about ID or name which I know it doesn't even have. Just the identification of individual users by the cookie GA uses, and a report of how much time the top 100 loyal users spent on my site.
is such a thing possible at all with GA?
From your comment on Colwin's answer:
I don't need google if I have to track this for GA, I just hoped it already has this information such as "page visit duration" on a per-user, ongoing basis. If I had to feed Google that information myself, I can feed my own database and run analytics on it. Thanks anyway.
The Google analytics sessions is
a group of user interactions with your website that take place within a given time frame. For example a single session can contain multiple page views, events, social interactions, and ecommerce transactions.
Average session duration will be calculated as
total duration of all sessions / number of sessions
I don't think this is available from GA out of the box. But you can build something like this with Custom Dimensions available within GA
This will let you setup and send custom metrics dimensions for users that you can then create reports for.
Google Analytics doesn’t allow you to out in PII but random visitor id's should be fine. You can then compare against your own database outside of GA if needed too.
This will allow tracking the same visitor even without them being logged in to your site.
Sending the custom dimensions could possibly look like this.
ga('send', 'pageview', {
'dimension5': '1234567890'
});
You get 20 free custom dimension slots with GA and 200 with GA 360 -> More info here
I think this article has what you are looking for
https://webanalyticsguy.com/2018/01/18/google-analytics-capture-client-id-reporting-purposes/
It shows how to capture the client id which is a decent way to track a specific user. And goes further to explain how to associate that with a metric, in this case the author uses PageView.
You could change this to Average Session Duration or another metric that gives you a sense of time spent.
I guess that you are looking for something like this:
http://www.analytics-ninja.com/blog/2015/02/real-time-page-google-analytics.html
You can get the counts of the users on your site. You can get the seconds they spent on your website page.
I guess this answer will be helpful too: https://qr.ae/TWpkI0
I wonder whether someone can help me please.
I have a user who under a specific property, sporadically receives the following error:
Some hits sent on 03-Jul-2018 to property ...... exceeded one or more hit quotas and were therefore not processed.
Hits can be dropped when daily or monthly hit limits are exceeded. You can view your hit volume levels in Property Settings in Analytics.
Hits can also be dropped if visitor hit limits are exceeded. This can happen when your site is incorrectly generating the visitor ID for a GA session. Contact your website administrator to check that the visitor ID generation has been correctly implemented.
They are not using the Premium account but when I look at the data for the day in question, there aren't any issues with regards to 'High Cardinality' which unless I've misunderstood I'd expect to see.
Could someone look at this please and offer some guidance where the issue may be because this area is fairly new to me.
Many thanks and kind regards
Chris
Collection limits are influenced by 2 factors:
The tracker: whether you use ga.js,gtag.js,analytics.js etc... here are the details.
The property type: whether you are using GA (10M hits / month) or GA 360 (2B hits / month).
In your case you are facing a property limit. To find out when such limits where reached, you can create a custom report using a time dimension (eg date+time) combined with the hits metric. You can also combine the hit metrics with other dimensions (country, browser, device) to see if you find any patterns as to why you're getting so many hits.
Cardinality is something else: it refers to the number of unique value combinations for your dimensions. For instance if you have 500K events where each event category is different, you'll have a Cardinality of 500K on the event category dimension. The more hits, the more likely you'll have a high cardinality, but the 2 aren't necessary related (if you send 10B events with the same category, the cardinality on the category is 1).
So focus on identifying and solving your limits/quotas issue, as it's the real issue here:
If the number of hits is legitimate (you have a huge amount of traffic), then the only options are to upgrade to GA 360 or reduce the number of hits for each session
If the number of hits is abnormally high (eg traffic is stable but hits increased dramatically), look for implementation issues, especially generic event trackers such as error tracking with tools like Google Tag Manager
I track eCommerce transactions with GA and GTM, and trying to create a custom metric which will count how many people are involved in each transaction.
So I created a hit-scoped custom metric and try to pass its value along with the transaction tag in GTM:
Please see screenshot here:
As we know, a transaction in GA is a series of hits: one "transaction" hit and one or more "item" hits. The problem is that GTM sends the custom metric value with ALL of the hits, not just with one. So when I use my hit-scoped metric to measure something, it's measured more than once.
For ex., in a transaction where 2 people are involved, this value (2) is send twice (once with "transaction" hit, once with "item" hit) and in the GA reports I see figure 4 (instead of 2) associated with this transaction.
I didn't find a way to ask GTM to send the custom metric just once.
Am I missing something here? Any suggestions?
Thanks!
You can use a separate tag with the custom metric information, which is triggered on the same event as the transactions. This will create another request to GA, which isn't the best solution in terms of performance.
Maybe you can combine this information with a tag, which is already triggered on the same page? An "all pages" Universal Analytics tag is maybe present and has the information {{QuantityOfInsured}} available at the time the "all pages analytics tag" is triggered.
I'm having an issue with Unique Events and Total events. I don't really understand why unique events are greater than total events (image attached: https://analytics-a-googleproductforums-com.googlegroups.com/attach/584c3c65bd24cfec/Screenshot%20at%202013-05-14%2017:00:40.png?gda=9qkpgUYAAADqfLbDOUx1KZ9vP-6pB8mH0QevsNJBCwpb2zqmxh9R_FqJw8mf6kYUxitGhb4bDE5x40jamwa1UURqDcgHarKEE-Ea7GxYMt0t6nY0uV5FIQ&view=1&part=4).
Someone can explain how this is posible?
Santiago Vázquez
Found the thing: you will see that "Unique Events" are great than "Total Events" when you look at an event category or action, put "Event Label" as a secondary dimension and the event has been triggered some times with no label input. Google Analytics hasn't the option "(not set)" for this particular dimension, so it just doesn't show you those events in the Total Events Count, but still counts as "Unique Events" all the users that executed this particular event category / action.
I am seeing this same issue in my the first view of my Custom Report as well. I don't know WHY it is showing more, but there seems to be a more accurate Custom Report drilldown for you to use. In my reports, one page shows in my Page drilldown with 30 total events but 62 Unique Events. However, when I click into the next dimension drilldown view, in other words click to narrow in on just one page, it shows that same page with 30 total events and only 29 unique events. That seems more accurate.
My dimensions drilldowns for this custom report are "Page" and then "Event Label"
Hope this helps!
I think Google Analytics is simply buggy.
They have to work on event reporting a bit more.
We are tracking events and e-commerce data to our own database, and we realised that both Google Analitics and Universal Analitics misses some events and e-commerce data.
We are trying to find the reason for this, but no luck yet.
If you have a segment applied it's probably sampling. You can confirm or deny sampling is the cause by seeing if there is a yellow background note above the graph but below the date selection on the report page. There is also a grid of filled in and not filled in circles next to the new scholar cap (also below the date selection) sometimes.
Unique events are calculated by session, while total events are determined by the main dimension.
In the example report below, I wanted to look at how many events occurred on each page. The dimension drilldown is Page, with Total Events and Unique Events as metrics.
Users can visit a page, but not send an event by that page ( 0 total events ). However, if their session includes an event, then unique events will be 1 or more.
Custom reports allow data combinations that may not be clear (not sure if someone already posted this point or if I saw it in another thread). Basically, my report should not include Unique Events to prevent this problem from happening, though this was probably the wrong way to go about this altogether.
Template: https://www.google.com/analytics/web/template?uid=XafJ7KvSSf-n5KWWPyvn_g
Google has deprecated (renamed) Unique Events metric as it was seriously confusing. We are expecting to see a number of times event with unique combination of category / action and label happened per other dimensions in report. Instead GA calculated a unique combination of every dimension in the report!
Now, this metric is deprecated and renamed to legacy.
New one: Unique Events is giving expected results.
I written about why total events are higher than in my blog as too many questions.
Total Events are calculated as the total number of interactions with a tracked web page object. On the other hand, where a single user session (or visit) has one or more events, this is calculated as a single Visit w/Event, or Unique Event in the reports. For example, if one user clicks the same button on a video 5 times, the total number of events associated with the video is 5, and the number of unique events is 1.
Are dynamic advanced segments retroactive at the session or visitor level? Can it retroactively recalculate session data or can it retroactively recalculate visitor data?
Here is an example as this is a foggy question.
Say I add an event tag to GA today. Tomorrow i run a report where the dynamic segment is for visitors who have triggered the event. The report requests unique visitors over time.
Now, if it is retroactive at the visitor level, the visitor is now tagged as having triggered the event. The report should show data going back in time (assuming these are not first time visitors). In this scenario GA will see if the visitors tagged arrived 2 days ago even though the events did not exist yet.
This answer no longer reflects up to date information.
Advanced Segments are not queried at the visitor level, and are thus not able to query data across sessions. They query particular sessions (or, visits), not visitors.
So, if you visit the site today, trigger an event, and then visit the site again tomorrow and don't trigger the event, an advanced segment for that event will be a query that says "Show me all sessions in which this event was trigger"; the former will be included and the latter excluded.
Similarly, if you do an advanced segment for a particular page, what you're saying is "Filter down to all the sessions in which this page was viewed" (this can be confusing for people who apply an advanced segment for a particular page, and the result contains more than just that page.)
However, they are dynamic and can be applied to the retroactively. In other words, the results of the advanced segmentation are not contingent on when the advanced segment itself was created. (This stands in contrasts to, say, account filters, that do not apply themselves retroactively.) They tend to be calculated on the fly; you'll notice that complex advanced segments can often take a long time to process, and tend to increase the likelihood that Google Analytics will return sampled (or, "fast access") data.
There is no way to use advanced segmentation to query across sessions.