Key takeaways
- AdPix cookie consent is a banner built into the AdPix tracker, on every plan including Free, so the same code that asks for consent also enforces it before any page view, event or cookie.
- There are four categories: Necessary, Preferences, Statistics and Marketing. Rejecting Statistics means the visitor is not measured at all; rejecting Marketing means they are counted without attribution cookies.
- Opt-in mode fails closed: a visitor who never answers the banner is never recorded, so the drop in your reports is larger than the rejection rate the consent log shows.
- Every decision becomes a consent record with the mode, revision and a fingerprint of the banner the visitor saw, and every event row carries the categories accepted when it was collected.
- The banner enforces AdPix's own tracker; it is single-language, does not scan your site for other cookies, and its export returns at most the latest 50,000 records.
AdPix cookie consent is a consent banner built into the AdPix tracker. It asks the visitor, stores the answer, and then the tracker itself refuses to send page views, write cookies or set attribution until the matching category is allowed. It is included on every plan, including Free. You choose four things: which categories start on, opt-in or opt-out, how long a choice lasts, and how the banner looks. In return you get a consent log that proves what each visitor agreed to, and event rows stamped with the consent they were collected under. This page covers how it works, how to set it up, what it does to your numbers and where it stops.
Consent management platform (CMP) is the software that shows a cookie banner, records each visitor’s choice by category and makes the site’s tags respect that choice.
What does AdPix cookie consent answer?
It answers two questions a marketing team usually cannot answer with a bolted-on banner: “Am I only measuring what visitors agreed to?” and “How much data is the banner costing me?” Because the banner and the tracker are one product, the first answer is enforced in code, and the second is visible in the same console as your reports.
Most banners are separate tools that send a signal to other tags and hope they obey. In AdPix the banner is served from the same collection domain as the tracker, writes the visitor’s choice into a cc_cookie cookie, and the tracker checks that choice before every page view, event and cookie (AdPix docs: set up the consent banner). There is no second script to install and no tag manager rule to keep in sync.
The cost question matters as much. Turning on a banner in opt-in mode removes real visits from your reports. AdPix shows the acceptance rate per category in the Consent log tab, so you can tell how much of the drop is rejections and how much is people who never answered.
Who is AdPix cookie consent for?
It fits four kinds of site:
- Iranian sites with visitors abroad. A Persian shop or SaaS with customers in Europe may need opt-in for those visitors. AdPix cannot yet switch mode by region, so the docs advise opt-in for everyone if you have European visitors.
- Sites with no CMP yet. Teams on the Free plan get a working banner, categories and a consent log without paying for a separate consent tool.
- Teams that need proof. Agencies and in-house marketers who may be asked “what did this user agree to in March?” get one record per decision, exportable to CSV.
- Anyone reconciling numbers. If analytics, ad platforms and the order backend disagree, knowing the Statistics acceptance rate explains a share of the gap. The cookie consent analytics guide shows how to correct channel reports with that rate.
It is a weaker fit if your site runs many third-party tags that all need consent. The AdPix docs describe the banner enforcing AdPix’s own tracker, not GA4, Google Ads or Meta tags, so those still need their own consent wiring.
How does a consent banner work in general?
A consent banner works by asking before storing or reading anything non-essential on the visitor’s device, recording the answer per category, and making every tag behave according to that answer. The asking part is the visible bit; the recording and enforcing parts decide whether the setup holds up.
European guidance sets the bar most banners are built to. The European Data Protection Board’s consent guidelines say that silence, inactivity or “merely proceeding with a service” is not consent, that pre-ticked boxes are invalid, and that scrolling or swiping “will not under any circumstances” count as a clear affirmative action. Withdrawing must be as easy as giving consent, the controller carries the burden of proving consent was given, and access to a service should not depend on accepting cookies (so-called cookie walls) (EDPB Guidelines 05/2020). Which rules apply to your site depends on your visitors and your jurisdiction, so treat this as background and check your own position with whoever owns legal questions in your company.
On the tag side there are two common designs. Google’s consent mode lets a CMP pass consent states to Google tags. In basic mode Google tags do not load until the visitor interacts with the banner; in advanced mode they load immediately, adjust their behavior to the consent state and allow modeling to fill gaps (Google: consent mode overview). Either way the CMP and the analytics tag are separate products that must agree. AdPix takes the other design: the tag enforces consent itself.
How does consent work inside AdPix?
Inside AdPix, the tracker decides before every page view, event and cookie whether the relevant category is allowed right now. It compares three inputs: the website’s consent settings (module on or off, default mode, current revision), the visitor’s cc_cookie, and whether the revision in that cookie is current (AdPix docs: consent enforcement).
What does each category open?
| Category | What it opens in the AdPix tracker | If the visitor rejects it |
|---|---|---|
| Necessary | Always on; the tracker gates nothing on it | Cannot be rejected |
| Preferences | Nothing in AdPix; it exists for your own site’s preference cookies | No effect on AdPix data |
| Statistics | Page views, custom events, e-commerce events, identify, the anonymous-ID and session cookies | The visitor is not measured at all |
| Marketing | First-touch and last-touch attribution cookies, the cross-domain ID handoff, fingerprint enrichment | Counted, but with weaker attribution, likely under “(direct)” |
Two placements surprise people. Identify (a sign-in or sign-up) sits under Statistics, not Marketing, so a visitor who accepts Statistics only still gets tied to their account. Preferences is empty on the AdPix side but still recorded, so your own preference cookies have a captured answer.
What is the difference between opt-in and opt-out?
Default mode has two values. Opt-in means nothing non-necessary runs until the visitor chooses. Opt-out means everything runs until the visitor rejects. Under opt-in, AdPix fails closed: if the banner has not appeared yet, the visitor has not chosen, the choice has expired or it was made under an older revision, the tracker behaves exactly as if the visitor rejected. No page view is sent and no durable ID is written; a temporary ID lives in the page’s memory and disappears when the page closes.
The mode applies to every visitor. The hint in the console mentions region-based mode, but the docs state that switching by region is not implemented yet.
What happens at the moment a visitor chooses?
The choice takes effect without a reload. Cookies of rejected categories are cleared at once, and the gates stay shut so they are not re-created. If the visitor accepts Statistics, the tracker sends that page’s view immediately, and a page view fires at most once per URL, so a visitor who hesitated still produces one page view, not two.
Every event then carries the categories accepted at that moment in a consent_flags field on the event row. A rejected category is simply absent. You never need to reconstruct what your settings were on a given day; the consent is written on each row.
When does the banner ask again?
Two settings control re-asking. Consent expiry is how long a choice lives, 182 days by default; after that the choice cookie expires and the banner returns. Revision is a number on the configuration; raise it and every older choice becomes stale, the banner reappears and, under opt-in, those visitors stop being counted until they answer again. The docs advise raising it only when the meaning of consent changes (a new category, a new use of data, a new privacy policy), not to fix a typo.
What does the AdPix consent log record?
The consent log stores one record per decision, created only when a visitor clicks Accept all, Reject all or saves their own choices. A visitor who sees the banner and leaves creates nothing (AdPix docs: consent log and export).
Each record keeps the timestamp and consent ID; the action (first consent, update or withdraw); accepted and rejected categories; the mode in force; the revision; a fingerprint of the banner configuration the visitor saw; the locale; the anonymous ID; and the IP address as a hash only, plus the user agent. The fingerprint is the column that proves which version of the banner text a visitor was shown, which matters once your banner has changed a few times.
The Consent log tab shows four figures, and they count records, not visits:
| Figure | What it counts |
|---|---|
| Consent prompts | Records stored in the selected date range |
| Accept-all rate | Share of records in which Marketing was accepted |
| Reject non-essential | Share of records in which only Necessary was accepted |
| Records stored | All records for the website, all time |
Below them, the Category opt-in rate chart shows how often each category is accepted. The Statistics figure is roughly the share of deciders you still measure; the gap between Statistics and Marketing tells you how much attribution you lose.
Export CSV and Export JSON return nine columns: consent ID, decision time, action, accepted, rejected, mode, revision, configuration fingerprint and locale. The export ignores the date range and filters and returns only the newest 50,000 records, cut without warning on busier sites, so the docs recommend exporting on a schedule, for example monthly.
Which AdPix plan includes cookie consent?
The cookie consent banner is on every AdPix plan, including Free. Plans differ in allowance and other features, not in consent (AdPix pricing).
| Plan | Price | Page views a month | Cookie consent |
|---|---|---|---|
| Free | Free, no card, no time limit | 100,000 per website | Included |
| Starter | 499,000 toman/month | 1,000,000 | Included |
| Pro | 2,990,000 toman/month | 10,000,000 | Included |
| AdPix 360 | By contract | Tailored | Included |
Page views the tracker never sends, such as those from visitors who rejected Statistics under opt-in, cannot count against your allowance.
How do you set up the AdPix consent banner?
Setup takes one page in the console and needs an Editor role or higher; below that the page does not appear in the sidebar.
- Open Configure → Cookie consent and check that the right website is selected at the top. The page has three tabs: Builder, Consent log and Cookie declaration.
- Set the categories. In the Categories card, decide which categories start switched on in the visitor’s preferences panel. Out of the box Preferences and Statistics start on and Marketing starts off. If your site sets no marketing cookies, switch Marketing off so the banner asks less.
- Pick the mode and expiry. Under Consent settings, choose Opt-in or Opt-out for Default mode and keep or change the 182-day Consent expiry.
- Write the banner. Under Content & language, pick the Locale and write the title, description and button labels in your own words. Say what the data is used for; the docs note that the defaults work, but copy that explains the purpose works better.
- Shape it. Choose a layout (Box, Cloud or Bar) and position that do not cover your content, and set Button weighting to Primary so the accept button is visible. Keep the re-open button on, or call
window.__apxConsent.open()from your footer so visitors can change their mind. - Publish on a test website first. Turn on the Module switch and select Publish; nothing is saved until you do. Changes reach visitors within about a minute. In a private window choose Accept all once and Reject all once, then check that two records with the right categories appear in the Consent log.
- Update your cookie policy. The Cookie declaration tab lists AdPix’s own cookies with purpose, expiry and category (AdPix docs: cookie declaration). It does not scan your site, so add your ad pixels, chat widget and other tools yourself.
If AdPix is not on your site yet, the AdPix install guide covers the tag and the settings for the first hour.
How much data will opt-in cost you? A worked example
Take a hypothetical store where 10,000 visitors a day see the banner after switching to opt-in. The consent log shows 6,000 records a day: 2,700 accept all (45%), 1,500 accept Statistics without Marketing (25%) and 1,800 reject non-essential (30%). The other 4,000 visitors leave without answering and create no record.
| Visitors a day | Measured? | Attribution cookies? | |
|---|---|---|---|
| Accept all | 2,700 | Yes | Yes |
| Statistics only | 1,500 | Yes | No |
| Reject non-essential | 1,800 | No | No |
| Never answer | 4,000 | No | No |
| Total | 10,000 | 4,200 (42%) | 2,700 (27%) |
Reports fall by 58%, although the log’s Reject non-essential figure says 30%. The difference is the 4,000 non-deciders, who appear in no chart. Of the 4,200 visitors still measured, 1,500 (36%) carry no attribution cookies and drift toward “(direct)”, so paid and social channels look weaker than they are.
Orders sent from your server do not pass through the browser, so consent does not gate them. If the store records 120 orders a day from its backend, revenue per measured visitor jumps after the switch even though nothing about the business changed. The AdPix troubleshooting page uses exactly this pattern, a step drop in browser metrics while server-side orders hold, to confirm that consent is the cause (AdPix docs: consent is blocking data). The server-side tracking guide explains that path and why consent still applies when your server sends an event.
The docs list three honest levers: pick the right mode, show fewer categories, and raise acceptance with clearer copy and layout. Switching the banner off to restore numbers collects data visitors never agreed to. Keep the source of each order in your own database as well; the first-party data guide shows how to rebuild a channel report from it.
What are the limits, and when should you use something else?
- It governs AdPix, not every tag. The docs describe enforcement inside the AdPix tracker. GA4, Google Ads and Meta tags need their own consent handling, such as Google consent mode fed by a CMP.
- One mode for everyone. Region-based switching is not implemented, so a site with even a few European visitors ends up on opt-in for all.
- One language per banner. The banner does not switch with the browser language. A bilingual Persian-English site has to pick one.
- No site scan. The cookie declaration lists AdPix’s cookies; everything else you document by hand.
- Export cap. The export returns the newest 50,000 records, so busy sites must archive regularly.
- Withdrawal is not deletion. Withdrawing stops collection and clears cookies, but recorded events stay until you use the erasure path.
- Legal judgment stays with you. AdPix gives you the means to capture, enforce and prove consent; which category needs opt-in for which visitor is your call.
If you run many third-party tags across several regions and languages, a dedicated CMP with geo rules and a site scanner will cover more than a built-in banner. If AdPix is your main measurement tool, the built-in banner gives you enforcement and proof in one place for free.
Where does consent fit in AdPix?
AdPix is a web analytics platform that replaces Google Analytics 4: realtime, acquisition, engagement, conversion and e-commerce reports, plus attribution, lift testing and marketing mix modelling, with no data sampling and a free plan. Cookie consent is its data-quality layer: it decides which visits enter every other report.
Consent also shapes other features. Funnel step one shrinks when Statistics is rejected, so read the AdPix funnels guide with your acceptance rate in mind, and the AdPix features overview shows where consent sits next to e-commerce, invalid-traffic detection and the AI assistant. Before you switch to opt-in, write down today’s daily page views and the date, publish to a test website, then watch the Category opt-in rate for a week. That rate, not a guess, tells you how much of every report you are about to lose.
Measure your site with AdPix today
The free plan covers 100,000 page views a month for each website, no credit card. Setup takes under five minutes.
Frequently asked questions
Is the AdPix cookie consent banner included in the Free plan?
Yes. The cookie consent banner is on every AdPix plan, including Free, which allows 100,000 page views a month for each website with no credit card and no time limit. It is a module of the tracker, so there is no second script to install.
What is the difference between opt-in and opt-out in AdPix?
Under opt-in, nothing non-necessary runs until the visitor chooses, and any unresolved state counts as a rejection. Under opt-out, everything runs until the visitor rejects a category. The mode you pick applies to every visitor, because region-based switching is not implemented yet.
Why did my AdPix numbers drop after I turned on the consent banner?
Under opt-in, visitors who reject Statistics and visitors who leave without answering are not recorded. The drop shows up as a step on the day you published, across users, sessions, page views and browser-side revenue together, while orders sent from your server keep counting.
Can I prove what a visitor consented to with AdPix?
Yes. Each decision is stored as a consent record with its timestamp, action, accepted and rejected categories, mode, revision, banner fingerprint and locale, with the IP address kept only as a hash. Records export to CSV or JSON from the Consent log tab.
Does the AdPix banner block Google Analytics or ad pixels on my site?
The AdPix documentation describes the banner enforcing AdPix's own tracker, not other vendors' tags. If you also run GA4, Google Ads or Meta tags, give them their own consent handling, for example Google consent mode driven by a CMP.
Does withdrawing consent delete a visitor's data in AdPix?
No. Withdrawing stops collection from that moment and clears the cookies of the rejected categories, but events already recorded stay. Deleting data goes through AdPix's separate erasure request path.
Sources and methodology
Screen names, categories, modes, cookie names, record fields and limits of AdPix cookie consent come from the official AdPix documentation pages listed in the sources (all updated 3 August 2026), read on 18 November 2026. Plan placement comes from adpix.io/pricing as recorded on 13 November 2026. General consent rules come from the EDPB consent guidelines and Google's consent mode overview, read on 18 November 2026. The site, its visitors and every consent rate in the worked example are hypothetical; the drop, attribution and revenue figures are simple arithmetic done in this article. Nothing here is legal advice.
- AdPix Docs: Set up the consent banner
- AdPix Docs: How consent is enforced in the tracker
- AdPix Docs: The consent log and export
- AdPix Docs: Consent is blocking data
- AdPix Docs: Cookie declaration
- AdPix pricing
- EDPB Guidelines 05/2020 on consent under Regulation 2016/679
- Google Tag Platform: Consent mode overview
This article was drafted with AI assistance and reviewed by the AdPix team before publishing. Editorial policy