Contact Data
Part of CRM for relationship-led businesses
Recording referral sources accurately
Record who introduced an opportunity without confusing a personal referral with web traffic or CRM creation source.
Record who introduced a particular enquiry or opportunity when that is known. Keep the business introduction separate from website traffic attribution and from how a CRM record was created. These three values can differ for the same customer, so a field labelled “referral” needs a clear meaning before it is used in a report.
Decide which source question matters
| Question | Example answer | Where to record it |
|---|---|---|
| Who introduced this work? | An existing customer, confirmed by the prospect | Referral details on the enquiry or opportunity |
| How did a person reach the website? | A referring website | A tracked traffic-source field, if available |
| How was the CRM record created? | An import | The CRM’s creation-source field |
These are different events. Someone may visit through search after a personal introduction. The web visit does not disprove the introduction, and the introduction does not change how the record was created.
Capture the introduction on the work it brought in
When an existing customer introduces a new prospect or project, record the introduction on the resulting enquiry or opportunity. An account-wide “referred by” value can mislead if later work comes through someone else. Record the referring party and how the team learned of the introduction when those details are known and appropriate to keep.
Use a small, defined set of categories with an honest “unknown” option. Store a specific person or organisation separately where the CRM and the organisation’s information-handling rules permit it. Mark a reported introduction as unconfirmed until checked. If two parties contributed, agree whether the report credits both or uses one primary source with a note.
An illustrative entry: “Prospect confirmed on the first call that the operations manager at an existing customer made the introduction.” “Word of mouth” alone does not identify who introduced this opportunity or how the team knows.
Avoid software-field confusion
HubSpot’s Original and Latest Traffic Source properties describe known contact interactions; their Referrals category can identify a referring website domain and URL. Those properties can also be edited on a contact, and tracking may be incomplete, so the category alone does not prove a named personal introduction.
Associated company and deal traffic-source properties mirror contact values. HubSpot’s Record Source instead describes how a record was created, including offline methods.
Pipedrive distinguishes a system-generated source origin from editable source channel fields on leads and deals. Its documentation describes source channel as the sales or marketing tool that added the data, not a verified person who introduced a customer.
Keep a personal-referral definition separate from those creation and tool fields. Pipedrive also says editing or deleting a source-channel option affects existing records, so inspect its current use before changing it.
Report what the field can support
Define the population and period before counting referrals: enquiries received, opportunities opened or deals won answer different questions. Review a sample against its supporting note or confirmation. Show unknown and unconfirmed entries rather than silently treating them as verified referrals.
A useful referral report lets a reader identify the work item, the referring party when known, and the evidence behind the classification. Keep any recognition or payment decision separate from an unverified CRM label.
