I want to know how many people (in percent) comming from a specific referer (like direct, paid search, organic search and so on) click on at least one outgoing link on my website. (If somebody clicks 10 outgoing links it should count as much as somebody who only clicks one link).
What i did was to create a custom event which is triggered every time a user clicks an outgoing lnik. This is working so far, but how can i filter the data in the way i explained before?
Thanks for your help.
Use Unique Events.
http://searchenginewatch.com/article/2350415/How-to-Use-the-Google-Analytics-Event-Tracking-Report
Unique Events: Events of the same type within the same session have
been removed from total events to de-duplicate them, this helps you
identify events which are triggered multiple times per session or if
an event is only important once then this is more important to you
than total events.
Alternatively, you could drop a key in localStorage (or a cookie) per link so you would only fire the event once per session/cookie.
Related
I am trying to create a "Custom Report" in Google Analytics but cannot get the dimension/metric to work. My goal is to retrieve all pages of a user that triggered an event(also a goal) on which pages before they converted(purchased - ecommerce)?
Like this:
1) User enters the main page ("/")
2) User goes trough 3-4 article pages (20 seconds activity triggers an event that also is a goal in GA.
3) User fills out form and submits (Enhanced Ecommerce - transaction)
My Goal is to list out either:
1) How many times a user triggered this particular event before purchasing
2) List all pages on where user triggered this particular event before purchasing.
My Custom Report looks like this:
But gives 0 rows in return.
This is caused by the filter that you are using, where you are trying to combine Hit level data with session data. Events are gathered at hit level, where as the question you ask needs to be looked at from a sessionalization perspective.
Let me describe what I believe is happening. Since a user on your website is browsing the articles page, they trigger an event called "Content viewed". Not sure how many times or the exact coding here, but let's say it triggered four times. This is then tied to the Event as a Hit to the page that it triggered on.
On the following page, the order page, they trigger the event "Order Completed" after they register, which again, the event is registered Hit level on that page. This means that on pages ABCD, they trigger the event for "Content viewed".
What you need is a segment to do this kind of analysis. A segment ties together sessions and users from Hit level data, so you can answer questions like: "Which Users have triggered "Content viewed" and then completed registration?"
Sessionalization works by creating sessions tied to a User (client ID) and what happened during that Session. A Session carries different Hits, which are then aggregated as a Unique Visitor, or User, over a number of sessions.
Hope my explanation helped!
I would like to compare some data between a 3rd party analytics tool and GA.
Now I would love to see the IP addresses that Ga is receiving however it seems that they do not reveal this information, fine, however, I cannot find a way to use the flat table in the GA custom report to show me the following if possible;
Full Date Time (Seems as though they don't want you to have this either)
Browser Version
Browser Width & Height
Page (from the hit)
And I would like this data not to be grouped by the metric, this way I can see that if the same user has hit a page 3 times it isn't grouped.
If anyone can help please let me know. If the question is poorly phrased please let me know.
Thanks,
Connor.
This requires some work, and it will allow the breakdown only for future hits, not for hits that are already collected.
To view individual hits you need to create a hit based dimension that is unique per hit. Unless your page has an amazing amount of traffic a timestamp in milliseconds (e.g. new Date().getTime()) will be sufficient (for your report you might want to format that in a nice way). So in the admin section of your GA property you go to custom definitions, create a hit scoped custom dimension, and then modify your pagecode to send the timestamp to that dimension. Hit scoped means it is attached to the pageview (or other interacton hit) it is sent with.
If you want to break down your report by user you need the clientid (clientid is how Google recognizes that hits belong to the same user). Again, send it as a custom dimension.
This does not tell you how many sessions the user had (there is no session identifier in GA). If you need to know that you can create a session scoped custom dimension and send a random number along ("session scope" means that GA only stores the last value in a session, so you don't need to maintain a session id over multiple pageviews, since the last value will be set for all hits within the session). The number of different sessions ids per client id then tells you the number of sessions per user.
The takeaway is that GA only shows aggregated data, and if you want to defeat this mechanism you need to throw data at it that cannot be aggregated further. You might run into other constraints (i.e. there is a limited number of rows per report).
I'm trying to find the number of unique users who fired the event of enabling the widget using Google Analytics.
I created a segment based on the relevant Category and Action of this event but I'm not sure if I should filter it by users or by sessions- can someone please explain the difference.
Moreover, I'm not sure on which number I should look after applying this segment. Should I look on:
Audience-> Overview-> users
Audience-> Active users
Behaviour-> events-> unique events
can someone please explain the difference of these three numbers.
Thanks in advance
Liran.
My situation in Google Analytics is as follows:
Everytime, user clicks a particular element on my website, it is recorded as an event (call it EVENT1).
The problem is that my GA goal is to have at least three of those elements clicked per visit.
We can say that the goal is fulfilled when a user causes 3 EVENT1 events per one visit.
Is it possible to define this?
I know it is possible to track number of pages/visit. But it is not what I am looking for, as there are many pages that does not include the element which can be clicked.
I guess another way would be to use javascript and send "CLICKED 3 TIMES" event to GA. But I would like to avoid this.
Create an advanced segment of the "sequence" type. Make every step the same event. Apply the segment to see the number of visitors included in that segment.
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.