Adapty's placements feature enables the display of paywalls at various stages of the user journey within an app. By linking specific paywalls or A/B tests to each placement, Adapty offers the convenience of remotely modifying the displayed content without the need for any code changes.
To begin working with placements in Adapty, navigate to the Placement section within the app's interface. The Placement list provides a clear overview of all the different locations within the user journey where paywalls or A/B tests can be displayed. Each item in the list represents a specific placement, and you can easily manage and modify them as needed. You can edit the details of each placements, associate it with the desired paywall or A/B test for a specified audience, or remove unnecessary placements.
To create a new placement, simply click on the Create placement button, and you will be directed to the placement creation page.
When creating a new placement, you will need to fill in the placement name and Placement ID fields. These fields provide general information about the Placement.
- The placement name be filled with a name that accurately represents the placement within the Adapty system. This name serves as a means of identification and helps you organize and manage your placements effectively. You have the flexibility to edit the placement name even after it has been created, allowing you to refine and update the name as needed.
- The placement ID is automatically generated from the Adapty SDK and cannot be modified once it has been created. It guarantees the uniqueness and integrity of each placement. To ensure accurate identification and avoid conflicts, each placement ID must be unique and not already exist in the system. By enforcing this requirement, Adapty maintains the integrity of placement and enables precise tracking and management within the system.
In the context of placement within Adapty, adding an audience to a placement allows you to target specific user segments with tailored content, such as paywalls or A/B tests. By associating an audience with a placement, you can ensure that the right content is displayed to the right users at the appropriate stages of their user journey.
Clicking the Add audience button triggers the display segments of a dropdown menu. These segments represent different audience groups that have been defined and created within Adapty.
To associate a specific audience with the placement, users can simply select the desired segment from the dropdown list. Once an audience is selected, it is immediately reflected in the designated audience selection field on the placement page. This clear association allows to precisely align the placement with the chosen audience, ensuring that the right paywalls or A/B tests are displayed to the intended users.
Furthermore, you can add paywalls or set up A/B tests for the selected audience by navigating to the appropriate section on the placement page. This enables the creation of targeted experiences tailored to specific audience segments. In cases where multiple audiences are associated with the same placement, you can easily manage their priority. By leveraging a simple drag-and-drop functionality, audiences can be repositioned in the desired order, reflecting the priority in which the placements should be displayed.
The Run paywall option allows you to display a specific paywall exclusively for a certain placement, ensuring that all users within the associated audience segment see the same paywall. This option is particularly useful when you have already identified the best-performing paywall and want to consistently deliver it to your targeted audience.
To learn more about running paywalls in Adapty and optimizing their performance, you can refer to our documentation on paywall functionality.
The Run A/B test option allows you to show different paywalls to app users within a specific audience. By running an A/B test, you can compare different options and determine the most effective paywall for that audience segment. You can select an existing paywall bundle or create a new A/B test from scratch. The selected paywalls will be displayed on the placement detail page, with significant results highlighted in green. Running an A/B test helps you optimize conversions and find the best paywall option for your audience.
You can refer to the documentation on creating and running A/B tests for more detailed instructions. This documentation will provide step-by-step information on setting up A/B tests and leveraging them effectively within the Adapty dashboard.
Adapty provides robust metrics and tracking capabilities for placement, allowing you to gain valuable insights into the performance of your paywalls and A/B tests. These metrics enable you to measure the effectiveness of your monetization strategy. To learn more about the placement metrics and how to interpret them, you can refer to the documentation.
With the new placements system, you can create and run paywalls without requiring a release in the app stores. This applies when the paywalls are created within existing placements that have already passed moderation and are live in the store. Similarly, for A/B testing, you can create any number of new variants without the need for a release in the existing placement.
Regarding audiences, the same logic applies. You can make changes to the audience targeting without requiring a new release in the app stores.
However, it's important to note that if you add another placement for the paywall display location, a new release in the stores will be necessary.
Adapty allows you to provide fallback paywalls that will be used when a user opens the app and there's no connection with Adapty backend (e.g. no internet connection or in the rare case when the backend is down) and there's no cache on the device.
The fallbacks are available in the JSON representation of your paywalls/products list, following the exact same format as provided by the Adapty backend. To learn how to set up fallback paywalls using Adapty, please consult our detailed documentation.
Updated about 1 month ago