Your ads send prospects to Canopy Connect. Google and Meta never see who finished.
You put an "Import my insurance" button on the agency site, the modal opens, and the prospect logs into their carrier or uploads a dec page. Canopy Connect gets a full policy profile; Google Ads and Meta get a page view. We tag each pull with the ad click that started it and send finished pulls and bound policies back from the server.
Free30 minutesNo obligation
Canopy Connect · what breaks
What goes wrong with Canopy Connect and your ads
- 01
"Meta reports more leads than Canopy shows pulls"
The Pixel fires on the "Import my insurance" click, so Meta counts everyone who opened the modal. Prospects who quit at the carrier login then teach it to find more people who quit, and you pay for each one.
- 02
"I can't tell which campaign sent the auto quote"
The pull lands in your dashboard with policy data but no record of the ad, keyword or audience behind it, so you renew budgets on guesswork.
- 03
Texted links break the trail completely
When a producer texts the app.usecanopy.com link after a call, the prospect opens it with no ad click attached, so the pull looks like it came from nowhere.
- 04
Bidding stops at the import, not the policy
The money moment is a bound home, auto or commercial policy in your agency system weeks after the pull. Without it, Google Ads values a renter price-shopping a single line the same as a business owner insuring a fleet, and spends accordingly.
Canopy Connect · the fix
What changes after we fix it — Canopy Connect
One conversion per finished pull
Google Ads and Meta count a lead when Canopy Connect reports the pull complete, deduplicated on the pull ID, so opened-and-abandoned modals stop inflating results.
Every pull tied to its ad click
The GCLID, fbclid and UTMs ride inside the pull's meta_data, so your team and the ad platforms both see the campaign.
Campaigns optimized toward bound premium
Quoted and bound outcomes flow back from your AMS, so P&C and commercial lines campaigns chase buyers, not shoppers.
Canopy Connect · architecture
What Canopy Connect actually lets you hook into
Canopy publishes a JavaScript SDK, webhooks and a pulls API. It documents no Google Ads, GA4 or Meta connection of its own, so tracking is built on these pieces.
- 1
Website SDK and snippets
Button and Modal, Embedded Widget or Link, generated from the dashboard and loaded from cdn.usecanopy.com.
- 2
pullMetaData
Any JSON you pass when creating the handler is returned on the pull as meta_data. This is where the GCLID, fbclid and UTMs go.
- 3
Widget events
authenticationSuccess, userAction, sectionViewed and exit fire in the page with the pull ID. The exit error codes show where prospects drop.
- 4
Webhooks and GET /pulls
COMPLETE, POLICIES_AVAILABLE, AUTH_STATUS and ERROR post to an endpoint you register in Settings or the Webhooks API.
- 5
Zapier and AMS hand-offs
Zapier lists one trigger, Pull Completed, which also fires on submissions with incorrect credentials, so it can't be the lead signal on its own. Data also moves into raters and agency systems like EZLynx and AgencyZoom; we confirm what reaches yours.
Canopy Connect · diagnose
Where Canopy Connect tracking breaks, in the order we check
Most agency sites over-count first, so we start in the browser and work toward the agency system.
- 01
What fires when the button is clicked
If a Meta Lead or Google Ads conversion fires on the click, every abandoned login is counted.
- 02
Whether the click ID reaches meta_data
We run one import from a GCLID-tagged landing URL, then check that pull's meta_data for the click ID.
- 03
Which links bypass the website
Producer texts, QR codes and the Facebook share button open app.usecanopy.com without your ad parameters. We confirm whether Canopy's cc-meta link parameters can carry a source tag on those links.
- 04
Which webhook the conversion listens to
POLICY_AVAILABLE fires for each individual policy, so a household bundling three policies can turn into three leads. COMPLETE fires once per pull.
- 05
Whether bound policies flow back
Whether the pull's contact reaches your AMS with its source decides if bound premium can ever reach the ad platforms.
Canopy Connect · prove
The QA evidence — Canopy Connect
Run on live pulls through the button on your real agency site, with a test carrier login or sample dec page.
Source of truth
Canopy Connect pull records (pull ID, completion status, meta_data) matched to quoted and bound policies in your agency management system
- One pull started from a GCLID-tagged URL, with the click ID visible in the pull's meta_data.
- Exactly one Google Ads and one Meta conversion per completed pull, deduplicated on the pull ID.
- A pull abandoned at the carrier login confirmed absent from both platforms.
- A multi-policy household confirmed as one lead, not one per policy.
- A bound policy imported to Google Ads with the correct click and value.
- Rechecked after 30 days, and again whenever the widget snippet, link alias or webhook endpoint changes.
Canopy Connect · free audit
What we check in the free audit
- What fires when the button is clicked
- Whether the click ID reaches meta_data
- Which links bypass the website
- Which webhook the conversion listens to
- Whether bound policies flow back
Checked against
Canopy Connect pull records (pull ID, completion status, meta_data) matched to quoted and bound policies in your agency management system
Free30 minutesNo obligation
Canopy Connect · when not to buy
When Canopy Connect tracking can wait
Plenty of agencies use Canopy Connect without running ads to it, and that's fine.
- If producers only text the link to people who already called in from referrals or renewals, there's no ad click to recover. Track the call, not the pull.
- If you spend a few hundred dollars a month on one platform and every completed pull already lands in AgencyZoom with its source, a quarterly spot check is enough.
- If your ads point at a quote form or phone number and Canopy Connect only appears later, fix tracking on that first step instead.
- If your one problem is a Lead event firing on the import button, that's a one-tag move to the COMPLETE moment, and we'll walk you through doing it yourself.
Canopy Connect · what we deliver
The event map on Canopy Connect
Import started
The CONSENT_SUBMITTED moment in the widget, kept for diagnostics and never used for bidding.
Pull completed
Fired on your server when the COMPLETE webhook arrives; the pull is fetched with GET /pulls and the click ID read from its meta_data. This is the lead conversion.
Dec page upload completed
Tracked separately off the widget's DOCUMENTS_SUBMITTED action, when the prospect uploads a dec page instead of logging into a carrier.
Quote delivered
Taken from your agency system once a producer quotes the household or business, sent as a qualified-lead conversion.
Policy bound
The conversion that matters, with premium as value where your AMS records it, imported to Google Ads and sent to Meta.
Excluded on purpose
Monitoring refreshes, DATA_UPDATED events, renewals and pulls that end in a login error never count as new leads.
Written guarantee
95%+ tracking accuracy
Measured against Canopy Connect pull records (pull ID, completion status, meta_data) matched to quoted and bound policies in your agency management system. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Canopy Connect questions, answered
Not directly. Its documentation covers an SDK, webhooks, a pulls API, a Zapier trigger and agency system hand-offs; we found no Google Ads, GA4 or Meta Pixel connection, so conversions are sent from your own server.
Only roughly. The Pixel sees the button click, but the pull isn't finished until Canopy's COMPLETE webhook fires, so the reliable lead signal comes from the server through the Conversions API.
Through pullMetaData. We read the GCLID, fbclid and UTMs from the landing URL, pass them when the SDK handler is created, and Canopy returns them on the pull as meta_data.
Those pulls have no ad click to match. We tie them to the original tracked call or form lead by phone or email instead.
Both, weighted differently. The completed pull gives Google and Meta volume; the bound policy from your AMS tells them which prospects are worth paying for.
More on Canopy Connect
- Stripe → Walmart ConnectConnecting Stripe to Walmart Connect
- PayPal → Walmart ConnectConnecting PayPal to Walmart Connect
- Shopify → Walmart ConnectConnecting Shopify to Walmart Connect
RELATED GUIDES
Booking tools beside Canopy Connect, and what their bookings feed
- TrustedFormTrustedForm conversion tracking: stop Google and Meta counting leads you can't legally call
- Paubox FormsYour Paubox intake form fills up, but Google Ads says nobody converted
- 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
- WaiverSignWaiverSign conversion tracking: Saturday's waiver list is full, and your ads can't see a single rider
- WaiverForeverWaiverForever conversion tracking: guests sign before they arrive, and your ads never hear about it
- HubSpot FormsYour HubSpot form fills up, but which ads bring clients you'd actually call back?
- Google FormsWhy can't I track my Google Form in Google Ads or Meta?
Free · 30 min
Find out which ads produce bound policies through Canopy Connect
Free30 minutesNo obligation
