Clarvivo

Free tool by Clarvivo · no login

Check whether campaign context can reach your CRM form

Inspect a public campaign landing page for attribution fields, storage, and the form handoff—without entering data or creating a lead.

Campaign form URL

Paste a public campaign URL that leads to your CRM form. We inspect public form fields and attribution storage without entering or submitting a lead.

This tool answers: Can this campaign's UTM and click-ID context reach my CRM form?

Enable JavaScript to run the check — the diagnosis itself is free and needs no account.

Why this happens

Your CRM is where leads become revenue, so it's where campaign attribution matters most. But most CRM records don't know which campaign produced them. The UTMs and click IDs were in the landing URL, and somewhere between that page and the form submission they were dropped.

It usually happens in one of three places. The form has no hidden fields for campaign data. The visitor browsed to another page before converting, and nobody stored the parameters. Or the form is an embed in an iframe that can't see the parent page's URL at all.

This checker follows your campaign URL to the form and reports whether the campaign identifiers are still there, whether the form has somewhere to put them, and whether they were stored for later.

Next checks

These answer the questions this one tends to raise.

How this check works

So you can trust the result — and your developer can verify it.

  1. Paste a campaign URL that leads to your form

    Include real UTM parameters or a click ID, for example ?utm_source=google&utm_medium=cpc&utm_campaign=demo.

  2. We follow the journey to the form

    The page is loaded in an isolated browser and we check which campaign identifiers survive to the page where the form lives.

  3. We inspect the form fields

    Each CRM-facing form is checked for campaign or click-ID fields. Forms that post to another origin without them, and forms inside iframes, are flagged.

  4. We check attribution storage

    We look for redacted storage keys that hold campaign context (cookies or local storage), which is what lets a visitor browse before converting without losing their source.

Common causes and fixes

No hidden fields
Add hidden inputs for utm_source, utm_medium, utm_campaign and the click IDs you use, populated by a small script on page load.
Parameters not stored on the first page
If the form is on a second page, read the parameters on landing and store them in a first-party cookie or local storage.
Form posts to the CRM without context
Forms that post directly to a CRM endpoint only send what's in the form. If campaign fields aren't there, the CRM never sees them.
Iframe forms can't read the URL
Embedded forms run on the provider's domain. Pass campaign values into the embed through its hidden-field or URL-parameter support.

Frequently asked questions

Does the tool create a lead in my CRM?
No. It never types into or submits a form.
Which identifiers does it look for?
UTM parameters and ad click IDs such as gclid, gbraid, wbraid, fbclid, msclkid, ttclid, li_fat_id and rdt_cid.
Should I store first-touch or last-touch values?
Both if you can. First-touch shows what started the journey; last-touch shows what converted it. Keep them in separate CRM fields.
Why does storage matter if the form has hidden fields?
Hidden fields populated from the current URL are empty if the visitor reached the form from another page. Storage keeps the values across pages.
What should I run next?
If your CRM upload to Google Ads matches poorly, run the Offline Conversion Match-Rate Diagnoser.

Keep lead source tied to the outcome that follows.

Clarvivo connects campaign evidence to downstream revenue so lead capture does not stop at a browser event.

Connect lead sources to revenue

What this tool reads, and what it keeps