Tracking referral rate

A customer telling another customer about your product is one of the cheapest ways to grow. Most PLG teams still can't say, with any precision, which accounts are doing it or how much revenue it brings in.

Why referral rate is hard to track in a self-serve motion

In a sales-led business, a referral usually comes with a name attached: a rep hears about it directly. In a self-serve motion, someone signs up on their own, and the fact that a colleague or contact recommended your product often lives nowhere except that person's memory. There's no form field for it, no CRM note, nothing structured to query later.

Some teams try to patch this with a "how did you hear about us" survey field at sign-up. It captures something, but self-reported and inconsistent: people skip it, misremember, or pick the closest-sounding option instead of the accurate one. It's better than nothing, but it isn't a reliable measurement.

A more durable signal is behavioral: a referral link or invite feature built into the product itself, if you have one, or a domain-match pattern where a new sign-up shares an email domain with an existing paying account and follows shortly after that account's active usage. Neither is perfect, but both are observable and consistent, which a memory-based survey field is not.

How Funnelsight approaches this

Funnelsight tracks acquisition source alongside downstream product and revenue outcomes in a single view, so a referral signal doesn't have to live in isolation from what happens after sign-up. This is tracking and reporting, not a referral program in itself: Funnelsight doesn't create invite links, manage incentives, or run the mechanics of a referral program, the way a dedicated referral or loyalty platform would. It surfaces what's already happening so a team can decide what to build on top of it. If your product has an invite or referral mechanism, the sign-ups it produces can be tracked through to activation, conversion, and retention, the same way any other acquisition source is, on the activation tracking side of the funnel. That matters because a referral channel with a small number of sign-ups but strong downstream conversion is worth more attention than the raw count suggests, and that only becomes visible once acquisition and product data sit in the same place.

The scoring and alerting layer also applies here: if a team wants to flag when a specific account crosses a usage threshold that historically correlates with referring others (frequent use of a sharing or invite feature, for instance), that rule can be set up the same way a PQL threshold is, with the weighting visible and editable rather than a black box.

Starting simple

You don't need a dedicated referral program or a built-in invite feature to start measuring this. A team with no existing tracking can begin with something as basic as a spreadsheet listing known referred accounts (from support conversations, sales notes, or founder-led anecdotes) and manually check their conversion and retention against the account base as a whole. That's a smaller scope, not lower-quality data: it covers fewer accounts at first, but every account on the list is a verified referral, not a guess. The mechanism can get more automated later, once there's a pattern worth building toward.

A concrete example

Say a team notices that accounts created by a colleague of an existing user (same email domain, sign-up within two weeks of that user's active period) convert to paid at a higher rate than the account base overall. Once that pattern is visible, tracked the same way as any other acquisition source rather than buried inside a blended "organic" or "direct" bucket, it becomes something to act on: prioritize a lightweight invite mechanism, or flag those accounts for a different onboarding email, rather than treating every sign-up the same way.