Pay for events, not configuration

A single tracked action – a page view, a sign-up, a purchase, a server-side conversion or a webhook from your billing provider. Fidero counts each one once, wherever it comes from: a conversion sent from both browser and server is deduplicated, so it counts as one event, not two.

A self-contained configuration bundle: tracking setup, consent settings, destinations and enrichment rules for one environment or brand. Most teams run staging and production as separate projects, or give each brand its own. Multiple sites can share a single project when their tracking is identical.

All of them – just not as a black-box score. Fidero enriches every event with first and last touch in real time, and lands the full touchpoint detail behind them (campaign, click IDs, referrer, channel) in your warehouse as an ordered journey log. Multi-touch models (linear, position-based, time-decay) are a query over that log, run by your team or your AI agents – you pick the model, see exactly how it works and change it whenever you like.

Your data keeps flowing – there's no penalty rate and no cut-off. The difference is billed at your plan's overage rate: £0.12 per 1,000 events on Growth, £0.08 on Pro, £0.05 on Scale. You can move tiers whenever your volume changes, and we'll tell you when moving up would save you money.

It's scoped from your audit rather than priced from a menu – from £2,000, with simple setups sitting near that floor. Complex ones cost more, because they're worth more. Your £250 audit fee is credited in full, and the guarantee applies: measurable improvement against the agreed target, or we refund the implementation fee.

The implementation builds and deploys your data engine. The subscription keeps it running. Identity resolution, enrichment, consent enforcement, adapter updates and delivery are live operations, not a one-off setup. Think of it as the electricity bill for the infrastructure: switch it off and you're back to the fragmented data you started with.

You could – and on the day they finished, it would work. Then Meta updates its API, your checkout changes, a consent rule shifts, and the configuration drifts silently: dashboards stay green while your signals stop matching. That's the pattern our audits keep finding. Implementation drifts, infrastructure doesn't. The real question isn't who sets it up – it's what keeps it correct six months later.

Honestly: the engine switches off – enrichment, identity resolution and delivery stop. But nothing is taken away. Your data has been streaming to your own warehouse and tools all along, so everything you've collected stays exactly where it already is. Events land with the identity Fidero had resolved at the time, and any identity state Fidero still holds is yours too – returned on written request within 30 days of exit, in a documented, machine-readable format.