Connection & usage

The Connected badge and the SDK usage graphs.

The dashboard gives you two read-path signals per environment: a live connection badge and usage graphs. Both are about confirming that SDKs are fetching your config — they are deliberately not analytics about your users.

The Connected badge

Each environment shows a connection badge:

  • Connected ✓ — an SDK using this environment's key has fetched the config recently.
  • Never — no fetch has been seen for this key yet.

The first time any client fetches the config, the badge flips to Connected within seconds — this is the payoff moment in every quickstart. It's the fastest way to confirm your sdk_key is correct and your app is wired up.

Usage graphs

The usage panel charts how often the config is being fetched from the edge over a window you pick (last hour, day, week). It's useful for confirming traffic is flowing and spotting a sudden drop (a deploy that broke SDK setup, say).

Read the labels honestly

These graphs count config fetches, not flag evaluations or users. Specifically:

  • A data point is a poll — an SDK fetching flags.json — not an enabled() call. Your app evaluates flags locally, in-process, and those checks never touch the network, so they're invisible here (and uncounted).
  • The count reflects running SDK instances, not unique people. Ten server processes polling is ten times the traffic of one, for the same number of end users.

So the graph is a delivery health signal — "is my config reaching clients" — not a daily-active-users or engagement metric. Don't read it as DAU.

Next