Server-side GTM · GA4 · Consent Mode v2
Server-side tracking setup with consent handled properly
In shortWeDevelop is a Romanian software company that sets up server-side tracking with GA4, server-side Google Tag Manager, Consent Mode v2 and platform APIs such as Meta Conversions API. It suits shops and lead-generating sites that spend on ads and no longer trust their numbers. Engineers implement it and validate the data against real orders or leads, and consent rules still apply: it improves data quality, not the right to collect.
At a glance
- Provider
- WeDevelop, a software company from Romania
- Clients
- Romania, the EU, the UK and North America
- Languages
- English and Romanian
- Invoicing
- EUR, GBP or RON
- Pricing
- Quoted after scoping, from your brief
- Contact
- office@wedevelop.ro
01Is this for you
When server-side tracking is worth setting up
Server-side tagging is a real improvement for some sites and an unnecessary cost for others. It tends to pay off when several of these apply.
- GA4, the ad platforms and your shop report noticeably different numbers.
- You spend enough on ads that weak conversion signals have a real cost.
- Ad blockers, browser cookie limits or consent choices are visibly cutting into your data.
- You want to decide exactly which data each platform receives.
- Offline sales or CRM stages should count as conversions, and browser tags cannot see them.
- Not a fit yet: your existing events are wrong, since the server will forward the same errors, or you have little traffic and no paid media. A clean browser set-up is cheaper and sufficient.
02What you get
What a tracking setup delivers
The tagging server is only one part. Most of the value lies in knowing what you measure and proving that it is right.
Audit
Double counting, missing conversions, cross-domain breaks on payment redirects and consent behaviour, checked in the live set-up.
Measurement plan
The events and conversions that matter, defined once in a document that every tool and every colleague can follow.
Server container and consent
A first-party endpoint under your domain, on our EU infrastructure or yours, with Consent Mode v2 connected to your consent platform.
Validation and handover
New numbers compared with real orders or leads, then documented so your team knows what fires, when and why.
03Which option
Client-side, server-side or a direct API: what to choose
Most of the marketing around server-side tagging treats it as an upgrade everyone needs. In practice there are several set-ups, and the simplest one that answers your questions is the right one.
| Set-up | Best when | Trade-off |
|---|---|---|
| Client-side tags only | A small site with little ad spend and a simple funnel. | Exposed to blockers and browser limits, and each tag runs in the visitor's browser where it can slow the page. |
| Server-side GTM | Meaningful ad spend, several platforms, and a need to control what each one receives. | A server to host, monitor and pay for, with more set-up, and it still relies on good events from the site. |
| Browser plus server events | The usual practical choice when using Meta Conversions API or enhanced conversions alongside tags. | Both routes must be deduplicated, or sales get counted twice. |
| Direct API from shop or CRM | Conversions are confirmed in your backend, including offline ones. | Engineering work on your own systems, and consent status has to travel with the data. |
| Self-hosted Matomo | Data has to stay on your own infrastructure, as in some privacy-sensitive organisations. | Less reporting depth and weaker ad platform integration than GA4. |
Moving tags to a server does not create better data by itself. An event that is wrong in the browser is wrong on the server too, which is why the audit comes first.
04Cost
What decides the cost of server-side tracking
There are two costs to plan for: the one-off set-up, and the running cost of the tagging server. These factors move the first; traffic moves the second.
| Factor | Why it matters |
|---|---|
| Data layer quality | Clean events from the shop make the job simple. Without a usable data layer, one has to be built first on your platform. |
| Number of destinations | GA4, Google Ads, Meta and others each need mapping, testing and deduplication. |
| Consent starting point | A working consent platform integrates quickly, while a missing or misconfigured one adds work and a review of what your legal adviser requires. |
| Hosting | The tagging server runs on our EU infrastructure or yours, with an ongoing cost that grows with traffic. |
| Offline and backend data | Importing CRM stages or confirmed orders adds integration work on your own systems. |
| Reporting | BigQuery export, data modelling and Looker Studio dashboards are optional, and they are a piece of work on their own. |
You receive the estimate after the audit, because the condition of the current set-up is what separates a straightforward job from a repair project.
05How to start
From access to validated numbers
Duration depends on the data layer, the number of destinations, the consent starting point and how quickly changes can be deployed on your side, so the timeline is set after the audit.
Grant access
Analytics, tag manager and ad accounts, plus the site's stack and the name of whoever deploys changes.
Audit
This usually reveals double counting and missing conversions, and it typically explains the gap with your shop within days.
Measurement plan
The conversions that matter and their value, agreed before any tag is moved.
Implement on staging, then production
The server container, consent integration and forwarding to each platform, tested before going live.
Validate against real data
Real orders or leads are compared with the new numbers before anything is optimised on them.
06For an accurate quote
What to include in your tracking request
We can size the job quickly if we know how your data travels today.
- The site URL, platform and who deploys changes.
- The conversions that matter, and what each is worth to you.
- Which ad platforms you use, and roughly how much depends on them.
- Your consent banner and any privacy requirements from legal or from clients.
- Where the true numbers live: shop, CRM or ERP.
- Any payment redirects or extra domains in the customer's journey.
07Questions
Questions buyers ask about server-side tracking
How much does server-side tracking cost?
Set-up cost follows the state of the data layer, the number of platforms and the consent work, so we quote after the audit. Allow for a second, ongoing cost too: the tagging server has to be hosted and monitored, and that grows with your traffic.
How long does a server-side GTM setup take?
There is no fixed duration, because it depends on whether a usable data layer exists, how many destinations need testing and how quickly changes can be deployed. The audit usually explains the data gap within days, and you get a timeline for the rest after that.
Does server-side tracking get around ad blockers and consent?
It must not be used to get around consent: if a visitor refuses, that choice still applies on the server. Where consent exists, it can reduce losses from browser restrictions and some blockers, but the amount varies by site and audience, so nobody can honestly promise a figure.
Is server-side tracking GDPR compliant?
It can be, but not automatically, because GDPR applies to the processing and not to where the tag runs. You need valid consent, clear information and control over what goes to each platform, which server-side makes easier. Your legal adviser or DPO should review the final data flows.
Will server-side tracking increase our conversions?
It does not create sales; it changes how many of your existing sales you can see. Better signals can help ad platforms optimise, but the size of any improvement cannot be promised in advance. We validate against real orders or leads so you know the numbers are correct.
Do we need server-side tracking for a small site?
Probably not, if you spend little on ads and your funnel is simple. A correct GA4 and tag manager set-up with proper consent will answer most questions, at no server cost. Reconsider it when ad spend grows or when several platforms depend on your conversion data.
Does it work on Magento, WooCommerce or a custom site?
Yes on all three, and those are platforms our engineers work on regularly, so a missing data layer can be built rather than just reported. Hosted platforms can restrict what may be changed, and we would confirm that during the audit.
Do the projects on this page use server-side tagging?
Not as described in their case studies. They show consent and tracking work with Google Tag Manager and cookie consent, on a maintained Magento store and on a public hospital website. We would rather state that plainly than stretch them into something they are not.
08Related projects
Work we have done in this area
Optimum Medical — medical consumables store on Magento 2.4, maintenance
Online store for medical consumables and surgical supplies — needles and syringes, wound care, sutures, examination, surgery, emergency — with fast delivery across Romania, on Magento 2.4 with the Martfury theme. We keep it patched, compatible and quick.
Magento 2.4Martfury theme (MageBig)PHP 8MySQLView case studySovata-Niraj Hospital — public hospital website with transparency documents
Website for a public hospital: management and governance pages, regulations, medical services by department, patient information, transparency and financial documents, declarations of assets, and contact and appointment forms.
WordPressContact Form 7Formidable FormsDocument libraryView case studyRequest a quote
Describe what you need. The enquiry goes to our team, and we reply by email with the next step.