Route every conversion through a server you own.
Server-side Google Tag Manager, Meta Conversions API, TikTok Events API and Google Ads Enhanced Conversions, set up on your own subdomain.
Where conversions get lost
A browser pixel has to survive the visitor's browser before it reaches an ad platform. Three things stop it.
Ad blockers
Blocklists target the domains that pixels load from and report to. When the script never loads, the purchase never reaches the platform.
Safari cookie limits
Safari caps cookies set by JavaScript at seven days, and at one day for visits that arrive through tracked ad links. A returning customer looks like a new one, and the conversion loses its ad click.
Consent gaps
When a banner and your tags disagree about what was allowed, tags fire without consent or stay silent with it. Either way, the data your platforms receive is wrong.
Same checkout, two setups
Five events from one session. Switch between a browser-only setup and one routed through your server.
One checkout session, five events
| Event | Sent to | Result |
|---|---|---|
| view_item | google-analytics.comsst.yourstore.com | sent, cookie expires in 7 days200, forwarded to GA4 |
| add_to_cart | analytics.tiktok.comsst.yourstore.com | blocked by ad blocker200, forwarded to TikTok Events API |
| begin_checkout | googleadservices.comsst.yourstore.com | blocked by browser200, forwarded to Google Ads |
| purchase | connect.facebook.netsst.yourstore.com | blocked by ad blocker200, forwarded to Meta Conversions API |
| purchase | google-analytics.comsst.yourstore.com | 200200, forwarded to GA4 |
1 of 5 events arrived intact5 of 5 events forwarded from your subdomain
Illustration, not client data
Your site sends each event once, to a container on your own subdomain. The container forwards it to every platform through their server APIs, and the cookies are set by your server instead of a script.
What we set up
- Server-side GTMA server container on your own subdomain that receives events from your site and forwards them to each platform.GA4Meta Conversions APITikTok Events APIGoogle Ads
- GA4 server-sideGA4 collection routed through your server, with first-party cookies set by the server instead of a script.GA4
- Meta Conversions APIPurchases and leads sent to Meta from your server, deduplicated against the pixel with shared event IDs.Meta Conversions API
- TikTok Events APIServer-to-server events for TikTok, matched to the pixel so each conversion is counted once.TikTok Events API
- Google Ads Enhanced ConversionsHashed first-party customer data attached to conversions so Google Ads can match more of them to clicks.Google Ads
- Consent Mode v2Consent signals wired from your banner to every Google tag, including ad_user_data and ad_personalization.GA4Google Ads
- First-party cookies and custom subdomainTracking served from a subdomain of your own site, with identifiers set by the server.GA4Meta Conversions APITikTok Events APIGoogle Ads
- Offline conversion trackingEvents that happen in your CRM or backend, such as a qualified lead or a paid order, sent to your ad platforms through a webhook.GA4Meta Conversions APITikTok Events APIGoogle Ads
- Tracking auditA review of your current tags, events and consent setup, with a written list of what is broken and what to fix first.
We also connect any other platform that supports a Conversions API.
How we work
Scope
You send the details through the quote form. We reply with a scope and a price for your setup.
Access
We prepare the setup and collect the access we need: your tag manager, analytics and ad accounts.
Build
We set up the server container, tags and consent wiring in your own accounts, and test every event before it goes live.
Publish
The setup goes live on your site, and we confirm that each platform is receiving events.
Monitor
Two weeks of monitoring after launch, free of charge. If something drifts, we fix it.
For agencies: a tracking partner behind your brand
Your team owns the client relationship and the media. We build and maintain the tracking under your name, in your client's accounts, and stay out of the way.
Get a quoteCommon questions
What is server-side tracking?
Instead of each ad platform's script collecting data in the visitor's browser, your site sends events to a server you control. That server forwards them to GA4, Meta, TikTok and Google Ads through their server APIs.
Will it replace my existing pixels and tags?
Usually not. Most platforms work best with both: the browser pixel and the server event carry the same event ID, and the platform keeps one of them. We set up that deduplication as part of the work.
Who hosts the server container?
[ЗАПОВНИТИ: hosting options and who pays for them]
Does it work with Shopify and WordPress?
Yes. Both can send events to a server container. On Shopify the setup also covers checkout events, which need separate handling because Shopify hosts the checkout.
How does it handle consent?
The server only forwards what the visitor agreed to. Consent choices from your banner travel with each event, and Google tags read them through Consent Mode v2.
How long does a setup take?
[ЗАПОВНИТИ: typical timeline]
What shapes your quote
Every project is priced for its scope. Four things decide it.
Service
An audit of the tracking you have now, or a full server-side setup.
Platforms
How many destinations receive the data: GA4, Meta, TikTok, Google Ads and any others you run.
Events
How many events you need tracked, from a single purchase or lead to the full funnel.
Consent banner
Whether one is already in place. Every tag has to respect the visitor's choice, so it changes the work.
No prepayment
We start without an upfront payment, because we're confident in the work.
Request sent
Thanks, . Your request has reached us and we'll reply to .
- Service
- Platforms
- Events to track
- Consent banner
Preview mode: this request was not sent anywhere.