Skip to content

Configuration & changes

Fidero has no configuration dashboard, and doesn’t need one: changes are requests. You describe the outcome you want, the change lands in your project’s configuration on Fidero’s servers, and nothing on your side redeploys. This page covers how to make a request and what happens to it.

The request lifecycle

Section titled “The request lifecycle”

  1. Ask for the outcome

    Send requests however you already work with us: email, Slack or the shared Git repository if your setup includes one. A request is one sentence naming the outcome – “Enable Google Ads enhanced conversions” or “Add checkout.example.com as a trusted domain”. If the change needs something from you, such as credentials or an account ID, that’s the only other thing to include.

  2. The change lands

    Standard changes are in your project’s configuration within 24 hours, and you’ll hear from us when yours is live.

  3. Everything picks it up

    The SDK reads the updated configuration the next time it loads, and the API applies it from the next event onward. Your pages and your servers keep running what they already run – nothing needs deploying. You can watch it take effect yourself: Verify your setup has the checks.

What counts as a request

Section titled “What counts as a request”

Anything that lives in your project’s configuration: enabling a destination, rotating credentials, adding a trusted domain, switching on a warehouse sync or splitting it into a new project. Sending an event you already track to another tool is a request too, and every request is included in your subscription.

Designing or building something new isn’t a request, whether that’s a new event or new logic that filters or transforms your data. We scope that with you as its own piece of work before it starts. Once it’s live, sending its events to your destinations is a request like any other.

If you’re not sure which kind of change you need, ask and we’ll tell you which it is. How we work covers the rest of the split, including the changes your engineers make in your own code.

Updates you never request

Section titled “Updates you never request”

Every destination is delivered through an adapter that Fidero maintains. When a destination changes its API – and they all do – we update the adapter on our side, and every project picks it up automatically. There’s nothing to request and nothing to accept.

Section titled “Related”
How we work The operating model: what you own, what Fidero runs and why there's no dashboard.
Projects & configuration What one project contains, and when to use several.
Destinations What a destination is, and the tools Fidero delivers to.

The platform overview explains why Fidero is configured by outcomes at all.