If GA4 shows more data than Sealmetrics, it's likely due to implementation issues. In other words, GA4 could be tracking without consent, or the Sealmetrics pixel may be blocked by Google Tag Manager (GTM) or the cookie banner. Below are the steps to investigate this issue.
Steps to Follow:
Check if the Cookie Banner is Blocking Cookies Before Consent Often, GA4 cookies are not blocked by the cookie banner. This means GA4 is tracking 100% of the traffic, which violates privacy regulations. You can check which cookies are added to your site without user consent using our free Cookie Scanner tool. If GA4 is measuring more traffic than it should, this is likely the cause.
Ensure the Cookie Banner is Not Blocking the Sealmetrics Pixel Cookie banners typically block the JavaScript that generates the cookies, not the cookies themselves. Incorrect implementation may cause the cookie banner to block Sealmetrics' JavaScript, resulting in Sealmetrics tracking less traffic, as it only measures data when the user gives consent.
Verify That Consent Mode v2 is Implemented Correctly Sometimes, Consent Mode v2 is set up in a way that web analytics cookies are accepted by default, causing GA4 to fire cookies without user consent. You can verify this with our Consent Mode Checker tool. If the result is blank, your Consent Mode might not be set up properly, or you're using the Basic version instead of Advanced.
Review Your Google Tag Manager Configuration If the cookie banner operates through rules set in GTM, it might be that Sealmetrics' pixel only triggers after user consent. Make sure GTM is configured so that Sealmetrics can accurately measure traffic.
Following these steps can help ensure accurate measurement and compliance with privacy regulations.