> ## 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.

# Release checklist

> Verify the PNLight SDK setup, App Store integration, Remote UI placements, ad attribution setup, and analytics events before shipping a new app build.

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.
* Attribution data is sent after the attribution provider returns it.

## App Store

* **Integration → AppStore** contains the correct issuer ID and shared secret.
* The `.p8` in-app purchase key is uploaded without renaming the file.
* App Store Server Notifications use the project notification URL shown in **Integration → AppStore**.
* The notification URL is saved in both production and sandbox fields in App Store Connect.
* App Store Server Notifications use version 2.

## Remote 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 networks and campaigns are configured if you use paid acquisition.
* Test users are marked correctly if you rely on debug-only Remote UI or QA traffic.
* Team members have the right access.

<Note>
  Keep this checklist with your app release process. Most PNLight issues found after release come from using the wrong project token, missing App Store integration settings, or disabled Remote UI placements.
</Note>