Skip to main content
ePayPolicyPayments and financing

ePayPolicy conversion tracking: your ads see the quote request, never the bound policy

Your PayNow button sends the insured to a page on ePayPolicy's domain, and invoice links land in the same place. Google Ads and Meta stop at the quote form on your site, so a shopper collecting three quotes scores the same as a trucking company that bound a commercial auto policy. Fixed looks like this: the first premium payment, read from your ePayPolicy transactions and your AMS, goes back to the ad click behind the quote request, while renewals and AutoPay installments never touch your bidding.

Free30 minutesNo obligation

ePayPolicy · what breaks

What goes wrong with ePayPolicy at an insurance agency

  1. 01

    Renewals paying their premium look like new leads

    PayNow exists so insureds can pay premiums and installments, so most of the people clicking it already hold a policy with you. If that click is a Google Ads conversion, Smart Bidding spends your budget finding people you already insure.

  2. 02

    The quote request is the last thing your ads ever see

    The policy becomes real when the insured pays on the ePayPolicy page, where ePayPolicy documents no place for your tags. A price shopper and a contractor who bound a general liability policy look identical to Google Ads, so cheap quotes beat real premium.

  3. 03

    Financed policies carry an amount that isn't the premium

    With Finance Connect, the insured picks financing over paying in full and e-signs the premium finance agreement. ePayPolicy documents that financing is tracked in your dashboard, not what amount a financed policy records, so payment-based conversion values can underweight your best commercial accounts.

  4. 04

    Refunds and bounced ACH never reach your management system

    ePayPolicy documents that refund details and bounced ACH payments aren't written back to integrated management systems (FinancePro syncs voids only). If your AMS feeds conversion values, cancelled policies and failed payments stay counted as revenue.

ePayPolicy · the fix

What changes — ePayPolicy

  • New business separated from money you already had

    Only a first premium payment on a new policy counts; renewals, AutoPay and recurring payments are logged but never sent to the ad platforms.

  • Bound premium attached to the ad click

    The quote request stores the GCLID or fbclid; the ePayPolicy payment is matched to it by email or policy number and sent to Google Ads and Meta valued at the premium.

  • Reversals handled where your AMS can't see them

    Refund, void and returned ACH details are read from the ePayPolicy dashboard, which ePayPolicy says is where they live, and reversed wherever each platform allows.

ePayPolicy · architecture

What ePayPolicy actually lets you hook into

ePayPolicy documents nothing about Google Analytics, Google Tag Manager or the Meta Pixel on its payment page. What it does document is enough to close the loop from your side.

  1. 1

    A hosted payment page with a unique URL

    The PayNow button on your site and in email signatures points at your dedicated payment page URL on ePayPolicy's domain. Your tags end at the click, a hand-off, not a conversion.

  2. 2

    Prefill parameters on the payment link

    ePayPolicy documents a payer name, EmailAddress, Amount and Comments as URL attributes on the payment page, plus account-specific search attributes on integrated pages. This is how payment and quote request get a shared key.

  3. 3

    Quotes and Invoices with a direct link

    Invoices go out through Create Email or Copy URL and switch to a dated Payment status once paid, linked to the transaction. That status is the cleanest bound signal on the platform.

  4. 4

    Transaction search and downloads

    Downloads come straight from the dashboard up to 250 records and are emailed above that; batch reports arrive about a business day before deposits. Either feeds the server-side send.

  5. 5

    A custom API, no documented webhooks

    The API tokenizes a payment method and creates a transaction, and a Token Page Session redirects to a success URL. Nothing documented pushes a completed payment to you, so the loop runs from your records on a schedule.

ePayPolicy · diagnose

Where ePayPolicy tracking breaks, in diagnostic order

Start with the PayNow button, because the costliest fault at an agency is renewals bid on as new leads.

  1. 01

    Check whether PayNow clicks are a conversion action

    In Google Ads and GTM. If it is, pull the ePayPolicy payer list and count the existing clients.

  2. 02

    Confirm the quote request stores a click identifier

    Submit one from an ad-tagged URL and open the record in your AMS or CRM.

  3. 03

    Test whether the invoice link carries the insured's email

    Open a real Create Email invoice and compare its URL with the documented prefill parameters.

  4. 04

    Compare new-business payments with reported conversions

    Per policy, over a closed month, using the transaction download.

  5. 05

    Find where refunds and returned ACH are recorded

    ePayPolicy says they live in its dashboard, so AMS-fed values stay inflated until they're pulled in.

ePayPolicy · prove

The QA evidence — ePayPolicy

Run on a real invoice from your ePayPolicy dashboard, paid on the live page, not the sandbox.

Source of truth

ePayPolicy transaction records and invoice statuses, cross-checked against policies bound in your management system

  • One quote request from an ad-tagged URL, click identifier confirmed on the lead record.
  • That quote's invoice paid on the live page, its Payment status matched to the lead by email or policy number.
  • Exactly one conversion per new policy at Google Ads and Meta, with a shared event ID.
  • A renewal and an AutoPay installment confirmed absent from every acquisition conversion.
  • A Finance Connect policy counted once, valued from the AMS premium.
  • A refund or returned ACH reversed from the dashboard record.
  • Matched policy by policy across a closed month, repeated 30 days later.

ePayPolicy · free audit

What we check in the free audit

  • Check whether PayNow clicks are a conversion action
  • Confirm the quote request stores a click identifier
  • Test whether the invoice link carries the insured's email
  • Compare new-business payments with reported conversions
  • Find where refunds and returned ACH are recorded

Checked against

ePayPolicy transaction records and invoice statuses, cross-checked against policies bound in your management system

Get my free conversion tracking audit

Free30 minutesNo obligation

ePayPolicy · when not to buy

When you don't need this on ePayPolicy

Some agencies only need one conversion action removed, and we'll say so.

  • If you don't run Google, Meta or Microsoft ads, the ePayPolicy dashboard already tells you everything about your payments.
  • If your only fault is a PayNow click counted as a conversion, deleting that action is a ten-minute job you can do yourself.
  • If almost all new business comes from carrier referrals or walk-ins, your AMS reports already answer the question.
  • If the insured pays the carrier directly, ePayPolicy isn't where the money lands and we'd look at the carrier flow first.

ePayPolicy · what we deliver

The event map on ePayPolicy

  • Quote request on your site

    The lead: form or tracked call, with the click identifier stored on the record for the later payment to match.

  • Quote or invoice sent from ePayPolicy

    Leading indicator, taken from the Quotes and Invoices tab when the Create Email link goes out.

  • First premium paid

    The conversion. Read from the invoice status changing to Payment on a date, or from the transaction search, and matched to the quote request.

  • Policy financed through Finance Connect

    Counted as bound and valued from the premium in your AMS, once we confirm what the dashboard records for a financed policy.

  • Renewal, recurring and AutoPay payments

    Excluded from every acquisition conversion and kept for retention reporting only.

  • Refund, void or returned ACH

    Reversed from the ePayPolicy transaction record, since these aren't written back to your management system.

Written guarantee

95%+ tracking accuracy

Measured against ePayPolicy transaction records and invoice statuses, cross-checked against policies bound in your management system. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

ePayPolicy questions, answered

Not as far as ePayPolicy documents. The page is hosted on its domain and the help center covers branding, attachments and recurring payments, not tracking scripts. The payment is read from your records and sent server-side instead.

Free · 30 min

Get ePayPolicy tracking right

Free30 minutesNo obligation