Skip to main content
PNLight Remote Config delivers typed app settings from the dashboard to the SDK. Use it for non-sensitive runtime behavior such as feature flags, copy variants, limits, and paywall settings. Remote Config is separate from Remote UI. Remote UI returns renderable screen configs. Remote Config returns typed values that your app reads and applies in its own code.
Do not store secrets in Remote Config. Never put API keys, credentials, shared secrets, or other sensitive values in Remote Config.

Configure values in the dashboard

Create the base configuration, add targeted overrides, and publish the draft in Remote Config. See Remote Config dashboard setup for the workflow. Supported top-level value types:
  • Boolean.
  • String.
  • Number.
  • String array.
  • JSON.
Keys are flat. If an override changes a JSON value, it replaces the whole value instead of deep-merging nested fields.

Initialize with local defaults

Provide app-owned defaults during SDK initialization. Defaults stay on the device and are never sent to PNLight. The SDK uses them before the first successful fetch, when offline, or when a remote value is missing or has a different type.

Fetch and activate

Call fetchAndActivate after initialization when your app is ready to refresh Remote Config. By default, the SDK:
  • Waits briefly for AppsFlyer attribution so PNLight can apply attribution-based overrides.
  • Throttles successful fetches for 15 minutes.
  • Persists the active configuration per SDK token and PNLight user.
  • Keeps the previously active configuration if a fetch fails.
Use an immediate fetch only for development, QA, or a startup path that must not wait for attribution.

Read typed values

Use typed getters with fallbacks. If a key is missing or the active value has a different type, the SDK returns the fallback.
  • Keep app-critical defaults in the app so first launch and offline sessions work.
  • Read Remote Config through typed getters instead of casting raw JSON.
  • Use minimumFetchInterval: 0 only in development or QA.
  • Fetch after forwarding attribution when campaign-specific overrides matter.
  • Coordinate key names and value types between dashboard owners and app developers before publishing.