Record the referral source at intake, keep it in the same field, and carry it through the sales process. Most practices already have a referral source field.1 Across the behavioral health practices HireGaynell supports, two or three sources typically drive more than 70% of new clients.2 That concentration makes capture quality a commercial issue because a blank or messy field can direct attention to a weaker source.
Capture at intake
Capture the source during intake, before the first conversation is forgotten and while the contact is still available. Ask "How did you hear about us?" in a form field.3 Store the answer in a single source field,4 use that field for every new contact, and keep the available source labels consistent across the team.
If the answer points to a person, ask "Who sent you this referral?".5 Record that person in a contact field when the referrer or prospect identifies who made the introduction.6
Separate the route from the person
The source tells you how the contact arrived. The referrer tells you who created the introduction. Keep both in the record so the report can show channel performance and give you a person to follow up with.
Referral source tracking answers where every dollar of new revenue originated.7 Use the source after intake to compare contacts that became customers with those that did not.
Tracking can show where customers came from, which platform converted them, and who referred them.8 Keep those outcomes attached to the same record. When a referral arrives, contact the referral source and provide updates during the sales process, including when the referred person does not become a client.9
Keep web referrals in their lane
Web analytics and person-level referral capture answer different questions. Web data shows the route, while the intake record preserves the person who made the referral.
A referral is traffic that arrives through another source, such as a link on a third-party domain.10 Analytics identifies the domain that sent traffic immediately before the visit and displays it as a referral source in reports.11 Google Analytics shows the websites that sent visitors. A separate record is needed to identify the customer who sent a friend.12
If domains in your own workflow should not count as referral sources, create conditions for those domains.13 The conditions are evaluated on every web page that has the Google tag.14 A third-party payment processor can create this problem when a user returns to the site after checkout.15
When a configured condition matches, Analytics appends ignore_referrer=true to the matching event.16 That parameter tells Analytics to leave the referrer out of the traffic source.17 Keep this cleanup separate from the intake question. Removing a technical referral domain does not identify the person who referred the contact.
Review the report
Review the record on a fixed cadence. A monthly check is enough to catch missing entries, label drift, and sources that appear busy without producing customers.
Review a referral report monthly.4 A tracked system gives you source-specific client counts.18 Use those counts to decide where to spend marketing budget, which referral relationships to nurture, and whether paid channels produce paying clients or only clicks.19
Keep the review focused on productive sources and appropriate follow-up. The report should change who you contact and where you spend attention, rather than become a separate administrative project.
What not to do
- Keep the source field populated, use consistent source names, and review the report. One reported pattern found the field empty on 60 to 70% of charts, the source names inconsistent, and the report not reviewed.20
- Use source-specific counts instead of a general impression. A general sense cannot show which sources produced each client.21
- Count referrals from every channel, including printed cards and text messages, to avoid under-crediting advocates who refer offline.22
- Prioritize productive sources and appropriate follow-up over documenting every interaction.23
- Treat the work as operational. Having tracking software does not by itself provide the answer, because the gap between the tool and the answer is operational.24