Your compliance questions answered: What data Tiide stores

Server-side tracking sounds technical and complicated. It isn't – not the way we run it anyway.

But when your users’ data is involved, you should know exactly what Tiide sees, what it stores and how that data is handled.

Here are the facts.

The problem we're solving

Ad blockers and browser privacy changes mean a significant amount of conversion data never makes it to your ad platforms.

Tiide helps recover that missing data through managed server-side tracking.

But “server-side” raises a fair question: if data is passing through Tiide’s infrastructure, what does Tiide actually see – and what gets stored?

What Tiide stores

For each user, Tiide stores just three things:

• Browser name
• Whether they’re using an ad blocker
• Number of requests

That’s it.

No names. No email addresses. No raw IP addresses. No personally identifiable information at all.

We store only what’s needed to identify and report on tracking gaps, helping recover conversions your ad platforms would otherwise miss and giving you a clearer, real-time view of your marketing performance.

Where it fits in the flow

Your website triggers events. Tiide sits in the path as managed infrastructure – a conduit, not a destination. Traffic passes through it in real-time and is forwarded on immediately, through Google Tag Manager, to your ad platforms (Google, Meta and others) for conversion tracking. The only data the platform looks at is what's needed to recover a conversion that would otherwise be lost.

Want to share  how it works?

For a breakdown of the data flow you can share, see the resource below.