Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pnlight.app/llms.txt

Use this file to discover all available pages before exploring further.

Use this checklist before you submit a build or enable PNLight for production traffic.

​
SDK

  • The app initializes the SDK with the production project SDK token.
  • Development and staging builds do not send data to the production project unless intended.
  • The app can read the PNLight user ID.
  • Purchase checks return the expected result in a sandbox purchase test.
  • Attribution data is sent after the attribution provider returns it.

​
App Store

  • Settings contains the correct bundle ID and App Store ID.
  • The issuer ID and shared secret are saved.
  • The .p8 in-app purchase key is uploaded.
  • App Store server notifications use the project notification URL shown in Settings.

​
Server-driven UI

  • Each placement has a stable ID.
  • Required locales have valid JSON configs.
  • The placement is enabled.
  • Test users can render the screen in the app.
  • Button actions are handled by app code.

​
Dashboard

  • Installs appear in Analytics.
  • Purchases appear on customer profiles.
  • Ad sources and campaigns are configured if you use paid acquisition.
  • Team members have the right access.
Keep this checklist with your app release process. Most PNLight issues found after release come from using the wrong project token, missing App Store credentials, or disabled server-driven UI placements.