Leads · 7 min · 2026-11-07
Where each contact came from: how to keep the source and campaign of every request
Without the source stored on the request, you cannot tell which campaign brings customers. How UTMs get lost and how to carry them to the CRM.
Summary
What matters before moving forward.
- Google Analytics shows where visits come from, but not which contact request came from which campaign or whether that contact became a customer.
- UTM parameters on each campaign link identify source, medium and campaign. Used inconsistently, reports end up with missing or duplicate values.
- UTMs sit in the first page's address. When the visitor navigates to the contact page they are lost, unless the website stores them.
- Storing the first visit's source in hidden form fields carries that information to the CRM, alongside the request.
- With the source in the CRM, you can compare campaigns by customers won, not just clicks or requests.
What Analytics does not answer
Google Analytics answers questions about visits well: how many came from each campaign, which pages they viewed, how long they stayed. It does not answer questions about customers: which ad did this quote request come from? Did this customer who signed come through search or a social post?
For that, the source has to travel with the request to wherever the request is handled, the CRM or the spreadsheet.
UTM parameters done right
UTM parameters add the source, medium and campaign name to each campaign link, for example newsletter, email and autumn-sale. Google's documentation recommends always setting the main ones, because missing parameters show up in reports as not set.
Values are case sensitive. Meta and meta count as different sources. A simple lowercase convention, written in a shared document, avoids reports split into ten variants of the same channel.
Where UTMs get lost
The visitor lands on a page with UTMs in the address, reads, clicks the menu and goes to the contact page. By then the address no longer has the UTMs. If the form only looks at the current page address, it stores an empty source.
The same happens when the visitor comes back days later, directly, to fill in the form. The visit that first brought them no longer shows.
Carrying the source to the form
The fix is for the website to store the first visit's source, the UTMs and landing page, and fill it automatically into hidden form fields. The request then reaches the CRM with the right source, even if the visitor browsed several pages.
You can store both first and last source, because they answer different questions: what brought the person to the brand, and what led them to get in touch.
This storage has to respect the website's cookie and consent rules, and ad click identifiers should be treated as personal data.
Measuring by customers, not clicks
With the source in the CRM, each request can be followed to its outcome: proposal sent, customer won, value. After a few months you can compare campaigns by the value of the customers they brought.
Often the campaign with most clicks is not the one that brings most customers. Without the source on the request, that difference never shows.
How Vokzar stores request sources
We agree a UTM convention for every campaign and configure the website to store first and last visit source, within consent rules.
We pass the source in hidden form fields to the CRM or spreadsheet, alongside each request.
We set up a simple report of requests and customers won by campaign.
Related next steps
Next steps.
Proof and validation
- UTM rules, including case sensitivity and not set values, come from Google Analytics official documentation.
- Storing the source in the browser must respect the cookie policy and visitor consent.
- First or last source attribution is an analysis choice, not a single truth.
Official documentation
Validated sources.
Technical strategy should be auditable. These sources link directly to the official documentation behind this guide.
Frequently asked questions
Common questions about this topic.
Does Google Analytics tell me which campaign brought each customer?
It tells you where visits came from, but does not link each contact request to a campaign or say whether it became a customer. For that, the source has to go with the request to the CRM.
Why do my reports have duplicate sources?
Because UTM values are case sensitive and may be written differently. A lowercase convention fixes it.
Why does the form store an empty source?
Because the UTMs were on the first page and were lost when the visitor navigated. The website has to store the first visit's source and pass it to the form.
Can I store ad click identifiers?
Yes, within the website's consent rules, treating them as personal data.

