Your ads see the click to Proof. They never see the notarization finish.
When a client taps "Notarize online" on your site, they leave for Proof's own app, where the ID check, the video meeting and often payment happen out of your tags' reach. So Google Ads and Meta credit the button click and never learn who finished. Fixed means every completed Proof transaction is matched to the ad click that started it.
Free30 minutesNo obligation
Proof · what breaks
What goes wrong when Proof sits behind your ads
- 01
Google shows conversions daily. My Proof log shows a few.
The only thing your site can see is the outbound click to your Proof EasyLink, so that click becomes the conversion. Smart Bidding then spends your budget finding more people who tap the button and bail at the ID check.
- 02
I can't tell which ads bring signers who finish
KBA questions, the live notary meeting and the signature all happen inside Proof's app. None of it flows back to the campaign that paid for the visit, so you keep funding ads without knowing which ones end in a completed session.
- 03
The fee is paid on Proof or by Zelle, never on my site
Notary-sourced clients can pay through Proof's Stripe checkout or outside it with Zelle, Venmo or Cash App, so no fee ever reaches your ad accounts and every session looks worth the same.
- 04
A remote closing and a one-seal affidavit look identical
A remote closing for a title order and a one-seal power of attorney land in the same conversion bucket, so budget drifts toward whatever is cheapest to click, not what pays.
Proof · the fix
What changes after we fix it — Proof
Bidding learns from finished notarizations
Google Ads and Meta receive the completed transaction from the server, so the algorithm optimizes toward signers who clear KBA and the meeting.
Each campaign carries its real fee
The conversion carries the fee you set on that Proof transaction, so a loan signing outranks a single-seal affidavit in your reports and in bidding.
Dead ends stop counting
Transactions that expire, get declined or fail the ID check are filtered out, and partial completions with rejected documents are flagged rather than counted as wins.
Proof · architecture
What Proof actually lets you hook into
We found no Google Ads, GA4 or Meta Pixel integration in Proof's developer docs. What Proof does document is an API with webhooks, redirects and external IDs, which is enough to build the loop server-side.
- 1
Webhooks V2 subscriptions
Created through the API, with events such as transaction.completed, transaction.released, transaction.completed_with_rejections and transaction.expired. Proof retries failed deliveries up to 16 times over 48 hours and may send an event twice, so our receiver ignores repeats.
- 2
external_id and the transaction ID
API-created transactions and signers accept your own ID, and the create call returns Proof's transaction ID. Transaction-level webhook payloads don't echo external_id back, so we store both IDs against the lead and match completions on the transaction ID.
- 3
Post-signing redirect
A per-transaction redirect, or forceRedirect on an API key that also generated the EasyLink, can send signers back to your thank-you page. It's a browser signal, so we treat it as a backup.
- 4
EasyLinks
Built in the Proof dashboard and shared as a URL, button or QR code. Proof doesn't document passing query parameters through them, so we test what survives.
- 5
Notary-sourced accounts
Proof's notary-sourced help pages don't mention webhooks or redirects. For solo mobile notaries we confirm which tier you're on before promising the automated route.
Proof · diagnose
Where Proof tracking breaks, in the order we check
Most of the damage happens at the hand-off, so that's where we start.
- 01
What your ad accounts count as the conversion
If it's the button click or a page view of the EasyLink, bidding has been trained on intent, not completions.
- 02
Whether the click ID survives the jump to Proof
Click your own ad, start a session and see if anything ties the Proof transaction back to that visit.
- 03
Whether a webhook subscription exists
Integrations built in the Notarize era may still run on V1 webhooks, which Proof says are no longer updated, or have no subscription at all.
- 04
How rejected and failed sessions are handled
Completed-with-rejections and KBA lockouts should never count as a full win.
- 05
Where the fee gets paid
Proof's Stripe checkout, or Zelle, Venmo or Cash App outside Proof. Each needs a different way to attach the fee to the conversion.
Proof · prove
The QA evidence — Proof
Every check runs on a real Proof session started from an ad-tagged URL on your live site, not in a sandbox.
Source of truth
Proof transaction records: completed and released transactions by date, with transaction ID, external_id, signer and fee
- A live session from a Google Ads click, with the lead ID and Proof transaction ID stored together before the signer starts.
- The completed webhook received, verified against its signature header, and processed once even when Proof retries it.
- Exactly one conversion each in Google Ads and Meta, deduplicated on a shared event ID.
- A KBA failure and an expired request confirmed absent from both ad accounts.
- Completed Proof transactions reconciled one by one against uploaded conversions over a closed month.
- Rerun a month after launch, and again whenever an EasyLink is regenerated or an API key is rotated.
Proof · free audit
What we check in the free audit
- What your ad accounts count as the conversion
- Whether the click ID survives the jump to Proof
- Whether a webhook subscription exists
- How rejected and failed sessions are handled
- Where the fee gets paid
Checked against
Proof transaction records: completed and released transactions by date, with transaction ID, external_id, signer and fee
Free30 minutesNo obligation
Proof · when not to buy
When you don't need this on Proof
Some notaries and title shops should leave it alone.
- If you don't run paid ads and your Proof work comes from lenders, realtors or repeat business clients, ad attribution won't tell you anything new.
- If you only take sessions as a notary on Proof's on-demand network, those signers come from Proof, not from your ads.
- If you do a handful of remote sessions a month and most revenue is in-person mobile signings, track phone calls first.
- If your title orders are sent to you on Proof by a lender, the lender, not your ads, created that transaction.
Proof · what we deliver
The event map on Proof
Intake captured on your site
Name, email and document type taken before the hand-off, with GCLID, fbclid and UTMs stored against a lead ID.
Hand-off to Proof
The click to your EasyLink or access link, logged as a micro-step and never used for bidding.
Transaction sent to the signer
The qualified-lead signal, created with your lead ID as the external_id where the API is available.
Meeting requested or joined
The signer has cleared upload and is waiting for, or talking to, a notary.
Notarization completed and released
The primary conversion, valued from your fee, sent server-side to Google Ads and Meta once.
Excluded and reversed
KBA failures, declines, cancellations, expirations and recalls, plus repeat work from existing business accounts.
Written guarantee
95%+ tracking accuracy
Measured against Proof transaction records: completed and released transactions by date, with transaction ID, external_id, signer and fee. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Proof questions, answered
Not through anything Proof documents. We found no Google Ads, GA4 or Meta Pixel setting in Proof's developer docs, and the session runs in Proof's app, not on your site, so the completed transaction has to be sent from a server instead.
It's the same platform under a new name, and integrations built in the Notarize era may still run on V1 webhooks, which Proof says are no longer updated. Moving to Webhooks V2 is usually part of the fix.
We capture the click ID on your site before the hand-off, create the Proof transaction with your lead ID as the external_id, and store the transaction ID Proof returns. When the completed webhook arrives, that ID leads back to the original GCLID we send to Google Ads.
It can load a thank-you page, but signers who close the tab skip it, and Proof doesn't document passing IDs on the redirect. It's a backup to the webhook, not the main signal.
Yes, though the route depends on your account. If webhooks aren't available on your tier, we match completed sessions from your Proof history to captured leads and upload them as offline conversions.
More on Proof
- 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 Proof, and what their bookings feed
- OrderryOrderry conversion tracking: see which ads book repairs, not just clicks
- ISNPaying for clicks but can't tell which ones book ISN inspections?
- ACTIVENetFamilies pay for programs on ACTIVENet every week. Google Ads says your ads sold nothing.
- Instagram & Facebook Book Now"Instagram keeps booking clients through the Book button. Ads Manager says my ads booked nobody."
- EnrollwareYour CPR classes fill up on Enrollware. Your ads can't see who registered.
- FittleBugConversion tracking for FittleBug
- RelatientRelatient conversion tracking: find out which ads actually fill your Dash schedule
- OfferingTreeOfferingTree conversion tracking that shows which ads fill your classes
Free · 30 min
Find out how many Proof sessions your ads really produce
Free30 minutesNo obligation
