Bidding systems and AI agents optimize on the data they're given. They don't correct for what's missing; they inherit it and act on it.
More than half of all sessions go unrecorded
When consent banners decide which sessions are recorded, every system built on that data inherits the gap: your analytics, your bidding and your AI.
48%
Average website consent rate, April 2026.
The share of visits that opt out of statistical or analytical tracking.
+15 points
Consent lift from nudging banners (55% against 40%).
The consent it collects is invalid.
10-20%
Estimated ROAS drag
The estimated loss in machine-learning bidding performance caused by consent-induced data gaps.
Autonomous attribution agents, campaign copilots and anomaly-detection systems adjust spend without human review. They can't correct for what the dataset leaves out. Consent-dependent tracking is a technical liability, not only a compliance one.
Source: 2026 Consent Benchmark Report, drawn from etracker's measurement dataset.
The consent gap is a compliance risk and a data problem
Consent-dependent tracking doesn't just expose you legally. It decides which half of your traffic every report, bid, and model gets to see.
The banner
Reject must sit on the same layer as accept, with the same size, weight, and styling, and no extra clicks. Miss one point, and the consent may not survive an enforcement review.
Where it shows: "Reject" one layer down, behind "Settings".
The channel comparison
SEO traffic consents at 57%, social at 34%. A channel with higher consent records more of its conversions, so it looks stronger even when it isn't.
Where it shows: channels ranked by consent behavior, not performance.
The models
Where it shows: generative AI referrals, the fastest-growing channel, consenting at 53%.
The inbox
Permission to send an email carries no permission to measure it. Open and click tracking needs its own opt-in, with its own way out.
Where it shows: one checkbox covering both.
The approach that closes the gap works differently. It measures every session without depending on consent, and asks for consent where it adds depth.
When half of every session never enters the dataset, every model and agent built on it inherits the gap.
What's on the table at the end
Your own consent gap in numbers, and a point-by-point view of where your consent setup holds.
Measured on consent
Half the picture
Reports, bids, and AI systems run on the sessions that consented. Whether that consent holds is an open question.
Measured on a complete base
The full picture
Your gap quantified on your live site, every consent touchpoint checked, and a base layer that doesn't depend on the banner.
The size of the gap
The absolute size of the dataset you're missing today, measured against your traffic rather than industry averages.
Where it concentrates
The gap broken down by channel (SEO, paid search, AI referrals, direct, and social), so you see which reports undercount most.
What a complete base changes
Which channel comparisons, bidding signals, and AI-driven decisions shift once the denominator is complete.
A banner verdict
Your consent dialog checked against the four-point standard and all three layers: design and function, first-level information, and granular detail.
A tag and pixel map
What loads before consent on the website, and which email campaigns load a tracking pixel without a tracking opt-in.
A consent record check
Whether every contact's form state, timestamp, and context are stored, and whether the records export when an audit asks for them.
Two check-ups, ten checkpoints
The consent gap check-up measures what your data is missing.
The consent compliance check-up tests whether the consent you collect holds up.
Check-up 1 · Consent gap
Parallel deployment
etracker's consent-exempt tracker runs alongside your existing consent-based stack. Your banner, tools, and reports stay untouched.
30 days of live traffic
Measured on your site and your traffic, not on industry averages.
The gap by channel
Consent-based and consent-exempt figures side by side, for SEO, paid search, AI referrals, direct, and social.
Decisions rechecked
Where consent bias distorts your channel comparisons, bidding signals, and the inputs to your AI systems.
Check-up 2 · Consent compliance
Banner design
Top-level rejection, visual parity, equivalent controls, and no artificial friction. No banner on the imprint or privacy policy, and a way to revoke consent on every page.
Information and categorization
Two distinct consents shown at the first level, with transfers outside the EEA, profile enrichment, and the number of recipients disclosed. Every service categorized, with no "Other" category.
Tags and consent management
What fires before consent: Google Analytics 4 in Advanced Consent Mode, embedded maps and videos, and server-side endpoints. Whether tags and consent rules live in one workspace, or drift apart in two.
Email sending basis
Opt-in for consumers and opt-out for professionals in their professional role. The soft opt-in exception and its three conditions. Partners named at capture, each with its own opt-in.
Email pixels and withdrawal
Consent-mandatory pixels loaded only with a tracking opt-in. A separate tracking-withdrawal link in every footer, enforced at the endpoint, so mail already delivered stops reporting.
Consent records
Form state, date, method, and wording stored for every contact, and exportable on request, including for purchased or rented lists.
Marketing AI is only as good as the data it inherits
Attribution agents, campaign copilots, and anomaly detection act on the data they're given, faster than any analyst could catch an error. A complete, lawful base is the precondition, not the model.
No personal data
etracker AI has no access to personal data. It works only with data that has been anonymized and aggregated first, with no reasonable means of re-identifying individual users.
No model training
Your data is protected contractually, conceptually, and technically from being used to train or improve AI models. Processing takes place in the European Economic Area.
A human decides
The AI drafts tags and dashboards; it doesn't change live website code. An administrator reviews each draft and activates it.
How the check-ups run
Scoped around your website, your email program, and the markets you serve.
Time
The consent gap measurement runs for 30 days.
Participants
Marketing operations, CRM owners, web and analytics teams, and in-house counsel.
Method
We review your martech stack and consent workflows against EU, German and French requirements. For the consent gap, our tracker runs alongside your existing stack on your live site, against your traffic, not industry averages.
What we need from you
Access to your banner and tag setup, and the ability to add the tracker to your site.
Result
Findings by criterion, a gap list, and the size of your consent gap.
Built for manufacturers with a distribution network to manage
Four situations this plan is built to solve.
Performance and growth teams
You're not shipping direct-to-end-customer only. Documentation has to reach partners you don't fully control.
Teams building AI on their own data
A specification change doesn't mean one email. It means version tracking across models and locales.
Web, CRM and marketing operations
Engineering signs off the content. Someone else has to handle the rollout, without added headcount or budget.
In-house counsel
You're still relying on the corporate website, your ERP, or a plan to build it internally.
The number that matters is yours
Industry averages describe the industry. A conversation with a solutions advisor starts with your site.
Built for the way European privacy law works
We help you enforce consent, not just record it, and measure what consent can't reach.
30+ years of experience
Digitalizing customer relationships for mid-sized and large organizations.
Trusted by 4,000+ companies
Global manufacturers, luxury brands, and public infrastructure run on JustRelate.
Tags, consent, and email in one system
Tag and consent rules in one workspace, with unmapped tags blocked by default. Email Builder injects or suppresses the tracking pixel from the consent record, with no custom code.
European by design
Data hosted in EU-based data centers. Teams in France, Germany, and Poland.
Questions about tracking and consent
Clear answers to the questions teams ask before they book.
48% as of April 2026, according to the 2026 Consent Benchmark Report, which is based on etracker's measurement dataset. That's essentially flat against 47% a year earlier. Rates vary by industry, from 65% in financial services to 37% in science and education. They vary by traffic source too: 57% for SEO, 34% for social media.
48% as of April 2026, according to the 2026 Consent Benchmark Report, which is based on etracker's measurement dataset. That's essentially flat against 47% a year earlier. Rates vary by industry, from 65% in financial services to 37% in science and education. They vary by traffic source too: 57% for SEO, 34% for social media.
Yes, but the extra consent doesn't count. Banners that visually favor "Accept" average 55% consent, against 40% for compliant layouts with equivalent buttons. Under EDPB guidance on deceptive design, nudged consent is invalid, so data collected on that basis was never lawfully held.
Yes, but the extra consent doesn't count. Banners that visually favor "Accept" average 55% consent, against 40% for compliant layouts with equivalent buttons. Under EDPB guidance on deceptive design, nudged consent is invalid, so data collected on that basis was never lawfully held.
No. Wherever a server-side setup reads device attributes, sets cookies, or sends data to ad networks for user matching, prior consent is still required. Anonymizing data afterward doesn't change that: under the European Court of Justice ruling in C-413/23, personal-data status is fixed at the moment of collection.
No. Wherever a server-side setup reads device attributes, sets cookies, or sends data to ad networks for user matching, prior consent is still required. Anonymizing data afterward doesn't change that: under the European Court of Justice ruling in C-413/23, personal-data status is fixed at the moment of collection.
Yes, with a consent-exempt architecture that works within four constraints:
- functional local storage only, with no tracking cookies or fingerprinting
- processing as an isolated service provider
- no persistent user IDs, with recognition expiring within 24 hours
- IP truncation at the edge, before anything is logged
etracker measures up to 99% of visits and conversions this way. Following visitors across sessions beyond 24 hours still requires consent.
Yes, with a consent-exempt architecture that works within four constraints:
- functional local storage only, with no tracking cookies or fingerprinting
- processing as an isolated service provider
- no persistent user IDs, with recognition expiring within 24 hours
- IP truncation at the edge, before anything is logged
etracker measures up to 99% of visits and conversions this way. Following visitors across sessions beyond 24 hours still requires consent.
No. Under French law, sending an email and measuring it are separate acts with separate legal bases. Tracking pixels used for campaign optimization, profiling, or individual open tracking need their own opt-in, in B2B as well as B2C. Recipients also need a way to withdraw tracking consent without unsubscribing.
No. Under French law, sending an email and measuring it are separate acts with separate legal bases. Tracking pixels used for campaign optimization, profiling, or individual open tracking need their own opt-in, in B2B as well as B2C. Recipients also need a way to withdraw tracking consent without unsubscribing.
etracker's consent-exempt tracker runs for 30 days alongside your existing consent-based stack, on your live site. Your existing setup stays untouched. At the end, you see:
- the absolute size of the dataset you're missing
- where the gap concentrates by channel
- what a complete base would change in the decisions your team and your AI systems already make
etracker's consent-exempt tracker runs for 30 days alongside your existing consent-based stack, on your live site. Your existing setup stays untouched. At the end, you see:
- the absolute size of the dataset you're missing
- where the gap concentrates by channel
- what a complete base would change in the decisions your team and your AI systems already make
etracker data is stored and processed in EU-based data centers. etracker AI has no access to personal data. It works only with data that has been anonymized and aggregated first, with no reasonable means of re-identifying users, and customer data is never used to train AI models.
etracker data is stored and processed in EU-based data centers. etracker AI has no access to personal data. It works only with data that has been anonymized and aggregated first, with no reasonable means of re-identifying users, and customer data is never used to train AI models.
Start with a conversation
Talk to an expert about your consent setup, and which check-up to start with.
Bring us your setup. We'll scope the checkups with you.
- A first conversation
You talk with an expert about your website, email program, and markets. - A scope that fits
Together, we agree which check-ups and checkpoints to cover. - The check-ups begin
The consent-exempt tracker goes live alongside your stack, and the compliance checks start in parallel.