When using multiple tools to measure website traffic, discrepancies between the data reported by different platforms can be confusing and potentially frustrating. First let's check how we can view the number of Banner view from the Termly Dashboard.
How to view Banner views
The number of views of your website’s Consent Banner can be seen directly when you log in to your Termly Dashboard. The report is displayed as a graph, with the vertical axis showing the number of views and the horizontal axis showing the monthly breakdown.
If you have multiple websites, you can easily view the banner statistics for all of them using your Centralized Dashboard.
If you're noticing that the consent page views reported by Termly do not align with those reported by your analytics software (such as Google Analytics), there are several factors to consider that could explain these differences.
Key reasons for discrepancies
Blocking by consent preferences: Termly might block other third-party scripts including analytics tools depending on the user's consent preferences. If a visitor declines tracking cookies, Termly will prevent analytics scripts from loading, thus causing your analytics tool to under-report page views compared to Termly.
Ad blockers and browser tracking prevention: Many users employ ad blockers or use browsers that have built-in tracking prevention. These tools can block analytics scripts like Google Analytics but typically do not affect CMPs like Termly. Therefore, Termly will record a page view that your analytics tool may miss.
Implementation and script load order: Discrepancies can also stem from how Termly and other scripts are implemented on your site. If Termly loads first and is set up correctly, it captures all page views. Any misconfiguration in the load order of scripts could prevent analytics tools from recording some visits.
Troubleshooting tips
To ensure the accuracy of your data and minimize discrepancies, consider the following steps:
Verify installation: Double-check that the Termly script is the first script loaded on your pages. This setup minimizes the chances of other scripts being blocked before they can load.
Check for multiple triggers: Ensure that Termly is not being triggered multiple times for a single page view. This could artificially inflate the page views reported by Termly. Review the setup to ensure it triggers once per page load.
Review consent settings: Examine how consent preferences are managed and how they influence the loading of other scripts. Make sure that the settings align with your expectations and legal requirements.
Conduct cross-tool analysis: Regularly compare the data from Termly and your analytics tools. Look for patterns in discrepancies that could indicate specific blocking behaviors or misconfigurations.