PLATFORM

The data engine underneath your stack

Fidero is a Stateful CDP: it remembers what other platforms forget, so every tool you run gets complete, correct data.

SAMPLE · CRM WEBHOOK

Field RECEIVED DELIVERED
event opportunity_created
user_id 8842 8842
gclid –
utm_source –

A CRM sends this opportunity 6 days after the click. Fidero re-attaches what it kept.

FORMATTED FOR
Google Ads GA4 Warehouse
THE PROBLEM ALL CHECKS PASS

Silent failure, up close

Four failure patterns we see in real audits. In every one of them, nothing looks broken.

Delivering data is the easy part. An event can arrive successfully, appear in the dashboard and still be useless to the tool that received it: Meta can't match it, GA4 files it under "Unassigned" and nobody gets an error to investigate. Engineering built it exactly as the guides said, so no one looks for a bug.

Your sales stages never reach your ad platforms

LEAD · WEB
day 1 · reaches Google Ads
QUALIFIED · CRM
within the hour · not sent
OPPORTUNITY · CRM
day 6 · not sent
WHAT BIDDING SEES
1 lead · 0 later stages

Without every stage sent as a conversion, bidding learns who submits forms and you can't choose a stage that suits your volume or test another.

The signup that split one person in two

ANONYMOUS · WEB
device_id=a1b2c3 · utm_source=meta
AFTER SIGNUP · APP
new device_id · user_id=8842
IN PRODUCT ANALYTICS
2 users – 1 real person

The site's anonymous ID never reached the app, so no event carried both IDs and Product can't tie the channel to what users do next.

The sale Meta can count twice

BROWSER · PIXEL
event_id=order-8842
SERVER · CAPI
event_id=order_8842
META DEDUPE BY EVENT_ID
no match

Meta can't match the two IDs, so it can count the sale twice, inflating reported conversions and the data its ad system learns from.

One redirect, and every tool loses context

THE HANDOFF · BROWSER
cross-domain redirect · context bundle lost
GA4
new user · self-referral
META
fbclid gone
GOOGLE ADS
gclid gone

The redirect splits the journey in GA4 and leaves Meta and Google Ads with only the hashed customer data they have, so the tools disagree.

ARCHITECTURE BROWSER + SERVER

What's inside the engine

Fidero is server-first by design – built that way from day one, not adapted to it later. The browser does as little as possible and the server does the thinking.

IN THE BROWSER

The Fidero SDK

One lightweight script captures what only the browser knows (UTMs, click IDs, referrer, consent choices and a first-party ID) and sends it to the server before redirects or browser limits can destroy it.

  • Manages consent with native CMP adapters
  • First-party identity across tabs and domains
  • A simple API: track, page, updateIdentity
/?fbclid=…&utm_source=meta
In the browser
fbclid gclid utm_source consent fid_aid
Fidero API

Captured before redirects can strip it

ON THE SERVER

The Stateful Enrichment API

Every event lands here. Fidero validates it, works out who it belongs to, attaches the stored context, checks consent per destination and delivers it. Failures raise alerts instead of numbers that stop adding up.

  • Accepts events from the SDK, your servers, webhooks and CRM triggers
  • Merges anonymous visitors into known users
  • Delivers to your tools and warehouse
Enrichment API
event from sdk · server · webhook
  1. Validate
  2. Resolve identity fid_aid → user_id
  3. Attach context + fbclid
  4. Check consent
  5. Deliver
Delivered to
GA4 Meta Warehouse
CORRECTNESS DECISIONS, REMOVED

Correct by default

Every destination has its own rules. Fidero already knows them, so your team doesn't have to learn them.

Meta wants email addresses hashed and click IDs left as they are. On other platforms, every rule like that is a setting your team has to get right. Fidero has the rules built in, and when a destination changes them, we update Fidero for every customer. You say what you want in plain words, and your configuration changes on our servers. No one needs data tracking expertise, and your team has nothing to deploy.

Correctness lives in the product

IMPERATIVE PLATFORMS

2 sources × 2 destinations per platform × per-event mappings × per-property rules = hundreds of choices.

Each choice is a potential silent failure, and correctness depends on getting all of them right, forever.

FIDERO

Send qualified leads to Meta and Google Ads as conversions

Credentials, plus your account-specific identifiers, are all you add to that request. Standard events and properties map automatically. Enrichment and deduplication live in platform code – your team never touches destination configuration again.

MEMORY WHAT 'STATEFUL' MEANS

Complete by default

Delivery is half the job. Most data fails because it forgets: who the user was, what they allowed, which click started everything.

Some of the conversions that matter most never happen in a browser. A sale closes in your CRM, or a renewal comes from your billing provider, and neither knows about the ad click behind it. Platforms that only route data pass these events on as they are, so they reach Google Ads without a click ID. The alternative is to build a memory layer yourself and keep maintaining it. Fidero has memory built in, and it's on by default.

1
Capture

Grab the context

When someone first lands, the SDK captures which ad, which campaign and which click brought them, before redirects or privacy limits can strip it away.

2
Persist

Remember the person

The Stateful Enrichment API stores that context server-side, tied to the person rather than the page. It survives across sessions, devices and domains.

3
Re-attach

Complete every event

When any later event arrives for that person, from any source, Fidero re-attaches the original context automatically. A March renewal reaches your warehouse with January's campaign.

