I found 10% high number of sessions in the GTM analyitcs data than the GA. Both has different tracking properties, have similar settings(as Simoahava mentioned #here), Hence the Ecommenrce rate is affecting due to huge difference of sesions data in both properties. Any insights ?
Screenshots :
Session via GTM Session via GA
Even when out of scope for the question i need to advice you to remove the legacy UA code from site and just duplicate the hits from GTM. (Simo has a post about it)
Now going into the question it self this can have a couple of reasons:
Does the filters on both views match?
Does both views has the same region (on the config)?
And i have another theory but this is not at all checked. (i would like to look into it)
GTM has a noscript snippet which allows to send non-script dependent tags even when javascript is not enabled. This is an advantage against the old GA code which doent have this feature.
Point i may have to look into:
Does the pageview count as a non-script dependent tag?
Is the traffic without javascript that relevant in volume? (10% is a lot)
Hope it helps !
Related
Question about migrating manually inserted Meta pixels/Events to GTM. Any feedback is much appreciated!
We manually installed the FB Pixel and manually created events b installing the code into our website a few months ago.
Now, we want to migrate all of these events, including the pixel loading code to GTM.
My question: If I delete the existing pixels loading/event creation code on the website and create the appropriate tags/trigger in GTM:
a) will those 'new GTM' events be pushed as new events to Meta
b) will the pixel have to re-learn?
c) will I lose the data flowing into my existing ads?
For example, if I delete the following code from the website and create the appropriate tag in GTM how will these events change?
<script>
fbq('track', 'Lead');
</script>
a) No, there is no magic whatsoever. Inspect how the network requests to Meta look right now, then reimplement them in GTM and in GTM preview on your lower env make sure the GTM-spawned network requests are exactly like they are on prod. As long as the requests are the same, the endpoint won't know the difference.
b) No, it won't know anything has changed. Exceeept... Note that some adblockers may block GTM, but allow facebook, so the volume of conversions may be slightly lower, but that shouldn't affect FB's learning.
c) You may lose some data, but not much since most of the adblockers block both, facebook and GTM. The data loss is likely to be low enough to be immeasurable and insignificant.
But again, during the development, test your network requests if you don't want surprises. The data should not change unless you make mistakes.
So I've been working on a website for a while. GA account has been up for a couple months but I waited for the website to be finished before putting up the actual JS tag.
In the meantime, the website is being HTTP password restricted (basic authentication) so it isn't even accessible unless you know the user/pwd combination.
To my surprise, I realized today that GA has logged several hundred views to the root of my website. Paths are mostly things like:
/
/?from=http://social-widget.xyz/
/?from=http://www.traffic2cash.xyz/
Bounce% and exit% both at 100% for all of them.
I realize this looks like referral spam, and there are ways to prevent it. Came across this upon googling:
http://botcrawl.com/block-social-widget-xyz-referral-spam-in-google-analytics/
My question is: how can GA log anything anyway when no tag is up and the website isn't even accessible?
Thank you very much in advance
Because it's spam. They hit Google Analytics directly with random GA codes and don't even go through your website.
GA can't tell if these are real hits (from website visits) or fake hits (from spam bots who hit GA directly calling the same ode as they would if on the website). Though arguably they should do more about this.
Massively annoying - particularly when first starting out as this can be a heavy proportion of your "traffic".
It's easy to set up a filter rule is to catch a lot of this by filtering on hostname. As they are randomly hitting GA and don't even know what website they are hitting GA for, they don't usually set this correctly. Real traffic should only come from yourwebsitedomain.com so add a filter for that.
STRONG piece of advice: abandon the default UA-########-1 tracking code of your new website -- simply do not use it!
Create a second and third property on the Admin screen, then use the tracking code for the third property. You will immediately see a lot less spam. No filters or segments necessary!
If you want the whole sad story about spam visits in GA, I have been maintaining the Definitive Guide article for over a year now:
http://help.analyticsedge.com/spam-filter/definitive-guide-to-removing-google-analytics-spam/
I am working on a third party website that contains a web application embedded in an iframe on the home page. This iframe is hosted on the same same sub/domain.
Currently page views are being tracked with _trackPageview. Due to a requirement by marketing both pages use the same Google account Id.
Since the iFrame was implemented the marketing department has noticed that the bounce rate has dropped to almost nothing. I suspect that this is because Google is interpreting the pageView event on the iframe as the visitor hitting another page on the website.
Just for additional information, the domain of the _gaq object is being set to "none" for both the container page and iframe.
Does Google provide a mechanism by which you can trigger PageView in such a way that it isn't interpreted as subsequent pageview in this scenario? (I know that trackEvent has a noninteraction property to deal with this?)
Am I better off just disabling the PageView for the default iframe page?
Does Google provide a mechanism - apparently yes, but probably not for your use case.
The field documentation for Universal Analytics describes the non-interaction field thusly:
Specifies that a hit be considered non-interactive.
So in UA this does no seem limited to events but to apply to all hits (which would include pageviews). I want to point out that I have no tested it and that it seems counterintutive, so it might simply be that the documentation is incomplete/wrong here.
However as you are using "classical" Analytics this does not apply to you. Since upgrading the code is a good idea in any case you might want to push for an update to Universal Analytics (this piqued my curiosity so I will test this over the next few days and update this answer with the results - maybe you want to wait until then, or simply test it yourself).
It's possible, but not 100% clear to me that disabling the PageView event on the iframe will prevent your users from registering a page exit (the pageview may get recorded regardless). You can try removing that event and see if it works.
But a better way may be to implement a custom filter on a new View excluding traffic to that specific class of iframes. Make sure you keep your old View (or create a new one with further filters) to make sure you're capturing those iframe views, if you think that's necessary.
If a website has two GTM code installed, how does GA count traffic? Does it mean the traffic we see in GA report is duplicate?
They are different containers but same GA property.
Thank you!
If both containers have the same GA account and both populate on the page (e.g. have the same rules), then yes, you'll have double the pageviews.
Well, first of all, why do you have 2 GTM codes?
When you set up a container and install the GTM on every page, you must also set up GA tracking as one of your tags on the Tag Manager container settings, when you set this up, you will have to choose which pages you wish to track, most likely, you need to select "All pages". With the live preview you can verify your tag is working and you can go to the GA real time traffic dashboard to make sure data is being recorded appropriately, of course, depending on your traffic, it might not be easy to tell if you are double-counting.
I guess I would say if you set up your Universal Analytics tag properly, you shouldn't have duplicate data...
Back to my question, maybe I can help you better if I know why exactly you have 2 GTM codes?
:)
I am using Google Tag Manager on all my sites now to implement Google Analytics and future proof them for any other scripts.
I am putting GTM in my boilerplate.
Is there any reason this might not be good practice?
Any reason why a website (that needs GA) should avoid Google Tag Manager?
Most websites will require some sort of Javascript code added in the future for affiliate tracking, various analytics and having GTM installed will allow for easy installation of any such JS code easily.
Or, as Google puts it: "Why wait months for site code updates? Google Tag Manager lets you launch new tags any time with a few clicks, so you never miss a measurement or marketing opportunity."
Since GTM does not come with a service level agreement you could (very very tenuously) argue that GTM adds an additional point of failure. And if one wanted to be pedantic one could point out that not all ways of analytics tracking work with GTM (if you track serverside via the measurement protocol).
But real life argument, there is none (IMO).
There might be pages that do not greatly profit from GTM (or any other Tag Management) if all you do is to deploy a single analytics tag to track pageviews. But the second you need to track an event or pass data GTM is already worth it.
This is not meant to be merely opinion based, it's more that in 2,5 years of using GTM on large sites I have been unable to find any scenario where the tag management code has caused any technical problem or interfered with existing code. On the other hand I do not write click handlers or submit handlers anymore, I have a boilerplate template for a container tag in which I just have to replace values for a few macros before I import it to GTM and have tracking up and running, I can set data fields with much less trouble than via the code... so I think there is a real technical argument to make in favour of GTM, and none against it.