How to show or hide template blocks and sections based on dynamic variables

If you want to show/hide conditions based on profile data (e.g., location, language, etc.), you need at least 1 profile with that data. 

Profile and custom properties can be added in the following ways: 

• Sign-up forms
• CSV uploads
• Ecommerce integrations 
• List growth and loyalty integrations, like Typeform or Yotpo

Learn more about profile properties in Klaviyo. 

Similarly for event properties, there must be 1 event in your Klaviyo account. Then, you can show/hide blocks based on that flow’s trigger event using custom-coded blocks. You cannot reference event data using the logic builder. 

So, in an abandoned cart flow with the trigger Started Checkout, you can build show/hide conditions based on a cart’s value or the specific items the customer added. 

If you prefer more control, or if you’d like to build a condition using event data, dates, or booleans, custom code your show/hide blocks rather than using the logic builder. To start from scratch using code, select the Use code button from the show/hide logic settings. 

Alternatively, convert an existing show/hide condition to use code with the Convert to code button. 

If you choose to use code, make sure you have a strong understanding of Django, programming logic, and Klaviyo’s data types. Klaviyo’s support team is not able to provide direct support or troubleshooting for custom code. 

Learn more about supported condition structures. 

Show/hide conditions based on event data

If your email is sent as part of an event-triggered flow (e.g., an abandoned cart or order confirmation flow), you can show/hide blocks based on the details of that flow’s trigger event. So, in an abandoned cart flow with the trigger Started Checkout, you can custom code show/hide conditions based on a cart’s value or the specific items the customer added. Learn more about event variables.

Understand how data is stored

Before configuring your show/hide condition, check to see how your data is stored. There are 5 data types in Klaviyo: 

• Text
• Number
• Date
• Boolean
• List

How your data is stored will influence which show/hide conditions will work for you. Learn how to identify data types in your own account.

Craft your message

The first step to adding custom-coded show/hide conditions in a message is to build the email template. This section will walk through a specific example, but you can follow the same steps to set any block to display based on your own criteria.

For example, if your company sells leather bags, you may collect customer preferences for how they use their bags with a sign-up form, as shown below. 

You can then display a different image based on your customer’s bag preference. For example, if the customer’s preference is “Work,” the bag will appear in an image next to a laptop. If the customer’s preference is “Outdoors,” the bag will appear near a scenic overlook on a hiking trail. 

1. Create a campaign or flow message.
2. Add an image block.
3. Upload the work-related image to the block.
4. Click Display from the image block’s customization menu.
5. Under Show/hide logic, select Use code. 
6. Add this condition: person|lookup:'Bag Preference' == 'Work'. 
7. Click Save Changes. 
8. Click Done on the block.

This block will show only to people who have selected “Work” as their preference. 

Next, add in the travel-related image to a new block under the work-related image. Follow the same steps as before, but this time, use the condition person|lookup:'Bag Preference' == 'Outdoors'. 

This block will only show to people who have selected “Outdoors” as their preference. 

Finally, add in an image to appear for anyone who hasn’t selected either “Work” or “Outdoors.” Use a more generic image, and this condition: person|lookup:'Bag Preference' != 'Work' and person|lookup:'Bag Preference' != 'Outdoors'.

Here, != means "does not equal", so this condition looks for people who have chosen something other than “Work” or “Outdoors,” or have never selected a preference. 

Once you’ve configured each of the blocks, preview your message using 3 profiles. These profiles should be subscribers who meet one of each of the image criteria:

• Customer who chose “Outdoors” 
• Customer who chose “Work”
• And customers with no preference/other preference

You can use these steps to show or hide blocks based on any profile or event data in your account. 

Create a show/hide condition with profile data

If you are building a custom-coded show/hide condition based on a profile property, replace the sample variable from the tables in the conditional logic reference (e.g., person|lookup:'Favorite Color') with your profile property. 

To find the correct variable to use:

1. Click Personalization to open the personalization menu.
2. Choose an option from the menu to add it to the text block.
3. Copy the variable name from within the tag. To identify the variable name, remove the curly brackets around the variable, as well as |default:'' at the end (if present), along with any other filters.
   For example, in the screenshot below, the full tag is {{ person|lookup:"Accepts Marketing"|default:"" }}. The variable name is person|lookup:"Accepts Marketing", so select that portion to use in your show/hide condition. 

Create a show/hide condition with event data

You can use event data to show or hide a block if your message is part of an event-triggered flow. Only data within the trigger event can be used in a show/hide condition. 

To identify event variables:

1. From the template editor, click Preview & test.
2. Under Preview data source, click Event.
3. From the dropdown menu, select the event that will trigger the message you’re building. 
4. Scroll through the Event properties to find the data you’d like to include. 
5. Click the property name to copy the tag. 
6. Paste the tag into a text block or text editor. 
7. Remove the curly brackets (i.e., {{ and }}) from the tag, as well as any filters.
8. Use the variable that remains in your show/hide condition.

In the screenshot below, you’ll see the tag {{ event|lookup:'Item Count' }}. You’ll only need the text event|lookup:'Item Count' for your show/hide condition. Note that your data may use a different structure, like {{ event.extra.line_items.0.title }} or {{ event.ShippingAddress.address1 }}. Use the variable as it appears in your event data. 

Customize your show/hide conditions

Learn how to build custom show/hide conditions using the conditional logic reference. This resource contains sample conditions, which you can customize using your own profile and event data.