Confirm scope
Choose the agreed 4–6 fixture or campaign window, primary commercial outcomes and named decision owners.
This is the operational layer behind the sales page: what we need in week zero, who owns what, how each decision cycle runs and what evidence defines success.
Choose the agreed 4–6 fixture or campaign window, primary commercial outcomes and named decision owners.
Fixture keys, ticket transactions, scans, campaign identifiers and a pseudonymous supporter key.
Agree attribution boundaries, privacy rules, baseline windows and what counts as a valid result.
Generate one opportunity, review assumptions, test the action plan and confirm the post-match scorecard.
Build the integration before receiving club data
Shared across calendar, campaigns and post-match analysis.
One row per ticket prevents quantity and scan ambiguity.
UTM and content keys work with synthetic records.
Calculated in demo mode; requires gate data for actuals.
The club must generate the stable hash.
Requires records across multiple fixtures.
The pilot workflow keeps authorised ticket-grain data outside this repository. Matching happens locally, and the product stores only fixture-level and repeat-cohort aggregates.
Raw CRM/ticketing files remain outside the product repository and are never used as demo content.
A stable supporter hash can be used to calculate repeat behaviour without names, emails or phone numbers.
Fixture summaries and cross-fixture cohort counts are the only club evidence written into the live product state.
No authorised club CRM/ticketing aggregate is connected. Raw or pseudonymous supporter-level records are never stored in the repository.
Owns the pilot outcome, removes blockers and approves material decisions.
Owns audiences, campaign execution and channel coordination.
Provides fixture, transaction, scan and product data.
Defines attribution, scorecards and post-match learning.
The pilot can report attribution with campaign identifiers, but incremental impact needs a counterfactual. Each decision cycle should choose the strongest practical design in advance.
Keep an eligible slice unexposed so incremental lift can be estimated against the same audience at the same fixture.
Use a comparable audience, territory or timing window when randomization is not operationally acceptable.
Compare against a defined historical or pre-campaign benchmark, while keeping the causal claim explicitly limited.
Observed purchases and campaign attribution remain useful decision evidence, but they stay descriptive.
Opportunity, audience hypothesis and evidence review.
Approve action, budget, owner, measurement and blockers.
Execute with campaign and fixture identifiers intact.
Close result, attribution, attendance and next-decision implications.