Paywall

A Paywall is a set of products. Paywalls allow you to dynamically change the products shown to your customers without app releases.

Paywall structure

A paywall consists of a name, a unique ID, ordered products, and optionally custom JSON payload. A paywall name is used across Adapty Dashboard.

Paywall ID

Paywall ID is unique within the app. This identifier is used in Adapty SDK and can't be edited once created. Most likely it will resemble a paywall name.

You can check the following article to learn about how to configure the Paywall ID on the SDK side

Products

Products are an ordered set of products, which will be shown to your customer.

You can add up to 5 products to a paywall. The order of the products is preserved on the SDK side, so keep it in mind when configuring a paywall. You can optionally specify an Apple promotional offer for the product.

🚧

Make sure to indicate Bundle ID for iOS and Package Name for Android in Adapty Dashboard, without them SDK can't fetch product info from stores.

🚧

Since the paywalls are configured remotely, the available products, the number of the products, and the special offers (eg free trials) can change over time. Make sure your code handles these scenarios. For example, if you get 2 products, the 2 products will be displayed, but when you get 3, all of them should be displayed without code changes.

Don't hard code product ids, you won't need them.

📘

To use promotional offers, you have to upload Subscription Key to Adapty Dashboard, so Adapty can sign the offers.

Paywall Remote Config

If you'd like to further customize your paywall, a remote config may be useful to you.

You can enter any JSON formatted data up to 10 kB. You can access this data from SDK using remoteConfig or remoteConfigString properties of AdaptyPaywall, and make some adjustments to your paywall. Here are some examples of how you can use a remote config.

{
    "screen_title": "Today only: Subscribe, and get 7 days for free!"
}

# Test titles or others texts

{
    "background_image": "https://adapty.io/media/paywalls/bg1.png"
}

# Test images on your paywall

{
    "font_family": "San Francisco",
    "font_size": 16
}

# Test fonts

{
    "subscribe_button_color": "purple"
}

# Test colors of buttons, texts etc.

{
    "photo_gallery": "https://adapty.io/media/paywalls/link-to-html-snippet.html"
}

# Any HTML code that can be displayed on the paywall

{
    "hard_paywall": true
}

# By setting it to true, you disalow skipping paywall without subscribing
# You have to handle this logic in your app

{
    "title": {
        "en": "Try for free!",
        "es": "¡Prueba gratis!",
        "ru": "Попробуй бесплатно!"
    }
}

You can combine different options, and make up your own. This way you can test different titles, texts, images, fonts, colors, and so on.

Remote Config Table View

If it's not common for you to work with code and there is a need to correct some values of the JSON, Adapty has a JSON table view for you.
It is a copy of your JSON in a format of a table that is easy to read and understand. The columns are type, key, and value. Color coding helps to recognize different data types. We automatically check the values and types mapping and show you an alert if your corrections may lead to an invalid JSON.

Localizations

You can have several localizations of your paywall to fit different countries and cultures. The legacy option of having all localizations in one JSON is still available, but we recommend adding localizations separately as the old way will be deprecated in several months.

🚧

Please note that if you update your Adapty SDK version to 2.3.0, but do not enable this feature in the dashboard, the SDK will not receive any values for remoteConfig. Therefore, it is recommended that you enable and configure the feature using the With Localization option in your dashboard after updating your SDK version to ensure that you receive the necessary remoteConfig values.

Versioning

Every time the products are changed, a new version of the paywall is created. This is done to collect paywall metrics separately for every meaningful change. For the custom JSON payload change, you may choose if you would like to save it as a new version or not with the checkbox near the saving button. The list of the paywalls shows the metrics for the latest (current) version of the paywall. You can view the metrics for all paywall versions on the Paywall metrics page.

To help ensure that your paywalls meet the guidelines of the stores, a confirmation popup appears every time you create or edit a paywall. The popup will prompt you to check specific requirements before publishing the paywall. Additionally, you have the option to confirm this for all future paywalls and prevent the message from appearing again.

Metrics

Adapty collects plenty of metrics to help you better measure the performance of the paywalls. All metrics are updated in real-time, except for the views, which are updated once every several minutes. All metrics, except for the views, are attributed to the product within the paywall.

• Revenue is the amount of money in USD from the purchases and renewals. So every time the subscription is renewed, it adds up to the LTV metric. Calculated before the App Store / Play Store commission.
• The conversion rate (CR) to purchases is the number of purchases divided by the number of views. 10 purchases / 100 views = 10% CR purchases.
• The conversion rate (CR) to trials is the number of trials started divided by the number of views. 30 trials / 100 views = 30% CR trials.
• Purchases are the sum of the following transactions (renewals are not included):
  • New purchases made on the paywall;
  • Trial conversions of trials that were activated on the paywall;
  • Down/up/cross-grades of the subscription on the paywall;
  • Subscription restores on the paywall (e.g. if the subscription was expired without auto-renewal).
• Trials are the number of activated trials
• Trials cancelled are the number of trials with auto-renewal switched off. It happens when the user manually unsubscribes from the trial.
• Views are the number of views of the paywall. If the user visits the paywall two times, this will be counted as two visits.

🚧

Make sure to send paywall views to Adapty using .logShowPaywall() method. Otherwise, paywall views will not be accounted for in the metrics and conversions will be irrelevant.

You can view the paywall metrics for every version and platform (OS).

Deleting paywall

To delete the paywall, open it, click Delete paywall, and confirm the action by entering the paywall name you're about to delete.

All deleted paywalls are stored in the Inactive tab, and you can still view the metrics.

❗️

Deleting the paywall will delete it from SDK. Don't delete paywalls that are used in production, it may break your app logic. You won't be able to restore the paywall after deleting it.

Converting paywall to A/B test

When you ready to test different products or designs, you can convert an existing paywall to an A/B test. The best thing is that you don't have to change anything on the SDK side. This way, you can start using a single paywall and then add other options without having to release a new version of your app.

To convert a paywall to an A/B test, click Convert to A/B test at the right top corner of the paywall editor.

Learn more about working with A/B tests in the next section.