You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Docs for testing paywalls
* Move images to the correct folder
* Fix 1 image that shouldn't have moved
* Fix broken link
* Add Android Studio testing instructions
This page refers to testing paywalls to ensure they're working as expected before releasing them to production. If you're looking to learn about A/B testing paywalls, see [Experiments](/tools/experiments-v1).
9
+
:::
10
+
11
+
There are several ways to test your paywalls before releasing them to production. Here are a few options to consider:
12
+
13
+
## 1. Preview in the RevenueCat app
14
+
15
+
You can preview paywalls directly on device using the RevenueCat iOS app version 1.2 and above. This provides a quick way to see how your paywall will look, without building your app.
16
+
17
+
Just tap on "Projects" in the bottom menu, navigate to your project, then tap on "Paywalls" to see a list of all your paywalls.
18
+
19
+
:::info Draft paywalls
20
+
The RevenueCat app also supports previewing draft paywalls, which you'll see as unique options in the list to select and preview.
21
+
:::
22
+
23
+

24
+
25
+
You can also modify how the paywall view is built (e.g. Full Screen vs. a Modal Sheet view), and whether dark or light mode is used.
26
+
27
+

28
+
29
+
:::warning Variable preview values
30
+
Please note that the RevenueCat app uses preview values for any variables your paywall uses, so the prices displayed will not reflect the actual prices of your products. They're only intended to reflect how your paywall will look when real values are inserted in your app.
31
+
:::
32
+
33
+
## 2. Override a Customer's Default Offering
34
+
35
+
The simplest way to test a paywall is by overriding an individual customer's offering through their Customer Profile in the RevenueCat dashboard:
36
+
37
+
1. Navigate to the Customer Profile for your test device
38
+
2. In the current offering section, click "Edit"
39
+
3. Select the offering containing your test paywall
40
+
4. Launch your app and navigate to the paywall to see the paywall of your overridden offering
41
+
42
+

43
+
44
+
## 3. Create a Targeting Rule for an internal app version
45
+
46
+
You can create a Targeting Rule to show specific paywalls to internal builds of your app:
47
+
48
+
1. Create a new Targeting Rule
49
+
2. Set the condition to "App Version equals X.Y.Z" using your internal build version
50
+
3. Set the offering to the one containing your test paywall
51
+
4. Install the internal build on your test device
52
+
53
+
This approach is useful for testing paywalls across your team before releasing to production.
0 commit comments