Missing Google Analytics transactions are on my top list of frequently asked questions via the support forum or email. If you are running an e-commerce store and tracking orders using Google Analytics, most probably you encountered the problem: you see a purchase on your admin backend but you doÂ not see this in your Google Analytics reports. And this is usuallyÂ not related to the webshop system you are using: WooCommerce store owners face this issue maybe daily just as Magento users or even Shopify store owners.
But why is that? Is this a bug? A “feature”? Something youÂ need to live with or something that can be fixed? Let’s get through some explanations and possible fixes.
First, let’s go through two reasons around the technology being used:
#1 Your payment gateway doesÂ not send the user back to the thank you page
This is one of the most common reasons forÂ not tracking transactions in Google Analytics especially if you are using Google Tag Manager to deploy your measurement.
Some 3rd party payment gateways give the users the option to visit their wallet or other parts of the website without theÂ need to go back to the merchant. Although your webshop will beÂ notified about the successful payment in the background,Â not forcing the user to go back to the thank you page can be an issue if we are talking about tracking: the Measurement Protocol that I will explain below in more detail can be a solution here as well: when the webshop getsÂ notified about the payment, some plugins can also execute their own codes that can include a server side Google Analytics tracking as well.
Google Tag Manager is however different: it is a purely browser based solution, there isÂ no option (currently) to trigger tags within your container from your server. The user has to visit your order thank you page with the browser used while checking out. Without this, the corresponding tags within your Google Tag Manager container willÂ not fire, your Google Analytics tracking willÂ not be executed and you will miss the transaction in your GA reports.
Most 3rd party payment gateways offer an option that will redirect your customer back to the order thank you page after a payment. You should check this and enable where possible.
#2 Some orders are coming from your mobile app
This could be trivial but let’s just add this to the list: if your webshop also has a mobile app where users can place an order, you should definitely check whether this app has Google Analytics ecommerce tracking as well. IfÂ not, you may see the order on your webshop admin but it will be missing from your Google Analytics reports for sure.
If you are using WordPress (and maybe WooCommerce), there can be some additional reasons which can also apply to other e-commerce systems in a similar manner:
#3 A WooCommerce extension alters your default order received page
WooCommerce by default doesÂ not include any Google Analytics tracking. YouÂ need to use a plugin to achieve this. Most plugins rely on some hooks and functions on the order received page that WooCommerce executes by default. There are some WooCommerce plugins however that alter this order received page allowing you to select a custom-made page instead of the default page. This is shiny and useful in most cases but some plugins doÂ not execute the same hooks and codes on those custom order received pages, preventing other plugins to see that the user just placed an order.
Obviously, you should either avoid using such plugins or contact the plugin author to update the plugin so that it mimics all elements and behavior of the default order received page.
#4 Your Analytics / Tag Manager plugin doesÂ not support your ecommerce plugin
Although manyÂ native Google Analytics plugins support WooCommerce for example, some of them only put theÂ necessary ecommerce tracking code into the webshop if you purchase the paid version. Some Google Tag Manager plugins doesÂ not support any ecommerce plugin at all (not mine of course 🙂 ). If you areÂ using other ecommerce plugins than WooCommerce, you will see that many GA/GTM plugins areÂ not yet capable of tracking ecommerce purchases. You should carefully choose your ecommerce platform and of course your plugin to track the choosen ecommerce platform 🙂
In some cases, you miss a transaction from your GA reports because of user intent:
#5 The user has opted out from Google Analytics tracking
This kind of blocking can be easily detected thus you may override it programmatically but I wouldÂ not recommend doing so. Respecting the intent of your user should be more important than seeing the purchase in your Google Analytics reports even if you willÂ not be able to completely evaluate your marketing campaigns.
(If you really want to get your tracking back, you or your programmer should read how this kind of blocking works. It shouldn’t be a problem to re-enable data collection. But again: this is against your user and shouldÂ not be used)
#6 The user is using an ad blocker or any other privacy related browser extension
A better-known fact is that most popular ad blockers usually also block Google Analytics tracking. That means that if your visitor is blocking ads, you usually doÂ not know much about these visitors. Usually reallyÂ nothing,Â not even the fact that this user visited your website/webshop. There are other browser extensions that allows users to take control of websites and website tracking. The main purpose of those browser add-ons are to improve security which also includes the ability to disable Google Analytics or other kind of tracking.
This kind of opt out is a decision of your visitor too therefore overriding this and tracking those users is aÂ no-go decision for you. Some plugins and extensions of popular e-commerce systems gives owners the ability to use a method called server-side tracking. This means thatÂ no tracking code is added to you website thusÂ nothing can be disabled or blocked. Instead, the so called Measurement Protocol of Google Analytics is being used to send data to GA while your page loads. The data is being collected and sent in the background, on your server andÂ not in the browser of your user. This also means that some data might be missing this way (like screen size) but many other – and important – data will be available in your reports regardless of what blocking the user is using.
But again: this is against the wish of your user and therefore should be avoided.
Now let’s go through some more technical reasons than can explain a missing Google Analytics transaction regardless of the used e-commerce system:
#7 A script in the page prevents tracking to work on your order thank you page
Most websitesÂ nowadays use several scripts to improve user experience and deliver dynamics to your webpage. Scripts and programs can sometimes fail evenÂ next to extensive testing. This is because it isÂ nearly impossible to test every website in every browser with every possible options and extensions on every internet connection. Some combinations fail.
#8 The Analytics / Tag Manager tracking code has some errors
This is very similar to the previous reasons but in this case your Google Tag Manager / Google Analytics codes include issues.
"Cool Product with 4" display"
From the browsers perspective, the text in blue willÂ not be threatened as part of the productÂ name but it canÂ not be evaluated as a command either bringing the browser into an unexpected state where it has to abort the current operation: for example, tracking your purchase data.
There are two reasons related to the limitations of Google Analytics tracking:
#9 Too many products are included in one transaction
This one applies if you are using the so called enhanced ecommerce tracking of Google Analytics. This is theÂ next generation of ecommerce tracking within GA, it has lots of possibilities if you are using this with Google Tag Manager (which I would like to explain in a separate article too).
Now let’s learn something (probably)Â new: the definition of hit payload.
Think about all the data Google Analytics collects while your page loads. Even if you areÂ not using ecommerce tracking, by just putting the default tracking code into your website, you will see many-many data about your user in your reports: sources, maybe keywords, data about screen size, page title, etc.Â Now imagine a quite large order on your webshop with either lots of products or with fewer products but with very long product names. Add to this to the data being tracked by default.
Now think of a black paper where you start writing every collected dataÂ next to each other. You also write shortÂ names next to all data so that you know whatÂ numbers and texts belong to certain dimensions. After you’ve written all collected data to this sheet, this will be your so called hit payload, the data being sent to Google while your page loads. If this includes productÂ names, brand names, product category names (with lots of category levels), this can be quite long can’t it be?
Google Analytics will however drop this payload andÂ not send to Google’s servers if the size (length) of this payload grows over 8kB. That is 8192 byte which is usually 8192 characters except for someÂ non-latin (or non-latin1) languages where more than one byte isÂ needed to identify a single character. On a thank you page with lots of products in the order this can be achieved quickly.
But what can you do in such cases?
- Google Analytics allows you to import product data like productÂ names, brandÂ names, categoryÂ names using a CSV upload orÂ with a programmatic way. Here you send within the hit payload only the SKUs of your products and join other product data on the Google Analytics UI using CSV upload for example. Google Analytics will look at your uploaded CSV product data while processing the incoming purchase data with your SKUs and if it finds the ordered products within this CSV, it will populate ecommerce reports using the data found in your uploaded CSV
- You or your programmer may hook into the flow of Google Analytics data collection and divide all hit payload into smaller parts. A great solution can be found in this article by LunaMetrics.
#10 Too many interactions has been tracked in one session
Another limitation of Google Analytics tracking is that it allows you to send “only” 500 hits per session. A hit is usually a pageload but a click on your product on your category page or on the add to cart button will be also a hit if you track them as those events should be tracked.Â Now imagine a user that really tries to find the proper products. It searches for lots of products, puts them into the cart and when this user finally reaches your order thank you page, this will be interaction#501 in this session. AndÂ in this case, Google drops the hit that includes the purchase data.
Websites with higher pages / session metrics can be affected by this limitation but a lower pages / sessionÂ next to lots of event tracking can prevent proper tracking too.
As you can see there can be several reasons for any missing transaction in your Google Analytics reports. You should always respect user privacy at first and then try to fix other possible reasons.100% accuracy and parity can be usuallyÂ not achieved but you can sometimes improve the ratio of tracked purchases. Accepting this is usually the better choice as to try to track everything and everybody regardless of the choice of your user.