Referral tracking

Track a referred person from intake to the outcome that makes the referral worth paying for. Give each record a clear source, a credit rule, and a path through the pipeline. A clean record shows which relationships convert quickly and where the next growth effort should go.¹ Tracking lets you invest more in sources that work, since referrals can continue while effective sources remain unknown.²

Define the credit rule

Start with the rule that decides when a referral earns credit. Write it so everyone handling intake, pipeline, revenue, and rewards applies the same interpretation.

A documented definition can count Referral Revenue after services are delivered and collected under a binding agreement or purchase order executed within one year of lead submission.³ Use that as a starting point, then specify the event that begins attribution and the event that closes it. Ask what makes the referral count and what must happen before it earns a reward.

Before launch, set the program's success criteria and decide how to account for cannibalization.⁴ This separates genuinely incremental referrals from demand that would have arrived through another route. The credit rule should be clear enough for the person entering a lead and the person approving a reward to reach the same answer.

Capture the referral at intake

Capture the identity as the referral enters the pipeline. A source added after the opportunity has moved stages is harder to verify and easier to lose.

Referral tracking has two fundamental approaches: automated systems and manual CRM-based tracking.⁵ An automated path can attribute signups with referral codes, unique links, UTM parameters, and cookies.⁶ A manual CRM path uses three custom fields to create the record.⁷

Start tracking at the lead stage so referred pipeline stays visible before a deal closes.⁸ Record who sent the referral, the referral source, and the account that should carry the relationship. Log the referred title in the record.⁹ When one person refers you to another, record that referral at the account level.¹⁰

Use code names that you can identify later, such as a campaign or partner label.¹¹ Add UTM parameters alongside the referral code when you need campaign detail.¹² Keep the reporting responsibilities separate: the referral report tracks the ref code, while external analytics handles the UTM data.¹³

Route and validate the record

Routing turns an attribution field into usable pipeline. Give each referral a review step and keep accepted, rejected, misrouted, and returned referrals visible.

Assign a referral coordinator to review each referral for qualification and record the decision.¹⁴ Track misrouted referrals and referrals returned by other teams in the inventory.¹⁵ This helps you find routing failures instead of treating missing pipeline as a source problem.

Test the handoff before putting the process into regular use. Transition and implementation of the controls matter for reliable referral intake and routing reports.¹⁶ Check whether the referral was accepted, where it was sent, and what happened after the handoff. Every incoming referral should have a recorded status and a visible next action.

Follow the referral to the outcome

Keep the referral source attached as the opportunity moves through qualification, sale, and onboarding. The source record should explain both pipeline creation and the quality of what arrived.

Tracking the full lifecycle from referral through onboarding completion lets you measure whether the program produces the predicted retention lift.¹⁷ You can then see whether the customers or accounts it creates reach the outcome your program promised, rather than just count introductions.

Add a Referral LTV field to the original referrer's contact as a rollup or calculated field.¹⁸ It can sum every deal value where Referred By names that person and update whenever a referred deal closes.¹⁹

Review speed and downstream value by source. A source that creates many early-stage leads may call for a different decision from one that produces fewer leads with stronger progression. The record should be traceable from the referral source to the outcome that matters for your program.

Report contribution and reward

Build the report around decisions, including where to invest and what reward the economics can support, rather than activity counts that stop at the first handoff.

Analyzing referral-program results enables you to calculate return on investment and the upper bound for the reward.²⁰ Report the source, pipeline stage, outcome, collected revenue, and referral LTV so the same record supports attribution and reward decisions.

An attribution model tells partners what their contribution is worth. That affects the time and content they put into the program and whether they choose to promote it.²¹ Make the result visible to the people who send referrals. Teams can adjust targets by reviewing referral buckets.²²

Report back to the person who referred you throughout the process.²³ When referred people become clients, tell the referrer what work is being done.²⁴ This strengthens the relationship and helps the referrer understand what fits.²⁵

What not to do

• Wait until a deal closes to record the referral source. Referral tracking should begin at the lead stage.⁸
• Leave the referred title out of the record.⁹
• Treat a code missing from the report as proof that nobody used it. Codes with no visits do not appear in the report.²⁶
• Assume every code in the report came from your own setup. Other organizations can introduce codes through shared links.²⁷
• Judge the program from referral-page conversion alone. Referral contribution against the full business is a harder test.²⁸
• Keep referral performance invisible to the referrer. Visibility of the score changes behavior.²⁹