Usage

Consent flow

1. On first visit, optional categories are blocked.
2. Visitors accept, decline, or customize categories.
3. Allowed services load and the consent record is saved.
4. The floating button lets users revisit or revoke consent.

Pattern management workflow

Use one or a mix of these methods:

1. Preset Library for common services (Google Analytics, Meta Pixel, Fonts, Maps, etc.).
2. Site Scanner to auto-detect external resources from your pages.
3. Manual editing for custom services and edge cases.

Recommended process:

1. Start with presets.
2. Run scanner on key pages.
3. Add manual fragments for anything not detected.
4. Re-test in a private window.

Frontend script guarding

For inline scripts that must wait for consent, use:

<script type="text/plain" data-consent="analytics">
  // your script
</script>

Supported category values are analytics, marketing, functional, and preferences.

Audit trail

• Each visitor token has its latest saved consent state, not a timeline of every choice.
• Retention can purge records automatically.
• Export the audit log as CSV from the Advanced tab.

Pro workflows

For a managed service inventory, scheduled scans, and technical setup checks, start with the Pro usage guide. The consent banner's appearance, text, and manual patterns remain in the system plugin settings.