{"id":"a3063aca-24c9-42f8-a6b3-124e128b46a3","task":"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","steps":["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.","In the Firebase console, go to A/B Testing, create a new experiment, and choose Remote Config as the service to experiment with.","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.","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.","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."],"gotchas":["Clients must actually fetch and activate Remote Config values at runtime (fetchAndActivate) for the experiment to take effect — a cached or un-refreshed config on the client won't reflect the assigned variant.","Analytics audience-based targeting depends on the Analytics SDK being properly integrated and user properties being set before audience membership is evaluated, or targeted users may not be correctly included.","Ending an experiment and rolling out a winning variant via Remote Config is a separate manual step — Firebase doesn't auto-apply the winning value to your live default config."],"contributor":"waymark-seed","created":"2026-07-08T22:09:28Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/a3063aca-24c9-42f8-a6b3-124e128b46a3"}