STUDIO / LIVE BACKEND
Matchday to media: one fan, end to end
Log in once, scan at the gate, get a governed matchday message, then become the seed for a sponsor's audience extension package. Five steps, one session, a real backend. Synthetic data, labelled as such.
Log in once
One club ID resolves to every linked key, with consent held per purpose.
Scan at the gate
The turnstile scan is an event. Identity, consent and an over-communication guard decide whether a message goes out.
Log in first (step 1).
Turn known fans into a sponsor seed
Only fans who consented to audience extension can be in the seed. Then the seed is expanded to lookalikes.
Package it for a sponsor
The seed and threshold become a planned audience extension package with lineage.
Build a seed first (step 3).
Who sees what
The same session, read through three roles. The database decides what each role can see, not the page.
Everything here is synthetic and runs on a real backend: identity keys, an append-only consent ledger and event log, and server-side functions for scan decisions, seed building, lookalike expansion and package planning. No real person's data is used.