Insureio conversion tracking: know which ads write term life policies
You run Google or Facebook ads to the page with your Insureio quoting widget, leads land on the dashboard, and nobody can say which campaign produced the case that went in force. The widget saves a quoter URL, source and tags on each consumer record, but it never reports back to Google Ads or Meta. We carry the ad click into that record and send submitted applications and in-force policies back as conversions.
Free30 minutesNo obligation
Insureio · what breaks
What goes wrong with Insureio and paid ads
- 01
"Google shows a pile of leads, and I can't find the ones that bought"
The quoter's contact step is usually the only thing tracked, so Smart Bidding chases quote shoppers who never pick up the phone, and you keep paying for more of them.
- 02
Every quoter lead says the same source
One widget, one Advanced Options source, and Google, Facebook and your email list all show up as "website". You can't cut the campaign that's losing money.
- 03
Bought leads mixed in with ad leads
Leads you buy through the Insureio Marketplace and contacts from CSV imports sit on the same dashboard as quoter leads. Count them as conversions and your ads look better than they are, so you keep funding campaigns that don't earn it.
- 04
Health answers leaking toward Meta
Life quoters ask about tobacco use and health class. A careless Pixel setup can pass those answers to Facebook alongside the visitor's identity, a privacy problem you don't want attached to your agency's name.
Insureio · the fix
What changes — Insureio
Bidding learns from submitted apps
Google Ads and Meta get submitted applications and in-force policies with the original click, so budgets move toward the keywords and audiences that write business.
Cost per in-force policy, by campaign
Each consumer record carries its own campaign tags, and Google Ads and Meta report placed policies against the campaign that paid for the click, right next to what it cost.
Only clean signals leave Insureio
Ad platforms see a stage, a timestamp and a hashed contact for matching, never a health class, tobacco answer or carrier.
Insureio · architecture
What Insureio actually lets you hook into
Insureio has no built-in Google Ads, GA4 or Meta Pixel setting that we could find in its docs. What it does document is enough to build a closed loop around.
- 1
Quoting widget with Advanced Options
Pasted onto your page as embed code. Each widget can assign lead type, source, referrer, tags and agent split codes, and it saves a quoter_url and the visitor's IP on the record.
- 2
io_tags on the host page URL
The widget reads io_tags[] values from the address of the page it sits on. The io_ prefix keeps them from clashing with your page's own parameters. This is where the click ID rides in.
- 3
Status-driven webhooks and payload templates
A task tied to a status sends a payload template you design to Zapier or any endpoint you enter. This is how submitted and in-force cases leave Insureio.
- 4
Lead import API
One consumer per request, with lead type, source and referrer. Useful for landing-page forms you host yourself.
- 5
Things we confirm on your account
Whether your widget renders inside an iframe on your page, whether an InsuranceDivision site lets you add your own tags, and which statuses can carry a webhook task, since the Submitted to Carrier stage is handled by Insureio's fulfillment partners. We test before building on any of it.
Insureio · diagnose
Where Insureio tracking breaks, in the order we check
We start on a live consumer record, because that tells us what the widget really saved, not what the setup screen says it should save.
- 01
Run a test quote from an ad-tagged URL
Then open the consumer record and look at quoter URL, source and tags. A missing click ID here explains most of the gap.
- 02
Check what your thank-you signal fires on
If it fires on a page view or click outside the widget, it counts quote shoppers and refreshes, not contacts.
- 03
Count leads by source and lead type
Marketplace, import and widget leads should be separable. If they all read the same, attribution is guesswork.
- 04
Review status rules and existing webhook tasks
A change-status task moves a record on and cancels the remaining tasks in that status, so a webhook task queued behind it may never run.
- 05
Audit every tag on the quoter page
Look for Pixel or GA4 events that pick up health class, tobacco or condition fields from the widget.
Insureio · prove
The QA evidence — Insureio
Proven on a real quote through your live widget, then on a month of actual cases.
Source of truth
Insureio consumer and policy records: source, lead type, tags, quoter URL and status history for each case
- A test quote from a Google ad URL shows the gclid and campaign in the record's tags.
- One Meta lead per real contact, deduplicated by event ID between browser and server.
- A status change to application submitted reaches Google Ads and Meta within the expected window.
- Marketplace and imported consumers confirmed absent from every ad conversion.
- Payloads inspected line by line: no health class, tobacco, carrier or condition field sent out.
- A closed month of in-force cases matched record by record against platform conversions.
- Rechecked 30 days later and after any widget or status rule change.
Insureio · free audit
What we check in the free audit
- Run a test quote from an ad-tagged URL
- Check what your thank-you signal fires on
- Count leads by source and lead type
- Review status rules and existing webhook tasks
- Audit every tag on the quoter page
Checked against
Insureio consumer and policy records: source, lead type, tags, quoter URL and status history for each case
Free30 minutesNo obligation
Insureio · when not to buy
When you don't need this on Insureio
Plenty of agents running Insureio don't need us, and we'll say so on the call.
- If you don't run paid ads and your leads come from the Marketplace, referrals or a book you already own, Insureio's own source reports cover it.
- If you get a handful of quoter leads a month, there isn't enough data for Smart Bidding to learn from submitted apps anyway.
- If you sell mostly by phone from inbound calls, call tracking matters more than the widget, and we'd scope that instead.
- If your only problem is that every widget shares one source, setting a distinct source in each widget's Advanced Options is a quick fix you can do yourself.
Insureio · what we deliver
The event map on Insureio
Quote shown
If your term life or LTC widget exposes the quote step on your page, we record it for audiences only, never as a bid target.
Contact submitted
The consumer record is created with quoter URL, click ID and campaign tags. The primary lead conversion.
Contacted
The record moved out of the Opportunity stage (Prospect, Attempting Contact) into Contacted, which filters out fake numbers and quote browsers.
Application submitted
The case reached App Fulfillment or the status your team sets when the app goes out. The conversion we recommend Smart Bidding optimizes toward.
Policy in force
The case closed in the Completed stage as in force, valued from the premium you choose to report, matched to the original click.
Excluded on purpose
Marketplace leads, CSV and API imports, withdrawn or closed cases, and every health or underwriting field.
Written guarantee
95%+ tracking accuracy
Measured against Insureio consumer and policy records: source, lead type, tags, quoter URL and status history for each case. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Insureio questions, answered
Not natively, as far as Insureio's documentation shows. You connect them through the widget's io_tags parameters on the way in and status webhooks on the way out.
Yes, if the ad's click ID and campaign values are passed into the widget as io_tags. They're saved on the consumer record, so each case keeps its own ad history.
Submitted applications, once you have steady volume. Quote contacts are cheap to get and many never answer, so bidding on them trains Google to find more of the same.
Not with our build. Only a stage, a timestamp, a value and hashed email or phone for matching leave Insureio, and we check every payload field before going live.
They shouldn't. You bought them separately, so we tag them by source and keep them out of Google and Meta reporting.
Often, but we test it first: whether that site accepts your own tags and passes URL parameters through to the widget.
More on Insureio
- 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 Insureio, and what their bookings feed
- LeapLeap shows the window job your rep signed in SalesPro. Google Ads still thinks it was a form fill.
- SteerSteer conversion tracking: which ads actually brought cars into your bays?
- LeadSquaredLeadSquared for healthcare: show Google and Meta which ads become booked consults
- BonzoBonzo is full of mortgage leads. Which ads actually funded loans?
- Unanet CRMOur pursuits live in Unanet CRM. Google Ads has no idea which ones it started.
- RepairShoprRepairShopr shows the repair tickets. Your ad accounts only see a redirect.
- PandaDocPandaDoc conversion tracking: Google Ads sees the inquiry, never the signed proposal
- boberdooboberdoo conversion tracking that counts sold leads, not form fills
Free · 30 min
Find out which ads write your policies
Free30 minutesNo obligation
