A useful lead-source report needs a traceable path from the campaign link to the business record and the reporting view. Adding UTM parameters is one step. We also need to understand whether the landing page receives them, how source fields are saved, which action counts as a lead and which attribution question the report answers.
This guide covers source information in an existing lead journey. The worksheet and worked example are planning tools. Account-specific conclusions require evidence from your setup.
In this guide
- Give each source field a clear job
- Keep Google Ads auto-tagging in view
- Check the journey from link to accepted lead
- Define source capture before adding hidden fields
- Complete a source-to-record worksheet
- Worked example: a source field disappears before reporting
- Compare like-for-like reporting views
- Turn the evidence into a focused next step
Give each source field a clear job
Google's campaign URL guidance describes UTM parameters as labels for incoming campaign traffic. Source identifies the origin, medium describes the channel and campaign groups a marketing effort. Content can distinguish creative variations. Values are case-sensitive, so consistent naming matters.
Start with a short naming register that someone else can apply without guessing. Keep campaign names understandable, stable and free of customer details. If your team renames campaigns regularly, document a stable campaign ID alongside the display name.
| Field | Illustrative value | Team rule |
|---|---|---|
| utm_source | partner_newsletter | Use the same label for this external sender |
| utm_medium | Use the agreed channel label | |
| utm_campaign | autumn_consultation | Identify the initiative consistently |
| utm_content | footer_link | Distinguish this placement from the main link |
Google recommends including source, medium and campaign together, plus other relevant parameters. A partially tagged link can leave reporting fields unavailable. Confirm how your chosen labels fit the channel definitions you actually report on; a tidy naming register alone does not validate channel classification.
Keep Google Ads auto-tagging in view
For a linked Google Ads setup, Google recommends auto-tagging for detailed Google Ads reporting. Review the existing configuration before replacing it with manual labels. A hand-built UTM link and an auto-tagged ad click do not provide identical evidence.
When manual and auto-tagging are both present, Google's traffic-source documentation explains their precedence and fallback behavior. Auto-tagged values generally supply traffic classification, while manually supplied content and term can populate their manual dimensions. If the click identifier cannot be used as intended, incomplete UTM values can become particularly important. Preserve the approved setup and investigate the actual link rather than inferring behavior from a campaign name.
Check the journey from link to accepted lead
- Record the published destination, including the approved campaign labels. Note where the link is configured and who maintains it.
- Follow the real navigation path in a permitted test. Record redirects and the final landing address without exposing customer information.
- Check whether the intended measurement receives the landing-page information under the test's consent state.
- Identify when the business accepts the submission and where any source fields are written.
- Compare the stored record with the relevant reporting dimensions after normal processing.
Redirects deserve their own evidence. Google's sitewide-tagging troubleshooting guidance calls out redirects that remove click identifiers. Review parameter handling with the website owner instead of assuming every short link or redirect preserves it.
Use campaign tags on external acquisition links. For a move from your own landing page to your own form, measure the navigation as an interaction rather than inventing a fresh acquisition campaign. Google notes that a newly encountered campaign does not start a new GA4 session; adding internal UTMs can still complicate event-level attribution and later interpretation.
Define source capture before adding hidden fields
A hidden form field is simply an input that visitors do not normally see. It needs a defined capture rule, a permitted storage mechanism and a reliable mapping to the final record. Its presence does not establish that it contains the original source.
For first-touch fields, specify the first eligible observation your system can actually retain. For latest-touch fields, specify what updates them and whether an untagged visit should overwrite an existing value. Keep capture time and field meaning clear. A CRM field called “source” might otherwise mix campaign labels, staff-entered referrals and imports.
For this review, our recommended URL rule is simple: keep names, email addresses, phone numbers, customer notes and other personal data out of UTMs. Google specifically warns against personal information in URLs and campaign dimensions. Store necessary business records through suitable private systems, with appropriate permissions and consent handling.
Complete a source-to-record worksheet
| Review point | Record your decision | Evidence to retain |
|---|---|---|
| Acquisition link | Approved source, medium, campaign and owner | Sanitized published link and configuration date |
| Arrival | Redirects and intended landing page | Permitted test path and observed parameters |
| Capture rule | First or latest eligible touch; overwrite rule | Field mapping and capture timestamp |
| Business event | Accepted inquiry, qualified lead or sale | Stage definition and system of record |
| Reporting view | Property, date range, time zone and scope | Exact dimension and metric names |
| Exceptions | Unknown, unavailable, test or repeat | Reason and owner of the next check |
Use separate exception labels when the evidence supports them. “No campaign parameter observed” and “field mapping failed” point to different next actions. An empty field by itself cannot tell you which happened.
Worked example: a source field disappears before reporting
This example is illustrative and uses invented observations. It is not a client result or a platform test.
Imagine an inquiry campaign with 18 accepted records in an agreed period. Fifteen records contain the approved campaign label; three contain an empty source field. The reporting team initially groups all three as direct traffic.
The worksheet changes the investigation. An existing, appropriately retained submission log shows that one of the three reached the form with a source value, but the CRM mapping omitted it. For the other two, there is no retained arrival evidence. The team now has one supported mapping issue and two unresolved records.
The next step is to verify and repair the mapping through a separately agreed implementation task. The two unknown records remain unknown unless reliable evidence becomes available. Adding a hidden field today does not recover historical source information that was never captured. Even the supported CRM correction does not automatically rewrite historical GA4 attribution.
Compare like-for-like reporting views
GA4 distinguishes first-user, session and event-scoped source dimensions. First-user source concerns acquisition of the user; session source concerns the session; event-scoped attribution distributes credit for key events. A saved CRM source field follows your own capture rule. Treat these as different definitions before comparing totals.
Keep collection evidence separate from the campaign-credit question. Our safe test guide explains how to plan an observation without treating one visible event as proof of the entire journey.
Also separate source continuity from journey continuity. If the user leaves for a booking or payment domain, use our cross-domain handoff guide. To clarify the counted outcome, read form submissions and qualified leads; for mismatched platform totals, read Google Ads and GA4 conversion differences.
Turn the evidence into a focused next step
Our US$195 one-time conversion tracking diagnostic reviews one existing website or funnel journey, one selected ad platform/account, one GA4 property where relevant and up to three agreed events. We deliver evidence and priorities. Implementation, new integrations, CRO and ad management are separate.