Workspace home

The screen every session opens on — your sites and their busiest campaigns, the two curves the workspace receives, the expected range beneath paid clicks, three breakdowns, and the plan card in the rail.

Updated October 26, 2026

The workspace home is the screen you land on. It lists your sites with their standing and their window figures, the five busiest campaigns across them, the workspace's plan facts, two workspace-wide curves — events received and paid clicks observed — with an expected range under the second, and three breakdowns of the same window. Everything else is a site's business and sits one click down.

The header

The locator row reads Workspace, then a Docs link that opens this page in a new tab; the title is the workspace's name. The window control on the right is the same period selector every site screen carries: Today, Yesterday, Last 7 days, Last 30 days, This month, or a custom range, with Last 7 days as the default. The window you pick here is the one a site opens on. When a window reaches further back than your plan can read, its start is pulled forward and the picker says so. See Time periods.

Left of the selector, Updated states how long ago the page was read, with a Read again button beside it. The stamp dates the reading, not the data; what each site last sent is the roster's job.

A workspace with no site goes to site creation instead of an empty home (see Install the tracker). A workspace holding more sites or members than its plan includes sees an over-capacity notice instead, which names who can act and, for the owner over the sites cap, lists the sites so one can be opened and removed.

Sites and campaigns

The first framed block is titled Sites and campaigns: your sites, and the campaigns that brought the most paid clicks in the selected period. Owners and admins find Connect a site and Settings (the workspace settings) in its header; a member sees neither.

Sites

The first card is the roster: every site in the workspace, in the workspace's own order, whether or not it received anything in the window.

On the rowWhat it is
NameThe site's name, or its domain when no name was set. When a name was set, the domain sits under it.
The pipThe site's standing, in a tooltip: Receiving events (the pip pulses), Last event 3h ago, Waiting for first event (never received anything), or Disabled.
eventsEvery event the site received in the window, all types.
paid clicksPaid sessions that arrived on the site in the window. A zero is drawn fainter — it is a real reading, not a missing one.
Realtime · Campaigns · ConversionsThree doors into that site — see Realtime, Campaigns, Conversions. The row itself opens the site's Overview.
The gearThat site's settings. Owners and admins only, and only when the workspace has more than one site; with a single site the gear sits in the card's header instead.

The card's header states the roster's standing: 2 of 3 receiving. With a single site it states the site's recency instead — Last event 7m ago — which is an all-time fact, not a window figure. A lone site still waiting for its first event reads 0 of 1 receiving.

If the workspace read does not answer, the roster still renders and both figures read 0, the same faint zero a site that received nothing shows. The Campaigns unavailable card beside it is what tells the two apart.

Top campaigns

The second card is a shortcut, not a report. Its header reads Top campaigns, By paid clicks: the busiest five across every site. Each row is the workspace's own name for the campaign, or No name when nobody set one, over what the network sent — the network, the raw campaign value (prefixed ID when it is a long numeric id, as Google's are), and the site it runs on when the workspace has several. A bar against the leader and the click count close the row.

A row opens the site's Overview already narrowed to that network and campaign. Campaigns are counted per site: two sites can both run a campaign called the same thing, and they stay two rows.

Untagged clicks have no row here; they are still counted in every other figure on the page. When no paid click in the window carried a campaign tag, the card says No tagged campaigns; when the workspace read did not answer, it says Campaigns unavailable.

On a one-site workspace with at least one tagged campaign, the card ends on All campaigns, the door to that site's Campaigns directory, which is the complete list. With several sites each row of the roster carries its own Campaigns door.

The Workspace card

The block's third column is the Workspace card: Plan (the badge; it opens Plans and billing for owners and admins), Sites as 2 of 3 against the plan's limit, Members as 4 of 5 (it opens Members and roles for owners and admins), and Readable window in days. Under it, owners and admins may see next steps: Install the tag on a site that has not received an event yet, and Tag your ads when paid clicks arrived in the window without a campaign tag. Below 1000 pixels of frame the card drops under the two lists.

The plan banner

