DPO Radio

Most websites struggle to apply the strict requirements of the GDPR and the ePrivacy Directive, which treat cookies and similar tracking technologies as non-essential unless the user explicitly opts in. Common setups load analytics, tags, and pixels before consent is given, or rely on cookie banners that pretend to ask for permission but continue tracking anyway. This creates misleading interfaces, inconsistent data, and potential exposure to regulatory scrutiny.
Opt-In Mode (EU) sets this opt-in consent model as the default behaviour for your site. In an opt-in setup, the consent banner presents granular choices and optional tracking is treated as inactive until consent is recorded. Where a site instead uses an opt-out model (California-type), the banner behaves differently and visitors can open the Shield of Privacy logo to review or change their choices rather than seeing a full opt-in prompt on first load.
For organisations, this creates predictable tracking behaviour across European audiences and provides a clean foundation for other regions. It avoids manual configuration errors, reduces cross-site inconsistencies, and aligns first-party data collection with EU expectations without slowing growth or adding operational complexity.
Built for organizations where data protection meets performance

Applies EU opt-in mode without rebuilding tracking setups.

Stops tags until users accept, reducing abandoned consent.

Limits tracking until consent, supporting regulated data flows.

Activates advertising scripts only after acceptance.

Runs analytics post-consent for public-facing transparency.

Blocks non-essential tracking to support privacy-sensitive visits.

Applies EU consent rules before any scripts activate.

Collects first-party data only after visitors opt in.
Applies EU-only opt-in rules by blocking tracking until explicit consent is given




Opt-In Mode is the default consent model for sites that follow prior-consent rules. AesirX starts from an opt-in baseline, then Geo-Handling rules can override this for markets that use opt-out behaviour, such as visitors with US-based language or time zones.

Review your category assignments and script blocking setup so only the right tools activate once consent is given.
Note that AI Auto-Blocking works for plugins and scripts loaded through WordPress’ standard architecture. Scripts hardcoded in theme files are not detected and must be added to blocking rules manually
Aesirx Consent Management Platform

Aesirx Consent Management Platform

GDPR-ready logic
Consent-first tracking
Predictable activationAesirX CMP for WordPress v1.6.0 with configurable opt-in/opt-out consent logic – giving full control to align with GDPR, ePD, CCPA, and regional legal models.
READ MORE




Opt-In Mode sets an opt-in consent model as the default for your site. It is designed for jurisdictions where non-essential tracking should not run until users accept, so your banner and consent logic follow an EU-style prior-consent approach when scripts are wired to AesirX CMP.
European laws such as the GDPR and ePrivacy Directive recognise consent before tracking. Opt-In Mode helps apply this behaviour, blocking scripts until a visitor chooses.
Yes, as long as analytics scripts are connected to AesirX CMP or blocked via AI Auto Blocking. In an opt-in setup, you configure analytics to wait for consent, so reporting focuses on visits where users accepted tracking instead of pre-consent activity.
In an opt-in configuration, cookies in non-essential categories remain inactive until the user opts in. AesirX applies this at script level, so cookies do not activate prematurely.
Opt-In Mode defines the opt-in consent model your site can use. You can then combine it with Geo-Handling rules that override the default in other regions, for example defaulting to Opt-In but applying Opt-Out logic for visitors whose browser language or time zone suggests a US context.