Ignition shows who signed, but not which ad brought them in
Google Ads says the campaign is converting, but when a client signs an engagement in Ignition you can't say which ad brought them in. The form opens on an Ignition link, the deal lands in your Ignition pipeline, and the proposal is accepted days later on Ignition's page, all out of sight of your site tags. We carry the ad click through to the accepted proposal and report the signed engagement, at its real fee, to Google Ads and Meta.
Free30 minutesNo obligation
Ignition · what breaks
What goes wrong when your leads run through Ignition
- 01
"Google counts the button, not the client"
Your Book a consultation button links out to an Ignition form, so your site only sees the click. Google Ads then optimizes toward people who press a button, and many of them never submit the form.
- 02
"I can't tell which ads signed engagements"
The real outcome is a proposal accepted on Ignition's page, often a week or more after the click. Without the click ID on the deal, every signed bookkeeping client looks like direct traffic.
- 03
"A one-off tax return counts the same as a monthly retainer"
Tax prep leads flood in from January to April, but the profitable work is recurring monthly bookkeeping. With one flat value per conversion, bidding chases cheap seasonal returns.
- 04
"One signed client showed up as three conversions"
Ignition's Service Accepted by Client trigger fires once per service in the proposal. Wire that to an ad platform and a three-service engagement gets reported three times.
Ignition · the fix
What changes after the fix — Ignition
Bidding learns from signed engagements
Google Ads and Meta get the accepted proposal as the conversion, so campaigns chase prospects who become clients.
Each Ignition deal knows its ad
The click ID and campaign travel into Ignition with the lead, so you see which keywords bring your best monthly clients.
Fees reported the way you bill them
One conversion per accepted proposal, valued from its services, with recurring and one-off work kept apart.
Ignition · architecture
What Ignition actually lets you hook into
Ignition lists no Google Ads, GA4 or Meta integration, and its help docs describe no place to paste your own tags. The useful hooks are its events and APIs.
- 1
Zapier triggers on proposal status
Documented triggers include Proposal Accepted, Service Accepted by Client, Proposal Moved To Awaiting Acceptance, Proposal Marked as Lost and Proposal Revoked. Only Proposal Accepted should feed ad platforms.
- 2
Zapier actions to create clients and deals
Create Client and Create Deal let a form on your own site start the Ignition record, so the click ID never leaves your domain. We confirm which field holds it.
- 3
Ignition Forms via a public link
Submissions become a new lead or a pipeline deal. The docs mention no redirect, hidden fields or UTM capture, so attribution is saved before the click to the form.
- 4
Ignition API and Reporting API
Admins create each as an OAuth app in the Developer hub, one API per app. The Ignition API (early access, every plan) creates and updates records; the read-only Reporting API (Pro+ and Enterprise) is what we reconcile against.
- 5
Server-side sending to the ad platforms
Ignition sends conversions nowhere. A first-party container sends accepted proposals to Google Ads as offline conversions with hashed email, and to Meta's Conversions API.
Ignition · diagnose
Where Ignition tracking breaks, in diagnostic order
Start with what Google Ads calls a conversion today. When your site links out to an Ignition form, it's often just a click on that button.
- 01
Check what your primary conversion action really measures
A button click or page view in place of a submitted inquiry is the usual culprit.
- 02
Submit a test inquiry from an ad-tagged URL
Open the resulting Ignition deal and look for the click ID or campaign.
- 03
Count conversions on one multi-service proposal
Per-service triggers firing to an ad platform show up here.
- 04
Compare accepted proposals with reported conversions
Client by client, for one closed month.
- 05
Check values against the proposal
Flat values, or monthly fees reported as a single month, understate your retainer clients.
Ignition · prove
The QA evidence — Ignition
Run on a real inquiry and a real accepted proposal in your Ignition account, not a demo practice.
Source of truth
Ignition proposal records: proposals accepted by date, with client, services, billing type and fee
- One inquiry from an ad-tagged URL, with the click ID confirmed on the matching Ignition deal or client.
- One multi-service proposal accepted and reported as exactly one conversion.
- Value checked against the accepted services, recurring and one-off work kept apart.
- A lost and a revoked proposal confirmed absent from every ad platform.
- Meta Conversions API events confirmed in Events Manager with a shared event ID.
- Accepted proposals reconciled client by client against Google Ads and Meta over a closed month.
- Repeated 30 days later, and again when tax-season volume starts.
Ignition · free audit
What we check in the free audit
- Check what your primary conversion action really measures
- Submit a test inquiry from an ad-tagged URL
- Count conversions on one multi-service proposal
- Compare accepted proposals with reported conversions
- Check values against the proposal
Checked against
Ignition proposal records: proposals accepted by date, with client, services, billing type and fee
Free30 minutesNo obligation
Ignition · when not to buy
When you don't need this on Ignition
Plenty of firms use Ignition only for engagement letters and billing, with no ad tracking involved.
- If new clients come by referral and you aren't paying for ads, there's nothing for this to improve.
- If you sign a handful of new clients a year and can ask each one how they found you, a source note on the Ignition client does the job.
- If your proposals mostly go to existing clients for renewals and add-on services, retention reporting matters more than ad attribution.
- If your inquiry form already lives on your own site and the only fault is a mislabeled conversion action, that's a quick fix you can make yourself.
Ignition · what we deliver
The event map on Ignition
Inquiry captured on your site
Click ID and UTMs saved before the visitor leaves for an Ignition form, or the form moved onto your own page.
Deal created in Ignition
Lead conversion, sent once the deal exists, carrying the stored click ID and hashed email.
Proposal sent (awaiting acceptance)
Qualified-lead signal, fired from Ignition's awaiting acceptance status rather than a page view.
Proposal accepted
The primary conversion, one per proposal, valued from the accepted services.
Recurring vs one-off value
Monthly retainers and single-filing tax work tagged separately so reports and bids can weigh them.
Lost, revoked and existing-client proposals
Lost and revoked proposals logged, never counted; renewals and upsells to current clients kept out of acquisition.
Written guarantee
95%+ tracking accuracy
Measured against Ignition proposal records: proposals accepted by date, with client, services, billing type and fee. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Ignition questions, answered
Not directly. Ignition's integrations page lists no Google Ads, GA4 or Meta connection, so accepted proposals reach the ad platforms through its Zapier triggers or its API and a server container.
Ignition's help docs don't describe anywhere to add your own tracking code. Attribution is saved on your site before the visitor leaves, and conversions are sent from Ignition's events.
All three get tracked, but the accepted proposal is what Google Ads and Meta should bid toward. Inquiries and sent proposals act as earlier signals while volume builds.
Each accepted proposal is valued from its services, with recurring work tagged apart from single filings, so a January rush of returns doesn't pull budget from monthly clients.
Often the conversion action counts clicks on the button that opens your Ignition form. That count runs well ahead of real inquiries, let alone signed clients.
Yes, as long as the first inquiry carried the click ID onto the prospect's Ignition client record. We check that hand-built proposals attach to that client rather than a duplicate.
More on Ignition
- 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 Ignition, and what their bookings feed
- LeapLeap shows the window job your rep signed in SalesPro. Google Ads still thinks it was a form fill.
- Insurance ToolkitsYour ads send people to your Insurance Toolkits Lite Link. Google and Meta never see a policy.
- LeadsPediaGoogle counts every LeadsPedia post, but buyers only pay for sold leads
- Element451Inquiries pile up in Element451, but your ads can't say who applied
- HomebotConversion tracking for Homebot
- AnchorYour ads bring inquiries, but Google never sees who signs in Anchor
- AgencyBlocAgencyBloc conversion tracking: Google sees form fills, you get paid on in-force policies
- Rent ManagerGoogle Ads reports leads. Rent Manager can't tell you which ad filled the unit.
Free · 30 min
Find out which ads actually sign clients in Ignition
Free30 minutesNo obligation
