iubenda Server-Side Tracking · Coming soon
Better data. Higher ROAS. Cleaner consent.
Recover the conversions your ad platforms aren’t seeing, lift ad performance, and keep the legal side clean. Fix your tracking in minutes, without engineering effort or cloud infrastructure.
Early access is coming soon. Some features roll out through general availability.
Built on the platform 2.5 million websites already trust
Startups, scaleups, enterprises. Whatever you’re building, you’re in good company.
Your marketing data has gaps, and they’re only getting worse
This is hurting your ads performance. Your campaigns optimize on partial data, and your ROAS quietly pays for it.
Browsers are restricting cookies
Safari and Firefox already block third-party cookies. Chrome is following. First-party cookies have shorter lifespans.
Ad blockers strip tracking scripts
In parts of Europe, roughly 1 in 3 people browse with an ad blocker running. Their browser drops your tracking scripts before conversions are captured. Source: Backlinko.
Consent gaps shrink your trackable audience
Users who reject cookies leave your campaigns optimizing on a fraction of real conversions, missing key buyers.
No alerts when conversions disappear
Your acquisition costs rise and conversions fall, with no clear cause. The data loss happens silently between your site and your ad platforms.
Recover your marketing signal, with consent enforced
Most server-side tracking accepts whatever consent signal it’s handed. We verify every event before it reaches your ad platforms.
Consent enforced
at the source
We check every event against a valid consent record before it leaves your server. If a visitor declined, we don’t send anything. If they consented, the signal goes through. Works with any consent tool.
See more of your traffic, including non-consented visitors
Two things your ad platforms can’t see today: the events ad blockers hide, and the traffic that declined consent. iubenda recovers the first and shows you the second, aggregated and anonymized.*
Set it up in minutes,
not weeks
No infrastructure to spin up, no engineering ticket. Turn on server-side tracking from the iubenda dashboard in minutes.
*Available above a minimum conversion volume to preserve privacy.
One product, three ways to use it
Whether you’re already on iubenda, running marketing campaigns, or managing client sites, server-side tracking fits into how you already work.
FOR MARKETING AND ANALYTICS TEAMS
Recover the signal, no consent gaps
Send consented events to your ad platforms even when browsers and ad blockers strip the client-side ones. Your retargeting audiences stay accurate, and your campaigns optimize on the real signal. We enforce consent by default, so your privacy team doesn’t need to catch up later.


FOR AGENCIES AND CONSULTANTS
Consent-first tracking for all your clients, from one dashboard
Manage server-side tracking for every client from one place. Offer consent-first tracking as a service, not a custom build per account.
Consent-enforced, not just consent-aware
Other tools trust the signal they’re given. We check every event ourselves, block anything without valid consent, and apply the right rules per visitor. That doesn’t change when you bring your own CMP.
Standalone SST tools
Consent-aware
Accept whatever consent signal your CMP sends. No enforcement of their own. If the signal is wrong or late, events still fire.
CMP-native SST
Consent-enforced, one CMP
Consent is enforced, but only if you use their CMP. Different tool, different vendor lock-in.
iubenda
Consent-enforced, any CMP
We enforce consent at the source. Native to iubenda’s Privacy Controls and Cookie Solution. Integrates with any other CMP too. No lock-in.
How we’re different
How iubenda’s approach compares with the most common server-side tracking setups on the market.
iubenda
Other providers
Setup
Minutes, no setup fee.
Days to weeks, often includes a setup fee.
Technical expertise needed
None. Guided setup from the dashboard.
Cloud setup, custom code, engineering time.
Visibility into non-consented traffic
Shows you the traffic that declined consent, aggregated and anonymized.*
Not surfaced. You only see consented events.
Consent enforcement
We block events without valid consent by default, and only process consented data.
Events are sent without properly checking consent.
Multi-jurisdiction logic
Applied per user based on where they are. Built in.
Customer configures GDPR, CCPA, LGPD separately.
Audit trail
Consent state on every event. Signed records ship with beta.
Limited or no per-event consent record.
Data residency
Runs on EU infrastructure. No US provider in the processing path.
Often US infrastructure, or EU regions on US cloud.
*Available above a minimum conversion volume to preserve privacy.
Why iubenda?
Fast to turn on, cleaner data to your ads, and 15 years of privacy experience behind it.
Better conversion data,
on proven infrastructure
Recover the signals browsers and ad blockers strip. Your ad platforms get the data they need to optimize, and your ROAS follows.
Go live in minutes, not weeks
No cloud infrastructure, no engineering ticket. Set up server-side tracking from one dashboard and start sending events.
2.5M+
websites and apps using iubenda
100+
countries where our clients operate
27
languages supported (no AI translations)

