# Event website performance measurement decision matrix

Copy one row per page, audience, phase and question. This is a planning worksheet, not a claim that a tool already measures a provider's checkout.

| Event phase and question | Page or journey | Owner / provider boundary | Synthetic condition and success signal | Field metric and audience segment | Available samples / gaps | Privacy and access review | Next decision / owner |
|---|---|---|---|---|---|---|---|
| Before sales: can guests reach event details? | Public page | Event-site owner | Repeatable device, region, network and cache; expected content | Existing visits if available | Low traffic; visitors who cannot load are absent | No personal URL parameters | Investigate missing or slow path |
| On-sale: which attendees are slow? | Registration entry | Identify ticketing handoff | Reproduce affected region and device | Distribution by coarse region and device class | Document sampling and time window | Aggregate data only | Name owner and mitigation |
| After release: did a page regress? | Exact changed page | Event-site owner | Compare with same earlier lab settings | Compare relevant post-release window | Note differing traffic and cache | Review retention and access | Decide whether to revert or optimize |
| Hosted checkout: what can we observe? | Provider URL | Provider liaison | Approved test mode only, if available | Ask provider for aggregate evidence | Event-site RUM does not automatically cover provider | No live orders or attendee data in probes | Escalate with provider |

## Reading rule

- State the exact question before choosing a tool. Availability, responsiveness and completed purchase are different outcomes.
- Record page, time window, event edition, release, device, network, location and cache for comparable synthetic runs.
- Read field values as a distribution of instrumented real visits. Low traffic can leave segments inconclusive.
- Investigate disagreements instead of averaging synthetic and field scores. Field data excludes visitors who never loaded the page.
- Recheck provider boundaries, data collection and privacy obligations when changing ticketing flows.