I'm currently trying to figure out what percentage of my hourly views have a Visit Duration of 00:00:00.
It's easy enough to create an Advanced Segment for views of '0 seconds' and compare that to my total views - what I'd like to know is: can you combine these two segments, to create a parameter which is '#total-views / #0-sec-views'? And, if so, how?
In other words, how can I define my own parameter which tells me how many of my views lasted for 0 seconds?
Thanks, J
Zetland, just select both segments:
your custom segment for 0s visits
pre-defined segment for All Visits
Tick both and you should see the comparison, even with percentage difference right in the table below the chart.
One more suggestion: 0s visit is a very unusual segment, as it tracks visits that didn't include more than 2 pageviews (hence the time-difference couldn't be measured). I would suggest using Bounce Visits or Non-converters (or anything similar).
Hope this helps!
Related
Hello FullCalendar team,
I am looking to build a feature that would limit the type of events that could go into a specific timeslot.
For example, I would like to indicate to a front-desk end-user that only a certain type of appointment was allowed to be entered into the timeslot. Perhaps the timeslot only takes meeting types that are tagged "check-ins" and "follow-ups" arbitrarily set by some higher up admin.
What would be the best way to go about building this limitation and displaying it to the user? I saw that there is an overlap function I might be able to use along with background-events. The higher-up admin might be able to create background-events that if they overlap with another requested event then limits the type. THen it would be very clear that any certain color-coded event set by the higher-admin would indicate that only certain types could be added.
But am I missing a very obvious way to do this? I was hoping there might be an easier way to templatize the day for end-users. Appreciate the advice.
I am trying to create a funnel of the signup process (i.e. how many users bail out at each step).
However the numbers don't match up with the site statistics. I think the funnel is session based and not unique users based. And it also seems that a user can be counted multiple times.
What is the suggested way to get a funnel that simply tells me how many of the distinct users bail out at which step?
I don't think Google Analytics supports user based funnels.
As an alternate you can create sequential advance segments to simulate user level funnel.
Example:
Assuming your funnel has 3 steps (URLs), create 3 user based segments as below:
Level 1:
Level 2:
Level 3:
After creating the three segments, apply them to Audience > Overview report in the right order:
Although it doesn't provide you the percentage drops outright, you can calculate them manually.
Hope this helps.
NOTE: If your site receives high volumes of traffic, sampling can impact the results.
I'm trying to get all unique visitors for a selected time period, but I want to filter them by date on the server. However, the sum of unique visitors for each day isn't the number of unique visitors for the time period.
For example:
Monday: 2 unique visitors
Tuesday: 3 unique visitors
The unique visitors for the two days period isn't necessarily 5.
Is there a way to get the results I want using the Google Analytics API (v3)?
You're right that Users aren't additive, so you can't simply add them day by day. There are several ways around this.
The fist and most obvious is that if you've implemented the User-ID you should be able to straight up pull and interrogate the data about which users saw your site on which days.
Another way I've implemented before is to dynamically pull the number of Users from the Google Analytics API whenever you need it. Obviously this only works if you're populating a live web dashboard or similar, but since it's just the one figure you're asking for, it wouldn't slow down the load time by much. Eg. if you're using a dashboarding tool such as Klipfolio, you may be able to define a dynamic data source, and query Google whenever you needthe figure (https://support.klipfolio.com/hc/en-us/articles/216183237-BETA-Working-with-dynamic-data-sources)
You could also limit the number of ways that the data can be interrogated, and calculate all of them. For example, if you only allow users to look at data month-by-month or day-by-day, then you only need those figures.
Finally, you can estimate the figure with reasonable accuracy by splitting it into two parts. New Users are equal to New Sessions (you're only new on your first Session), which is additive, so that figure can be separated out and combined as required.
Then, you could take a rough ratio of new to returning Users (% New Users) from, say, 1 year of data, and use that with the New Users figure to generate an average on any level.
Within GA, is it possible to segment metrics into ranges?
For example -
Average Page load time > 2s
Average Page load time 2 - 4s
Average Page load time < 4s
Or is this only doable with further processing in excel/sheets?
Edit -
Specifically, I am looking to build a report that looks at average load time and the effects on conversion, bounce rate, AOV, etc. for the site and for specific pages.
Short answer is no. The longer answer is that you could try the following two things:
Filter the report as this will allow you to define ranges:
screenshot
Implement your own user timing logic and set a time-format custom metric
Just keep in mind that if you did go for #2 that you'd be setting a hit-scope custom metric so when you come to use it in a segment you'll be forced to look at sessions/users who had a page load time within a session or group of sessions with your given thresholds.
If you had a specific business question in mind it may be more appropriate for me to provide a solution to that as it may be different...
The numbers that are shown within a goal flow node do not match the numbers shown in the table below it in the total row.
Could someone please explain why this is or if these numbers represent something different?
The numbers in the table below are visits. The numbers in the nodes are pageviews. Where you get a loop back from one node to another, you'll notice more pageviews than visits (because one visitor has seen the page twice).