Service
GA4, server-side tracking and Conversions API setup
We build and test GA4, Google Tag Manager, browser and server-side conversion tracking for agencies and brands that need dependable measurement. We connect the event model to advertising platforms and, where available, CRM outcomes, so optimization follows the right signal.
The work behind the service.
Server-side tracking is not a reason to collect more personal information. It is a way to control how approved events are processed and delivered. We start with the actions the business actually needs to measure and the consent requirements around them. The technical design follows those constraints rather than treating privacy as a final checklist.
The browser and server need to describe the same event consistently. When both send a purchase or lead, a shared event identifier helps the receiving platform deduplicate it. Without that check, a successful installation can inflate results. We test real submissions and compare the event record against the action that produced it.
A working event is not the same as a useful conversion. Form starts, page views and accepted enquiries have different meanings. We distinguish them in the event model and decide which should be used for reporting or bidding. CRM feedback can add a quality layer, but only when the sales process produces a dependable record.
What's included.
- tracking audit
- GA4 event model
- GTM web and server containers
- Meta Conversions API
- Google enhanced conversions
- CRM offline conversions
- deduplication testing
GA4 and Google Tag Manager setup.
A GA4 property can be running and still tell you very little. Common problems include key events that count the wrong action, duplicate tags, internal traffic in the reports, missing consent settings and a data retention period left at its default.
We review what's there and agree on the actions that matter, then build a clear event plan in Google Tag Manager. We also check that GA4, Google Ads and your other platforms are counting those actions in a way you can explain when their numbers differ.
What server-side tagging does.
With browser tracking, tags run in a visitor's browser and send data directly to each platform. With server-side tagging, data can go first to a server you control, which then passes approved events along.
That gives you more control over what gets sent and where. It can also make delivery more reliable in some situations. It adds hosting costs and more to maintain, and it doesn't remove consent requirements, so we recommend it when those benefits justify the work.
Meta Conversions API.
The Meta Conversions API sends events from a server to Meta, usually alongside the browser pixel. When both send the same event, a shared event ID lets Meta count it once.
It's common to find a setup that looks healthy and isn't. Events may be deduplicating poorly, sending the wrong action or coming from a connection nobody on the team knew about. Before saying where server events come from, we check the dataset's connection settings in Events Manager and every outbound request on the live page. Then we test real actions from start to finish.
Enhanced conversions and offline conversions.
Google's enhanced conversions and Meta's matching parameters can use hashed customer information to improve how conversions are matched. Used properly, with consent, they can give platforms a better signal.
Offline conversions go a step further by sending back what happened after the lead, such as a qualified status or a sale. That helps platforms look for the people who actually become customers. It only works if your CRM records those outcomes reliably, so we check that first.
Common tracking problems we find.
- the same conversion counted twice
- a page view or form start counted as a lead
- thank-you pages that can be reached without submitting
- test traffic mixed into live data
- forms that changed and stopped firing events
- pixels or datasets owned by an account nobody can access
- consent banners that don't actually control the tags
- sensitive information sent in URLs or event parameters
How it works.
- 01
Audit the existing signal
We inspect the website, tag containers, platform events and available CRM records. We identify duplicates, gaps and test traffic. The audit ends with an agreed event map, not a list of every possible interaction to collect.
- 02
Design the event model
We define names, parameters and consent behaviour for each required event. We decide what belongs in the browser and what belongs on the server. Access requirements and hosting dependencies are included in the scope.
- 03
Build the delivery paths
We configure the agreed web and server containers, platform integrations and offline conversion connections. Credentials and permissions stay controlled. We document where each event originates and how it reaches its destination.
- 04
Test and deduplicate
We submit real test actions and inspect the receiving event records. Browser and server events are compared using their identifiers and timestamps. We check consent paths and confirm that a conversion cannot be created by merely opening a form.
- 05
Hand over and monitor
We provide a readable event map and operating checks. Your team knows how to confirm a recent event and where failures will be visible. After launch, we review the signal before treating a change in reported conversions as a campaign result.
Proof from the work.
For a Quebec health clinic, through an agency partner, we resolved a permissions blocker and shipped verified browser and server-side tracking for a paid social pilot. Client performance figures are not published.
- Quebec health clinic: browser and server-side tracking, verified end to end before launch
How we price it.
We bill hourly and set the scope in hours. Strategy and advisory are CAD $175/h. Media management and execution are CAD $110/h. We separate those kinds of work in the estimate so you can see what is being bought, rather than hiding them inside a percentage of spend.
We agree on the deliverables, dependencies and review points before starting. If new work appears, we discuss the hours before expanding the scope. Engineering builds, hosting, software subscriptions, creative production and advertising budgets are identified separately where relevant. We confirm the applicable engineering rate in the scope rather than assigning a media rate to a technical build.
You can engage one discipline without buying the others. A tracking correction does not require ongoing media work, and a media engagement does not require a website rebuild. We recommend a sequence only when the evidence shows a dependency. The estimate makes that relationship visible, so your team can decide what to do now and what can wait.
We also agree on how progress will be reviewed and how hours will be reported. Your team should be able to connect the time used to the work delivered. When an access issue or an approval blocks delivery, we explain the dependency rather than letting it disappear inside an open-ended engagement.
Questions before we start.
Do you offer GA4 setup and audits?
Yes. We can audit an existing GA4 property, build a new event plan and fix what's wrong. You can engage us for that alone, without any media work.
What is the difference between GA4 and Google Tag Manager?
GA4 is the analytics tool that stores and reports on data. Google Tag Manager is where you manage the tags that send data to GA4 and other platforms. They do different jobs and are usually set up together.
Why don't GA4 and Google Ads show the same conversions?
They can use different attribution rules, counting methods, time zones and conversion definitions. Some difference is normal. We check whether the gap makes sense or points to a real tracking problem.
Is server-side tracking worth the cost?
It depends on your data needs, ad spend and technical setup. It's useful when you need more control or better delivery and can maintain it. Some businesses are well served by a clean browser setup, and we'll say so.
Can you fix tracking on a site another team built?
Yes, with the right access. We'll need the tag containers, the ad accounts and sometimes a developer's help for changes to forms or code.
How do we know the tracking is working?
We test real actions, then check the receiving platform's event record against what actually happened. You also get an event map and simple checks your team can run afterward.
What is server-side tracking?
Server-side tracking processes agreed events through a server before sending them to measurement or advertising tools. It gives more control over event delivery and data handling. It does not remove consent requirements or make every conversion observable.
Do I need it if I already have the Meta pixel?
A pixel alone may be enough for some needs, but it does not establish that the event model is correct. We audit the signal first. Browser plus server delivery is useful when it improves reliability and can be deduplicated properly.
How long does a build take?
The timing depends on access, the website, consent setup and any CRM connections. We scope the build after inspecting those dependencies. Permissions and custom forms can take longer than the container configuration itself.
Does it help with ad blockers and iOS?
It can improve delivery in some situations, but it is not a way to bypass a person’s privacy choices. We test the permitted paths and keep consent requirements in place. We do not promise complete recovery of events lost to blockers or device restrictions.
Related services.
Notes from the work.
Fix tracking before you raise the budget
Every account we audit that plateaued at scale had the same root cause. The platform was optimizing toward a number nobody trusted.
Rebuild the number from its inputs
Four Quebec projects turned on a number that did not hold up. None were caught by looking harder at a slide.
What server-side tracking is and when it's worth it
Moving tags to a server gives you control over what data leaves your site, and that control comes with a hosting bill and someone who has to look after it.
Start a conversation.
Tell us what you are trying to move. We will tell you which disciplines are worth engaging, and which are not.