Clarvivo

Free tool by Clarvivo · no login

Check whether your lead form can produce trustworthy conversions

Paste the public page that contains your form. We inventory the form structure and the tags that fire during a safe browser visit, then separate what the page proves from what needs a controlled test submission.

Public form page

Paste the page that contains your lead form. We inspect its safe, public structure and the tracking requests that fire while the page loads; we never submit a form or send test leads.

This tool answers: Is this form set up to record a real submission instead of a click or validation error?

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

Why this happens

A lead form can look perfectly normal while the conversion behind it measures the wrong thing. The tag might fire on a button click rather than a successful submission, on page load, or on a thank-you URL anyone can revisit. Ad platforms then optimise for attempts, validation errors and repeat visits instead of real leads.

The second failure is quieter. The form submits fine, the lead lands in the CRM, but nothing on the form captures where the visitor came from. UTMs and click IDs disappear between the landing page and the submission, so the CRM record says nothing about the campaign that paid for it, and offline conversion imports have no click ID to match.

A public scanner cannot responsibly submit an unknown form: it might create a sales lead, trigger an email, or start a workflow. This tool is useful because it audits everything that can be seen without submitting, and is explicit about the one thing it cannot prove: that a real submission fires a real conversion.

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. We find every form on the page

    The scan loads the public page and inventories each HTML form: its action URL, method, submit controls and named fields. Forms inside iframes are flagged separately, because the parent page usually cannot see what happens inside them.

  2. We look for attribution fields

    We check whether each form carries hidden fields for UTMs or click IDs (gclid, fbclid, msclkid and similar). A form that posts to another origin, such as a CRM or form provider, without those fields will lose the campaign context.

  3. We record conversion beacons during page load

    Any conversion request that fires before anyone has submitted anything is reported. A Lead or conversion event on page load means reporting starts before the business event exists.

  4. We never submit

    No field is typed into and no form is posted. The result separates what we observed from what still needs proof with a real test submission.

Common causes and fixes

The conversion is attached to the submit button
A click is not a successful submission. Client-side validation errors, network failures and double clicks all fire a click-triggered tag while the CRM receives nothing. Trigger the conversion from the success response or the confirmation state.
No attribution fields on the form
UTMs and click IDs usually live in the landing URL and vanish on the next navigation. Add hidden fields populated from first-touch storage, or map them server-side, so every lead record carries its source.
A conversion fires on page load
A Lead event on the form page before any submission inflates conversions with every visitor. Move it to the confirmed-success moment.
The form submits with GET
A GET form puts submitted values into the URL, where they end up in analytics, server logs and referrer headers. Switch to POST, especially for anything containing personal data.
The form lives in a third-party iframe
Embedded forms from providers often submit inside their own frame. The parent page cannot fire a reliable conversion unless the provider sends a success message. See the Iframe Form Tracking Checker.

Frequently asked questions

Why doesn't the tool submit the form to test it?
Submitting an unknown form can create real leads, send emails or trigger sales workflows. The scan stays passive and tells you what a single manual test submission still needs to confirm.
What counts as an attribution field?
Hidden or visible inputs named for UTM parameters (utm_source, utm_medium, utm_campaign and so on) or ad click IDs such as gclid, wbraid, gbraid, fbclid, msclkid, ttclid, li_fat_id or rdt_cid.
My form posts to HubSpot or another CRM. Is that a problem?
Not by itself. It's a problem when the form posts to another origin without carrying attribution fields, because the CRM then never sees the campaign context. For HubSpot embeds, also run the HubSpot Form Tracking Checker.
Is a conversion firing on page load always wrong?
For a lead or sign-up conversion, yes. A page_view or view_content event on load is normal; a Lead, Contact or SubmitForm event before submission is not.
How do I confirm the success-based conversion after fixing it?
Submit one real test lead, watch the network requests in your browser's developer tools, and confirm one conversion fires after the success response and none on page load or failed validation.
Does it work for multi-step forms?
It inspects the first public step. Later steps that only appear after input cannot be reached without typing, so check those manually.

A lead only counts when it reaches your business.

Clarvivo keeps campaign, conversion and downstream revenue evidence connected, so a browser event is never mistaken for a qualified lead.

Connect lead sources to revenue

What this tool reads, and what it keeps