Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 14 additions & 8 deletions src/content/docs/version-3.0/ab-tests.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -112,18 +112,24 @@ Regular, onboarding, and cross-placement tests appear on separate tabs that you
/>
</Zoom>

## Crossplacement A/B test limitations
## Crossplacement A/B test limitations and priority

Currently, crossplacement A/B tests cannot include onboarding placements.
Crossplacement A/B tests guarantee that the user sees the same variant across all placements in the A/B test, but come with the following limitations:

Crossplacement A/B tests guarantee the same variant across all placements in the A/B test, but this creates several limitations:
* Crossplacement A/B tests cannot include onboarding placements.

- They always have the highest priority in a placement.
- Only new users can participate, i.e. the users who have not seen a single Adapty paywall before (to be precise, `getPaywall` SDK method was called). That is done because it's not possible to guarantee for the old users that they will see the same paywall chain, because an existing user could have seen something before the test has been started.
* Crossplacement tests only affect new users — those who have not seen a single Adapty paywall, and whose app never called the `getPaywall` SDK method. Adapty cannot guarantee that the paywall chain of other users remains consistent.

* The first placement encountered by the user determines which paywall Adapty displays for them. You cannot change which paywall a user is assigned, nor enroll the same user in more than one crossplacement A/B test.

* Once a user is assigned a crossplacement paywall, they see it for 90 days, even after you stop the test. Use the **[Cross-placement variation stickiness](general#9-cross-placement-variation-stickiness) setting to control the duration of this assignment.

* Crossplacement A/B tests always take priority over regular and onboarding A/B tests. If a new user qualifies for both a crossplacement test and a regular test on the same placement, the crossplacement test is shown.

* When multiple crossplacement A/B tests with the same audience share the same placement, Adapty automatically assigns test priority based on the order they were added. The first test gets the highest priority. You cannot manually change it.

* Tests that target smaller segments of your audience automatically take priority over those targeting the All Users segment.

:::important
By default, once a user is assigned to a cross-placement test variant, they stay in that variant for 3 months, even after you stop the test. To override this behavior and allow showing other paywalls and A/B tests, configure the **[Cross-placement variation stickiness](general#9-cross-placement-variation-stickiness)** setting in the **App settings**. However, note that, even then, they won't be able to be a part of any other cross-placement test ever.
:::

:::note
In Analytics, a cross-placement A/B test appears as several child tests — one per placement. They follow the naming pattern `<test-name> child-0`, `<test-name> child-1`, etc., matching the order of placements on the A/B test details page. To view results for a specific placement directly, filter by **Placement** instead.
Expand Down
Loading