datalayer
The website's own code signals when something happened: form, call, booking, purchase.
Under its own name, with clean data, not guessed from button clicks.
GA4, GTM and server-side tracking: every business event under its own name, on your own domain, with consent.
From event to destination
It means every business event, form, call, booking and purchase enters the tracking under its own name, and a server running on your own domain forwards it to Google and Meta.
So GA4 and the ad platforms see real customers, not clicks. Consent is respected throughout.
Consent Mode v2
Four signals decide: ad_storage, analytics_storage, ad_user_data, ad_personalization. By default everything starts as denied, and events without consent are not forwarded to the ad platforms.
Server-side tracking does not bypass consent: the signals apply on the server too.
Four links, from the first click to the ad platform. We test every one of them before handover.
The website's own code signals when something happened: form, call, booking, purchase.
Under its own name, with clean data, not guessed from button clicks.
The browser-side Google Tag Manager collects the event and passes it to your own server.
Consent is handled according to Consent Mode v2.
Server-side GTM on Google Cloud, on your own subdomain, for example data.yourcompany.com.
So the data is first-party, and browser restrictions do not cut it off.
GA4 key events, Google Ads conversions, Meta Conversions API, TikTok Events API.
Every platform receives the same event with the same ID, so nothing is counted twice.
We do not guess from clicks, the code tells us when something happened.
| Event | When it fires | In GA4 |
|---|---|---|
| generate_lead | form accepted by the server | key event |
| booking_complete | successful appointment booking | key event |
| purchase | paid order | key event, with value |
| click_to_call | click on a phone number | event |
| file_download | download | event |
We test every event end to end
Before handover we run through every event: GA4 DebugView, Tag Assistant, Meta's event match quality and Google Ads conversion diagnostics. Every test is listed in the handover report.
The tracking accounts are in your name, we receive access to them.
Sized for your traffic
The server-side GTM runs in your Google Cloud project, its fee depends on traffic and is charged to your project. Low traffic needs few server instances, high traffic needs more; we size it to your traffic during setup.
Details on the server-side conversion tracking page.
The price of the tracking setup depends on the number of events, the destinations and the technical background of the website. The server fee is separate and is charged to your Google Cloud project. After an assessment we send a precise quote.
Tell us what counts as a conversion for you and where you advertise, and we will get back to you with a quote. Work starts once we have an agreement.
We built this software and use it every day ourselves.
Cookie consent with Google Consent Mode v2: the banner asks for consent per service, passes the decision to Google, Meta, Microsoft, TikTok and Amazon, and logs every decision.
Free Google Consent Mode v2 checker: in 30 seconds it shows whether your website tells Google about your visitors’ consent.
Free cookie checker: in 30 seconds it shows which cookies land on a visitor’s device before they consent.
Our own project hub where clients follow and approve the work: post copy, photos and videos in one place, and approved posts go live on Facebook and Instagram from here.
Tell us how we can help and we will get back to you within one working day.
A service, reference, article, film or software