Discuss your event

THE FULL EXPLANATION / JOURNEY 06, STEP 05

Which orders are confirmed, and which routes can we match?

Provider records establish the purchase totals for the event. Returned references can connect supported orders to campaign routes. Keep orders, ticket quantities, refunds and unmatched records distinct and reconciled.

← Return to this step in the journey

Website-only coverage

When only website activity is connected, visits and outbound handoffs can be reported. Confirmed orders and campaign sales remain unknown.

Unknown is not zero. Replacing missing sales with a ticket-click count would change the meaning of the number and mislead the promoter.

Orders without campaign references

A provider feed or agreed export can confirm order records for the relevant event and period. That does not automatically identify where each order came from.

Agree the event identifiers, reporting window, record definitions and handling of changed statuses with the provider. The demonstration does not implement or change payment, settlement or refund systems.

Matched and unmatched orders

The fictional example includes 268 provider orders: 215 matched to the tracked campaign records and 53 not matched to them. These counts refer to orders, not individual tickets or unique people.

The unmatched group stays separate. It could include other sales routes or records without a usable match; the dashboard should not assign a reason without evidence. Matching rules and coverage must be explicit in a real integration.

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)

YOUR NEXT EVENT

Give your event its own digital home.

Tell us about the show and what you want to achieve. We’ll agree the right scope together.

Discuss your event