Fallback paywalls

To maintain a fluid user experience, it is important that you set up fallback versions for your paywalls and onboardings.

When your application loads a paywall, the Adapty SDK requests paywall configuration data from our servers. But what if the device cannot connect to Adapty due to network issues or server outages?

• If the user accessed the paywall before, and the device cached its data, the application loads paywall data from cache.
• If the device did not cache the paywall, the application looks for a locally stored configuration file. It allows the application to display the paywall without an error.

Adapty automatically generates fallback configuration files for you to download and use. Each file contains platform-specific configurations for all your placements.

Get started

1. Download the fallback configuration file from Adapty.
2. Use the Adapty SDK to configure your fallback paywalls:
   • iOS
   • Android
   • React Native
   • Flutter
   • Unity
   • Kotlin Multiplatform
   • Capacitor

Limitations

Fallback paywalls are hard-coded and locally stored, so they lack the dynamic capabilities of regular Adapty paywalls.

• Fallback paywalls don’t support internationalization. The file always uses the en locale, so offline users only see English. Upgrade to SDK v4 to lift that limit — its fallback file carries every locale.
• Each placement can only have one fallback paywall. If your setup inlcudes different paywall configurations for different audiences, Adapty uses the configuration intended for “All users”.
• Fallback paywalls don’t support A/B testing. If a paywall participates in an A/B test, its fallback configuration file will include the variation with the highest weight.
• Fallback paywalls cannot be managed remotely. If you want to update the configuration file, you need to release a new version of the app on App Store / Google Play.