Onboarding
There’s no signup flow behind these docs – setting up Fidero is joint work. There are three stages between first contact and live data: an audit, an implementation sprint and then the running platform. This page describes what each stage involves and what exists at the end of it.
The audit
Section titled “The audit”Everything starts with the Data Infrastructure Audit: a focused diagnostic of your most expensive data problem, evidenced from the destination side – what Meta, GA4 or your warehouse actually received, not what your tags report. It’s delivered within 48 hours as a one- or two-page PDF covering the architectural gap, its business impact and recommendations in ROI order.
The readout call presents the findings and the implementation proposal together, so there’s one decision to make: proceed to the sprint or stop with the audit in hand.
The implementation sprint
Section titled “The implementation sprint”The 30-Day Implementation Sprint is scoped from what the audit found and varies account by account. Fidero brings the plan: journey mapping, identity strategy, implementation tickets and QA checks. Your engineers implement and deploy in your own codebase – if Fidero writes any of the changes, that’s scoped and agreed up front. We set up the platform side as the sprint runs: your project, its configuration and your destinations.
The sprint is measured against weekly acceptance gates, and the subscription starts after the final one, not before.
Going live
Section titled “Going live”Live means data flowing end to end: the SDK on your site, server events from your backend where they apply, and destinations receiving enriched events. Verify your setup confirms each piece. From there, day-to-day life is Configuration & changes for requests and How we work for the wider model.