Experiments are not normal Remote Config reads in AppActor. Your app asks for a specific experiment assignment and receives the variant context for the current customer.

​
SDK read

Wrapper SDKs expose the same concept:
  • Flutter: getExperimentAssignment("onboarding_paywall")
  • React Native: getExperimentAssignment("onboarding_paywall")
  • Android: getExperimentAssignment("onboarding_paywall")
If the user is not eligible, outside traffic allocation, or the experiment is not running, the call returns no assignment.

​
Assignment fields

Use experimentKey to decide where in the app the assignment belongs. Use variantKey for analytics labels and debug output. Use payload to render the actual experience.

​
Render safely

Keep the app safe when:
  • the experiment is paused or stopped
  • the user is outside the traffic allocation
  • the payload type does not match the code path
  • identity changes and a new customer has no assignment yet
  • the network is unavailable before the SDK has a cached assignment

​
Remote Config relationship

Remote Config and Experiments can share a payload shape, but they are separate reads: Use Remote Config for stable server-driven behavior. Use Experiments when assignment and analysis matter.

Splitting Rules

See how AppActor gates traffic and assigns variants deterministically.