Skip to content
AppDues
Log in
Contact salesSign up

Paywall Rules: Conditionally Show, Hide or Reword Paywall Components

A single paywall can serve several situations if its components respond to what the customer is being offered. Paywall Rules let you control component visibility, and in some cases text, from preset conditions and custom variables, so you do not need a separate paywall variant for every case.

What Paywall Rules change

Rules are attached to paywall components and decide whether a component appears, or in some cases what text it shows. They can respond to the package a customer selects (for example, whether that package includes an introductory or promotional offer, or matches a defined package identifier) and to custom variables passed when the paywall is rendered.

Typical uses: show a trial timeline only when a trial exists, swap which package is displayed based on a custom variable, or adjust messaging for a promotional offer. The practical benefit is fewer paywall variants to maintain, because one paywall adapts to context instead of being duplicated.

Which rules exist and what each can change

The following table lists the supported rules, when each takes effect, and whether it can change visibility, text, or both. The table is reproduced exactly as published.

{{TABLE:table0001}}

Reader guidance: pick the rule by the outcome you need. If your goal is to remove or reveal a component, any of the visibility-capable rules can work. If your goal is to change wording, only offer.intro, offer.promo and offer.multiphase support text overrides; package.identifier and custom variable rules are visibility only.

Creating your first rule

In the paywall editor, open the Paywall logic tab in the left sidebar and choose the option to create a new rule. Building a rule has two parts: choosing the rule that will control component visibility, and choosing existing or new components the rule applies to.

A useful default to know: any component you add while viewing a rule is set to be visible only for that rule. You can widen that later if the component should appear in more cases. The preview highlights in purple to show how the paywall looks with the rule applied.

Rules are evaluated at runtime after the paywall is published, and a component can carry multiple rules. Rules apply in the order shown in the rule table above, and custom variable rules are evaluated in alphabetical order.

Components that cannot take rules

Most components support rules, but the following do not currently: express checkout buttons, individual pages of a carousel, individual tabs, footer, sheet, and the purchase button. If a component you need to condition is on this list, plan around it rather than expecting a rule to apply.

Worked example: a trial timeline that only appears when a trial exists

Suppose your paywall includes a timeline component that explains the free-trial period. For customers whose selected package has no introductory offer, that timeline is misleading. Attach an offer.intro rule to the timeline so it is visible only when the selected package includes an introductory offer. Because a component added while viewing a rule defaults to that rule only, the timeline will not leak into other contexts unless you deliberately broaden it. If you later want the timeline to also appear for a promotional offer, add a second rule to the same component; the rules are evaluated in the documented order.

Pre-publish checklist

  • Confirm the component you want to condition is not on the unsupported list (express checkout buttons, carousel pages, tabs, footer, sheet, purchase button).
  • Choose the rule by outcome: visibility only, or visibility plus text override.
  • Decide whether the component should be visible only under the rule, or under the rule plus other cases.
  • If multiple rules apply to one component, check the evaluation order and the alphabetical order of custom variable rules.
  • Use the purple-highlighted preview to confirm the paywall looks right with the rule applied.
  • Publish, since rules are evaluated at runtime after publishing.
Supported paywall rules, when they take effect, and what they can change
RuleWhen the rules will take effectWhat Rules are available
offer.introIf the user selects a package that includes an introductory offerVisibility and text overrides
offer.promoIf the user selects a package that includes a promotional offerVisibility and text overrides
package.identifierIf the user selects a package that matches the defined identifierVisibility only
Custom variableIf the paywall is rendered with or without the defined custom variable.Visibility only
offer.multiphaseIf the user selects a package that includes a promotional offerText overrides only

Reproduced exactly as published; availability and supported rule types may change.

Frequently asked questions

Can every rule change both visibility and text?

No. offer.intro and offer.promo support visibility and text overrides. package.identifier and custom variable rules are visibility only. offer.multiphase supports text overrides only.

In what order are rules applied?

Rules apply to a component in the order shown in the rule table, and custom variable rules are evaluated in alphabetical order. A component can carry multiple rules.

When are rules evaluated?

At runtime, after the paywall is published.

If I add a component while viewing a rule, where does it appear?

It is set to be visible only for that rule by default. You can edit this later so the component appears in more cases.

Which components cannot take rules?

Express checkout buttons, individual pages of a carousel, individual tabs, footer, sheet, and the purchase button.