Analytics attribution and CRM attribution answer different questions
Analytics attribution
Where did the visit or measured conversion event originate?
CRM and revenue attribution
Which source produced this actual lead, opportunity, and sale?
A conversion event is useful evidence that something happened in the browser. It does not prove the campaign values reached the lead record, remained intact through opportunity creation, or stayed associated with closed revenue.
What are UTM parameters?
UTM parameters are names added to a campaign URL. utm_source identifies the platform or referrer, utm_medium describes the channel, and utm_campaign names the marketing effort. Term and content fields can add keyword or creative detail.
Use a consistent naming standard. Small spelling or capitalization changes can split one campaign into multiple report rows.
How do UTMs reach a form and CRM?
The landing page reads the parameters, preserves them if the visitor moves to another page, and submits them with the form or integration payload. Hidden fields are a common method. The integration then maps those values to CRM properties rather than leaving them only in analytics.
Calls, chats, and third-party booking tools need their own source handoff. A booking link that crosses domains or a call-tracking number can preserve attribution differently from a website form.
First touch, latest touch, and overwrite risk
Original source answers how the relationship began. Latest source answers what brought the person back most recently. One field should not silently serve both jobs. A direct return visit, email click, duplicate merge, import, or workflow update can overwrite the campaign that actually created the opportunity.
Common attribution failure patterns
- A redirect removes campaign parameters before the landing page loads.
- The analytics tag sees UTMs, but the form has no source fields.
- The form submits values that the integration does not map.
- The CRM stores a source on the lead but not the opportunity.
- A later touch overwrites the original campaign.
- Closed revenue sits in a separate system with no durable join to the lead.
- Google Ads auto-tagging is present, but the click identifier is not stored with the lead.
Verify with one controlled path
Open a tagged link, confirm the landing values, complete the real public lead method, inspect the raw receiving record, verify source and campaign fields, then follow the same record into the opportunity and outcome. Compare exact identifiers and timestamps instead of matching totals by eye.
For the detailed setup, see how to pass UTM parameters into a CRM. If the source is blank or wrong, use the lead-source troubleshooting guide. If reports disagree, reconcile analytics conversions with CRM leads.
Related AvertSignal tools
Use the Lead Tracking & Revenue Path Map to document the whole customer path. Use the CRM Lead Delivery Troubleshooter when the record itself is missing. Use this audit when the lead arrives but its source does not survive.
Frequently asked questions
How do I track UTM parameters in my CRM?
Capture source, medium, and campaign from the landing URL; preserve them across pages; submit them with the lead; map them to CRM fields; and verify they remain on the opportunity and outcome.
Why is my CRM lead source missing?
Common causes are missing tags, stripped parameters, absent hidden fields, field-name mismatches, failed mappings, duplicate behavior, and source-overwrite automation.
Does a high completeness score prove accurate attribution?
No. The score only shows how many stages have affirmative evidence in this self-audit. Accuracy still requires a controlled end-to-end test and consistent field definitions.