Rules decide when a Remote Config should return something other than its default value. AppActor evaluates active rules in priority order. The first matching active rule wins. If no rule matches, the SDK receives the default value for that key.

​
Scope first

Remote Config has three scope levels: When the same key exists at more than one scope, AppActor chooses the most specific scope: app beats platform, and platform beats project.

​
Rule conditions

Use conditions to narrow a value to the right audience: All conditions in a rule must pass. If a rule needs entitlement state, the SDK request can require user context so AppActor can resolve active entitlements before returning the value.

​
Priority

Lower priority numbers run first. Put the narrowest, highest-risk rules first and keep the default value safe.

​
Payload safety

Rules can change what the app renders, so keep the client defensive:
  • Treat missing keys as a normal cold-start case.
  • Validate JSON shape before rendering complex screens.
  • Keep local app defaults for required UI decisions.
  • Use entitlement APIs for access decisions.
Remote Config is not a secret store and not an entitlement authority. Do not put private credentials, unlock decisions, or irreversible purchase logic in a config payload.

​
Next

Test and Launch

Validate a rule with QA-scoped configs and safe fallbacks before turning it on broadly.