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.
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
CallfetchAndActivate 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.
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.Recommended use
- 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: 0only 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.