Your ads get credit for quote forms. AMS360 knows which ones turned into policies.
A quote request lands in an inbox, a CSR keys the person into Customer Center as a Prospect, and the ad click that paid for them is gone before the first call. When the account binds, Google Ads and Meta never hear about it. We carry the click from your website into the AMS360 prospect record and send bound, new-to-agency policies back to the ad platforms, so your P&C or commercial agency can see which campaigns actually write premium.
Free30 minutesNo obligation
Vertafore AMS360 · what breaks
What goes wrong between your ads and AMS360
- 01
Google thinks every quote form is a win
The prospect gets retyped into AMS360 from an email, so the click ID never arrives. Smart Bidding learns from form fills, cheap personal-auto shoppers included.
- 02
Commercial accounts bind months after the click
You log an X-date and the account moves at renewal. By then nobody knows which campaign started it, so the ad that found your best account looks like a loser.
- 03
Carrier downloads and rewrites look like new sales
Downloads, AL3 imports, rewrites and book conversions all add policies. If they feed ad reporting, cost per policy looks better than it is.
- 04
A renters quote counts the same as a workers' comp account
AMS360 stores Full Term Premium on every policy, but your ad conversions carry no value. Bidding can't tell a renters policy from a commercial package, so budget drifts toward the campaigns that produce the most forms, not the most premium.
Vertafore AMS360 · the fix
What changes — Vertafore AMS360
Every web prospect keeps its campaign
Click ID, UTM source and campaign ride from your quote form onto the AMS360 customer record and survive the retyping.
Bound policies go back to the ad platforms with premium
Active, new-to-agency policies are sent to Google Ads and Meta server-side, valued from Full Term Premium, so bidding learns from what you actually write.
You can cut campaigns that only make quotes
A Target List by campaign shows which ads bring commercial premium and which bring tire-kickers.
Vertafore AMS360 · architecture
What AMS360 actually lets you hook into
AMS360 is the agency's back office, not a website tool, so the documented hooks are data fields and APIs rather than tags.
- 1
No pixel, GA4 or Google Ads connection
We found none in Vertafore's documentation. Browser tracking lives on your website, not in AMS360.
- 2
Agency-Defined Fields on the customer record
Documented for information not stored elsewhere. The click ID and campaign go here.
- 3
Fields that separate new from old
Customer Type, Date Added, Business Origin, the Business New to Agency checkbox, and the read-only Origin field (Data Entry, Download, Conversion, AL3 or SalesTrack).
- 4
Web Service API
Set up in the Administration Center at no additional charge, with entities that support retrieve, add, update and delete, varying by entity. We confirm which entities your build needs.
- 5
Vertafore API Developer Portal
OAuth credentials for AMS360, limited to the scopes your agency has contracted. Vertafore activates them when an app goes Live.
- 6
Fallback if API access isn't available
A scheduled export of new-business records, uploaded as offline conversions. We confirm which report exports cleanly.
Vertafore AMS360 · diagnose
Where AMS360 tracking breaks, in diagnostic order
Start upstream. The data you need is usually in AMS360 already; the ad source is what's missing.
- 01
Does the click ID survive the quote form?
Check the form submission and the email your CSRs work from.
- 02
Is the source written on the prospect?
Open the test prospect in Customer Center and look for the campaign.
- 03
Is Business New to Agency filled in consistently?
If producers skip it, new business can't be separated from rewrites and cross-sells.
- 04
How do carrier downloads mark new business?
Check the Retain Rewrite Transaction download option.
- 05
Do reported conversions match bound policies?
Compare a closed month of Google Ads and Meta conversions with new-to-agency Active policies.
Vertafore AMS360 · prove
The QA evidence — Vertafore AMS360
Done on a real quote through your live agency website, followed into your live AMS360 database, not a sandbox.
Source of truth
AMS360 policy records: Active policies with Business New to Agency checked, by effective date, with Full Term Premium, line of business and the prospect's ad-source fields
- A test quote from an ad-tagged URL, with the click ID confirmed on the AMS360 prospect.
- A tracked phone quote confirmed with its source on the prospect record.
- Exactly one bound-policy conversion per policy in Google Ads and Meta, sharing an event ID.
- Renewals, rewrites and download-only policies confirmed absent from the upload.
- Uploaded premium checked against Full Term Premium for each policy.
- Bound new business reconciled policy by policy over a closed month.
- Repeated 30 days later and after any change to your quote forms or AMS360 setup.
Vertafore AMS360 · free audit
What we check in the free audit
- Does the click ID survive the quote form?
- Is the source written on the prospect?
- Is Business New to Agency filled in consistently?
- How do carrier downloads mark new business?
- Do reported conversions match bound policies?
Checked against
AMS360 policy records: Active policies with Business New to Agency checked, by effective date, with Full Term Premium, line of business and the prospect's ad-source fields
Free30 minutesNo obligation
Vertafore AMS360 · when not to buy
When you don't need this on AMS360
Some agencies are better off leaving AMS360 alone.
- If your growth comes from referrals, acquisitions and producer relationships and you don't run paid search or social, there's nothing to send back.
- If your 'ads' are purchased leads you import as a leadlist, there's no ad click to match, so judge vendors on bound policies per batch instead.
- If a front-end CRM like AgencyZoom or Salesforce already sends sold policies to Google and Meta, fix it there and use AMS360 only to check the totals.
- If you spend a little on ads and your producers can name the source of every new account in a monthly review, that review is enough for now.
Vertafore AMS360 · what we deliver
The event map from your website into AMS360
Quote request submitted
Form or tracked call, with GCLID, fbclid and UTMs captured through a first-party server container.
Prospect created in AMS360
Customer Type set to Prospect and the ad fields filled in Agency-Defined Fields. Names imported from purchased leadlists stay out.
Submission or quote opened
A policy or submission started: a mid-funnel signal with no value.
Policy bound
Active with Business New to Agency checked. The main conversion, valued from Full Term Premium.
Kept out on purpose
Renewals, rewrites, download-only policies and records with an Origin of Conversion.
Not taken or canceled
Flagged so value is corrected wherever each platform allows it.
Written guarantee
95%+ tracking accuracy
Measured against AMS360 policy records: Active policies with Business New to Agency checked, by effective date, with Full Term Premium, line of business and the prospect's ad-source fields. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Vertafore AMS360 questions, answered
We found no direct connection in Vertafore's documentation. Tracking starts on your website, and bound policies go back from AMS360 data through its Web Service API or a scheduled export.
In Agency-Defined Fields on the customer record: one for the click ID, others for source and campaign.
Often, yes, but Google keeps a click ID for offline imports for only 90 days, and many commercial accounts bind later than that. So we also send an earlier quote-opened signal inside the window and check each bind against its click date before uploading.
Not once the upload is filtered on Business New to Agency, the Origin field and the rewrite download setting. Only new-to-agency Active policies count as conversions.
Not always. The Web Service API is set up in AMS360's Administration Center at no additional charge; the Developer Portal issues OAuth credentials limited to the API scopes your agency has contracted with Vertafore.
A tracked number on your site ties each caller to the ad click. Your CSR enters the tracked source in the prospect's Agency-Defined Fields while keying them into Customer Center, or we match the caller's phone number to the new prospect.
More on Vertafore AMS360
- 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 Vertafore AMS360, and what their bookings feed
- ProposifyProposify conversion tracking: your ads see the inquiry, Proposify sees the win
- OrbundYour ads fill Orbund with inquiries. Google can't tell which ones signed an enrollment agreement.
- Little Green LightLittle Green Light shows the gifts. Your ads can't see which campaign raised them.
- ConnectWise CPQConversion tracking for ConnectWise CPQ
- RingyRingy conversion tracking: your agents close policies in Ringy, and Google and Meta never hear about it
- boberdooboberdoo conversion tracking that counts sold leads, not form fills
- InsureioInsureio conversion tracking: know which ads write term life policies
- IgnitionIgnition shows who signed, but not which ad brought them in
Free · 30 min
Find out which ads write policies in AMS360
Free30 minutesNo obligation
