A reject click is not a missing visit

A visitor opens your pricing page and clicks Reject all. The page still rendered. The newsletter still sat in the footer. Google Analytics never heard about it.

That is not a configuration bug. Tools that wait for a cookie wait for a yes. In the EU a large share of people say no. Ad blockers say no for them. Safari already clips third-party tags. The visit happened. Your report pretends it did not.

What the missing row does to your numbers

Traffic looks smaller than the server logs. Conversion rate looks better than it is, because the denominator shrank. Campaigns that send privacy-conscious readers look weaker than campaigns that send people who click Accept.

You then spend the next quarter optimizing a sample, not the site. We will not invent a lift percentage. Your two totals, same week, are the case study.

This is not an ads suite

We count the landing, the source, and the named goal. Ads platforms still do conversion tags. Many sites run both. Cookie Free Analytics does not ingest ad spend or revenue, so it does not print return on ad spend.

If you still load Google Ads, Meta, or GA4, keep the banner for those tags. This script does not wait for a yes. Your counsel owns the final call.

Count the page, not the consent

Cookie Free Analytics sends one tiny request when the page loads. No cookie, no localStorage, no fingerprint. There is nothing to accept. The pageview is the fact that the HTML ran.

Keep Google Analytics if you need ads audiences. Run this next to it for a week. Compare totals. The gap is the part your banner threw away.