Meta and Google Ads report fewer purchases than my CRM
Blockers and browser limits drop part of the events. We duplicate events from the server and reconcile them with your CRM, so the gap is visible in numbers.
Server-side tracking: your ad platforms see the sales they drive
Ad blockers, Safari and cookie limits hide part of your conversions from Google and Meta. We move event sending to a server you own (sGTM and Meta CAPI), so the algorithms get fuller data. It is the link between site and customers: cleaner data makes ads more precise, and your CRM and automations work from real events.
Quote and schedule after your brief
Who it's for
- Online stores spending on Google Ads and Meta Ads
- Lead-gen sites where the CRM shows more leads than the ad account
- Businesses that want to send real CRM sales back to ad platforms, not just clicks
- Owners who do not trust their analytics numbers and want to verify them
Problems we solve
Ad algorithms learn from incomplete data and spend budget in the wrong places
Algorithms optimise for the events they see. Server events with correct parameters give them a fuller picture.
I worry that one purchase is counted twice
We set up deduplication with a shared event_id, so a browser event and a server event count once. We check it in Meta Events Manager and GA4 DebugView.
I am wary of sending personal data to ad platforms
A server gives you control: we decide which fields go out and hash emails and phone numbers before sending. User consent is built into the tag logic.
What's included
- Audit of current tracking: GTM container, pixels, GA4, events, duplicates
- Server-side Google Tag Manager container (sGTM, a tag manager running on your server)
- Cloud setup (Google Cloud Run or Stape) under your own account
- Custom tracking subdomain, so requests come from your own domain
- Meta Conversions API (CAPI, sending events to Meta straight from the server)
- Server-side events to GA4 and Google Ads
- Deduplication and parameters: value, currency, hashed email and phone
- Testing in Meta Events Manager, GA4 DebugView and Tag Assistant
- Handover document and access: everything sits on your accounts
Choose the scope
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
01
Start
One site, one ad platform, simple events
- Audit of current tracking
- SGTM on your cloud account
- Tracking subdomain
- Meta CAPI or server-side GA4, your choice
- Event testing
02
Standard
A store or lead site advertising on both Google and Meta
- Everything in Start
- Meta CAPI and server-side GA4 together
- Google Ads Enhanced Conversions
- Deduplication and hashed customer data
- Video walkthrough and an agreed period of support after launch
03
Advanced
Several sites, or a funnel with a CRM and offline sales
- Everything in Standard
- CRM stages sent back to ad platforms (offline conversions)
- Several domains or languages in one server container
- Reconciliation report: ads, GA4, CRM
- Pilot with a KPI agreed before we start
How we work
Brief and requirements
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
Pilot KPI
Before we start, we agree what success means. For example: every CRM purchase has a matching event in the ad account, with no duplicates.
Server and subdomain
We create the cloud account in your name, deploy sGTM and connect the subdomain. You own all access under the agreed terms.
Tags and events
We configure CAPI, GA4 and Google Ads, then add deduplication and the required parameters.
Verification and handover
We test on real orders, compare against your CRM and hand over documentation. Payment is made in stages.
Scope and limits
- We do not promise ad numbers will match your CRM order for order: some users are invisible to any tracking setup.
- We do not promise more sales. We fix the data; ad results also depend on your offer, creatives and budget.
- We do not bypass user consent. If someone opts out of tracking, we respect it.
FAQ
What is server-side tracking in plain words?
Normally a pixel sends data from the visitor's browser straight to Meta or Google, and a blocker can cut it. Here the browser sends data to your server, and the server passes it to ad platforms. Fewer events get lost.
How much does the server cost to run?
We prepare a quote after reviewing your brief and requirements. A first stage can cover: audit of current tracking; sGTM on your cloud account. Scope, payment and schedule are agreed before work starts.
Do I need this if my ad spend is small?
With a small budget and few events, a standard setup may be enough. We will tell you that honestly during the audit instead of selling you extras.
What do you need from me?
Access to GTM, GA4, Meta Business and Google Ads, plus your hosting or DNS for the subdomain. The Advanced package also needs CRM access. You grant the access, and everything stays on your accounts.
Will this break my current setup?
No. We work in test mode first and switch nothing off until the new events are verified. The existing pixel stays until we confirm there are no duplicates.
Why is this cheaper than an agency?
We compare implementation options and agree on the scope. An engineer still configures and tests every event by hand. We prepare a quote after your brief.
Start with your task
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.