Hi @Beebs,

Welcome to the Community.

Due to how consent is stored, we're unfortunately not able to use Show/Hide blocks based on consent. This feature as it only works with Profile or Event properties. Consent is technically not stored as an accessible profile property for this feature.

The workaround would be to use custom properties. While collecting consent you would also want to collect or sync over a custom property that can be used to allow for Show/Hide blocks. This could be setup as a hidden field in a signup form. 
 

Submit Hidden Fields

Hidden fields are additional properties that will be added to a subscriber's profile in Klaviyo. This allows you to track viewers who interact with your form. By default, all new signups must have a $source property — this is what identifies how they were added to your account. You can analyze how people come into your account in the List Growth Report.

 

Additionally, you can configure this property name (e.g. Newsletter Popup). Similar to text inputs on forms, if you add additional hidden fields for properties that already exist in someone's profile, they will be overwritten by the new value when they submit the form. For example, if you’re using a form to gather collection preferences, and a customer has selected previously that they are interested in your men’s collection, if you have a form pointing to your women’s collection with a hidden field for interest in your women’s collection, this property will be overwritten. This option is only available for buttons that submit the form, not close form, go to URL,

For example, if you have a signup form that collects a customer property called SMS consent (separate from $consent) using Hidden Fields:

​​​​

As customers fill this out, a custom property SMS consent would be added with a value of True. You would then use the following syntax using Show/Hide:

person|lookup:'SMS consent' = 'True'

Likewise, you can add custom properties via CSV update to add this property on existing profiles. Keep in mind however this custom property is not the same as $consent and would not allow you to send SMS to profiles that are not truly consented to receive SMS. 

Hope that helped!
Alex

Thanks so much, I’ll try this approach, I think it should work