Assignment and Payloads

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

let onboarding = try await AppActor.shared.experiment("onboarding_paywall")

onboarding.isEnrolled                       // false when the customer is not in the experiment
onboarding.variantKey                       // "control", "short_onboarding", … or nil
onboarding.isVariant("short_onboarding")
onboarding.boolValue(default: false)        // also stringValue / intValue / doubleValue
onboarding["headline"]?.stringValue         // one key of a JSON payload

Wrapper SDKs expose the same shape:

Android: AppActor.getExperiment("onboarding_paywall")
Flutter: AppActor.instance.getExperiment('onboarding_paywall')
React Native: AppActor.instance.getExperiment('onboarding_paywall') (get(key) instead of a subscript)

The result is never null. If the user is not eligible, outside traffic allocation, or the experiment is not running, isEnrolled is false and every typed getter returns the default you pass — control renders with no extra branch. The raw assignment below is available as .assignment (null in that case), or directly from getExperimentAssignment.

Assignment fields

Field	Meaning
`experimentId`	Server identifier for the experiment
`experimentKey`	Developer-defined key used by the app
`variantId`	Server identifier for the assigned variant
`variantKey`	Developer-defined variant key
`payload`	Variant value used by the app
`valueType`	`boolean`, `number`, `string`, or `json`
`assignedAt`	Assignment creation timestamp

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

let onboarding = try await AppActor.shared.experiment("onboarding_paywall")

switch onboarding.variantKey {
case "control", "short_onboarding":
    renderPaywall(payload: onboarding.payload)
default:                                    // not enrolled, or a variant this build does not know
    renderDefaultPaywall()
}

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:

Surface	SDK result
Remote Config	resolved `key`, `value`, `valueType` items
Experiment	`isEnrolled`, `variantKey`, typed payload getters with defaults, and the raw assignment (`experimentId`, `experimentKey`, `variantId`, `variantKey`, `payload`, `valueType`, `assignedAt`)

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.

Overview

Get Started

Testing and Go Live

Features

Remote Config

Experiments

Platform Resources

AI-Ready

Assignment and Payloads

SDK read

Assignment fields

Render safely

Remote Config relationship

Splitting Rules

​SDK read

​Assignment fields

​Render safely

​Remote Config relationship

Splitting Rules

SDK read

Assignment fields

Render safely

Remote Config relationship