Select the reporting period
Open Traffic and choose 7 days, 30 days, 90 days, or Change dates. Check the displayed period and freshness message before comparing results.
Reporting date boundaries use Europe/Brussels, including daylight-saving changes. Today's activity can be provisional. A refresh does not guarantee every recent app signal has already reached reporting.
Read the metrics
| Metric | What is counted | What it does not prove |
|---|---|---|
| Card views | Recorded displays of your event card. | A distinct person viewed the event or intended to buy. |
| Event opens | Recorded openings of your event. | A unique visitor or completed purchase. |
| Buy tickets | Recorded selections of the ticket button toward Nooba checkout or an external link. | A ticket was purchased. |
| Participate | Recorded selections of Participate. | Checkout completion or actual attendance. |
Repeated interactions can count more than once. Use the information icon beside a metric for its definition.
Action rates
Rates compare recorded action counts. For example, five Event opens compared with ten Card views give a 50% ratio. They do not establish that five distinct people moved through the same journey.
Repeated actions and direct entry can make a later count greater than an earlier one, including rates above 100%. When a denominator is zero or data is unavailable, a dash is more useful than an invented percentage.
Zero, unavailable, and stale
- Zero: no matching activity was recorded in the available report data.
- Dash or unavailable: the metric is not available or cannot be calculated.
- Stale: the screen is retaining a previously loaded snapshot that may be out of date.
Use Refresh traffic and read the resulting state. If confirmed orders exist but expected activity remains missing, follow the analytics troubleshooting checks.