Between the first block and Activity, a Free workspace's owners and admins see one card: You're already collecting all of this. The line under it names the cheapest paid plan that unblurs — today Starter — and what it reads back: the provider and the full address, 30 days of history instead of 7, and the full session log, closing on its monthly price (€19/mo.). The Upgrade to Starter button opens Plans and billing.

Retention is unlimited on every plan, so a Free workspace is not missing data — it holds data it cannot read yet. A paying workspace never sees this card, and neither does a member.

Activity

The next block is titled Activity, with one line under it: Events and paid clicks observed across every site in this workspace. Platform-reported totals can differ. Two cards share the row, one curve each, on their own scales: events outnumber paid clicks by an order of magnitude, and one shared scale would flatten the clicks.

Each card leads with the window's total and, beside it, the change against the previous period: +18.4%, −7.1%, new when the previous window had nothing, stopped when this one has nothing. Hovering the change names the baseline: vs 1,204 · Jul 27 – Aug 2. When the plan's window cannot hold the previous period whole, the slot reads no baseline; on Free a window of a week or longer never fits one. A sign carries the direction and nothing colors the change — whether a figure is good is yours to judge.

The card's subtitle names the bar width: 2-hour volume on a week, 6-hour volume on a month, 15-minute volume on a day. The last bucket of a window that ends now is drawn faded, and the readout dates it so far. The readout follows the pointer and states the bucket's time in UTC and its count.

A window with nothing in it draws no curve; the card reads No events in this period. or No clicks in this period. A window holding a single bucket prints that bucket's count and time instead of a curve.

Events counts every event the workspace received in the window — all sites, all event types. It is the same population the monthly meter counts, which is why the two reconcile on a paid plan. On a one-site workspace the card ends on All events, the door to that site's Events.

Paid clicks counts paid sessions across every network, by the bucket they arrived in. It is not the site Overview's curve, which follows one network, so the two are not meant to match on a site running ads on two networks. When the window spans at least two calendar days, today counted, this curve is drawn by day — daily volume — because the expected range beneath it is a daily quantity.

The expected range

Under the Paid clicks total, a second line answers one question: what would this workspace have received if nothing had changed, and how far is that from what arrived? It is a counterfactual, not a prediction. It compares the window with the 28 days before it, so a change you make — a campaign cut, say — shows as the gap. See Forecast.

The reading leads with the gap, in clicks a day — −76 /day — and within range beside it when the observed mean sits inside the interval. The sentence under it states the pair and the days it covers: Sep 29 – Oct 4: 124 a day observed against 200 expected, if nothing had changed. Below ten a day the figure keeps one decimal. Nothing colors the gap in either direction.

On the plot, the range is a ribbon behind the curve with its median through it. The readout prints it with its bounds: Expected 208 (155–254). Until it appears, the line reads Against what was expected.

The silences

When the card cannot show the range it says why:

On the cardWhat it means
No complete day yetThe window's only day is still running, so there is nothing whole to compare. A custom range longer than 92 complete days reads the same.
Not enough history yet / From Sep 8The workspace has not been receiving for the 28 days the comparison needs. When the wait has a date, the date is stated.
Beyond your plan's windowThe 28 days before the window reach past what your plan can read. Free reads 7 days, so this is Free's reason whenever a complete day exists. Starter's 30 days clear it only in front of a window that starts yesterday, so it is Starter's reason on every window that starts earlier.
Not included in your planThe window fits, but the plan does not include the expected range. It is included from Solo.
Bounded by your allowanceA month over its allowance touches the window or the 28 days, and the comparison would not be honest.
Could not be readThe range came back empty.
The expected range could not be read.The read failed. The figure is an em dash and this sentence stands under it.

A plan boundary keeps the em dash and, for an owner or admin, links to billing. A wait draws a still mark.

When the range cannot be shown but the history is there, the card falls back to what the workspace usually does: the gap against the median of those 28 days, within its usual range when it sits inside the band the days usually stay in, and the sentence Usually 158–229 a day over the 28 days before Sep 29. The plot then carries two dashed hairlines for that band, named Usual, per day in the readout.

The allowance note

