Tracking implementation
The Meta Conversions API, Enhanced Conversions for Google Ads, server-side tagging or the list from an audit: we build it, from website and app to server, and stay on top of it after launch.
What we do
We build new setups and extend existing ones. Everything ties in with your goals, and is set up so the numbers add up and someone else can still follow it later. After hundreds of setups we know which choices come back to bite you, and we make sure it keeps running well after launch.
The platforms and tools we work with, per part. If yours isn't here, just ask.
Analytics
Events and conversions that measure what counts for your business.
Conversion tracking
Conversions that add up, so your campaigns steer on the right signals.
Server-side tagging
More control over which data goes where.
Consent
Measuring within what your visitor allows.
In your situation
For websites and apps alike, on standard platforms, custom and headless builds. What differs is mostly your type of business:
Online shops
Your measured revenue has to match your backend. So we measure the purchase from the order itself instead of from the browser: a thank-you page that is closed or reloaded changes nothing, and item, shipping and discount data come along. Then we put your real orders next to what your analytics and ad platforms recorded, so you can see what is still missing.
Multi-domain sites
Several shops, countries or brands on one stack need a setup that keeps the overview. We set up one server container for all your domains, and each domain sends its data first-party through its own path on its own domain. Every domain keeps its own consent setting and conversion IDs, so the data per site or brand stays apart. When a visitor moves from one domain to another, they stay recognisable. And one container instead of a separate setup per site saves maintenance: you make a change once.
Lead generation
A filled-in form is not a customer. We connect the lead to your CRM and send the step that matters, such as a quote or a signed deal, back to the ad platforms.
Ticketing and events
The purchase often takes place in the ticketing provider's system, not on your own site. We pick the order up there and send it server-side to your analytics and ad platforms, with the right source attached.
SaaS and subscriptions
Often you measure the trial, while the value only appears at the first payment. We measure the sign-up straight away and send the payment back later as an offline conversion, so your ad platforms optimise on revenue instead of sign-ups.
Apps
In an app you measure with an SDK instead of a tag, and users often move between website and app. We make sure web and app give one picture together, with the same events and the same conversions.
“Excellent service and perfectly configured server-side tracking Freek from New North Digital set up the complete server-side tracking for Victoria Valenza in Stape and Google Tag Manager, and I am extremely pleased with the result. The implementation was executed correctly down to the last detail, clearly explained, and fully tailored to my setup. Since the optimization, my tracking has become noticeably more accurate and consistent. The data quality has significantly improved, allowing Meta and Google to optimize much better—resulting in a significantly higher ROAS on my campaigns. In short: professional, knowledgeable, and highly effective. Highly recommended if you seriously want to improve your tracking and advertising performance.”
Gert Jan GombertVictoria Valenza01 / 04What you get
Tracking audit
Not sure what you need, or where the problem is? Then start with an audit. That way we know what is there and can give you the best advice for an implementation that fits.
How it works
Start
Week 1Together we set down what you want to measure and why, and arrange access.
Build
Week 1–2We set up your tracking, on your website or in your app, and server-side.
Test and launch
Week 3–4We test every tag and every event, set up consent and publish.
Handover
Week 4You get documentation of what is there and why, and we hand it over to your team or agency.
Settle in
Month 290-day programmeThe first weeks of real traffic. Monitoring runs from launch: if a trigger behaves differently in production than in testing, we see it and fix it.
Review
Month 390-day programmeWe go through what happened, what we fixed and where your tracking stands.
Frequently asked questions
What's the difference between single work and the 90-day programme?
As single work we build what you need, such as an extra channel on an existing setup, and deliver it. The 90-day programme is a complete setup: server-side Google Tag Manager, Google Analytics 4, consent and two ad platforms. After launch we stay on for two more months, fix what goes wrong and close with a review.
Do I need an audit first?
Usually, yes. With an audit it's clear what is there, what goes wrong and what needs to change, and we don't build on a foundation that doesn't hold. If the question is already clear, such as adding a channel to an existing server-side setup, we start straight away.
Can I add a single channel on its own?
Yes. If your setup is already in place, we also add a single ad platform, such as Meta, TikTok or Pinterest.
Do you work with our own developers or agency?
Yes. We agree on what they need to deliver, such as events in the dataLayer, and test together before it goes live.
Related cases
All casesQuestions, or ready to start?
Should it keep adding up?
Every site change can hit your tracking. With monitoring we see it within the hour.





