Skip to main content
Question

Feature Request: Runtime visibility control for individual Paywall tabs

  • June 30, 2026
  • 3 replies
  • 27 views

Forum|alt.badge.img

Hi RevenueCat team,

We're using the Paywall Builder's Tabs component to present different subscription plans (e.g. PRO and PLUS), where each tab contains its own complete set of content (carousel, package stack, features, etc.).

We've noticed that while Paywalls support custom variables and Rules for controlling the visibility of many individual components, there currently doesn't appear to be a way to show or hide an individual tab within the Tabs component. The only available actions are rename, duplicate, copy, and delete. We would like to show only a single tab’s content depending on mobile app’s clicked features i.e. some should show both Plus and Pro plans, others only Pro. We would like to be able to show only Plus tab or preferably hide a single tab completely.

Requested feature

It would be very helpful if individual tabs supported runtime visibility, for example via:

Paywall Rules
Custom Variables
SDK parameters

Examples:

showProTab = true
showPlusTab = false

or

{
"show_pro_tab": false,
"show_plus_tab": true
}

or simply a Visible property on each tab that could be driven by a Rule.

Use cases

This would allow a single paywall design to adapt dynamically based on:

Country or region
Available products/offerings
Remote configuration
Feature flags
A/B tests
User eligibility

For example:

US users: PRO + PLUS tabs
UK users: PRO only
DE users: PLUS only

Today, the only practical solution is maintaining multiple nearly identical paywalls that differ only in which tabs are present. This leads to duplicated layouts and additional maintenance whenever the shared content changes.

Being able to conditionally hide individual tabs would significantly reduce duplication while keeping a single source of truth for the paywall design.

Thanks for considering this enhancement!

I think this request is fairly aligned with the direction RevenueCat has already taken by introducing Rules and custom variables. Extending that capability to the Tabs container would make dynamic paywalls much more flexible without requiring teams to duplicate entire paywall layouts.

Kind regards,
David

 

3 replies

Tarek
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • July 1, 2026

Hi David,

 

I'm Tarek from Developer Support, thanks a lot for reaching out, and for such a detailed and well thought out request.

 

You're reading it right. Today our Rules can control the visibility of most components, but individual tabs are one of the specific exceptions. So there's currently no built-in way to show or hide a single tab at runtime. It's called out under Limitations here: https://www.revenuecat.com/docs/tools/paywalls/creating-paywalls/rules

 

That said, I think we can get you most of the way to your goal today, without maintaining multiple paywalls. The idea is to drive visibility with a custom variable instead of relying on the tabs container:

  • Build each plan's content (PRO, PLUS) as its own stack rather than a tab.
  • Create boolean custom variables, for example show_pro and show_plus.
  • Add visibility Rules so each stack is shown only when its variable is true.
  • Pass the variable values from your app when you present the paywall, based on country, the feature the user tapped, an experiment, and so on.

That gives you a single paywall that adapts at runtime, which covers your "PRO only" and "PLUS only" cases cleanly (your UK and DE examples). Docs for both pieces:
Rules: https://www.revenuecat.com/docs/tools/paywalls/creating-paywalls/rules
Custom variables: https://www.revenuecat.com/docs/tools/paywalls/creating-paywalls/variables#custom-variables

 

However there is one caveat. This approach doesn't reproduce the native tab switcher, so it fits best when a given condition shows a single plan's content. If you specifically need the switcher while both plans are visible (your US case), you'd keep using the tabs component there.

 

On the feature itself, driving visibility based on the selected tab, and on component state more broadly, is something the team is exploring. I can't share a timeline yet, so I wouldn't want you to build around it landing on a specific date.

 

Best regards,


Forum|alt.badge.img
  • Author
  • New Member
  • July 1, 2026

Hi Tarek,

Thank you for getting back to me and for taking the time to look for a solution.

Unfortunately, this approach won't solve our problem. We need to support all three of the following scenarios:

  • Display only the PRO tab's content.

  • Display the PLUS tab by default while allowing users to switch to the PRO tab, and vice versa.

  • Display only the PLUS tab's content (not needed in our case but optional because we’d usually show the above option).

I hope you can pass this feedback on to the product owner as a potential feature request. Implementing this functionality would allow customers like us to use your product without having to create unnecessary workarounds that add complexity to the system. It would also help save time, effort, and resources while enabling us to achieve our goals in the most efficient way.

Thank you for considering this suggestion.

Kind regards,
David


Tarek
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • July 1, 2026

Hi there,

Thanks for the detail, that's genuinely helpful, and I agree with your points.

Today there's no clean way to cover all three of those scenarios from a single paywall. Per-tab visibility isn't supported, and the switcher in your second scenario is tied to the Tabs component, so it can't be reproduced with the custom variable approach.

I've flagged this to our Paywalls product team as a feature request, with your exact use case and the three scenarios you outlined. I can't share a timeline yet, but it's now logged with the team.

Let me know if you have any other questions.

Best regards,