Using Event Logs and Analytics
See the requests reaching your tagging server and the trends behind them.
Event Logs and Analytics are built from the traffic actually reaching your tagging server, so you can check that tracking works without opening browser dev tools.
Which plans include it
| Plan | History available |
|---|---|
| Free | Not included (the tab is hidden) |
| Pro | 3 days |
| Business | 7 days |
| Enterprise | 15 days |
Event Logs tab
- Choose a time range: last hour, 24 hours, 7 days or 30 days, capped by your plan's history.
- Filter by event type or by response status, and change the page size.
- A summary shows total requests, the share of successful (2xx) responses and the average response time.
- Turn on Live to refresh every few seconds while you test.
Analytics on the Overview tab
Charts show event volume over time, the distribution of event types, top events, purchases, conversion and revenue. Revenue is grouped by currency, so different currencies are never added together.
An important limitation
Event names, values and currencies are read from the request URL. Requests that carry their data in the request body (typically POST requests) still appear in the logs with their path, status and timing, but their event name and value cannot be read, so they show as blank. This is a limit of what is visible at the edge, not a fault in your setup.
Still stuck?
Open a support ticket from your dashboard and include the container name.