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!
Related
There are two events.
User visit /point1.
User visit /point2.
If the events occur in this order, I want the goal to be hit.
I have created a funnel for this, but the problem is that even if the user does not visit /point1, and visit /point2, the goal is hit! (destination is point2..)
I want the goal to be hit only when the user visit /point1 and /point2 in that order.How can I accomplish this?
Basically you can't (not via configuration, that is). Funnels only affect the visualisation, not goal completion.
You can either do a workaround in code - set a cookie on /point1, then fire an event on /point2 only when the cookie is set, and change your configuration to use an event based goal.
If you do not need to actual goal conversion, but just want to know how many users completed the steps in the correct order, you can create a segment of the "sequence" type (step1 page equals /point1 followed by step2 page equals /point2), which will limit the data displayed in the standard reports to sessions where users visited one point after the other.
I've got a process on my website that I would like to track as a funnel, except I am unclear on how to do so since the process has a loop.
We are building a single-page tool that calculates the number of products the user needs for their home, which is based on how many rooms the home has and the details of each room. Here is an example workflow:
Create Home
Add Room 1, set details, click Save
Add Room 2, set details, click Save
Edit Room 1 details, click Save
Click Analyze
As you can see from steps 1 and 2, the user can add a variable number of rooms. From step 4 you can see that they can go back to edit a room after they've created it.
I would like to see where users drop off, so I'd like to see this funnel, minimally:
Create Home -> Save at least 1 room -> Click Analyze
If I track "Save Room" as a page view (/save-room) there will be a lot of drop off once users start to add more rooms: it will look like they exit the funnel at /save-room by going to /save-room... right? Should I control this with Javascript to make sure that the /save-room pageview is only sent once per process? Is there a better way?
Additionally, I would like to track whether people with larger homes (more rooms) drop off more frequently. So if I prevent additional /save-room page views from being sent, I would lose this visibility. Should I track all of these operations as events as well?
Thanks in advance!
Funnels do (literally) not have loops (that's one of the reasons Google introduced flow reports).
One possible way would be to create a session based custom metric. You set it to 1 at the first "save room" pageload, then instead of doing more "save room" pageviews you track an event for each additional room and increment the custom metric in the event (thus saving the number of rooms; you'd need to create a custom report, since custom metrics do not show up in standard reports, but you would get the info for the number of rooms and still be able to use the funnel visualization).
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.
In our user sign-up process, conversion is being defined each time a user completes 4 steps and lands on their individual user home page (/publications\/.*). The RegEx is functioning properly, however I realized that GA is registering a "conversion" every time a user signs back in and visits that same page for the second time, third time, etc., since that page is just each user's "home" page on return sign-ins.
Is there a way to force GA to recognize the visits ONLY the first time a user hits that page?
Thanks for your help in advance!
No. You better create a new url for when the process completes, or maybe fire a virtual pageview once the user completes registration.
You can also mark the first step of the process as a required step. You create a URL Goal but add the sign-up form as a required step. The problem with this setp is that it only applies to the funnel view. The total conversions would still count all of them, but when you look at the funnel view you would only see the conversions that went through the required first step.
There are a couple of ways I could think of:
Eduardo's virtual pageview recorded on a successful sign-up would be
my number one recommendation. This pageview will become your Goal
Conversion URL and will take care of the repeat offenders.
Set a cookie for your registered users and have that determine the conversion tracking.
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.