Patrick A.
Hellenic Technologies

“At Hellenic Technologies, iubenda has been essential for delivering advanced compliance solutions to our clients. Their tools for server-side tracking with prior consent blocking help us meet strict GDPR standards. Integrating their consent management with our custom GTM implementations ensures no data is collected without explicit consent, keeping our clients secure and compliant.”
Common questions
What is server-side tracking?
Instead of running in a visitor’s browser, server-side tracking processes events on a server you control, typically through a first-party subdomain like data.yoursite.com. This makes your data collection resilient to ad blockers, cookie restrictions, and browser privacy updates.
What are the benefits of server-side tracking?
You recover conversion data lost to ad blockers and browser restrictions, rebuild retargeting audiences your ads had stopped seeing, get more accurate attribution in Meta and Google, and reduce page load impact. Because your ad platforms see the full conversion picture, they shift budget toward campaigns that actually work, improving ROAS and lowering your acquisition costs.
How is this different from server-side GTM or tools like Stape?
Server-side GTM moves tags to a server, but stops there. You still bring your own consent tool, wire it up manually, and pick your own infrastructure. Tools like Stape and JENTIS package the infrastructure layer, but the consent integration is still bring-your-own. iubenda closes both gaps. Consent is integrated from the start: your rules decide which events we forward, no integration code, no separate vendor. And instead of a server-side GTM container you run and maintain, we route events through a first-party gateway, so there’s nothing new to host.
Does it work with my current CMP?
Yes. iubenda’s Server-Side Tracking is CMP-agnostic by design. It’s the natural fit if you already run iubenda’s Privacy Controls and Cookie Solution, but it also plugs into any other consent management setup. The difference from standalone server-side tools: we don’t just accept your CMP’s signal, we enforce it at the source, sign it, and apply multi-jurisdiction rules per visitor.
How does server-side tracking work with GDPR?
Your data is only forwarded once you’ve collected valid consent. Here’s the chain: a visitor lands on your site, we capture consent and tie it to a verifiable record. When that visitor takes an action (a purchase, a signup), we check the consent record before sending anything to your ad platforms. If the visitor denied marketing consent, we don’t forward marketing events. If they consented, we forward the event with the consent record attached. That gives you a documented audit trail for every event, which is what GDPR and the ePrivacy Directive require for lawful processing.
How do you make sure only consented events are sent?
We check every event against a valid consent record before it leaves your server. If a visitor rejected marketing, no marketing event goes out. If they consented, the event is sent with a timestamped consent record attached. It’s not a policy or a promise, it’s a check every event has to pass.
Will it work on my current setup?
Yes. iubenda’s Server-Side Tracking integrates with your existing consent setup, so you don’t need to rebuild anything. The consent state your banner collects controls which tracking events we process and forward. Works with iubenda’s Privacy Controls and Cookie Solution, and with any other CMP too. No lock-in, no rebuild.
Which platforms will be supported?
At launch: Google Ads Enhanced Conversions, LinkedIn Conversions API, Meta Conversions API for Facebook and Instagram, Pinterest Conversions API, and TikTok Events API. More platforms after that.
Can I use this for my clients?
Yes. The product is multi-tenant by design. You’ll be able to provision and manage server-side tracking for every client from a single dashboard, with API access for automation. Agency and partner pricing will be available.
When will it be available?
We’re planning early access soon. Some CMP integrations and features roll out gradually through general availability. Sign up and we’ll notify you as your spot, and each feature, opens.
Your tracking data is disappearing. We’re building the fix.
We open soon. Sign up now to get:
Priority access when we open
We’re opening iubenda Server-Side Tracking to a limited group before the public launch.
A voice in what we build
Help us shape how features work, what to improve, and what to build next.












