Job conversion-paid-ads-tags-verified-with-test-conversion · revised 11 October 2026
Prove your Google Ads and Meta conversion tags each fire once on a test conversion
One test conversion fires your Google Ads and Meta conversion tags once each with the agreed value and currency, read in Tag Assistant and Meta Test Events; the Ads status is recorded as it stands.
You might be seeing
- The Google Ads conversion action reports as unverified or inactive while enquiries still come in
- Meta Events Manager shows no conversion event from the site, or shows a Purchase without a value
No passwords, keys, card details or admin invites needed to start.
What usually happened
The conversion tag on the confirmation step is not firing once, in the right place, with the right parameters. Google Ads needs the tag and its ad click information to survive to the conversion page, and, when each conversion has its own value, Google says the value and its currency must be passed to the event snippet at runtime. Meta marks value as required for a Purchase event and describes currency as the currency for that value. A tag that fires on every page, twice, without value, or before consent, produces a count that cannot be trusted.
Who it’s for: A small business or agency that spends on Google Ads or Meta and does not trust the conversion counts in either platform.
Usually starts when: Conversion status is Unverified or inactive, counts differ greatly from real enquiries or orders, or a site change happened since the tags last worked.
The result: A single test conversion makes the Google Ads conversion tag fire exactly once, shown in Tag Assistant with the agreed value and currency, and makes one Meta event with the agreed name, value and currency appear in Meta's Test Events tool. The conversion linker is in place where required, reloading the confirmation page fires neither tag again, and the Google Ads conversion status is recorded as it stands, not claimed as proof.
Check whether this job fits
Answer these without sharing account IDs or customer data.
Checks you can run yourself
Look at the tag firing on the thank-you step
Use Tag Assistant for Google tags and Meta Ads Data Advisor (formerly Meta Pixel Helper) for the Pixel, then perform the action once.
Look for: Count how many times each conversion tag fires, and whether the Meta event carries a value and currency.
What you get
- A tag-by-tag check table: trigger, parameters, consent settings, linker, once-per-conversion guard, result
- The repaired tags prepared in a workspace
- Screenshots of the test conversion in Tag Assistant, Meta Ads Data Advisor (formerly Meta Pixel Helper) and Test Events, and a note on the Google Ads status shown
Included
- One site, one Google Ads conversion action and one Meta standard event (for example Purchase)
- Check tag, trigger, conversion linker, value and currency, and consent settings for those two tags
- Repair the tags in a Tag Manager workspace for your approval, with a once-per-conversion guard so reloading the confirmation page does not fire either tag again
- Run one test conversion and read it in Tag Assistant, Meta Ads Data Advisor (formerly Meta Pixel Helper) and Meta Test Events
Not included
- Changing campaigns, bids, budgets, audiences or creative
- Server-side events and the Meta Conversions API, which is separate scope
- Reconciling platform conversion counts with revenue or deciding which platform is right
- Offline conversion imports and call tracking
- Any promise about ad performance, revenue or rankings
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
One test conversion makes the Google Ads conversion tag fire exactly once in Tag Assistant, the conversion value and currency the tag passes match the agreed ones (read from the tag's details in preview and checked against its configuration in the workspace), and the conversion linker is present where the tag setup requires it.
Evidence: Tag Assistant summary showing a single firing of the conversion tag and the linker, and the tag's value and currency as passed and as configured.
The same test conversion makes the Meta event fire exactly once in Meta Ads Data Advisor (formerly Meta Pixel Helper), carrying the agreed event name and, for Purchase, a value and currency, and Meta Test Events lists it.
Evidence: Data Advisor and Test Events screenshots with the event name, value and currency.
Repeating the test with the confirmation page reloaded does not add a second firing of either tag, because of the once-per-conversion guard.
Evidence: Tag Assistant and Data Advisor counts across the reload.
Sign-off. You inspect the three test results, sign off in writing and publish yourself. Payment follows sign-off.
If it fails. If the test conversion does not pass, you do not pay for this fixed scope. The Google Ads status is recorded as it stands: Google sets Active only after its first recorded conversion or a successful test event, so a status that has not changed yet is not a pass condition and is not claimed as proof.
When it fits, and when we stop
It fits when
- You can perform one test conversion on the live site or staging without a real charge or a real customer contact
- You hold the Google Ads and Meta accounts and can grant a scoped role to the identity we agree with you before work starts
- The site uses Tag Manager or has tags we can reach through an agreed route
- The confirmation step shows something Tag Manager can guard on, such as an order or enquiry ID, so a reload can be told from the first view
We stop and tell you if
- The only way to convert is a live payment you will not make or refund
- The conversion happens on a third-party domain we cannot reach
- Account ownership of Ads or Meta is disputed
- The confirmation page cannot tell a first view from a reload and you will not have it changed
What could go wrong
Your publish records the changes as a Tag Manager version; republish the earlier version to undo them. We make no changes inside Ads or Meta campaigns.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| Test events are counted by the platform as real activity. | Tests are recorded with time and a test marker in the handover, and we assume the platforms may count a test conversion as real activity. |
| Fixing one platform double-counts the conversion in another. | The test conversion is read in each tool and must show one firing per tag. |
A separate reviewer checks the firing counts and parameters, and that no test conversion was left in a live campaign optimisation without being noted. You publish under your own account.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the conversion, the platforms, the test route and the access route in writing
- Record the current behaviour of both tags on one test conversion
- Check trigger, linker, value, currency, and consent settings against the documentation
- Repair the tags and add the once-per-conversion guard in a workspace; re-test in preview and on the live site after you publish
- Read the result in Tag Assistant, Meta Ads Data Advisor (formerly Meta Pixel Helper) and Meta Test Events, and record the Google Ads status as shown
- Independent review, then hand over for you to publish
This is a one-off job, not a subscription or emergency cover. We confirm eligibility, the price, a start window and a delivery date before you accept. Work starts only after the agreed inputs and the least access the job needs are in place. Fees charged by Google, Meta, your host or any tool you use are not included. No charge or booking is created by an enquiry.
Need to keep it working?
A standing monthly check can repeat a test conversion and compare platform counts to enquiries.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Google describes conversion tracking and the Active, Unverified and Inactive statuses on its Ads help page. support.google.com
- Meta Ads Data Advisor (formerly Meta Pixel Helper) is a free Chrome extension that shows which Pixel events a page fired, and Meta's Test Events tool in Events Manager is where Meta suggests checking that events are visible. developers.facebook.com
Questions
Will this improve my ad results?
We make no promise about results. The job proves that each tag records a test conversion once with the right parameters.
Do you change my campaigns?
No. We do not change campaigns, bids or budgets.
Send an enquiry
Send us
- The conversion you care about, such as a purchase or an enquiry, and the page or step where it happens
- Whether the Google Ads conversion status is Active, Unverified or Inactive, and the last date you trusted the count
- No logins, no account IDs, no customer details.
Later, once you agree
- A scoped role on Google Ads and Meta Events Manager, and Edit access to the Tag Manager container (Google describes Edit as able to create workspaces and make edits but not create versions or publish; you publish), granted to the identity we agree with you before work starts
- A safe test route for the conversion
- Your named person to publish
You own the website, the Google and Meta accounts, the tag manager container and all the data. We ask for the lowest role that lets us do the job. Before any work starts we agree with you in writing which identity receives that role; you grant it and can remove it at any time. We never ask for your passwords. You keep the right to publish: we prepare changes and you publish them.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “conversion-paid-ads-tags-verified-with-test-conversion” as the subject.