Welcome to paywalls 2.0, the revolutionary paywall management system accompanied by the groundbreaking concept of placements. This innovative system transforms how you manage A/B tests and paywalls, providing unparalleled control and efficiency.
Placements serve as a powerful tool within paywalls 2.0, allowing you to group A/B tests and paywalls seamlessly. By associating specific A/B tests with targeted paywalls, you gain the ability to deliver content that resonates with your audience on a deeper level. To better understand the new concepts of placements, paywalls, and A/B test groups, and how they enhance your overall paywall management, refer to our documentation:
To ensure a smooth transition from the previous version of A/B tests and paywalls to the new and enhanced Paywalls 2.0 with placements, follow these steps:
To ensure a smooth transition to the new paywalls 2.0 system, follow these steps to transfer your existing paywalls:
Step 1: Paywalls transfer
Review your current paywalls: Assess your existing paywalls and identify which ones need to be transferred to the new system. The main factor to consider is which paywalls or A/B tests are primarily fetched by the Adapty SDK, particularly using the
.getPaywall method. For most apps, this should be 2-5 paywalls.
Move paywalls to the new version: Choose the paywall you want to transfer and click on the Transfer button next to these paywalls. In the transfer process, the name of the paywall will be utilized for both the newly created placement and any newly added paywalls, and each paywall's ID will be converted to the newly created placement ID. This ensures consistency and facilitates easier identification of the associated content within the new system. After completing the transfer process, you have the option to rename placements if necessary. But it's important to note that once a placement ID has been created, it cannot be changed.
Ensure placement ID uniqueness: Please note that during the transfer process, it is important to ensure that the placement ID remains unique across all placements. If there is an existing placement in the new system with the same placement ID as the paywall ID of the old paywall, it will not be possible to transfer that paywall to the new system. In such cases, you will need to either delete the existing placement or resolve the ID conflict before proceeding with the transfer.
Step 2: Placement activation
After the transfer, the new placements will be displayed in the new version with an Inactive status, indicating that further configuration is required before they can be activated.
Activate the inactive placements: Once you have completed the paywall transfer process to the placement, it is important to activate them in the new system.
Please activate the placement after verifying that the paywall has migrated successfully. You should carefully review the products, remote configurations, and localizations to ensure everything is in order before proceeding with the activation of the placement. You can open the old paywall in a new tab to compare it with the new version.
Note that metrics will be synchronized in the background, so there is no need to manually verify them
To do this, you can go to the placement detail page and click on Activate placement. The old paywall will be archived as it is deprecated, while the new paywall (2.0) will be live. No modifications are required on the SDK side. Once you have activated the placement, kindly verify the functionality of the paywall in your app.
During the transfer of paywalls and A/B tests, the audience prioritization within the new created placement is determined by the number of users within each segment. Segments with fewer users are given higher priority. However, please keep in mind that the All users segment, which includes all users, will have the lowest priority among the segments.
To ensure a seamless transition of your existing A/B tests to the new paywalls 2.0 system, please follow these steps:
Step 1: A/B test transfer
Review your current A/B test: Choose the A/B tests that specifically need to be moved to the new system. These should include only the A/B tests associated with the paywalls fetched by the Adapty SDK using the .getPaywall method. For most apps, this should be 2-5 A/B tests.
Transfer A/B tests to the new version: Click on the Transfer button next to the A/B test from the A/B test list. In the transfer process, the name of the A/B test will be utilized for both the newly created placement and each A/B test's ID will be converted to the newly created placement ID. For newly added A/B tests should be "A/B test name + segment". After the transfer process, you have the flexibility to rename placements if needed. However, please note that the placement ID cannot be changed once it has been created.
Ensure placement ID uniqueness: Make sure that the placement ID remains unique across all placements, including A/B tests, during the transfer process. If there is an existing placement or paywall group with the same ID as the A/B test, it can create conflicts. Resolve any ID conflicts by deleting existing placements or adjusting the placement ID of the A/B test to ensure uniqueness.
Paywall group creation: For each transferred A/B test, a corresponding paywall group will be automatically created in the new system. This paywall group will include the list of paywalls that were associated with the old A/B test. The naming for the transferred paywall groups should be "Paywalls groups title = Paywall 1 title + Paywall 2 title". Paywall groups serve as a convenient and efficient way to manage pre-made paywalls for various purposes, including A/B testing and creating different placement configurations. To learn more about paywall groups and how they can enhance your paywall management, refer to our documentation here.
Step 2: A/B Test Activation
Once transferred the new placements appear with the Inactive state in the new version, awaiting further configuration.
Activate the inactive placements: Once you have completed the A/B test transfer process to the placement, it is important to activate them in the new system. Before activation, you should verify that the A/B test has migrated successfully. Please check the audiences and weights, and for every paywall check the products, remote configs, and localizations. The placement ID must match the old A/B test ID. Open the old A/B test to compare in the new tab. Metrics will be synced in the background, so you don't have to check and wait for them.
After verifying you should click on Activate the placement button. This will immediately delete the paywalls from the old version and enable the running of paywalls in the respective placements. The old A/B test (deprecated) will be archived and the new A/B test (2.0) will be live.
Please also consider, that there are no changes on the SDK side that are needed. After activating the placement, check the paywalls in your app.
Apart from transferring paywalls, there is another option available called Duplicate paywall or A/B test. This option allows you to duplicate paywalls and A/B tests from the deprecated version to the new version, but without converting them into placements. The duplicated items will be visible on the paywall and A/B test lists in the new version. However, note that the metrics associated with the duplicated items won't be transferred.
Use the duplicate option when you want to maintain the paywall or A/B test configurations without associating them with placements in the new version. This can be useful if you have specific use cases where placements are not required or if you plan to reconfigure them later.
Keep in mind that duplicating paywalls or A/B tests without converting them into placements means you won't be able to take advantage of the enhanced control and efficiency offered by paywalls 2.0. Consider the benefits of using placements to optimize your monetization strategies and create a more tailored user experience.
When deciding which paywalls or A/B tests to transfer to the new system, it's essential to consider the logical flow of your app and the user experience you want to create. Here's an example of how you can structure your placements:
- Onboarding placement: This placement represents the first interaction your users have with your app. It's an excellent opportunity to introduce your users to your app's value proposition and set the stage for a positive user experience. Over 80% of subscriptions are activated during onboarding, so it's important to focus on selling the most profitable subscriptions here. With Adapty, you can easily show different paywalls to different audiences and run A/B tests to find the best option for your app. For example, you can run an A/B test for users from the US, showing more expensive subscriptions 50% of the time.
- App settings placement: If the user hasn't subscribed during onboarding, you can create a placement within your app. This can be in the app settings or after the user has completed a specific target action. Since users inside the app tend to think more thoroughly about subscribing, the products on this paywall might be slightly less expensive compared to those in the onboarding stage.
- Promo placement: If the user hasn't subscribed after seeing the paywall multiple times, it could indicate that the prices are too high for them or they are hesitant about subscriptions. In this case, you can show a special offer to them with the most affordable subscription or even a lifetime product. This can help entice users who are price-sensitive or skeptical about subscriptions to make a purchase.
Most apps will have similar logic and placements, following the user journey and key points where paywalls or A/B tests can be displayed to drive conversions and revenue. In each placement, you can configure multiple paywalls or A/B tests to experiment and optimize your monetization strategies.
By following these steps and considering meaningful placements, you'll smoothly transition to the enhanced paywalls 2.0 system and unlock unparalleled control and efficiency in managing your A/B tests and paywalls.
Updated about 1 month ago