Writing fallbacks for personalization

Hi , is the personalization mistake everyone has received at least once. It happens when a campaign uses a first name that some recipients do not have. The fix is not to stop personalizing; it is to decide, in advance, what each recipient sees when a value is missing. In Inbrovia that decision is a fallback, and Campaign Guardian checks that you made it.

Variables

A variable inserts a recipient's data into the campaign. Write it in double curly braces: {{ first_name }}. Inbrovia exposes email, first_name, last_name, full_name, company and tags for every recipient, plus every custom field from your imports, such as {{ plan }} or {{ country }}. Variables work in headings, text, buttons, subject lines and preheaders.

Fallbacks

A fallback is the value used when the variable is empty. Add it with the default filter: {{ first_name | default: "there" }}. If Sarah has a first name, she sees Sarah. If a recipient has none, they see there. Choose fallbacks that read naturally in the sentence. Hi there works; Hi valued customer rarely does.

• Greeting: Hi {{ first_name | default: "there" }},
• Company: Fresh ideas for the team at {{ company | default: "your company" }}.
• Plan: Picked for {{ plan | default: "you" }} members.

Conditions on blocks

Sometimes the right fallback is to show nothing at all. A VIP offer should not appear for a Standard customer, with or without a fallback. In Studio, select the block and add a condition, such as customer_type equals VIP or country equals USA. Blocks whose condition is false are removed from that recipient's email entirely, including their spacing. Conditions can be combined with and or or, and they can be placed on sections and columns as well as single blocks.

Previewing as different recipients

Inbox Lab lets you preview the campaign as a specific person. Inbrovia includes sample recipients with different data: Sarah Johnson is a Pro-plan VIP in the USA, Michael Lee is a Starter customer in Australia, and a third sample has no name at all. Switch between them and read the campaign each time. You should see the greeting change, the VIP offer appear and disappear, and the fallback text where a value is missing. You can also preview as any recipient in your audience.

What Campaign Guardian checks

Guardian reports how many selected recipients are missing each field, so you can decide whether to add a fallback, fix the data or remove the variable.

• Every variable has a fallback, or the field is present for every selected recipient.
• Variables reference fields that exist in the audience. A typo such as {{ frist_name }} is flagged before it reaches anyone.
• Conditional blocks evaluate to true for at least one recipient, so you notice a condition that hides content for everyone.
• The subject line and preheader are checked the same way as the body.

Good habits

Write the fallback at the same time as the variable, every time. Keep custom field values consistent across imports so conditions match. Prefer conditions for whole blocks over sentences that try to cover every case. And before every send, preview as the recipient with the least data; if the campaign reads well for them, it reads well for everyone.