Termerly logo

Per-site banner analytics replace the basic acceptances log

Released
AL

Adrián Lozano

The original cookie banner shipped with a simple acceptances log — one row per accepted consent, with not much more than a timestamp. Useful as a basic audit trail, useless for understanding how your banner is actually performing.

That log has been replaced with a proper per-site banner_events stream. Every event the banner emits (shown, accepted, rejected, category toggled, dismissed) now gets recorded with enough context that you can reconstruct the actual user journey.

In the dashboard you can now see:

  • Consent rate per site, per banner version, per day.
  • Category breakdown for granular consent — which categories visitors are most and least likely to accept.
  • Decisions over time, so you can correlate banner changes with consent shifts.

If you have been operating banners blind, this is the first time you can actually see what they are doing for you.

April 20, 2026

Activity feed

  • SO
    Santiago Ortega

    Consent rate per site per banner version is exactly the slice I need for our A/B tests. The previous acceptances log was useful for audit but useless for understanding banner performance.

    May 16, 2026

    Replay

  • RA
    Renata Aguilar

    What is the retention on the banner_events stream? We need to keep proof-of-consent records for 7 years for compliance.

    May 1, 2026

    Replay