---
description: "Read traffic totals, recent visits, UTM sources and cities from the organizer analytics projection."
group: "Resources"
order: 25
---

# Event traffic analytics

Bring the event's existing traffic projection into organizer reporting.

## Read traffic {#read-traffic}

GET `/{event_id}/traffic_logs/index.json` with organizer authentication and event access. It returns the existing dashboard-oriented projection.

| Field | Meaning |
| --- | --- |
| `totals_last_90_days` | Date/total rows for the recent reporting window. |
| `total_last_24_hours` | Recent visit count. |
| `last_hour_logs` | Recent domain, UTM source, city, country code and creation time records. |
| `top_utm_sources` | Source aggregates. |
| `top_cities` | City aggregates. |

## Interpret the projection {#interpret-the-projection}

This is the current organizer reporting projection, with legacy timestamps and count representations. It does not publish a generic analytics query language, arbitrary date-range API or a conversion-attribution guarantee. Parse documented stable fields and allow additional fields.

## Handle visitor data {#handle-visitor-data}

Keep visit-level data server-side and restrict reporting access to authorized organizers. Prefer aggregated totals where possible, and apply your retention policy. See [privacy and data handling](/en-us/docs/privacy-and-data.md) and [supporting data](/en-us/docs/supporting-data.md) for organizer context.