Quick answer
Opt-in means a person actively agrees before something starts, such as tracking or marketing email. Silence, a pre-ticked box or inaction is not opt-in. Opt-out is the reverse: it starts by default and the person has to act to stop it.
What does opt-in mean?
Opt-in means something starts only after a person actively agrees to it: ticking an empty box, pressing "Accept", switching on a permission. The reverse model, opt-out, starts the activity by default and leaves it to the person to switch it off. In privacy law "opt-in" is the everyday word for consent. The GDPR defines consent as a freely given, specific, informed and unambiguous signal of agreement, given by a statement or a clear affirmative action (Article 4(11)), and Recital 32 says that "silence, pre-ticked boxes or inactivity" do not amount to consent.
Outside privacy the idea is the same: opting in to a pension plan, a beta programme or a newsletter all mean the default is "no" until the person says yes. This page explains the concept and how it shows up in analytics; it is not legal advice, and which model applies to you depends on the country, the channel and what you do with the data.
Opt-in vs opt-out
| Opt-in | Opt-out | |
|---|---|---|
| Default state | Off until the person agrees | On until the person objects |
| Who has to act | The business must get a clear action | The person must act to stop it |
| What silence means | No | Yes, agreement is presumed |
| Proof | The business must be able to show the person consented (GDPR Article 7(1)) | The business must honour stop requests; under CAN-SPAM, within 10 business days |
| Where the law uses it | EU: marketing email, fax and automated calls need prior agreement (ePrivacy Directive Article 13(1)); GDPR consent | US: commercial email needs no prior permission, but each message must offer a working opt-out (CAN-SPAM) |
| Exceptions and penalties | Email to existing customers about similar products, if an easy opt-out was offered when the address was collected and in every message (Article 13(2)) | The FTC's guide lists penalties of up to $53,088 per violating email |
The same newsletter can sit under different models for different recipients. A list with readers in both the EU and the US is not "opt-in" or "opt-out" as a whole: the rule follows the recipient and the channel, so check each market before you copy one model everywhere.
What counts as a valid opt-in?
Under the GDPR a valid opt-in has six features. Each one has a version that passes and a version that does not:
| Feature | Passes | Does not pass | Basis |
|---|---|---|---|
| Affirmative act | The person ticks an empty box or clicks "Accept" | A pre-ticked box, scrolling, carrying on browsing | Recital 32; the Court of Justice held a pre-ticked box invalid for cookies (Planet49, 1 October 2019) |
| Specific | One choice per purpose: analytics, ads, email | One "I agree to everything" button for unrelated purposes | Recital 32; Recital 43 on bundling |
| Informed | The person can see who is asking and why | A link to a policy as the only explanation | Recital 42 |
| Freely given | Refusing does not block a service that does not need the data | "Accept or you cannot use the site" for data the service does not need | Article 7(4); Recital 43 |
| Easy to withdraw | Withdrawing is as easy as agreeing | Agree in one click, withdraw by writing a letter | Article 7(3) |
| Provable | You can show who agreed, when, and to what wording | "We think most people clicked yes" | Article 7(1); Recital 42 |
Keep the record that makes the last row true: the timestamp, the exact wording and version shown, which purposes were chosen, and the person's identifier or device.
Single opt-in and double opt-in
With single opt-in an address joins the list as soon as the form is submitted. With double opt-in the person must also click a link in a confirmation email. Double opt-in is a method, not a legal term: the GDPR only requires that you can show consent was given, and a confirmed click leaves two timestamps from two separate actions. Whether it is required in a given country is a question for local advice.
Sample data: 1,000 sign-ups through the same form.
| Single opt-in | Double opt-in | |
|---|---|---|
| Sign-ups | 1,000 | 1,000 |
| Added to the list | 1,000 | 640 confirmed (64.0%) |
| Undeliverable addresses | 70 (7.0%) | 3 (0.5% of 640) |
| Deliverable addresses | 930 | 637 |
| Evidence per address | One timestamp | Two timestamps and a clicked link |
How to recompute: 1,000 − 70 = 930; 640 − 3 = 637; 3 ÷ 640 = 0.47%, shown as 0.5%; 637 ÷ 930 = 68.5%. The confirmed list is 31.5% smaller in deliverable addresses, but every address belongs to a person who answered. The cost of the model is list size; the benefit is proof and fewer bounces.
What opt-in does to your analytics numbers
When tracking needs opt-in, the visitors who decline do not vanish from your data. What changes is how much you can know about them. Sample data: 10,000 visits from a region where consent is required, 35% accept.
| Visits | What is collected | |
|---|---|---|
| Accepted analytics (35%) | 3,500 | Full collection for the chosen tier: a pseudonymous visitor ID so returning visits link together, autocapture, identity if you use login |
| Did not accept (65%) | 6,500 | Page views and custom events only, with no persistent ID, no autocapture and no identity |
| All visits | 10,000 | 10,000 page views counted |
Under an opt-out model with 3% opting out, the same traffic would give 9,700 visits with full collection and 300 without. Page views are the same either way; what shrinks under opt-in is the number of people you can follow across days: 3,500 instead of 9,700. Retention and multi-day funnels then describe the consenting 35%, and people who accept may behave differently from people who decline, so do not read them as the whole audience. Cookieless analytics is one way to keep a baseline count of the other 65%, and a consent management platform is what records the choices.
Common opt-in mistakes
- Pre-ticked boxes. The most common failure, and the one Recital 32 and the Court of Justice address directly.
- Treating consent as permanent. People can withdraw at any time, and agreement to one purpose does not cover another.
- Bundling. Making a service depend on consent to data it does not need weighs against the consent being freely given (Article 7(4)).
- Confusing opt-out with deletion. Opting out stops future collection; rows already stored stay until retention expires or an erasure request removes them.
- Treating a stated preference as consent to everything. Zero-party data, such as an answer in an onboarding quiz, is volunteered for a purpose. Using it for a different purpose needs its own basis.
- Collecting more because they opted in. Consent does not change the rule that data should be limited to what the purpose needs; see data minimization. The wider picture across laws is in GDPR, CCPA and PIPL.
Opt-in and opt-out in TapCub
Take the 10,000-visit example above. Here is where each piece sits in TapCub.
- Choose the model per region. In Configuration › Privacy center, the default rule for the EEA and the UK is tier 2 with consent required, which is an opt-in model. Other regions inherit the project default. Each region rule can override the tier, the consent requirement, address truncation and geography (region rules).
- Pass the banner's answer to the script. Consent has three purposes: analytics, functional and marketing. Before consent, events are queued in memory by default, or dropped if you switch the behaviour (consent banner guide).
- Know what a "no" does. When consent is required and the payload has no analytics consent, collection falls to tier 1: page views and custom events are still stored; autocapture, identity operations and device IDs are not. That is the 6,500 visits in the table.
- Treat opt-out as a separate switch. A visitor's opt-out stops future collection, instantly, with no cooling-off period. Its scope defaults to every device of that person and can be limited to the current device. The mobile and cross-platform SDKs have
optOutandoptIncalls. It is not a data-subject erasure request (requests guide). - Expect privacy signals to win. Global Privacy Control and Do Not Track are honoured by default: the hit drops to tier 1 and the consent bits are cleared (how signals are honoured).
- Keep the receipts. Even at tier 1, consent, opt-out and opt-in receipts are accepted. The default retention for consent receipts is 730 days, subject to your plan's cap.
TapCub reads the choice your banner passes to it; deciding which model your law requires stays with you.
See also: What is geofencing? Marketing, accuracy, consent and a worked test.
See also: Location-Based Marketing: Consent First, Then Measure Visits and Lift.
Sources
- Regulation (EU) 2016/679 (GDPR): Article 4(11), Article 7, Recitals 32, 42 and 43.
- Directive 2002/58/EC (ePrivacy), Article 13: unsolicited communications and the existing-customer exception.
- Court of Justice, Case C-673/17 Planet49, judgment of 1 October 2019: pre-ticked boxes and cookies.
- FTC, CAN-SPAM Act compliance guide for business: opt-out requirements and penalties.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Data Engineer
Writes about event design, data quality, and collection workflows, with verifiable implementation methods for reliable analytics.