Ringy conversion tracking: your agents close policies in Ringy, and Google and Meta never hear about it
Your agents work every lead in Ringy, dialing, texting and moving it down the pipeline until a policy is written. Google Ads and Meta stop at the form fill, so they keep buying people who never pick up. We carry the ad click into the Ringy lead and send back quoted and sold.
Free30 minutesNo obligation
Ringy · what breaks
What goes wrong with Ringy and your ads
- 01
"Meta says we got a pile of leads. My agents say most were junk."
Meta logs the form fill the moment it lands, before anyone has dialed it from Ringy. Disconnected numbers and people who never answer your power dialer count the same as a household that buys, so you pay for more of them.
- 02
The lead lands in Ringy with no idea which ad sent it
When leads from your landing page or Facebook forms reach Ringy through Zapier or the API, only the fields someone mapped come across. If nobody mapped the campaign and click ID, a Medicare lead from your priciest keyword looks the same as one from a cheap broad ad.
- 03
Bought leads and ad leads blur together
Ringy's vendor reports show whether NextGen Leads or Benepath pays off. Your own Google and Meta campaigns get no such report, and once both streams share a pipeline, nobody can say what your ad spend wrote.
- 04
Sold policies never make it back to the ad account
Your agent moves the lead to sold in Ringy weeks after the click, and Google and Meta never hear about it. Bidding keeps chasing cheap form fills instead of households that buy a life or health plan.
Ringy · the fix
What changes once Ringy is wired in
Every ad lead carries its source into Ringy
Click ID, campaign and landing page saved on the lead, so you can filter your pipeline by the ad that paid for it.
Google and Meta learn from quoted and sold
The pipeline stages your agents already use become conversions, so bidding favors people who answer and buy.
Ad spend measured apart from vendor spend
Purchased leads keep their vendor tag and never count as an ad conversion, so your cost per sold policy from ads is finally honest.
Ringy · architecture
What Ringy actually lets you hook into
Ringy's public pages describe its API and integrations in broad strokes, so we treat anything beyond what's listed below as a check on your account.
- 1
Inbound API for leads
Ringy documents real-time lead import by API and lets you line up custom lead fields with the data you send, which is where the click ID and campaign go.
- 2
Event-triggered API requests
Ringy says an account can make API requests automatically on various events. We confirm which pipeline changes your plan can fire on.
- 3
Zapier, Boomi and Integrately
Listed as connected tools. We check which triggers and actions are actually available before building on them.
- 4
Facebook and Google Calendar
Shown as logos only, with no documented detail. Whether Meta lead forms reach Ringy natively or through Zapier is something we verify.
- 5
No native ad conversion sending
Ringy documents no posting of conversions to Google Ads, GA4 or the Meta Conversions API, so the return trip runs through your own server container.
Ringy · diagnose
Where Ringy tracking breaks, in the order we check
Most Ringy accounts run vendor leads and ad leads side by side, so we separate the two before judging anything.
- 01
Submit a test lead from a tagged ad URL
Then open the Ringy record and see whether any click ID or UTM survived.
- 02
List every path into Ringy
Vendor API, Zapier, manual entry, CSV import and the Lead Scraper extension each need a source tag.
- 03
Count conversions per real lead
A Meta Pixel on the thank-you page plus a lead-form event often report the same person twice.
- 04
Check which pipeline stage means sold
Ringy lets each account customize its pipeline, so we agree which stage means sold before a single conversion goes out.
- 05
Look at what leaves the CRM
Only hashed contact details, stage and value should go out, never health or coverage notes.
Ringy · prove
The QA evidence — Ringy
Done with real leads from live campaigns, then traced through to the policies your agents close in Ringy.
Source of truth
Ringy lead records: lead source, custom click fields, pipeline stage and the date each lead reached sold
- A test lead from a tagged Google ad and one from a Meta ad, each with its click ID on the Ringy record.
- One conversion per lead in Google Ads and Events Manager, with a shared event ID across browser and server.
- A lead moved to quoted, then sold, showing up as the right conversion at each platform.
- Vendor and CSV-imported leads confirmed absent from every ad conversion.
- Sold leads matched record by record against platform conversions over a closed month, then again 30 days later.
Ringy · free audit
What we check in the free audit
- Submit a test lead from a tagged ad URL
- List every path into Ringy
- Count conversions per real lead
- Check which pipeline stage means sold
- Look at what leaves the CRM
Checked against
Ringy lead records: lead source, custom click fields, pipeline stage and the date each lead reached sold
Free30 minutesNo obligation
Ringy · when not to buy
When you don't need this on Ringy
Plenty of agencies using Ringy aren't buying clicks at all.
- If every lead in Ringy comes from vendors like QuoteWizard or SmartFinancial and you run no ads of your own, Ringy's vendor reports already answer the question that matters.
- If your ads are pure brand awareness with no form or call to action, there is nothing to send back.
- If you write so few policies that a spreadsheet of ad leads versus sales tells you everything, start there.
- If the only problem is a duplicate Pixel on your thank-you page, that's a quick fix you can do yourself.
Ringy · what we deliver
The event map on Ringy
Ad form submitted
On your landing page or Meta form, with the click ID captured before the lead goes to Ringy.
Lead created in Ringy
Confirmed by the record, not the thank-you page.
Contacted
Set once an agent actually reaches the lead, so dead numbers stop counting.
Quoted or appointment set
The qualified conversion, sent from the matching Ringy pipeline stage.
Policy sold
The primary conversion, with the premium as its value if your team records one on the lead.
Excluded: vendor and imported leads
Anything arriving from a lead vendor, a CSV upload or the Lead Scraper extension stays out of every ad conversion.
Written guarantee
95%+ tracking accuracy
Measured against Ringy lead records: lead source, custom click fields, pipeline stage and the date each lead reached sold. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Ringy questions, answered
Not that Ringy documents. Its public pages describe an API, event-triggered requests and Zapier, but no built-in Google Ads or Conversions API connection, so sold policies have to be sent through your own setup.
The click ID and campaign have to be captured on your landing page or form and passed into Ringy custom fields when the lead is created. Without that, the record only knows the lead exists.
No. Leads from QuoteWizard, NextGen Leads or Benepath were never ad clicks, so counting them would teach Google and Meta the wrong thing. They keep their vendor tag and stay out.
Outbound dials don't create ad conversions. If prospects call you straight from an ad, that needs call tracking with click matching, which Ringy doesn't document, so we check how those calls reach your agents.
Only the minimum goes: a hashed email or phone, the pipeline stage and a value. Health conditions, plan details and agent notes stay in Ringy.
More on Ringy
- 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 Ringy, and what their bookings feed
- AgencyZoomYour ads count quote requests. AgencyZoom knows which ones you wrote.
- HawkSoftGoogle Ads counts quote requests. HawkSoft knows which ones became policies.
- HomebotConversion tracking for Homebot
- Better CaterBetter Cater fills up with catering inquiries. Google Ads says your ads got none.
- TurboRaterGoogle Ads counts TurboRater quote clicks. Your producers count written policies.
- ClassterConversion tracking for Classter
- Unanet CRMOur pursuits live in Unanet CRM. Google Ads has no idea which ones it started.
- PopuliYour ads fill the Populi inquiry list, but Google can't see who enrolls
Free · 30 min
Find out what your ads really write in Ringy
Free30 minutesNo obligation