On Free, when the month's event allowance ran out inside the window, a line under the curves states where reading stops: Reads stop at Aug 2, 14:00 UTC — this month's event allowance. followed by Everything after it was collected and is kept — a larger allowance moves the line and these curves fill in at once. For an owner or admin, a larger allowance links to billing. On a paid plan the overflow is billed, nothing stops, and this line never appears.

The breakdowns

Under Activity, three cards break the same window down. Each is a table of a label, a count and a share with a bar; the share is of the card's own population, said by its header.

CardRowsShare of
Event typesThe event types of the Events screen; a conversion is split by its tier, Conversion · primary or Conversion · secondary (no tier when none was sent).Every event in the window.
Traffic sourcesOne row per network, with its logo, counting Paid clicks.Every paid click in the window.
Visitor outcomesCompleted, with Came back and completed and Completed on a single paid click indented under it, then Engaged only, then No conversion. The words are the ones the Visitors page uses.Every identified visitor behind a paid click.

On a one-site workspace each card ends on a door to that site — All event types, All networks, All visitors — and a network row opens the site's Overview for that network. A card with nothing in the window says so (No event in this period., No paid click in this period., No identified visitor behind a paid click in this period.); when the workspace read did not answer, it reads Unavailable.

The rail

The rail brackets the workspace: Home on top, its settings at the bottom, and the screens of the site the workspace lands on in between — the site receiving now, else the one that has ever received, else the first.

GroupRows
WorkspaceHome — this screen
AcquisitionOverview · Realtime · Conversions
SourcesNetworks · Campaigns · UTM tags
TrafficSignatures · Visitors · Connections · Events
SettingsGeneral · Members · Billing — owners and admins only

On a workspace with several sites the rail carries the landing site's screens without naming it; the roster is where you choose a site. A member's rail ends at the site screens. See Workspace settings and Members and roles.

The rail's foot is the workspace card, on every dashboard screen: the workspace's name, its plan as a badge — Free, Starter, Solo, Growth, Agency or Enterprise — and the month's meter, a bar over 23,400 / 50,000 events. The count may exceed the allowance and visibly does; the bar turns to the caution color only when something is withheld, which is Free over its allowance. A paid plan past its allowance is billed, not warned. For an owner or admin the card opens Plans and billing; a member reads the same facts with no link. See the glossary for plan and allowance.

What this screen does not do

  • No rollup across workspaces. A workspace is the isolation unit; the home reads one.
  • The campaigns card is not the directory. No funnel, no comparison, no conversion columns — that is the Campaigns screen.
  • No verdict on a change. The change and the gap carry a sign and a magnitude; no red, no green, no "underperforming".
  • No prediction. The expected range says what would have arrived if nothing had changed, never what next month holds.
  • No counts in the rail. The rail says where you are; the roster is the site list.
  • Nothing about a visitor in the curves. No row describes a browser, a connection or a session, so no figure here is blurred by plan. What a plan governs on this screen is the window, the baseline and the expected range.
  • Nothing deleted to make room. The allowance bounds what a window reads this month; every event is kept on every plan.

Questions

Why does "124 a day observed" not match the Paid clicks figure above it?
The figure at the top of the card is the whole window, today included. The sentence under it covers the window's complete days only, because a part-day set against a whole day's expectation would show a shortfall every morning. The dates in front of the sentence name the days it covers.
Why do events here read lower than the meter in the rail?
On Free, a read stops at the month's allowance while the meter keeps counting everything that arrived. The note under the curves states where the read stops. On a paid plan nothing stops and the two agree.
Why does the card say "Beyond your plan's window"?
The expected range compares the window with the 28 days before it, and those days must fall inside the window your plan can read. Free reads 7 days, so the range never shows there. The expected range is included from Solo.
Why does a campaign read "No name"?
Nobody in the workspace has named it yet. The line under it is what the ad network sent — the network, then the raw campaign value, prefixed "ID" when it is a long numeric id.
Why do these totals differ from what the ad platform reports?
Every figure here is observed on your site — events the tracker sent, and paid sessions as they arrived — not what a platform billed. The Activity section says so under its title.