Would GA not count as a bounce if a scroll tracking event was sent from my landing page?
We currently have a simple ecommerce site selling 1 item therefore most of all the necessary info (testimonials, product description...etc) is on the very first page as a scroll down. There are a few separate pages (contact, about..etc) however with most of it being on the first page, my bounce rate is very high.
My main concern at this point is the high bounce rate is negatively effecting my Adwords Quality Score.
If I added a scroll tracking event on my landing page and visitors scroll down to a certain percentage, would GA not count it as a bounce?
Any thoughts would be appreciated
An event in Google Analytics will have an effect on your bounce rate, based on its non-interaction flag parameter. This is an optional parameter, and by default it is set to false, meaning event will count as interactive, and sessions with interactive events will not be counted as bounced sessions. For further details and explanations you can read through this support article.
The Google Analytics developers guide will show you the details, how to set this so called non-interaction flag of events, which will control this behavior. By default, without setting non-interaction flag to true, events will count as interactive, and will reduce bounce rate.
Related
I need some help with Google Tag Manager and Google Analytics.
I want to send a pageview to Google Analytics if a user is viewing an image in a gallery on an article. The user is staying on the same URL, when he is viewing an image.
I created a trigger group which consists of two events
• Consent given by the user to use Google Analytics
• Event which is fired when an image in a gallery is being viewed
This works so far so good. Unfortunately, the trigger group is only being fired once on a page. When a user open the gallery and views the image and scrolls to next image, he is staying on the same URL. In that case, the trigger group is only being fired once.
How can I achieve that the trigger group is being fired multiple times on the same page without removing the second trigger (consent)?
I found out that I can create a second trigger group and add two image views and the consent as a trigger. But this solution means that I have to create 100 new tags, which is kind of crazy. Is there any workaround?
Thanks in advance
Once consent has been given by the user in a way that each pageview can pick up (e.g. you're setting it in some persisted state: data layer, cookie, etc.), you're ultimately just looking at triggering when the event happens.
Since you describe a scenario where it happens only once, I'd urge you to take a look at the other triggers on your tag and remove the page-specific trigger your description suggests you have in place. Replace it with only your event and consent triggers and it should work every time an event is observed.
By Default while creating a tag, this Non interaction value is set to false . I have gone through some articles but couldnt understand this non interaction hit topic.
Non-interaction events are not accounted for when calculating bounce rate of time metrics. This means that if a visitor views a single page and fires a non-interaction event, the session is still considered a bounce and has a session duration of zero minutes. If the user views a single page but an interaction event is fired, the session is no longer considered a bounce, and the session duration is the time between the pageview and the event.
I'm receiving data from my GA, but it can be viewed only under the real-time reports events tab. But where GA stores these events? I mean where GA saves all received events? Is it possible to view for example events for several past days or several past months?
in the sidebar choose "all events" and select the event you are looking for.
you change the time interval on the top left of the page.
For example, if I have a news page that's already being tracked via GA and I add a javascript event to capture clicks on a specific link to the news page (e.g. navigation) am I then 'double counting'?
If a fake pageview is not beneficial in this situation, and from your description that you're looking to track an engagement click on your page, use Event Tracking instead of Pageviews.
Tracking a click/event is easy (especially if you're already using Javascript). The best part is that this event is not considered a page view, keeping those stats safe.
The implementation is simple and allows for quite a bit of customization:
_trackEvent(category, action, opt_label, opt_value)
Below is an example of a link that's been encoded with an event tag:
Play
Here's the Google Analytics resource page on Event Tagging:
http://code.google.com/apis/analytics/docs/tracking/eventTrackerGuide.html
Well it's not a real page view, but Google Analytics thinks that it is--i.e., it shows up in your pageview counts.
Fortunately, it's easy to filter those so they don't contaminate your pageview data.
So for instance,
_gaq.push(['_trackPageview', 'unique_virtual_pagename']);
So in your GA Browser, you'll see the number of clicks actually shown as the number of pageviews of *unique_virtual_pagename*, which is not good.
There are a two ways to fix this (that i am aware of): (i) set a temporary filter at the bottom of the pageview table; or (ii) set a persistent (c*ustom*) filter in your Admin Panel (which i think is best) to remove pageviews having only the name *unique_virtual_pagename*, or whatever name you've chosen. This will of course take up to 24 hours to set, so the best plan is to set the filter first, then add the javascript to your page. so the filter is active when you begin collecting clicks.
But that just solves the problem of disaggregating these virtual pageviews from your real pageviews, you still need a way to count/record them.
I prefer to create a separate profile in these cases. So first, i filter the virtual pageviews from my actual pageviews using a custom filter, then i create a new profile which has another filter excluding everything but these virtual pageviews. I usually give that profile a name based on the event.
What you're doing is registering what's called a 'virtual page view'. To GA it's seen as a real page view and shows up in your content report's and page view counts etc. This is often useful if you want to show a page view for media that GA can't track. It's also commonly used to count an event, such as a button click, as a goal conversion.
If you just want to record the event and not count a page view you should look at using GA event tracking instead.
A mortgage page on our website is accesible by multiple links on one page. In order to determine which of the links on that same page has been clicked on, I use event tracking. All events for these links are being stored under the category: "mortgage"
When I look at the total number of pageviews for this mortgage page and the total number of events for the event category "mortgage", the number of pageviews is 10%-20% higher.
My questions are:
Can I compare pageviews and events?
If not, why not?
Thanks,
Aart Nicolai (funda.nl)
You can create a report.
Create a new custom report
In the Metric Groups, select metrics: "visits" and "Pageviews"
In Dimension, select "event category", "event action", and "event label"
The 10%-20% that your seeing are people that are viewing the page and not clicking the link that you have the event on.
Comparing them is the best way to determine how well the site is performing in terms of enticing visitors to click on the link.
Incidentally, within Google Analytics, you can add the Page dimension to your Events reports to get a breakdown of which page the user was on when the event occurred. This is especially useful if you have similar events on different pages of the site.