Skip to main content
You will use the same core concepts in the SDK and in the dashboard.

​
Project

A project represents one app in PNLight. It keeps the app identifiers, SDK token, App Store settings, product IDs, attribution settings, Remote Config, Remote UI placements, team access, and analytics together. The dashboard home page is My apps. It lists every app you can access.

​
SDK token

The SDK token identifies the PNLight project from your app. Copy it from Integration and pass it to the SDK during initialization.
Treat the SDK token as an app configuration value. Do not publish it in public examples, screenshots, or issue reports.

​
User ID

PNLight creates or returns a stable user ID through the SDK. Use this ID when you send events, attribution, and Remote UI requests.

​
Attribution

Attribution links a user to a source such as AppsFlyer or internal click attribution. PNLight uses ad networks and campaigns to group paid traffic in the dashboard. You can choose the priority order in Settings and set how long PNLight should wait for a preferred attribution source before falling back.

​
Remote Config

Remote Config lets your app fetch typed settings from the dashboard. The base configuration defines each key and its value type. Targeted overrides replace values for matching app installations.

​
Remote UI

Remote UI lets your app render screens configured in the dashboard. A UI request uses a placement ID, locale, and user ID. Common placements include paywalls, onboarding prompts, and upgrade screens.

​
Placement

A placement is a named location where your app can show Remote UI. Use stable placement IDs such as paywall, onboarding_offer, or upgrade_prompt.

​
Analytics

Analytics pages help you follow users, app events, and purchases through your app. Review clicks, installs, revenue, spend, trials, subscriptions, ARPPU, rebills, App Events, Remote UI, and funnels in the dashboard. Open Customers and Events when you need to investigate one user or a raw event.