The data model for consent banners is in place
ReleasedAL
Adrián Lozano
The infrastructure release that made the consent banner feature possible: a proper data model for banners, events and acceptances, fully versioned and per-site.
The new schema captures:
- Banner configurations with theme, position, category settings, copy, and version pointers.
- Per-site mapping so a single project can run different banners on different sites.
- Acceptance records tied to a specific banner version, for proof-of-consent audits.
- Event records for analytics — what the banner did, what the user did, when.
The acceptances dashboard was reworked alongside the schema with cleaner filters (by site, by category, by date range) and a more legible visualisation. The result is a foundation we can keep building on instead of a quick demo that would have to be reworked under load.
April 18, 2026
Activity feed
- ABAva Bennett
The schema is clean and the event records are exactly the granularity I needed for our analytics. Modelling it in our warehouse was straightforward — clear primary keys and foreign keys, no surprises.
May 7, 2026
•Replay