Rules allow you to decide which users see a paywall when a trigger is fired.

  1. Rules are evaluated in order.
  2. Once a rule is matched, no other rules are evaluated within the campaign.
  3. A user's paywall or holdout assignment is sticky.

📘

Assignments Are "Sticky"

Once a user is assigned a paywall or a holdout within a rule, they will continue to see that assignment, regardless of the paywall's percentage, unless you reset assignments by clicking the reset icon next to Assigned or remove the paywall from the rule via the X button.

Remember: Changing a paywall's percentage only affects new users. It doesn't affect assignments for users who already saw that paywall.

This allows you to decide if you should continue showing an old paywall to users who already saw it. For example, you may decide to increase prices but keep the paywall with the old pricing visible for those who've already seen it.

Adding Rules

Add a rule to a campaign by clicking the Add Rule button from within a campaign.

Updating Conditions with the Rule Editor

Change a rule's condition by clicking the highlighted condition itself:

In this example, we add a condition that evaluates to true if user has logged greater than or equal to 3 days.

In this example, we add a condition that evaluates to true if user has logged greater than or equal to 3 days.

This opens the Rule Editor. Here, you can edit the rule to set conditions based on user, device or event parameters and set a limit to how often the rule is matched:

In this example, only users who have the en deviceLanguageCode and have a creator account_type will match this rule. They will only match this rule once every 2 days.

Clicking on the condition reveals a dropdown of possible conditions which you can filter on:

Conditions are added to this list when data is retrieved from the SDK via triggering paywalls or setting user attributes. If a condition doesn't yet exist in the drop down, you can manually add it by referencing it with dot syntax. For example, user.custom_parameter would reference custom_parameter on the user object. As with paywall text variables, the following objects are all available to use:

ObjectDescription
userUser attributes your SDK implementation sets on the user. See Setting User Attributes
paramsParameters defined when triggering a paywall. See Triggering Paywalls and Tracking Events
deviceDevice attributes that are gathered by the SDK.

Rule Settings

The following settings can be access by clicking the ellipse icon to the right of any rule

SettingDescription
Move UpSwaps the rule's order with the rule directly above it.
Move DownSwaps the rule's order with the rule directly below it.
PausePauses the rule, preventing it from being evaluated all together.
DeleteDeletes the rule.