Give every request an owner
Identify who controls the website property, search property, advertising account, email reports and ticketing event records. That may be the promoter, an agency or a partner. Agree the reporting scope and appropriate access method with each owner.
The connection record should state the source, owner, required inputs, what we configure or validate and what evidence becomes available. Reporting access or an agreed export may be suitable; the actual method depends on the provider and engagement.
Validate a sample before promising coverage
For website measurement, check the agreed events and labelled routes with consent handling configured. For platform context, align campaign IDs, dates, currency and definitions. These checks make comparison meaningful without assuming every source counts activity the same way.
For provider records, confirm event IDs, stable orders, quantities, statuses, timestamps and monetary/refund definitions. Source-level attribution additionally requires a reference that survives booking and returns with the order. Reconcile matched and unmatched records instead of assigning unknown sources.
Know what can launch without every connection
Website-only reporting can still show recorded visits and ticket handoffs. Confirmed purchases remain Unknown until supported provider records are available. Optional platform context can be added to the agreed scope without disguising the gap.
Open the complete source checklist. The presentation does not request credentials, connect accounts or change payment processing.
Explore the example.
The NOVA concert and campaign are fictional demonstrations. Links open the existing example in a new tab; they do not connect live data or complete a purchase.
Open the reporting example ↗ (opens demonstration in a new tab)
