STUDIO / UNIFY PROFILE

Fan profile: system of context

The system of context: one live fan profile assembled from every source, with field-level provenance and consent. This is the layer every channel and every agent reads. Synthetic data, labelled as such.

7 records, 7 fans as the club sees them

Source records (synthetic)

Ticketing2026-09-28 09:12 UTC
Mr J Okafor
TKT-77120
Postcode
N7 6QP
Status
Season-ticket holder
Seat
Block 112, Row 14, Seat 9
Gate
C
Annual value
1840.00
Consent: Marketing yesPush n/aPartner noProfiling yes
Membership2026-06-12 18:40 UTC
Jonathan Okafor
MBR-30551
Postcode
N7 6QP
Tier
Gold member
Since
Aug 2019
Consent: Marketing yesPush n/aPartner noProfiling yes
Retail web store2026-10-01 20:05 UTC
Jon Okafor
WEB-9ac41
Postcode
E8 3PN
Last order
Away kit, 1 Oct 2026
Saved address
Old address (pre-2024)
Checkout
Guest, marketing box left unticked
Consent: Marketing noPush n/aPartner n/aProfiling no
App2026-10-09 17:55 UTC
JO_Blues
APP-d81f3
Email
[email protected] (unverified)
Device id
ios-7F3A-91C2
Push opt-in
Yes
Sessions, 30 days
24
Consent: Marketing n/aPush yesPartner yesProfiling yes
OTT streaming2026-09-20 21:30 UTC
J Okafor
OTT-5520
Plan
Annual, 9.99 monthly equivalent
Hours watched, 90 days
11.5
Consent: Marketing yesPush n/aPartner n/aProfiling yes
Hospitality enquiry2026-08-14 11:20 UTC
Jonathan Chidi Okafor
HSP-2214
Email
[email protected] (unverified)
Postcode
N7 6QP
Enquiry
Lounge, 4 guests, derby fixture
Quote
640.00 (open, not counted as spend)
Consent: Marketing n/aPush n/aPartner n/aProfiling n/a
Stadium POS2026-10-04 15:50 UTC
Anonymous card
CARD-0081-7745
Loyalty card
Linked to ticket on scan
Visits
14
Consent: Marketing n/aPush n/aPartner n/aProfiling n/a

Three email variants, two names that disagree, an old postcode, a nickname, and a record with no marketing consent. Switch to After to see them resolved.

Survivorship rules

Rules apply to the merged profile. Switch to After to watch them take effect.

Latency: batch versus event-driven

Simulated. Timings are illustrative, not measured.
Nightly batch via warehouse
Profile updates next morning
  1. Scan lands in the ticketing system
  2. 02:00 nightly extract starts
  3. 03:30 warehouse load completes
  4. 06:00 profile rebuilt, campaign list refreshed
Event-driven integration
Profile updated in ~2 seconds
  1. Scan event published to the stream
  2. Identity matched to the fan profile
  3. Profile updated: attended, in the stadium
  4. Matchday welcome message queued

What it means: the matchday welcome message reaches the fan in the stadium, not the next day.

Agent grounding: what the profile lets an assistant say

Illustrative, rules-based; no model is called.

Fan asks
“Where is my seat and which gate?”
Answered

Block 112, Row 14, Seat 9. Use Gate C.

Field: seat and gate from Ticketing. A service answer, so no marketing consent is needed.

Fan asks
“Can I upgrade to hospitality for Saturday?”
Answered

Yes, a 4 guest lounge is quoted at £640. I will answer here only and will not email you a follow-up.

Fields: season-ticket status and open hospitality enquiry. Follow-up email is gated by Marketing email consent (currently no, Retail web store).

Fan asks
“Send me partner offers”
Refused

I cannot send partner offers. You have not given consent for partner sharing, and I will not infer it.

Purpose: Partner offers. Resolved no from Ticketing (Most restrictive).

Everything on this page is synthetic: one invented fan, invented records, and rules-based behaviour computed in your browser. Nothing is sent anywhere.