TrustedForm conversion tracking: stop Google and Meta counting leads you can't legally call
Google Ads reports a cheap cost per lead, then your dialer team finds part of the batch has no TrustedForm certificate, a certificate whose fingerprint doesn't match the lead, or a bot flag. The ad account counted every one of them the second the form posted. We found no Google Ads, GA4 or Meta Pixel connection in ActiveProspect's docs, so we put the click ID in the same form as xxTrustedFormCertUrl and send a conversion only after the certificate is claimed and passes your checks.
Free30 minutesNo obligation
TrustedForm · what breaks
What goes wrong when TrustedForm sits on your ad landing pages
- 01
Google pays for leads your dialer can't touch
The thank-you page tag fires whether or not a certificate came through. On a medical alert or home warranty campaign that lead goes unworked, yet bidding counts it as a win and buys more of the same traffic.
- 02
Bots look like your best keywords
TrustedForm Insights can stop a bot lead before it reaches your CRM, but nothing in ActiveProspect's docs passes that verdict to Google or Meta. A form-filling script on a mass tort page still shows up in Google Ads as a run of cheap conversions.
- 03
The certificate field and the click ID vanish together
ActiveProspect's docs say the hidden field isn't appended if your form is injected after the Certify script starts, or sits in an iframe without its own copy of the script. Popups and builders that load the form late can hit both limits, and a GCLID field filled the same way breaks with it.
- 04
Every page is its own certificate
TrustedForm creates a new certificate for each page running the script. A debt relief quiz that moves to a second page for the phone number and consent box produces two certificates, and the one your CRM keeps may not be the consent page. The click ID often drops at the same page change.
TrustedForm · the fix
What changes after the fix — TrustedForm
Bidding learns from callable leads
Google and Meta get a conversion once the certificate is claimed and your fingerprint and consent-text checks return success.
Junk traffic traced to the ad that sent it
Leads that fail TrustedForm's bot check or show autofill-only input are matched to the campaign and keyword through the stored click ID, so you can cut placements instead of guessing.
Consent proof and attribution on one record
Each CRM lead carries the certificate URL and click ID side by side, so a compliance pull and a revenue-by-campaign report start from the same row.
TrustedForm · architecture
What TrustedForm actually lets you hook into
Everything below comes from ActiveProspect's documentation. None of it reports to an ad platform, so the ad side is ours to build.
- 1
Certify Web SDK
A script placed before the closing body tag that injects a hidden xxTrustedFormCertUrl field into your form. The field name can be changed.
- 2
Claiming and Retain API
A REST call claims a certificate so you can keep it. The standard claim window is about 72 hours; extended claims of about 90 days are switched on through your account rep, and Retain stores certificates longer for a fee.
- 3
Verify scans and fingerprints
Hashed email and phone values are checked against the certificate, and required or forbidden consent text is scanned for, returning success or failure.
- 4
Insights properties
Documented certificate fields include form_input_method (typing, paste or autofill), event_duration_ms and is_framed, and Insights adds bot detection. We read them at claim time to decide what counts.
- 5
LeadConduit for Facebook Lead Ads
ActiveProspect's Facebook route runs through LeadConduit and attaches ad set and campaign metadata to the certificate. Confirm whether you already use it before we add anything.
TrustedForm · diagnose
Where TrustedForm tracking breaks, in diagnostic order
Start at the form, because a missing certificate field and a missing click ID usually share one cause.
- 01
Check the hidden field in developer tools, not page source
The Certify script appends the field after the page loads, so View Source won't show it. The click ID fields should sit beside it.
- 02
Submit a test lead and open the CRM record
Some builders show the hidden field but never send it on. Both the certificate URL and the GCLID need to land.
- 03
Look for a Content Security Policy block
A strict policy can stop the Certify script or its API calls from loading, which leaves no certificate at all. We check that your policy allows TrustedForm's script and API hosts.
- 04
Compare claimed certificates with reported conversions
Per lead, over a closed week, with bot-flagged and failed-scan certificates split out.
- 05
Confirm the certified page is the consent page
On multi-step funnels, the certified step should hold the consent text within 50 pixels of the submit button, as ActiveProspect advises.
TrustedForm · prove
The QA evidence — TrustedForm
Run on a live lead from an ad-tagged URL on your production form with sandbox mode off, since sandbox certificates can't be claimed.
Source of truth
TrustedForm claimed certificates and their Insights results, joined to your CRM lead records by certificate URL
- A test lead from an ad-tagged URL, with certificate URL and click ID both on the CRM record.
- The certified-lead event sent once, after a successful claim, with the certificate as the event ID.
- A lead without a certificate confirmed absent from Google Ads and Meta.
- A failed fingerprint or consent-text scan confirmed absent from the primary conversion.
- Repeated 30 days later and after any landing page or consent language change.
TrustedForm · free audit
What we check in the free audit
- Check the hidden field in developer tools, not page source
- Submit a test lead and open the CRM record
- Look for a Content Security Policy block
- Compare claimed certificates with reported conversions
- Confirm the certified page is the consent page
Checked against
TrustedForm claimed certificates and their Insights results, joined to your CRM lead records by certificate URL
Free30 minutesNo obligation
TrustedForm · when not to buy
When you don't need this on TrustedForm
If no ad points at your certified forms, or the certificates already arrive clean, there may be nothing for us to build.
- If you buy all your leads from vendors and run no ads of your own, certificate checks matter but click attribution doesn't.
- If nearly every lead already arrives with a valid certificate and no bot flag, a browser conversion on submit is close enough.
- If your only source is Facebook Lead Ads through LeadConduit, a simple CRM-to-Meta lead status feed may be all you need.
- If the only fault is a form loading after the script, moving one line fixes it, and we'll tell you so.
TrustedForm · what we deliver
The event map on a TrustedForm-certified form
Form submitted
Browser signal with the certificate URL present, kept as a secondary action that doesn't steer bidding.
Certificate claimed
Logged when your Retain call or LeadConduit step succeeds inside the claim window, keyed on the certificate.
Certified lead
The primary conversion: claimed, fingerprints matched to the lead's email or phone, required consent text found, no bot flag.
Contacted or qualified
Sent from your CRM or dialer disposition, for example a completed intake call for a mass tort claim.
Sale or signed case
A sold warranty plan, an activated alert device or a signed retainer, valued from your records.
Excluded
Leads with no certificate, failed scans, bot flags, sandbox certificates and your own test fills.
Written guarantee
95%+ tracking accuracy
Measured against TrustedForm claimed certificates and their Insights results, joined to your CRM lead records by certificate URL. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
TrustedForm questions, answered
Not that we found in ActiveProspect's docs. They list Facebook Lead Ads and Google Lead Forms as inbound lead sources, but nothing that sends conversions back to an ad account, so that link has to be built.
Your conversion fires on form submit, before anyone checks the certificate. Leads with no certificate, a failed consent scan or a bot flag all count.
It can flag and filter bot leads before they reach your CRM, but that verdict doesn't flow to Google or Meta on its own. We confirm how your account exposes the bot result and use it to hold those leads back from the conversions Google and Meta learn from.
Don't rely on it. The certificate is built to prove consent, so we capture click IDs in your own form fields and store them next to the certificate URL.
Yes, that's the typical setup: an owned landing page, a consent box and a dialer that needs the certificate before calling. The certified lead becomes the conversion; the sale follows from your CRM.
More on TrustedForm
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside TrustedForm, and what their bookings feed
- HIPAAtizerPatients fill out your HIPAAtizer form. Why can't Google Ads tell which clicks became admissions?
- HushmailYour Hushmail intake forms fill up, but Google Ads says no one inquired
- Google FormsWhy can't I track my Google Form in Google Ads or Meta?
- Paubox FormsYour Paubox intake form fills up, but Google Ads says nobody converted
- Canopy ConnectYour ads send prospects to Canopy Connect. Google and Meta never see who finished.
- SmartwaiverSmartwaiver conversion tracking: the waivers pile up, but Google Ads says nothing happened
- HIPAA FormsGoogle Ads stopped seeing intakes after you installed HIPAA Forms
- HubSpot FormsYour HubSpot form fills up, but which ads bring clients you'd actually call back?
Free · 30 min
Make your ad accounts count certified leads only
Free30 minutesNo obligation
