One of our clients has AMP templates set up for their Ecommerce site. They're capturing AMP & non-AMP data in the same GA property. When they're looking in GA and trying to filter for AMP traffic, there's been a bit of confusion.
There were two different ways that they were filtering for AMP traffic:
By looking at the Source/Medium, and manually selecting all Source/Mediums that had AMP contained in them ie: client-amp--mobify-com.cdn.ampproject.org / referral
By setting up a new segment that filtered for all sessions which contained AMP as a Data Source.
These two different ways however were giving vastly differing data.
I then noticed when looking through all the listed Sources/Mediums that there was actually an identical pair for client-amp--mobify-com.cdn.ampproject.org / referral, except one had a data source set as AMP and the other had a data source set as Web.
I'm confused here, as it seems like the data source for that should've been set to AMP and that there would only be one of those Source/Mediums as its very clearly coming from an AMP source.
Why is there a pair of identical Source/Mediums that have differing data sources when it's clearly an AMP data source?
Related
I want to use Firebase Analytics in my website in order to get some statistics for the visitors of each page (I don't want to track user journey in the site). I wanted to define multiple data streams (one for each url) in my google analytics dashboard, but then it warned me with the following message:
In most cases, a single web stream will meet your measurement needs. Using multiple web streams to measure different pages or sites in a single user’s journey may lead to inconsistent results.
in my case-where I want to see the statistics of my site based on its pages (urls)-should I define multiple data streams?
As the message says, it is not necessary to split based on the path in the web site.
You can in the Google Analytics console instead filter based on that path. This gives you the best of both worlds, as you can show stats for a specific path, but also for the site in its entirety.
I ended up using separate data streams in a similar situation where we had a multilingual site with a domain-per-language. The analytics dashboard lets you separate the data by domain, but the tools are bulky and don't seem available everywhere.
In short, creating a separate stream for data that is always going to be viewed separately can be a real convenience, even if it's not "the right way".
The main caveat from the data-streams documentation seems to be that you can miscount data. For instance, a user switching from the English site to the French site will be counted as a visitor on each rather than as a single visit. As long as you're aware of the data implications, you should be okay.
I am revising a site and some changes to page naming will be unavoidable. I would like to retain a relationship to the historical Google Analytics information for pages whose names will be changed.
When changing page names and extensions -- including changes that reorder folder structure -- how can I link the Google Analytics data for NEWPAGENAME.php, for example, to the data associated with the OLDPAGENAME.html page it has replaced?
You cannot match the data once they have been acquired in Google Analytics, so one possibility is to apply a filter that rewrites the names of the pages and transforms them into the original ones, eg: index.html -> index.php (does not reflect the reality but ensures that the data is comparable and aggregable).
There was a mistake and we used one google analytics script in two different websites. We removed the script from one of the sites but because of this mistake we now have a lot of invalid data.
How can I remove the data of the other website?
you cant remove data already in the reports. General "best practice" is to leave the default All Website Data view without any filters applied, and then create one (or more) reporting views (depending on reporting needs) and apply an Include Hostname filter. This prevents data from invalid hostnames ending up in reports (such as in this instance).
To view the historical report data without the erroneous site data included, you can create and apply a segment to only include sessions (or users) for hostname yourdomain.com
I currently manage quite a few Google Analytics accounts for different websites and am trying to work out how to remove certain Anayltics spam from these accounts. I have previously added filters like excluding Russia visitors as the businesses are local UK based but I am now getting a lot of traffic from:
Language - not set
&
Page - sharebutton.to
If i was to exlucde the above would that get rid of any actual visitors as well as spam or will it get rid of 100% spam?
If someone could help with this that would be brilliant.
Many Thanks
Paul
Filters based on countries or the name of the spam are not efficient because both can be easily changed by the spammers.
Also, it isn't possible to filter the (not set) entries in Analytics, this label is added after the visit is recorded when Analytics doesn't find a value for that dimension.
Instead what you should use
One hostname filter, this will help prevent the majority of the spam, whether it shows as referral, page, language, etc. and independently of the name used by the spammer.
A source filter for the sneaky crawlers which are far less frequent.
Here you will find detailed instructions on how to create the hostname filter and other measures you can take to prevent fake traffic.
Google Analytics is recording a page called ".../form", but separately it is also reporting redirects to that page as "/form?/=test"
Under Site Content they are both listed separately.
In a case like this am I right to assume these are separate metrics that need to be added together to provide a truer picture of activity.
Or is it a case where ".../form" also includes all traffic from "/form?/=test"
EDIT: The URLs were due to redirected legacy traffic and since both were recording data in GA just trying to see about data collected to date.
It seems to me that absolute URLs are needed rather than relative.
Is there somewhere to point to "http://my.domain.com/form" instead of just "/form"?