Dashboards and Metrics
The Analytics dashboard gives content authors a view of how visitors interact with their site — without exporting anything or asking a developer for a report. From here you can follow engagement trends, pageview volume and conversion activity across any date range, and see how each one breaks down by device, browser or language.
It has three tabs — Engagement, Pageview and Conversions — plus a site selector, a date-range selector, and a Refresh Data button. Every metric card also shows its trend against the previous period of the same length, so you can see direction as well as volume.
Today is not included, and data is not real-time
The date ranges cover complete days only. "Last 7 days" means the seven full days ending yesterday — the current day is excluded entirely, because it has not finished and its data would be partial. Nothing you do today shows up on any dashboard until tomorrow.
New data is also not available instantly. The figures behind the dashboards are recalculated periodically rather than live, so a day that has just closed takes a while to appear in full. Use Refresh Data to pull the latest available figures. The range selector requires a minimum of 7 days.
Just finished setting up?
Send a few test events, then check the dashboard tomorrow. To confirm tracking is working right now, use the browser's network panel instead.
Engagement#
Metric cards: Engagement Rate (with engaged-session count), Avg Interactions (Engaged), Average Session Time and Total Sessions. Charts: Engagement Breakdown (engaged vs bounced sessions), and Engagement by Language / Browser / Device.
Engagement. Engagement Rate carries the engaged-session count and a trend against the previous period; the donut splits engaged from bounced sessions. Note the card is labelled Avg Interactions (Engaged) — the denominator is engaged sessions, not all sessions.
What counts as an engaged session
- Session duration is longer than 10 seconds, or
- Session contains 2 or more pageview events, or
- Session contains at least 1 conversion event.
The rule is in the product. The info icon on Engagement Rate opens this panel, which states the three engagement criteria and the 10-second threshold. The documentation should match this wording exactly.
Pageview#
Metric cards: Total Pageviews, Unique Visitors (based on user_id) and Top Page Performance. Charts and tables: Pageviews Timeline, Pageviews by Browser, Pageviews by Device, and Top Performing Pages — sortable by title, URL or pageviews, and paginated.
Pageview. Unique Visitors is annotated Based on user_id. Bot shows up as its own category in both breakdowns — here 35% of all pageviews.
Top Performing Pages is sortable by title, URL or pageviews, and paginated. There is no language breakdown on this tab — language appears only under Engagement.
Conversions#
Metric cards: Total Conversions, Converting Visitors (shown as converting / total) and Site Conversion Rate — the share of all sessions that produced at least one conversion, not a rate among engaged visitors. Charts and tables: Conversion Trend, Traffic vs Conversions, and Content Present in Conversions — the table listing which content items were clicked, seen or viewed on the path to a conversion, with a per-item conversion rate.
Conversions. Converting Visitors is shown as a fraction. Site Conversion Rate reads 0% here even though 14 conversions were recorded — the true rate is 0.24%.
Content Present in Conversions is the only place clicks and impressions surface. The Type column tags each row content_click, content_impression or pageview, with a per-item conversion rate.
How Metrics Are Calculated#
| Metric | Formula |
|---|---|
| Unique Visitors | COUNT(DISTINCT user_id) |
| Engagement Rate | SUM(engaged_sessions) / SUM(total_sessions) × 100 |
| Avg Interactions (Engaged) | SUM(total_events_engaged) / SUM(engaged_sessions) |
| Average Session Time | SUM(total_duration_all) / SUM(total_sessions) — all sessions |
| Site Conversion Rate | SUM(engaged_conversion_sessions) / SUM(total_sessions) × 100 |
| Content conversion rate | attributionCount / totalEvents × 100 |
All rates are ratios of sums — never an average of daily rates — expressed as a percentage from 0 to 100. A zero denominator returns 0.0, not an error.
Unique visitors do not add up across days
Unique visitors are counted distinctly within each time bucket. A visitor who returns on three days counts once on each of those days, and once in the range total — so summing a daily column will not match the total. This is expected, not a data error. Page views and event counts, by contrast, are additive.
Bot traffic is included
Bots are detected and reported as their own category in the browser and device breakdowns, and they are counted in the totals. On a public marketing site this is routinely a third of all traffic, so read the totals with that in mind.