Sales sent from your systems
Purchases and payments are sent from your CRM or payment provider to Meta and Google, server to server, including sales closed on a call or paid by invoice.
Done whenA test sale shows in each ad platform’s event view.
Conversion tracking that counts each real sale once
Your CRM and payment provider know who actually bought. We send those sales to Meta and Google, once each and with consent respected.
Included in the standard lead-to-customer system. On its own, priced after a setup check.
Before
- Sales closed on a call are never counted
- One sale counted twice: browser and server
- A payment plan counted as six sales
- Nobody checks ad numbers against the bank
After
- Every sale sent from your CRM or payments
- One event ID per sale, so it counts once
- The plan counted once, at its real value
- Ad reports checked against your records
What we set up
Five parts, each with a test that says it is done.
Counted once
Each sale carries one event ID, so a browser event and a server event for the same sale are counted once, and a payment plan is not counted as several sales.
Done whenThe test sale shows once, not twice.
Consent respected
Events follow the choices people make on your cookie banner. Where consent is needed and has not been given, nothing is sent.
Done whenA visit that rejects cookies sends no ad events.
Checked against the CRM
We compare what the ad platforms received with what your CRM and payment provider recorded, and fix the gaps.
Done whenThe test sales match the CRM, sale for sale.
Watched
If events stop arriving or start failing, we get an alert and fix it before the ad platforms learn from bad data.
Done whenA deliberately broken event raises an alert.
Health businesses in the US
Ad pixels do not go on logged-in pages, intake forms, booking or checkout on a health site, and sending the same events from a server does not change that.
Where a health business wants to measure ads, the route regulators describe is a data platform that signs a business associate agreement (BAA) and removes identifying details before anything reaches an ad platform. We plan this with your lawyer. Read more on the telehealth page.
How it works
Questions people ask
Will this improve our ad results?
We cannot promise ad results. What changes is what the ad platforms learn from: real sales from your systems, counted once, instead of form fills and page views.
Is server-side tracking a way round cookie consent?
No. Sending an event from a server needs the same lawful basis as sending it from the browser. We connect the events to your consent choices.
Which ad platforms do you send to?
Meta and Google.
We sell health services in the US. Can you track our sales?
Not with ad pixels on your intake, booking or checkout pages, and not by sending the same events from a server. There is a safer route through a data platform that signs a BAA and removes identifying details first. See the telehealth page.
Is this included in the lead-to-customer system?
Yes. Ad conversions are one of the seven parts of the standard system, from £6,000. On their own, we quote after the setup check.
See what your ad platforms really count
A 30‑minute call where we compare what your ad platforms report with where your sales are recorded. There is nothing to pay and nothing to sign.