This is what 'stateful' means: context that persists, instead of resetting on every event.

GUARANTEES & COVERAGE IN WRITING

What we guarantee, and what we measure

Fidero guarantees what the platform controls end to end. The rest depends on your audience, so we measure it against your own traffic and improve it towards a target set per engagement.

Guaranteed

Deterministic – Fidero controls these end to end.

  • Consent enforced exactly, per destination – every signal Fidero can resolve, applied by rule, never inferred
  • Deduplication, deterministic and ID-based – wherever a transaction_id is present, the SDK blocks repeats and destinations like Meta and Google Ads receive it as their own dedup key
  • 100% identity resolution for every identified user – exact-match, never probabilistic

Measured against your traffic

Set per engagement, proven at the destination.

  • Attribution coverage – the share of your attributable conversions carrying a source, with the target set against what your audience realistically allows and never below 70%
  • Identity coverage – the share of users who reach a stable ID (the rest bounded by what the browser allows)

Delivery has one published target for every customer: ≥99.5% delivery success to reachable destinations, not counting an endpoint on your side that's down or misconfigured. Upfront, we agree coverage targets your audience can realistically reach, and the improvement is measured at the destination in your 30-Day Implementation Sprint.

Our guarantee

Clean data, or you don't pay.

We can put that in writing because correctness isn't something you configure – it's the platform's default.

FOUNDATIONS BY CONSTRUCTION

Built into the foundation

Four commitments that hold because of how Fidero is built – not because someone remembered a setting.

  • Privacy-native

    Consent is captured in the browser and enforced again per destination on the server. No third-party cookies, no fingerprinting, and deletion requests fan out to your tools automatically.

  • Warehouse-first

    Everything Fidero collects and enriches streams to your own warehouse, already cleaned and connected, ready for your analytics and models.

  • Zero lock-in

    Your data flows to your own tools and warehouse from the first event, so it all stays put if you ever leave.

  • AI-ready

    Fidero's configuration comes down to the outcomes you want and your API keys, which leaves very little for an AI agent to get wrong.

FAQ BEFORE YOU ASK

Platform questions, answered

We already send conversions server-side. Doesn't that cover it?

It covers delivery, which is the easy part. The hard part is making events matchable: the right identifiers, normalised and hashed correctly, sent from browser and server but counted exactly once, with consent enforced throughout. 'CAPI on' isn't the same as 'CAPI working' – your ad platforms show the connection as active but can match only some events to the people behind them. If that's your pain, the audit checks it against your own destinations.

How is Fidero different from Segment or RudderStack?

They're excellent routers – events in, events out, at scale. But a router has no memory: if attribution context isn't on the incoming event, it can't reach the destination, and building that memory layer is left to you. Fidero is stateful by default – context captured once, persisted and re-attached to every later event automatically. If you want to wire up the engine yourself and have the engineers for it, a router serves you well. If you want complete data as the default outcome, that's Fidero.

Why not managed GTM hosting, like Stape?

Stape solved the infrastructure problem brilliantly – server-side GTM hosting, accessible and affordable. We solve two different ones: configuration and memory. With GTM you still configure templates, manage containers and accept updates, and server-only events stay hollow without custom work. Teams with tag manager expertise get real value from that flexibility. Teams who want outcomes without the expertise choose Fidero.

Can't an AI agent just set up our tracking?

It'll say it can, write the tags and tell you everything's done and correct. Then you look at the numbers and they don't match. An email is hashed the wrong way, a conversion counts twice, a server event arrives without its click. There are just too many small details that break tracking, so Fidero handles them in the platform, whoever does the setup.

Does Fidero replace GA4, Mixpanel or our warehouse?

No – it feeds them. Fidero is deliberately dashboard-free: it perfects the data layer underneath, so GA4 and your ad platforms work from the same events, Mixpanel sees whole journeys, and your warehouse receives events already enriched. There's no new tool to learn – the ones you already run just start telling the same story.

Can our team ask an AI agent for the numbers?

Yes. Pointing an agent or BI tool at a database is simple. Getting the right answer back depends on the data in it and how your metrics are defined. Fidero gets correct, complete data into your warehouse, and we can help you define each metric in a layer on top. Any agent that can query your warehouse can read that layer, so your team can ask about anything defined there and everyone gets the same answer.

What does implementation actually involve?

One integration, once: your engineers install the Fidero SDK and point your server events at the API, guided by our tickets and QA checks. Most teams are live within the 30-day sprint. From then on there's no per-destination configuration and no ongoing maintenance – new integrations are enabled from the server, with no redeploys on your side.

Are we locked in?

No. Your data already streams to your tools and your own warehouse – Fidero holds nothing hostage. If you ever leave, your historical data is already where it belongs and stays there. We'd rather keep you by being useful than by being difficult to remove.

THE AUDIT SEE FOR YOURSELF

Get the evidence from your own stack

Bring the failure on this page that sounds most like yours. The Data Infrastructure Audit traces it through your setup to where the data breaks, and estimates what that costs you each month.

  • Annotated screenshots you can check yourself
  • A recommended first step, with no obligation attached
  • A short written report within 48 hours

£250 – fully refunded if you don't proceed, credited in full to your implementation if you do.

Clean data, or you don't pay.