It is normal to see some decrease in analytical data since some users may not allow analytical cookies or may simply ignore the cookie consent banner. It's important to note that the drop in data is not necessarily a direct result of implementing CookieHub, but rather a consequence of increased awareness of data privacy and users' choices to limit data collection.
In certain scenarios, users may choose to ignore the banner and proceed to browse the website, resulting in a significant decrease in analytical data after implementing CookieHub. You can enable the 'Block user interface' feature to force the users to take action and that will usually result in less decrease in analytical data.
Analytics data doesn't match sessions reported by CookieHub
The number of sessions reported by CookieHub is based on the number of times the widget is loaded from your site, which may not be an accurate representation of the number of sessions reported by analytics services due to potential caching of the widget in the user's browser. Typically, one session should be detected for each unique user visiting the website each day.
Analytical data is not being collected prior to consent even with Google Consent mode
Data collected by Google Analytics and Google Ads in anonymous mode, when using Google Consent mode, is not available and does not count in reports. However, once the user has given their consent, Google Consent mode can use the previously collected data to provide better details, and it can be useful for attributing conversions.