Why does the checker reload the page?

Because repeat firing is the single most common way Google Ads conversion counts get inflated. A refresh is the safest way to see whether the tag fires again without a new purchase or lead.

Can it see conversions imported from my CRM or sent server-side?

No. Offline imports, enhanced conversions for leads uploads and server-side tagging never pass through the visitor's browser, so a browser scan cannot observe them. The result says so explicitly rather than reporting them as missing.

The public page where the conversion is expected to fire, usually a thank-you or order-confirmation page. If that page requires a session or order token to load, the scan may only see the empty state; use a public test confirmation page if you have one.

Is a conversion without transaction ID always wrong?

For lead forms it is common and acceptable. For purchases it is a problem, because Google Ads can only deduplicate repeat conversions when the same transaction ID is sent.

The checker found two accounts. Which one is right?

Whichever account your campaigns run in. The account and conversion action IDs in the report match the IDs in Google Ads under Goals → Conversions, so you can identify and remove the stale one.

Does this test Google Ads Enhanced Conversions?

Only indirectly. Use the Enhanced Conversions Readiness Checker to see whether user-data markers are present on the conversion request.

Free tool by Clarvivo · no login

Check the Google Ads conversion your browser actually sends

Inspect the public confirmation page for Google Ads conversion beacons, their IDs and values, and the duplicate triggers that make paid reporting unreliable.

Conversion or confirmation page

Use the public page where the completed lead or order fires. We inspect browser-side Google Ads conversion requests and reload once to catch repeat firing.

This tool answers: Does my Google Ads conversion fire once with the value and order ID it needs?

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

Why this happens

Google Ads optimises toward whatever your conversion tag tells it. If the tag fires twice, misses the value, or reports a different conversion action from the one your bidding uses, Smart Bidding learns from the wrong signal and spends accordingly. None of that shows up as an error in the account; it shows up as a cost per acquisition that slowly stops making sense.

The most common failures are small. A confirmation page that fires the conversion on every reload. Two Google Ads accounts left on the page after an agency change. A purchase conversion without transaction_id, so Google cannot deduplicate it. A value of zero because the template variable was renamed. Each of these is visible in the request the browser sends, if you know which request to look at.

This checker loads the page where your conversion should fire, captures the Google Ads conversion requests the browser actually sends, and reloads once to see whether the same conversion fires again. It answers the narrow question your bidding depends on: does one completed action produce exactly one conversion with the data Google needs?

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.

We load your confirmation page in a real browser
The scan opens the public URL in an isolated Chromium session and records every request to Google Ads conversion endpoints, including gtag.js and Google Tag Manager-fired conversions. Nothing is submitted and no checkout is started.
We read each conversion request's parameters
For every Google Ads conversion beacon we extract the conversion account and conversion action IDs from the request path, plus the value, currency and transaction ID parameters. Missing or empty values are reported per conversion, not averaged away.
We count accounts and conversion actions
More than one Google Ads account or several conversion actions firing on one page is a common leftover from agency handovers and template copies. We list every account and action ID we saw so you can match them against the conversion actions your campaigns actually optimise for.
We reload once to catch repeat firing
After the first load settles we refresh the page and record whether the conversion fires again. A conversion that fires on reload will be counted again for every returning visit to the page unless a transaction ID lets Google deduplicate it.

Common causes and fixes

The conversion fires on every page load: Tags triggered by a page view of the confirmation URL fire on refresh, on back-button returns and when customers revisit the order page from an email. Fire the conversion from the purchase or lead success event, and send a transaction ID so repeats are deduplicated.
No transaction ID on purchase conversions: Without transaction_id Google Ads has no way to recognise the same order twice. Pass the order number from your checkout or form system, exactly as it appears in your back office.
Value or currency missing: A purchase conversion without a value makes value-based bidding blind, and a value without currency is interpreted in the account currency. Map value and currency from the order data layer, not from a static tag field.
Two Google Ads accounts on one page: After an agency change or account migration, old conversion tags often stay live. Each account counts the conversion separately, which is harmless only if nobody reads both. Remove tags for accounts you no longer use.
The wrong conversion action fires: Templates are copied between sites and funnels. If the action ID on the page is not the one set as primary in your campaign goals, bidding never sees these conversions. Compare the action IDs we report with the conversion actions in your account.

Frequently asked questions

Why does the checker reload the page?: Because repeat firing is the single most common way Google Ads conversion counts get inflated. A refresh is the safest way to see whether the tag fires again without a new purchase or lead.
Can it see conversions imported from my CRM or sent server-side?: No. Offline imports, enhanced conversions for leads uploads and server-side tagging never pass through the visitor's browser, so a browser scan cannot observe them. The result says so explicitly rather than reporting them as missing.
What should I paste?: The public page where the conversion is expected to fire, usually a thank-you or order-confirmation page. If that page requires a session or order token to load, the scan may only see the empty state; use a public test confirmation page if you have one.
Is a conversion without transaction ID always wrong?: For lead forms it is common and acceptable. For purchases it is a problem, because Google Ads can only deduplicate repeat conversions when the same transaction ID is sent.
The checker found two accounts. Which one is right?: Whichever account your campaigns run in. The account and conversion action IDs in the report match the IDs in Google Ads under Goals → Conversions, so you can identify and remove the stale one.
Does this test Google Ads Enhanced Conversions?: Only indirectly. Use the Enhanced Conversions Readiness Checker to see whether user-data markers are present on the conversion request.

A conversion is useful only when it maps to revenue.

Clarvivo connects paid acquisition with payment truth so a valid tag is not mistaken for a valid ROAS number.

Connect Google Ads to real revenue

What this tool reads, and what it keeps

We load the public URL in an isolated browser and inspect public document and tracking signals.
We do not log in, submit forms, complete checkout, or retain a page recording.
Redacted diagnostic evidence is retained for 7 days, then deleted.