📄️ Overview & How It Works
Paylisher can deliver in-app messages to your iOS app in two independent ways:
📄️ Integration
Enabling API-pull in-app messaging is a single config object on top of your normal SDK setup. When it is nil (the default), the SDK never issues a fetch, so the feature is off until you opt in. Set the config before PaylisherSDK.shared.setup(...).
📄️ Scenarios & Recommended Configs
The same feature supports several product patterns. Pick the one that matches your intent and copy its config. All snippets assume the SDK is already set up as in Integration.
📄️ Campaign Setup (Dashboard)
The SDK only renders what Engage returns. A fetch returns a message only when a campaign matches the requesting user and is authored for API-pull delivery. This page lists exactly what a pull campaign must look like. (The dashboard steps are the same for iOS and Android.)
📄️ Troubleshooting
Work top-down. Start with the raw curl from Integration → Verifying the fetch — it tells you whether the problem is the server (auth / campaign) or the client (SDK config / device).