Why Your Google Analytics Pageviews Are Wrong?

On This Page,You can easily know about Why Your Google Analytics Pageviews Are Wrong?.

Google Adsense is a program is run by Google. The program allows the publishers around the Google network of content sites to offer automatic text, video, images, advertisements to name a few. All of this is directly targetted towards the site content and the audience.

The Reasons To Your Google Analytics Pageviews Are Wrong

1. Using Old Code

There’s many old code out there. Multiple versions of Google Analytics are released, and older versions are simply not as accurate because the newer code. If you’re using old code on your site, you’ll want to upgrade to Google Tag Manager and Universal Analytics to enhance the accuracy of your pageviews.

2. Missing Tracking Code

Dorcas mentions this in her post 5 Common Mistakes in Your Google Analytics Tracking Code. It helps to truly have the tracking code on the page. we often see tracking code completely missing from entire sites, or from specific pages or subfolders of web sites , or from specific subdomains. If the tracking code isn’t on the page, it’s not getting to track any pageviews.

3. Incorrect Tracking Code

Sometimes the code is on the page but it’s just wrong. Somehow errors were inserted, and the code now has “smart/curly” quotes instead of standard ones, and it just breaks. Sometimes the incorrect Google Analytics property is listed and therefore the data is getting sent nobody knows where. If the code is all out wrong, for whatever reason, you’re not getting to collect the info from it.

4. Double Tracking

Too much of an honest thing? even if the code is great, and within the right place, and on all the pages, if you’ve got it on the page quite once then you’re getting to get what we call Double Tracking, that’s whenever the page loads, it’ll fire two pageviews. Often this is often caused by adding new updated code to the page, but not removing the older legacy code. this is often also a number of the worst news to deliver to a client. “Hey you know how you were already concerned about your traffic… Well hold onto something… It’s actually half what you thought.”

5. Custom Code

Custom code itself isn’t bad, but you’ll easily do bad things to it. Like rewrite all of your pagenames. once you send successful you’ll change just about any information about it including the URL that Google Analytics sees. you’ll literally re-write all the URL’s on your site to look like they were hits to the house page. There are numerous problems which will happen due to this.

6. Ajax Frameworks

Sites that use an Ajax framework can do a spread of things to not fire the proper pageviews, usually with the pages rewriting themselves instead of reloading employing a sort of techniques. If your site uses Ajax, you would like to account for this, and fire Virtual Pageviews when the page changes, instead of counting on the traditional page load for Google Analytics. Pageviews fire when the page loads. If the content swaps out but the page isn’t reloaded, then no additional pageviews.

7. Virtual Pageviews Instead of Events

Speaking of Virtual Pageviews, sometimes these can be fired on a page instead of employing a Google Analytics Event. If you’re firing a pageview when someone scrolls the page, or clicks on a banner, your pageview numbers are going to be affected. Use Events where it’s appropriate, instead of Virtual Pageviews. I wrote before about once you can appropriately Fire a Virtual Pageview in Google Tag Manager.

8. Iframes

If you set your code on every page, on the other hand use Iframes heavily on your site, you’ll load one page, but get 2 or more pageviews because of all of your iframes firing their own. take care when firing pageviews within iframes.

9. Meta Refreshes

Other sites will automatically refresh the page every so often, sometimes for content, but usually to serve new ads. this will fire another pageview, and suddenly it’s such as you have double tracking on the page.

10. Bad Filters

Bad filters in Google Analytics are an excellent thanks to destroy your data. the wrong use of an include or exclude filter can cause you to lose significant traffic, even all of it. Any filter that’s including only certain traffic, excluding other traffic, or employing a search and replace or advanced filter to switch your data can destroy it. confirm your filters are correct, and always maintain an Unfiltered View that never has any filters applied to it, ever. we’ve some oldie but goodie blog posts on mistakes with filters including Mistakes with Include Filters also as newer post about Basic Google Analytics Filters for each Site.

11. Lack of Good Filters

Good filters can make your data better. Filters to clean your data and lowercase everything to combine pages with different capitalization into one row of data. Advanced filters to change or clean up other bad data which is otherwise dispersing your pages into different row of data. Here’s Jonathan’s post about Cleaning URL’s in Google Analytics.

12. Default Pages

Incorrect use of the default page feature can also cause pages to be split up in your data. Consider whether you want, or don’t want, to use this feature, and be consistent. The amazing Jon Meck wrote about The Google Analytics Default Page.

13. Query Parameters

Query parameters on your URL’s will split your data up into different buckets, so you would like to use the Exclude URL Query Parameters feature when appropriate to remove any query parameters that aren’t meaningful to your analysis. If they’re important, but disparate, you also move them out of the URL when appropriate and into a custom dimension instead, so that you still have the data for analysis, but your page rows are condensed. Samantha wrote about Methods to Strip Queries from URLs in Google Analytics.

14. Bad Triggers

If you’re using Google Tag Manager, your tag won’t be firing on the right pages, because you’ve set up bad Triggers. If your triggers are bad, your tags won’t fire, and your pageviews won’t get tracked. many ways you’ll have triggers, but good ole Jon Meck wrote about some double negative trigger exceptions in GTM, which is simply a method in many people could get tripped up.

15. Container Version Not Published

Another common thing is to possess great tags and triggers, but they really aren’t published, and therefore the published version of your Google Tag Manager container has something else. make certain that you simply are working with the proper published container.

16. Someone Else is Doing #4

Instead of you sending your data somewhere else, someone is sending theirs to you. or maybe you’re sending the info from one of your sites, to the wrong property. Either way the Google Analytics property is getting data from somewhere it’s not supposed to. Usually this can be filtered out by excluding hostnames.

17. Third Party Widgets

Sometimes you’ll feed your Google Analytics property id into a third party widget that gets inserted onto your page to trace it. Unfortunately, this often results in something technically similar to #10 where the widget inserts an iframe onto your page, firing pageviews, and suddenly your on page events look like they’re being fired from /modal/emailform.html.

18. Adblockers and Script Blockers

Some users rather than turning of JavaScript and Cookies, because they realize the modern web relies on them so heavily, will instead address Adblockers and other browser extensions which will block the loading of certain files. Particularly Advertising and display ads, but often they’ll also block tracking scripts. Some extensions will even block Google Tag Manager. Like #21 often this is a small number, but counting on what your site is, and who the audience for it’s , the amount could climb and you’ll be missing out on significant numbers.

Leave a Reply