AgencyBloc conversion tracking: Google sees form fills, you get paid on in-force policies
Your Medicare, health or life ads fill AMS+ with leads, and Google and Meta can't tell which of them became policies. Nothing on the AMS+ record says which ad click produced it, and every resubmission fires the thank-you page again. We carry the click ID onto the record and send policy status changes back, so budget follows the leads that enroll.
Free30 minutesNo obligation
AgencyBloc · what breaks
What goes wrong with AgencyBloc and your ads
- 01
"Google counts leads, but which ones enrolled?"
The ad platforms only see the thank-you page after the AMS+ Lead Form, so a tire-kicker counts the same as a new enrollee and Smart Bidding chases cheap form fills.
- 02
One person, three leads
A prospect who submits your AMS+ Lead Form twice fires the thank-you page twice, so Google and Meta count two leads even if your team later merges the records. Your cost per lead looks better than it is, and bidding learns from the inflation.
- 03
Vendor leads mixed in with your ad leads
Bought leads arrive through the Lead POST API into the same pipeline. Counted alongside your ad leads, they hide which spend actually produced enrollments.
- 04
Phone enrollments vanish
Medicare and final expense prospects often call instead of finishing the form. We found no number swapping documented for the AMS+ dialer, so a call from a Google ad reaches your agents with no click attached, and the campaigns that make the phone ring look like they're failing.
AgencyBloc · the fix
What changes once it's fixed — AgencyBloc
Bidding learns from enrollments
Google and Meta receive application-submitted and in-force events from AMS+, so budget shifts toward the keywords and audiences that produce policies.
Each prospect counted once
Repeat submissions are matched on the stored click ID and email before anything is sent, and browser and server copies share one event ID, so a duplicate AMS+ record never becomes a second conversion.
Your own ads separated from bought leads
Lead source on each AMS+ record decides what reaches the ad platforms, so vendor leads, referrals and renewals stay out of your ad numbers.
AgencyBloc · architecture
What AgencyBloc AMS+ actually lets you hook into
These are the documented hooks we build on. None sends conversions to Google or Meta by itself, so each feeds a server container you own.
- 1
Lead Forms (HTML you paste on your site)
Built in My Agency Settings with a required thank-you page URL and custom fields, which is where the click ID lives.
- 2
Zapier triggers
AgencyBloc's Zapier app documents Individual, Group and Policy created and updated triggers.
- 3
HTTP Trigger in Legacy Sales Automated Workflows
Where your plan includes these workflows, an HTTP Trigger posts Sales Record data to a webhook when the workflow's filters match. Policy fields only come through when the workflow filters on carrier, product or policy status, and the Zapier side uses the premium Webhooks by Zapier app.
- 4
REST API and Lead POST
The REST API, billed monthly by request volume, creates, searches and updates leads and other records, custom fields included. Lead POST is how vendors push leads in.
- 5
No native ad-platform connection
We found no documented Google Ads, GA4, GTM or Meta integration and no number swapping on the AMS+ dialer, so calls need separate call tracking.
AgencyBloc · diagnose
Where AgencyBloc tracking breaks, in the order we check
Start at the form, because a click ID that never reaches the AMS+ record makes everything after it impossible to match.
- 01
Submit a test lead from an ad-tagged URL
Open the new record and confirm the click ID landed in its custom field.
- 02
Count conversions per submission
A form tag, a site-wide Pixel and a GA4 import can all claim one thank-you page visit.
- 03
Submit the same person twice
The second record must be deduplicated before anything reaches the ad platforms.
- 04
Trace lead sources
Lead POST, Facebook Lead Ads via Zapier and your own form should each stamp a distinct lead source.
- 05
Follow one policy to In Force
Change a test policy's status and confirm the trigger fires once, with click ID and value attached.
AgencyBloc · prove
The QA evidence — AgencyBloc
Run on a real lead through the Lead Form on your live site and a test policy in AMS+, not on a preview.
Source of truth
AgencyBloc AMS+ records: Sales Records or Individual Records by lead source and status, and Policy Records with app submit date and In Force status
- One ad-tagged submission, with the click ID visible on the AMS+ record.
- Exactly one Lead conversion in Google Ads and Meta Events Manager, sharing one event ID.
- A repeat submission from the same person producing no second conversion.
- A policy moved to In Force arriving once at every destination, with vendor and renewal records absent.
- In-force policies reconciled one by one against platform conversions across a closed month, then again 30 days later.
AgencyBloc · free audit
What we check in the free audit
- Submit a test lead from an ad-tagged URL
- Count conversions per submission
- Submit the same person twice
- Trace lead sources
- Follow one policy to In Force
Checked against
AgencyBloc AMS+ records: Sales Records or Individual Records by lead source and status, and Policy Records with app submit date and In Force status
Free30 minutesNo obligation
AgencyBloc · when not to buy
When you don't need this on AgencyBloc
Plenty of agencies running AMS+ don't need a rebuild.
- If nearly all new business comes from referrals, renewals or bought leads and you don't run Google or Meta ads, there's nothing to feed back.
- If you run only Meta Lead Ads and close a handful of policies a month, a Zap into AMS+ plus a manual review may be enough.
- If most enrollments happen by phone and you have no call tracking, fix call attribution first.
- If the only issue is a doubled tag on the thank-you page, we'll tell you how to remove it yourself.
AgencyBloc · what we deliver
The event map on AgencyBloc AMS+
Lead Form submitted
Fired on your thank-you page with a deduplication ID, and the GCLID, GBRAID or Meta click ID written to a custom field on the new record.
Lead qualified
Sent when the Sales Record or Individual status moves to the stage you choose, such as contacted or quoted.
Appointment booked
From an AMS+ Appointment Scheduler confirmation, with its Scope of Appointment or ACA consent step left inside AMS+.
Application submitted
Triggered when a policy gets its app submit date or a pending status, valued from the premium field if you want value-based bidding.
Policy in force
The main conversion, fired when the policy reaches a status you've marked In Force.
Excluded on purpose
Duplicate submissions, Lead POST vendor leads, renewal record types, Quote+ group transfers and anything from Rx Collect never reach an ad platform.
Written guarantee
95%+ tracking accuracy
Measured against AgencyBloc AMS+ records: Sales Records or Individual Records by lead source and status, and Policy Records with app submit date and In Force status. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
AgencyBloc questions, answered
Not directly, as far as its documentation shows. Conversions leave AMS+ through Zapier triggers, a workflow HTTP Trigger or the REST API, and we route them through a server container to each platform.
Lead Forms support custom text fields, so a field can hold the click ID. We make it a hidden input filled from the ad click and test it on a live submission before relying on it.
The thank-you page after the AMS+ Lead Form fires on every submission, so a prospect who submits twice counts twice. Matching on the stored click ID and email before sending fixes the ad-side count.
Yes. Once the click ID is on the record, a policy reaching an In Force status can be sent back to Google and Meta as the conversion they bid toward.
No. We send the event, a value and hashed contact details only, never plan, prescription or Rx Collect data from AMS+.
More on AgencyBloc
- 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 AgencyBloc, and what their bookings feed
- ConnectWise CPQConversion tracking for ConnectWise CPQ
- LeadPerfectionYour ads say leads. LeadPerfection says who sat and who signed. We connect the two.
- LineLeaderLineLeader shows who enrolled, but not which ad sent them
- AnchorYour ads bring inquiries, but Google never sees who signs in Anchor
- SpotioYour ad leads sit in Spotio next to every door your crew knocked. Google can't tell which ones signed.
- RingyRingy conversion tracking: your agents close policies in Ringy, and Google and Meta never hear about it
- TurboRaterGoogle Ads counts TurboRater quote clicks. Your producers count written policies.
- Vertafore AMS360Your ads get credit for quote forms. AMS360 knows which ones turned into policies.
Free · 30 min
See which ads fill AgencyBloc with people who enroll
Free30 minutesNo obligation
