Run a Firebase Remote Config A/B test targeted at a Google Analytics audience to validate a live-ops change before a full rollout

domain: firebase.google.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Define the Remote Config parameter(s) you want to experiment with (e.g., a difficulty tuning value or store price) and set a sensible default/control value in the Firebase console.
  2. In the Firebase console, go to A/B Testing, create a new experiment, and choose Remote Config as the service to experiment with.
  3. Set targeting criteria for the experiment — app version, country/region, and optionally a Google Analytics audience — combined with AND logic to scope who's eligible.
  4. Define experiment variants with different values for the chosen parameter(s), set the traffic percentage split, and pick a primary metric to evaluate variant performance.
  5. Start the experiment, monitor variant performance in the console as data accumulates, and roll the winning variant out to 100% of Remote Config once you have a statistically confident result.

Known gotchas

Related routes

Use Unity Remote Config to run A/B experiments and deliver live ops parameter changes
unity.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans