Request the right source for the question
Website measurement, search reporting, advertising reports, email reports and ticketing records are distinct sources. Start with the promoter’s intended decisions, then identify which sources and definitions can support them.
The connection record needs an owner, account/property scope, supported access or import method, reporting period and outstanding dependencies. Provider campaign references need sample validation in addition to an order feed. A website-only launch can still report useful activity with sales marked unknown.
What this gives the promoter
Clear setup responsibilities and agreed measurement coverage.
This delivery stage needs an owner and an agreed output. Record unresolved inputs and dependencies so the promoter can review the work in context. Preparation and approval are part of the service, rather than assumptions left behind the design.
Do we need to connect everything before launch?
No. Agree a launch scope and label its coverage. Optional context sources can follow. Confirmed sales claims require provider records, and source-level purchase attribution requires matching support.
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 concert example ↗ (opens demonstration in a new tab)
