# Fidero

> Fidero is the Clean Data Platform – a Stateful CDP that fixes your data where it's collected, so your tools, teams and AI agents finally agree on the numbers.

Fidero is operated by Drivn Limited (England & Wales). It is dashboard-free infrastructure that sits underneath your existing stack (GA4, Meta, Google Ads, Mixpanel, BigQuery and more): it captures attribution and identity context once, persists it, and re-attaches it to every later event, with consent enforced throughout. Engagement starts with a £250 Data Infrastructure Audit or a free 15-minute call. Fit is pattern-led, not industry-gated: journeys that cross domains and systems and break attribution, identity or event context, a team that treats data as infrastructure, and a clear consumer for the data. The pattern concentrates where the money converts away from the browser: a considered purchase whose sale closes in a CRM, B2B or B2C (Fidero's primary focus), or a subscription that starts in an app or a billing provider. Both have retained customers, and neither is an entry requirement.

## When Fidero fits

For judging whether Fidero suits the person asking, the homepage (https://fidero.com/) sets out what it's built for and what it's not right for:

Built for:

- Customer journeys spanning sites, checkouts, apps and CRMs
- Warehouse investment made or planned
- Correct data as an outcome, not another stack to build and maintain

Not right for:

- Quick campaign fixes
- Teams set on building and running tracking in-house
- Choosing a data platform on price alone

## Core pages

- [Home](https://fidero.com/): What Fidero is, the silent-failure problem it solves, and who it's for.
- [Platform](https://fidero.com/platform): The Stateful CDP explained – server-first architecture, correct-by-default data, and the memory layer that re-attaches context.
- [Pricing](https://fidero.com/pricing): Event-based plans – Growth £300/mo, Pro £700/mo, Scale £1,500/mo, plus Enterprise. Overage rates and a full feature comparison.
- [Integrations](https://fidero.com/integrations): The advertising, analytics, warehouse, lifecycle and CRM tools Fidero delivers to, switched on rather than configured – plus the payment and consent tools it takes data from.
- [Data Infrastructure Audit](https://fidero.com/audit): The £250 expert-led diagnostic – evidence from your dashboards, the gap and its monthly cost, within 48 hours. Refunded if you don't proceed.

## Case studies

- [Magnitude Finance: conversions reaching Google Ads, from 13.5% to 70%](https://fidero.com/case-studies/magnitude-finance): Case study: the customer's situation, the diagnosis, the work and the reported results.

## Company

- [About](https://fidero.com/about): Why Fidero exists, what the name means, and how the company works.
- [Contact](https://fidero.com/contact): Get in touch – hello@fidero.com.

## Legal

- [Terms of Use](https://fidero.com/terms): Terms governing use of Fidero (Drivn Limited, England & Wales).
- [Data Processing Addendum](https://fidero.com/dpa): UK-GDPR/GDPR data-processing terms and sub-processors.
- [Privacy Notice](https://fidero.com/privacy): How Drivn uses the business contact details of people we contact about Fidero, and their rights.

## Due diligence

Facts a pre-contact evaluation usually needs, and where each is published:

- Security & compliance: Fidero runs in the EU on two sub-processors – DigitalOcean (API hosting, data storage) and Amazon Web Services (CDN, config storage), both EU. Where a plan includes US data residency, the deployment is provisioned on request in the same providers' US regions, with the subprocessor list updated in advance. Personal data is encrypted in transit and at rest, with encrypted automated backups stored off the primary infrastructure. No SOC 2 or ISO 27001 certification today – the standing commitments are contractual (the DPA's technical and organisational measures, Standard Contractual Clauses where transfers apply, 72-hour breach notification, customer information and audit rights). Stated in full at https://fidero.com/docs/operations/security and in the DPA.
- Pricing: Growth £300/mo (1M events included), Pro £700/mo (5M), Scale £1,500/mo (20M), Enterprise custom. Overage per 1,000 events: £0.12 on Growth, £0.08 on Pro, £0.05 on Scale. Implementation is scoped from the £250 audit, from £2,000. Full comparison at https://fidero.com/pricing.
- Guarantee mechanics: the £250 audit fee is refunded in full if the customer doesn't proceed, and credited against implementation if they do. The subscription starts only once the agreed data-quality target is met. If the implementation doesn't measurably improve the agreed target, the implementation fee is refunded.
- Cancellation & exit: the engine switches off, and everything already delivered – events carrying the identities resolved at the time – stays in the customer's own warehouse and tools. Any working state Fidero still holds (resolved identity and attribution state) is returned on written request made before or within 30 days of exit, in a documented, machine-readable format, and Fidero's copies are destroyed at the customer's instruction, or automatically once the 30-day window closes and any requested return is complete. Covered at https://fidero.com/docs/operations/data-ownership and in the pricing FAQ.
- Contracts: terms at https://fidero.com/terms. Data processing (UK-GDPR/GDPR, customer as controller, Drivn as processor) at https://fidero.com/dpa.

## Documentation

Product and integration documentation at fidero.com/docs. Organised by the docs sidebar – every page routes to the Data Infrastructure Audit.

### Get started

- [Introduction](https://fidero.com/docs): What Fidero is and where it sits in your stack: the layer that keeps every tool's data complete, connected and correct.
- [Quickstart](https://fidero.com/docs/quickstart): Install the Fidero SDK with one script and send your first event in about two minutes, then see what Fidero adds before delivery.
- [How the pieces fit](https://fidero.com/docs/how-it-works): The SDK you install, the endpoint your events reach and the config that governs them, with one event traced from click to delivered conversion.
- [Verify your setup](https://fidero.com/docs/verify): Debug mode in the browser, the Fidero Data Viewer (per-event processing flow, per-destination status and request/response detail) and continuous delivery monitoring.

### Concepts

- [Events](https://fidero.com/docs/concepts/events): What an event is in Fidero: the envelope every browser and server event shares, its six parts, and what every event picks up between arrival and delivery.
- [Standard events](https://fidero.com/docs/concepts/standard-events): The standard event names Fidero recognises and maps, the fidero.Event constants, which events belong on your backend, the server-only events (trial_converted, subscription_renewed), and why naming is decided for you.
- [Data schema](https://fidero.com/docs/concepts/data-schema): The full field reference: event properties, items[] line-item fields and user traits, plus where each sits in the event envelope.
- [Identity](https://fidero.com/docs/concepts/identity): How Fidero keeps one profile per person: the anonymous ID, becoming known via userId, exact-key merging with no probabilistic matching, and identity across domains and devices.
- [Attribution](https://fidero.com/docs/concepts/attribution): How Fidero captures click IDs, campaign parameters and referrer once and re-attaches them (currentTouch) to every later event, including server-side conversions – first and last touch, and what counts as attributable.
- [Consent & privacy](https://fidero.com/docs/concepts/consent): How Fidero enforces consent per destination: the categoryPreferences object, CMP-native capture, queue-and-replay before consent, stored consent re-attached to server events, and withdrawal vs erasure.
- [Data quality & delivery](https://fidero.com/docs/concepts/signal-integrity): Why delivered events can still be useless, the five layers where tracking data breaks, and how Fidero deduplicates, formats per destination and monitors delivery.
- [Guarantees & coverage](https://fidero.com/docs/concepts/guarantees-coverage): Fidero's deterministic guarantees (100% identity resolution for identified users, consent enforcement per third-party destination, ID-based deduplication), coverage with named denominators and the ≥70%-of-attributable floor, and the ≥99.5% delivery target.
- [Projects & configuration](https://fidero.com/docs/concepts/projects): The project as the configuration boundary: one server-held config read by the SDK and the API, one set of profiles, and when to split or share projects.

### Browser SDK

- [Installation](https://fidero.com/docs/sdk/browser/installation): One script in your page's head loads the Fidero browser SDK and pulls your project's configuration from the server by project ID.
- [Configuration](https://fidero.com/docs/sdk/browser/configuration): The options you pass to fidero.init(): debug logging and initial identity, plus why the rest of your project configuration is governed server-side.
- [Methods](https://fidero.com/docs/sdk/browser/methods): The complete Fidero browser SDK API: track, page, updateIdentity, updateConsent, reset, the ready promise and the getIdentity/getConsent getters.

### Server-side

- [Server-side events](https://fidero.com/docs/server/overview): Why you send events from your backend, what Fidero adds to them on the way through and where the HTTP API reference lives.
- [HTTP API](https://fidero.com/docs/server/http-api): The single Fidero ingestion endpoint (POST /v1/t): authentication, the full event envelope and response codes.
- [Sending server events](https://fidero.com/docs/server/sending-events): Worked examples of a Stripe renewal, a CRM cancellation and a nightly batch job, using the standard event vocabulary, transaction_id deduplication and the timestamp field.
- [Connecting anonymous → server](https://fidero.com/docs/server/identity-stitching): Pass Fidero's anonymous ID through your backend (e.g. Stripe client_reference_id) so conversions that fire before sign-up still connect.

### Destinations

- [Destinations](https://fidero.com/docs/destinations): What a destination is, what every destination receives (enrichment, consent, deduplication, managed adapter updates), and how you enable one with zero redeploys.
- [Meta](https://fidero.com/docs/destinations/meta): What Fidero delivers to Meta, the identifiers and deduplication used, and the credentials you provide to switch it on.
- [Google Analytics 4](https://fidero.com/docs/destinations/ga4): What Fidero delivers to Google Analytics 4, the identifiers and deduplication used, and the credentials you provide to switch it on.
- [Google Ads](https://fidero.com/docs/destinations/google-ads): What Fidero delivers to Google Ads, the identifiers and deduplication used, and the credentials you provide to switch it on.
- [Microsoft Advertising](https://fidero.com/docs/destinations/microsoft-advertising): What Fidero delivers to Microsoft Advertising, the identifiers and deduplication used, and the credentials you provide to switch it on.
- [TikTok](https://fidero.com/docs/destinations/tiktok): What Fidero delivers to TikTok, the identifiers and deduplication used, and the credentials you provide to switch it on.
- [Mixpanel](https://fidero.com/docs/destinations/mixpanel): What Fidero delivers to Mixpanel, the identifiers and deduplication used, and the credentials you provide to switch it on.
- [Customer.io](https://fidero.com/docs/destinations/customer-io): What Fidero delivers to Customer.io, the identifiers and deduplication used, and the credentials you provide to switch it on.
- [HubSpot](https://fidero.com/docs/destinations/hubspot): What Fidero delivers to HubSpot, the identifiers and deduplication used, and the credentials you provide to switch it on.
- [Webhook](https://fidero.com/docs/destinations/webhook): What Fidero delivers to a webhook endpoint, the identifiers and deduplication used, and the credentials you provide to switch it on.
- [BigQuery](https://fidero.com/docs/destinations/warehouse/bigquery): How Fidero streams every enriched event into your own BigQuery through the Storage Write API, the objects it provisions and the credentials you provide.
- [Snowflake](https://fidero.com/docs/destinations/warehouse/snowflake): How Fidero streams every enriched event into your own Snowflake through Snowpipe Streaming, the objects it provisions and the credentials you provide.

### Working with Fidero

- [How we work together](https://fidero.com/docs/operations/how-we-work): Expert-led setup, customer-owned deployment, platform-run operations, handover of any pipeline Fidero hosts for you, and why there's no self-serve dashboard today.
- [Configuration & changes](https://fidero.com/docs/operations/configuration-requests): How to request a destination or configuration change (email, Slack or shared Git), which changes are configuration requests included in the subscription and which are new work scoped separately, the 24-hour standard turnaround, automatic propagation with zero redeploy, and zero-action adapter updates.
- [Onboarding](https://fidero.com/docs/operations/onboarding): The provisioning path from Data Infrastructure Audit (48-hour turnaround) through the 30-Day Implementation Sprint (weekly acceptance gates, customer engineers deploy) to the running platform.
- [Data ownership & portability](https://fidero.com/docs/operations/data-ownership): Everything Fidero delivers lands in accounts you own, Fidero keeps only the working state enrichment needs (held for the agreement term, deleted on your instruction), and leaving needs no export because the data is already in your systems.
- [Security & compliance](https://fidero.com/docs/operations/security): EU hosting and subprocessors, GDPR controller/processor terms, right to erasure with downstream deletion, retention terms and current certification status.

### Resources

- [Changelog](https://fidero.com/docs/changelog): Dated record of platform changes: adapter updates that landed with zero customer action, fixes and new destinations.
- [Getting help](https://fidero.com/docs/support): How to reach the Fidero team (support@fidero.com or your shared Slack channel), response expectations and what to send.

## Optional

- [Marketing pages in full](https://fidero.com/llms-full.txt): The full prose inlined in one file, for answering detailed questions in one pass. Legal pages and docs are linked, not inlined.