Your Activation Funnel Starts Before Signup — Measure It

Ask most SaaS teams to draw their activation funnel and the first box is signup. That is where the analytics starts counting, so that is where the funnel is assumed to begin. But for any product-led company, the decisive product experience increasingly happens before an account exists — in an interactive demo, a logged-out sandbox, a reverse trial, or a shared workspace link a colleague sent. Userpilot puts the shift bluntly: the goal of a modern signup flow is to “route a new user to a real product outcome inside the first session, not to collect data or maximize form completion”. If value now arrives before the form, a funnel that starts at the form is measuring the middle and calling it the top.

This is not a rounding error. Mixpanel’s 2026 read on growth names product as the new primary growth channel, which means the logged-out product experience is doing acquisition work that used to belong to marketing pages. When median SaaS activation sits around 30% (per a study of 500+ products), the teams that can see the whole path — from first product touch, through signup, to first value — have a diagnostic advantage the signup-anchored teams simply do not. This piece draws the pre-signup stretch as an explicit funnel stage and shows how to instrument it.

Signup is a midpoint, not the top of the funnel

The single most useful reframe is to stop treating account creation as the origin of the activation funnel and start treating it as a checkpoint inside it. In a product-led motion the real sequence is: a visitor enters the product experience → performs (or fails to perform) a core value action → decides to create an account → reaches first value as a known user. Signup sits in the middle of that chain. Anchoring your funnel there discards the first two steps, which is precisely where the strongest predictive signal lives — a prospect who created something real in your logged-out sandbox is a different lead from one who clicked “sign up” off a pricing page, even though your dashboard shows them as identical new users.

The downstream half of this funnel is already well understood: the signup-to-first-value funnel and the account-creation-to-verification dead zone cover what happens once a person commits. What almost no one instruments is the stretch before the commit — the anonymous product session that decides whether the commit happens at all. Extending the funnel upstream does not require new metrics; it requires firing your existing activation events one step earlier and keeping the identity attached across the signup boundary. The reward is that “our signup conversion dropped” becomes a question you can actually answer, because you can see whether the problem is fewer people reaching the product or fewer product-experiencers converting.

Interactive demos, reverse trials, and the logged-out sandbox

Three patterns have pushed real product value ahead of signup, and each needs to be modelled as a funnel stage in its own right. Interactive demos and logged-out sandboxes let a prospect use a scoped version of the product with no account; reverse trials give every new user full premium access for a window before downgrading; and product-led sharing (a link to a doc, board, or dashboard) drops a first-time visitor straight into live product surface. In all three, the aha moment is designed to fire before — or independent of — the account that your analytics keys on.

Reverse trials are the clearest case of why the old funnel breaks. Because the user gets premium access up front, the activation event and the monetization event decouple: the decisive experience happens in the premium window, often within minutes of arrival, while the paid decision comes days later at downgrade. A team that still defines activation as a milestone counted only after signup will see the drop-off in the premium stretch as an unexplained gap. The fix is to instrument the premium window as a distinct stage between acquisition and free-to-paid conversion, with its own entry, depth, and exit events — so a shallow premium experience shows up as a measurable cause of weak conversion rather than a mystery.

Why product analytics tools start counting too late

Most product analytics platforms ignore pre-signup usage for a structural reason: they are built around a known user identity. The data model attaches every event to a user, and funnels, retention, and cohorts are all computed per user — which presupposes the user exists. A logged-out visitor has no user record, so their events are commonly dropped, dumped into a throwaway anonymous profile that never gets merged, or captured only by a separate web-analytics tool that cannot join to product behaviour. You end up with two islands: web analytics that saw the anonymous visit and product analytics that saw the account, with no bridge between them.

That split is the same wall that separates product analytics from web analytics generally, and it is why the pre-signup stretch falls through the cracks by default rather than by decision. The good news is that it is a solvable instrumentation problem, not a law of nature. If you emit the same event taxonomy in the logged-out context and carry a stable anonymous identifier across signup, a single product analytics tool can render the full funnel — no second dataset, no manual join. The work is in the plumbing, and the plumbing is identity plus taxonomy.

Instrumenting the pre-signup stretch

The mechanics come down to two moves. First, assign a stable anonymous identifier — a first-party cookie or device ID — the instant a visitor enters the product experience, and fire your normal activation event taxonomy keyed to that ID: feature touches, core value actions, and the aha-moment event, exactly as you would for a logged-in user. Second, when the visitor signs up, run an identify/merge call so the anonymous event history is stitched onto the new known user rather than orphaned. Done correctly, the user’s pre-signup actions and post-signup actions live on one timeline, and any funnel or cohort query can span the signup boundary transparently.

Both moves lean on machinery you should already be building. The stitching is exactly the anonymous-to-known identity resolution problem — the identify call, the profile merge, and the places it silently breaks (a lost cookie, a cross-device signup, a consent reset). The events themselves depend on a disciplined event taxonomy and tracking plan: the aha-moment event must be named and fired identically in the logged-out and logged-in contexts, or the two halves of the funnel will not line up. Define the pre-signup aha the same way you derive the activation metric post-signup, and the upstream stage becomes a native extension of the funnel rather than a bolt-on.

The consent gap that undercounts the top of funnel

There is a catch that makes the pre-signup stretch harder to measure than the logged-in funnel: consent. Setting an anonymous identifier or firing analytics events in the logged-out context is exactly the pre-consent activity that regulators now scrutinise, and under GDPR/ePrivacy those events must not fire until the visitor has given a valid choice. That means a share of your pre-signup product-experiencers will be invisible not because they did not act, but because they declined tracking — and unlike a logged-in user, you have no account record to fall back on. The top of the funnel is therefore the part most exposed to consent-driven data loss.

The practical response is to measure the loss rather than pretend it is zero. Track the consent decline rate in the acquisition funnel and treat your pre-signup counts as a measured floor, not a true total. Where consent is declined, server-side or aggregate signals (page-level counts of product-experience entries, for instance) can bound the gap even when per-user events cannot fire. The goal is not perfect coverage; it is knowing how much of the top of funnel you can see, so that a dip in pre-signup reach is not confused with a change in consent rates. A pre-signup funnel reported without its decline rate is a number you cannot trust to move on.

Making pre-signup a funnel stage you act on

Instrumentation only pays off if the numbers change a decision, so define the pre-signup stage around three questions you will actually act on. Reach: of everyone who arrives, how many enter the product experience at all versus bouncing off marketing pages? Depth: of those who enter, how many perform a core value action rather than poking around? Conversion: what share of product-experiencers go on to create an account? Each has an obvious lever — reach is a landing-and-CTA problem, depth is a product-onboarding problem, and conversion is a signup-friction problem — so a drop in one points straight at the team that owns it.

The decisive comparison, though, is activation rate for users who experienced the product before signup versus those who did not. If the pre-signup group activates materially better, the logged-out experience is a genuine activation lever and belongs in your north-star funnel, funded and optimised like any other stage — and it becomes a natural input to product-qualified lead scoring, since pre-signup depth is behaviour that predicts conversion far better than form-fill demographics. If the two groups activate the same, you have learned something equally valuable: the demo is marketing theatre, not an activation driver, and you can stop over-investing in it. Either way, the answer only exists once the funnel starts where the product experience does — before signup.