Kualo / docs
On this page

Show content with display conditions

Show or hide a row based on a subscriber's attributes - the visual, no-code way to personalise.

2 min read Updated 10 Jun 2026

Display conditions let you show or hide a whole row of your email based on a subscriber's attributes - location, interests, age, anything you store about them. It's the visual, no-code way to personalise (for the HTML-based approach, see Use dynamic content). This guide covers setting one up.

Set a display condition

  1. Make sure the attribute you want to use exists on your list - see Add attributes to your list.
  2. Open the email you want to edit.
  3. In the email designer, go to the Rows section.
  4. Drag a row into the email and select it.
  5. In the row's properties, select Add Condition.
  6. Configure the condition - which attribute, and what it must match.
  7. Click Confirm.
  8. Preview with the eye icon, choosing different attribute values from the dropdown to see how each subscriber's version looks.

The condition then shows in the row's properties for easy editing.

Where it's useful

  • Location - region-specific offers, local events, timezone-aware content.
  • Demographics - age-appropriate recommendations, interest-based blocks.
  • Behaviour - content keyed to purchase history or engagement level.

Best practices

  • Start simple - one attribute like location or interest.
  • Always provide a fallback - default content for subscribers who lack the attribute, so nobody sees a blank.
  • Test thoroughly - preview across different attribute values, including empty ones.
  • Keep it relevant - only condition on things that genuinely improve the email.

Troubleshooting

Conditions don't work as expected - check the subscribers actually have data for that attribute, and that the values match your criteria exactly. Test with a few different profiles.

Content shows for the wrong people - review your AND/OR logic and check for conflicting conditions and data-type mismatches.

Subscribers see blank sections - always include fallback content; the gap means some contacts lack the attribute.

Performance issues - limit the number of conditions per campaign and avoid deep nesting; for very different audiences, separate campaigns can be simpler.

If a display condition misbehaves, open a support ticket.

Was this helpful?
Your feedback helps us find gaps in the docs.
Still need a hand?
Real people, around the clock - start a chat or open a ticket and we'll help you put it right.