Analytics | Measuring page velocity for page value? - google-analytics

I'm trying to give my pages a value equal to page velocity. I'm reading through this guide which says:
https://online-behavior.com/analytics/page-velocity
"To measure Page Velocity, we will need to send an Ecommerce transaction with an arbitrary value of $1 on every pageview so it receives credit for the future pageviews as well."
How would I go about doing this?

I hate to say this but the implementation 'depends' on different use cases. The blog you have shared is primarily intended for content heavy site and not ecommerce sites. The next step would be to create a completely different view so that the ecommerce numbers do not mess up your original numbers.
Second step would be to assign a page value in terms of 1 dollar to the goal pages (main content pages) or all pages depending on how you want to do it.
You just need to remember page value = (transaction value + goal value)/ unique pageviews.
Unique page views is ' the number of individual users who have loaded a given page per session'. Hope this makes sense

Related

Are goals the only way to track conversion rate of non-landing pages, in Google Analytics

It seems easy to look at conversion rates of landing pages in google analytics via:
behaviour > site content > landing pages
(there's an 'ecommerce conversion rate' column displaying conversion rate for each landing page).
However, if I want to look at the conversion rate for a page that a user wouldn't "land" on / enter the site on, such as a search results page, i can't work out how to do this.
Other than setting up goals. I wondered if there was an easier way?
Ideally - when i go to:
site content > all pages
If it had the ecommerce column, that would be ideal. But doesn't seem possible.
You can create Segments and analyze their Conversionrates. However pages can not have conversionrates because a page can be visited multiple times within one session, whereas landingpages and channels are 1:1 connected to one session. Within a segment you can set the condition "page contains /xyz/" this way you create a session scope for a hit condition.

Goal conversion rate per page view

When I go to the "Landing pages" section of Google Analytics (Behaviour > Site Content > Landing pages), I can see "My goal name (Goal 1 Conversion Rate)", which is "The percentage of visits that resulted in a conversion to the goal". This way I know that XX.XX% of user who landed on a particular page ended up reaching a goal.
Is there any chance I can retrieve the same data for ANY given page view instead (i.e. know that XX.XX% of users who viewed a page ended up reaching a goal)?
You can create a custom segment of your users or sessions, who have visited a given page, or have landed on a given page. (Look for Conditions under Advanced group of New segment dialog.) You can filter reports for this segment only, and get the information, you are looking for.

Destination Goal not taking funnel into consideration

I have a very basic site goal:
When someone gets to the '/my-account' page directly from the '/component/community/ajaxregister/ajaxregister' page, it needs to count it as a conversion (Registration).
I have a custom destination goal set up:
Destination = '/my-account'
Funnel: ON
Step 1 '/component/community/ajaxregister/ajaxregister' Requires? YES
The registration counts in my db do not match the goal count and the 'Reverse Goal Path' report shows that there are conversions being registered where the 'Goal Previous - Step 1' includes pages other than the registration page.
Any ideas on how to make this goal register only when one lands on my-account from the registration page?
The "required step" merely affects funnel visualization, not goal conversion. So by default there is no way not make this count only when people come from the registration page.
To solve this in code (and thus make the question on topic :-) ) you could
check the referring page on your goal conversion page, then
fire an event when the referrer is the registration pages, and
then switch to an event-based goal in the GA backend
That way you would not have a funnel (does not work with event based goals), but at least you'd have the "correct" number of conversions.

Can I filter a Google Analytics segment based on content grouping pageview count?

I want to create a Google Analytics segment for our users who view at least a certain number of pages on our site. From what I can tell (please correct me if I'm wrong) this is easy to do if you don't care about what kind of page they view: you create a filter for the segment that checks to see if Unique Pageviews is greater than some value such as 4. However our site has a whole bunch of pages that I don't really care if someone reads (our "about page" for example). So what I'm trying to do is create a segment of how many people view at least X pages of what we call "Learning Content" (basically two specific page types on our site). How can I segment the users who read a certain amount of learning content?
Two types of pages fit into our definition of learning content. The first one has a URL matching a regex that sort of looks like /learning_content_1/.* and the second matches regex /learning_content_2/.*. I've already created a content group for learning content that correctly identifies these two content groups. However I wasn't able to find any way to filter a segment based on how many unique pageviews (or even just pageviews) come from a specific content grouping. Is this even possible? If not, how might I work around that?
The research I've done so far: Google Analytics: How to segment by many groups of pages was somewhat helpful but didn't address the question of how to create an actual GA segment based on pageview information for a content grouping or content group.
The only way I can think of handling this, is by associating a specific custom event that gets triggered on this page. Then you can create a segment that matches users who have that event category:
and total events greater than 4:
It's a workaround, and it doesn't work if you are tracking other events, but maybe that works for you?

How are dynamic segments in Google Analytics retroactive?

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.

Resources