Introduction

Fidero is the data layer that sits between where your customer data is created and the tools that depend on it. Your website, app, servers and webhooks send their events to Fidero. Fidero captures the context around each event, connects it to the right person and delivers it to every tool you run – your ad platforms, analytics, CRM and warehouse.

Those tools are only as good as the data going into them. Fidero is the layer that keeps that data complete, connected and correct, so every team works from the same trustworthy picture.

Where Fidero sits

  YOUR SOURCES            FIDERO               YOUR TOOLS
  ------------            ------               ----------
  website, app            capture context      ad platforms
  servers, backend  -->   connect identity --> analytics
  webhooks                correct, deliver     CRM, warehouse

Everything flows through one place. Fidero is a Stateful CDP, built server-first: it keeps a memory of each customer’s context. So an event stays complete even when it never touched a browser – a renewal, a webhook, a CRM update. The platform overview explains the architecture behind that.

This is the 60-second version. How the pieces fit covers the implementation in detail: the SDK you install, the endpoint you send to and the config that governs both.

What Fidero ensures

Fidero ensures three things, each with its own concept page.

Complete

Campaign and journey context follows the customer everywhere, even to conversions that finish on your server. Marketing can prove which campaigns actually drive revenue. See Attribution.

Connected

One person stays one profile across domains, devices and sessions, from anonymous visitor to known customer. Product can follow a whole journey. See Identity.

Correct

Every event is formatted correctly, counted once, consent-checked and delivered. Engineering stops nursing tracking scripts, and Legal gets consent enforced across every third-party tool. See Data quality.

How you’ll work with Fidero

You tell Fidero the outcomes you want, like “send purchases to Google Ads” or “stream events to Snowflake”, and your engineers instrument the events in your code. We bring the implementation plan and the judgement. After that, Fidero runs the day-to-day: enrichment, integrations, delivery and monitoring.

There’s no self-serve dashboard today. Configuration is server-governed, so when something needs to change you request the outcome and it propagates without a redeploy. How we work covers the model in full.

Start here

New to Fidero? Read in order – each page builds on the one before.

Quickstart Send your first event and see what Fidero does with it. About two minutes.

How the pieces fit The SDK, the endpoint and the config, with one event traced end to end.

Concepts The vocabulary: events, identity, attribution, consent, data quality and guarantees.

From there the docs follow your data from collection to delivery: the Browser SDK and Server-side events that send data in, the Destinations it fans out to, and How we work for the part we do together.

Already set up? Jump straight to SDK methods, the HTTP API or Destinations.