Performance Command Center

Click a row for the full profile: attribution, revenue split and the GA4 web journey. The journey links via the product user-id and covers roughly a third of contacts — anonymous pre-signup visits stay unlinkable until the attribution identity map exists. Emails are internal business-contact data; treat them accordingly.

Directional, not gospel: every study defines “activated” and “PQL” differently. Our figures come from the BI contacts model for the selected window and follow the date filter.

How to read: sorted by Latest activity — the most recent commercial event (first purchase, free→paid conversion, or renewal), so anything that just happened is on top. In CRM since = when the org record first synced (for a converted free user this is earlier than the first payment; ≈ marks the initial backfill window). Signup cohort = the earliest linked user's Ninox signup. Current period = the running plan window — for monthly plans the start moves forward at every renewal, so it is not a win date. Click any row for its linked users.

Views · all vs Landed first — the distinction that matters: Views · all counts every view of the page, wherever it sat in the visit (a reader may have arrived on the homepage and clicked through to it). Landed first counts only the visits where this page was the entry point — the reader arrived here directly from Google, social or a link, so the page earned the visit. High views but a low “landed first” share = people read it once they are already on the site; a high share = the post pulls new readers in. Both are additive across rows.
Also: click any row for that post's top search terms (Search Console) and CTA breakdown (GA4). Time / view = summed engaged time ÷ views. Read ≥75% = blog_article_read_75 ÷ article reads. Signups · in session = a signup completed in the same visit that read the post (“landed” = that visit also started here) — session-based, so these overlap across rows and must never be summed.

One row = one distinct CTA (its wording × where it sits × what it does). location tells navigation apart from real conversion CTAs (e.g. blog_bottom_cta vs header).