FAQ
Answers to the questions we get most often from product, engineering, data and legal teams — grouped by topic.
This FAQ collects the questions our support and solution engineering teams answer most often, grouped by topic. Each answer links to the reference documentation when you need the full implementation details.
Browse by topic
| Topic | What you will find |
|---|---|
| Integration & getting started | The minimal path to a working paywall, running modes, entitlement architecture, SDK footprint, what requires an app release and what does not. |
| Users & identity | Pseudonymous identifiers, anonymous users, subscription transfer on login, logout behavior, unknown users. |
| Screens & paywalls | Layouts and components, fonts, localization, Audiences, and the rendering issues we see most often (missing prices, cut-off CTAs, cache). |
| Flows & BYOS | Multi-step journeys, transitions, how a Flow reports its outcome, and plugging your own native screens into a Flow. |
| Stores & billing | Store guideline compliance, StoreKit, Google Play Billing, offers and promo codes, Ask to Buy, family sharing, refunds, web checkout. |
| Testing & sandbox | What is normal store behavior in sandbox and TestFlight, and what is an actual bug worth reporting. |
| Console & environments | Copying a Screen from staging to production, why a Plan refuses to be deleted, roles and access, empty dashboards. |
| Analytics & data | Events, webhooks, exports, revenue reconciliation, A/B test reading, third-party forwarding, subscriber base import. |
| Privacy, security & compliance | GDPR roles, DPA, data processing register and consent API, children-oriented apps, certifications, data export and deletion. |
| Product capabilities | What the platform covers today, what is in beta, and how to influence what comes next. |
Still stuck?
- A Screen does not render as expected → use the Screen Issue Report Template so support can reproduce it on the first pass.
- Something is wrong in your integration → turn on Debug Mode on the device first, it exposes the SDK version, user IDs, Placement, Audience, A/B test and variant actually applied.
- Anything else → contact your Purchasely support channel with your app name, SDK version, platform and environment (production or sandbox).
Updated about 1 hour ago
What’s Next
Pick the topic that matches your question
Did this page help you?