The Home page
Home summarises a whole website in one scroll: a live strip, a scorecard, three trends and five cards. This page says exactly where each number comes from — including average session duration, which is not built from the gap between event timestamps.
What is on the page#
Home is not a report; it is a first look. Each block answers one frequent question and then hands you off to the full report on that subject.
| Block | What it shows | Link |
|---|---|---|
| Key metrics | The four headline numbers, each with a sparkline of its day-by-day shape over the range. Its header states the date range they all follow and carries the live widget — active users in the last 30 minutes with a per-minute pulse, plus identified users | Realtime report → /realtime |
| Users trend | Users, sessions and conversions over the range, one small chart each | View reports snapshot → /acquisition |
| Users by channel | The first seven channels with users (as an inline bar), sessions and conversion | Acquisition → /acquisition |
| Device share | Total users and the desktop / mobile / tablet split, as one share bar with a figure per device | View tech → /tech |
| Conversion funnel | One fixed five-step funnel as step bars, with each step's completion | Funnel → /funnel |
| When do your users visit? | A day-of-week × hour heatmap, with its busiest hour named above it | — |
| Where are your users? | The top countries and a world map of users by country | View demographics → /geo |

Everything except the live widget reads from the range you picked in the date selector at the top of the page — the chip beside Key metrics spells that range out. The live widget always shows the 30-minute window and ignores the range entirely.
Every block that has a full report links to it from its own header, opposite the title.
The four headline numbers#
| Number | Exact definition |
|---|---|
| Total users | Unique visitors in the range, keyed on the anonymous device ID |
| New users | Visitors whose first_visit event falls inside this range |
| Engagement | The share of sessions with more than one page view |
| Avg. session | The average of real engagement time per session |
Each number carries a sparkline: the same metric day by day across the range (engagement and session duration per day use the same definitions as the headline), so you can see whether the total was earned steadily or in a spike.
Engagement is the complement of bounce rate: a session with a single page view counts as a bounce, everything else as engaged. So if your bounce rate is 38%, this card reads 62%.
New users comes from an event definition, not from counting identity records. The tracker stamps each device's very first visit with a first_visit event, and Home counts that event inside the range. Because it is counted over the same rows and the same population that produce total users, it cannot exceed them.
Where average session duration comes from#
This is the most important detail on the page. In AdPix an event's time is its server receipt time, not the moment it happened in the browser. The tracker sends events in batches, so several events from one session can land in the same millisecond. Compute session length as the gap between the first and last row and it collapses to zero for a large share of sessions — which is exactly what used to happen.
So duration is read from the tracker's own signal instead: the engagement_time_msec parameter, carried on the user_engagement event, which holds the time the user was genuinely active on the page. AdPix sums that value per session, then averages those sums across the sessions in the range.
A tab the user left open but stopped using does not inflate session duration. In exchange, any error in page-view counting lands directly on this number too, because user_engagement travels alongside the page view.
Trends#
Three small charts — users, sessions and conversions — each with the range total above it. Conversions count the website's key events, so they stay zero until key events are defined.
Users by channel#
This card ranks the first seven channels by users and gives three numbers for each: users, sessions and conversion. When you compare segments, each channel gets one row per segment, side by side.
The Conv. column is that channel's key-event count divided by that channel's session count. Two consequences worth knowing:
- If no key events are defined for the website, this column stays zero for every channel.
- Because the numerator counts events and the denominator counts sessions, one session with several key events can push the figure above 100%. It is a ratio, not a rate.
Every event's channel is computed from your current channel rules when the report is read, not when the data was collected. Change a channel definition and this card immediately reclassifies all of history under the new definition — no reprocessing job is involved.
A channel with no recognised source appears as "(none)".
Conversion funnel#
The Home funnel is fixed and always follows the same five steps: page_view, session_start, add_to_cart, begin_checkout, purchase. Each step is a bar with its users and completion beside it. Steps with no users in the range are dropped, and if fewer than two remain you get this line instead of a chart:
"Not enough funnel events yet — wire add_to_cart / begin_checkout / purchase, or build one in Funnel."
So on a site with no e-commerce events the card is deliberately empty. For any other funnel use the Funnel report itself, where you choose the steps.
Visit times and the country map#
The "When do your users visit?" heatmap buckets event counts into a day-of-week × hour grid. Those day and hour buckets are evaluated in the website's timezone — not your browser's and not UTC. Change the website timezone and this grid shifts with it.
The card at the foot of the page lists the top eight countries next to a world map that covers up to 250 countries. For a city and region breakdown, go to the demographics report.
The live strip#
This is the one block that ignores the selected range. The large number is the count of unique visitors who sent at least one event in the last 30 minutes — the same definition and the same window the Realtime overview uses, so the two can never disagree. The small bars beside it are that window minute by minute.
"Identified users" belongs to the selected range rather than the last 30 minutes: unique users in the range who resolved to a real identity in your business.
Comparing with the previous period#
The green and red deltas on the four headline numbers and on the three trends, and the dashed previous-period line on each trend, appear only when you switch comparison on in the date selector. Home used to show that comparison unasked, and readers could not tell what the number was being measured against; now nothing is compared until you ask for it.
The invalid-clicks card#
When the website's plan does not include fraud protection, Home carries a card titled Invalid clicks on your ads: the paid clicks confirmed invalid in the last 30 days, their share of your paid clicks and, when you have imported cost data, the estimated ad spend on them. The numbers are a floor, not a ceiling: only the Confirmed tier is counted. With no paid clicks or no confirmed click, the card is not shown.
When a card is empty#
If the cards have data but the numbers are not believable, check page-view counting before anything else — it is the base number that engagement, session duration and the funnel all ride on. Page views and single-page apps covers the counting rule and the most common installation mistakes.
Frequently asked questions#
Why can new users never exceed total users?
Because both are counted over the same rows and the same population. A new user is a visitor whose first_visit event falls inside the selected range, and that is a subset of the visitors seen in the range. This number used to come from somewhere else and could exceed total users; it no longer can.
Why are Conversions zero on the Trends card and the Conv. column zero for every channel?
Because no key events are defined for this website. Conversions count key events, so with an empty key-event list they stay zero. Define your key events in Admin and both fill in.
Why doesn't average session duration match another tool I use?
AdPix builds duration from the engagement_time_msec parameter — the time the tracker actually observed the user active on the page — not from the span between a session's first and last event. A session where the user left the tab idle in the background gets a shorter duration here.
Is the live strip's number the same as the Realtime report?
Yes. Both count unique users active in the last 30 minutes, with the same definition and the same window. If you switch the Realtime page to a 5- or 60-minute window that figure changes there, but the Home strip always shows 30 minutes.
Thanks — your feedback helps us improve the docs.