To pass UTM parameters into a CRM, read source, medium and campaign from the landing URL, preserve them through later page views, submit them in hidden or integration fields, map them to dedicated CRM properties, and test the exact lead through opportunity creation.
What are UTM parameters?
UTM parameters are campaign labels added to a link. utm_source names the platform or referrer, utm_medium names the channel, and utm_campaign names the marketing effort. utm_term and utm_content can add keyword or creative detail.
Google Analytics uses those values to classify traffic. That is the website-reporting layer. The CRM needs its own durable fields if the business wants to connect the campaign to an identifiable lead, opportunity, and sale.
Standardize the campaign names first
Decide how source, medium, and campaign values will be written before adding automation. facebook, Facebook, and fb may create three report rows for one platform. Keep the standard short, documented, and owned.
Capture the landing values
Read the parameters when the visitor first arrives. Redirects, link shorteners, consent behavior, and landing-page builders can remove or delay values, so inspect the final loaded URL and the page data—not only the ad setup.
Google Ads may add a GCLID through auto-tagging. If offline outcomes will be returned to Google Ads, that click identifier must be captured and stored with the lead as well.
Preserve source across pages
A visitor may land on one page and submit a form on another. Preserve the original campaign in an appropriate first-party mechanism that follows your consent and retention rules. Do not put personal information in the campaign URL.
Keep original source and latest source separate. A later direct visit or email click should not silently replace the campaign that created the relationship.
Send the values with the lead
Hidden fields are a common form method: one field for each UTM value, connected to a CRM property. A webhook or native integration can carry the same data in its payload. Whatever the method, inspect the submitted payload and receiving record rather than assuming matching field names are enough.
Third-party schedulers, chat tools, iframes, and cross-domain forms may require their own parameter forwarding or integration mapping.
Map the CRM fields explicitly
Create clear properties for source, medium, campaign, landing page, and captured time. Map the form or integration fields to those properties and decide which fields are write-once, which may update, and what happens during duplicate merges or imports.
HubSpot distinguishes traffic-source properties from record-source properties, and hidden form fields can write URL values to contact properties. Salesforce Account Engagement can populate source from utm_source in supported setups. Zoho Forms requires CRM fields and integration mapping for the UTM values. Provider defaults differ, so verify the exact record.
Carry source into opportunity and revenue
A lead-level campaign is not closed-revenue attribution until the opportunity keeps a durable relationship to that lead or copies the governed source fields. Confirm the same opportunity retains the source after conversion, reassignment, merge, and stage changes.
Run one controlled test
- Open a tagged link in a clean, consent-valid session.
- Confirm the final landing page still has the expected values.
- Move to the real form or booking path.
- Submit governed test data.
- Inspect the form or integration payload.
- Find the exact CRM record and source fields.
- Create or inspect the linked opportunity.
- Verify original and latest source behavior.
Audit before you trust the report
Map the source handoff in minutes.
The UTM-to-CRM Attribution Audit identifies where campaign data is captured, persisted, mapped, assumed, or lost.