Start with read-only checks
- Confirm the selected event, not only its display name.
- Check that the reporting period includes the activity time. Reports use Brussels date boundaries.
- Read the freshness and availability messages. Zero, unavailable, and stale are different states.
- Use Refresh traffic or Refresh sales for the relevant panel.
- Note whether the activity came from the app, a plain ticket link, a tracking link, or an external provider.
Orders without views or opens
Orders and traffic have separate data paths. Direct checkout, signal availability, consent, reporting delays, or an older app's instrumentation can produce orders without corresponding traffic counts.
Today's analytics can be provisional. Do not assume a confirmed order guarantees a preceding Card view, Event open, or Buy tickets signal. In Path exploration, only qualifying app-origin admission orders enter the final purchase stage; web/custom-link orders remain part of Sales.
Missing source detail
Unattributed means the order has no recognized tracked source available, not that it failed. Confirm whether a tracking link was actually used and whether you are looking at the period of the order. Newly created links do not fill in missing historical attribution.
Contact the team
Use and describe the issue. Your organizer reply details are prefilled when you are signed in. Useful context includes the panel, event reference, approximate time and timezone, reporting period, app/browser version, expected result, and exact visible error.
Share personal order references only through the appropriate private follow-up channel. Redact screenshots. Never send passwords, authentication tokens, card details, full QR tokens, scanner codes, or unrestricted buyer exports.