Documentation

From activation to a reviewed consent workflow.

ACookies remains inactive on a fresh install. The setup flow lets an administrator choose what to enable before the public site changes or an external scan starts.

1. Consent defaults

Choose the site language. Optional analytics, marketing, and preference categories start denied for EEA opt-in use.

2. Managed scanner

Read and accept the scanner data terms. Free includes one scan of up to five public pages per calendar month.

3. Review findings

Review categories and descriptions. Scanner and AI output are suggestions, not automatic legal conclusions. A completed free generator scan can be imported with its seven-day code after scanner opt-in.

4. Script rules

Match a WordPress script handle or part of a script URL to analytics, marketing, or preferences. Unknown inline scripts are reported rather than broadly rewritten.

5. Policy and banner

Create a Cookie Policy page with the ACookies block, preview the balanced choices, and activate only when the configuration is ready.

6. Verify

Test accept, reject, customize, withdrawal, Google Tag Assistant, mobile keyboard navigation, and a new private-browser session.

Managed script rule format.

Add one rule per line in Settings. Examples:

handle:my-analytics|analytics
src:connect.facebook.net|marketing

A rule can delay a registered external script. It cannot safely neutralize every hardcoded inline script or iframe, so those require manual integration and verification.