Hey ​@janaug,

While you can dynamically change the content of a text element based on introductory offer eligibility (as you have probably seen here), there’s no built-in way to fully hide an element from the layout - yet! This conditional visibility for paywall elements (e.g., showing or hiding text based on variables like intro offer eligibility) is actively being worked on and is high on our roadmap. While we can't commit to a specific release date just yet, this feature will directly solve the layout problem you’re facing.

How to go about it right now

The common workaround (using an empty string and setting font size to 1) avoids showing the content, but still reserves space in the layout, which is why you’re seeing misalignment issues like off-centered buttons. This is one option of course, but a couple of other suggestions to go around this, as of now can be:

Use Two Separate Paywalls

Create two versions of your paywall, one for users eligible for an introductory offer, and one for users who aren’t. You can then assign each paywall to a different Offering and at runtime decide which Offering to display based on user eligibility.

This pattern is widely used for conditional UI in Paywalls v2. It gives you full layout control while keeping everything within RevenueCat's no-code system - things to consider here is the management of said Paywalls, which can grow in complexity if you have multiple cases like this.

Build a Custom Paywall

You could also use the SDK directly to create your own native UI and dynamically show/hide elements like text based on real-time intro offer eligibility.

This option would be the most flexible, but the one that requires more custom development too!

All in all, if you need a clean, reliable layout today (apart from the workaround you have found), duplicating your paywall and routing users based on eligibility is the best option. If you are in no rush for this behaviour and are able to wait a bit, the upcoming visibility controls in upcoming Paywalls v2 versions will offer a more elegant, native solution without needing workarounds or duplicated content.

I hope this helps! 

Best,

Unfortunately the 2 paywalls wouldn’t work for me because I have 1 product with offer, and two without offers. So depending on the currently selected product I need to show/hide the text.

I would need something like: showElement only if currently selected product has offer.

Hi ​@janaug ,

Ah I see, thanks for clarifying! This kind of conditional visibility based on the selected product is something we're actively working on, so stay tuned.

In the meantime, your current workaround or a custom paywall using the SDK are still the only reliable paths - but we know it’s not ideal.

I’ve also passed this extra feedback along internally, so thanks for reporting it!

Best,
Gui