Email content, banners, CTAs
Review the shared email fields and best practices used across OmniLab notification emails.
This guide covers the shared email fields used across OmniLab notifications: Email Subject Line, Email Preheader, Email Banner, Email Content, Email CTA Label, and Email CTA Link.
The shared email block
Every notification type uses the same email structure. What changes from one type to another is the trigger and the selected scope, not the fields themselves.
That makes these content rules reusable whether you are editing Winner, Touchpoint Unlocked, or a booking notification.
Email Subject Line
Use Email Subject Line to tell the recipient what happened before they open the email.
Good subject lines are:
- specific about the outcome
- short enough to stay readable on mobile inboxes
- clear even without the preheader
{{ contact_firstname }}, your booking for {{ event_title }} is confirmed
You won {{ reward_display_name }}
Your reward from {{ enterprise_name }} is readyEmail Preheader
Email Preheader is the short text many inboxes show next to the subject line. It is not mandatory for delivery, but it is strongly recommended because it improves context and often improves open rates.
Use it to add the next most useful detail, such as a date, location, or action:
- the booked slot
- the reward redemption step
- the reason to open now
Email Banner
Email Banner gives the message visual context at the top of the email.
Current banner guidance for notification emails:
- Recommended size:
900 x 600 px - Ratio:
3:2 - Supported formats:
JPEG,WEBP,PNG
Use the specs link in the upload control when you need example dimensions. Keep the focal point centered and avoid putting essential tiny text inside the banner image.
Email Content
Email Content is the main body of the message. Lead with the outcome, then immediately tell the recipient what to do next.
Best practices:
- Put the main outcome in the first two lines.
- Keep paragraphs short for mobile reading.
- Use clear headings or short sections when the message is longer.
- Do not hide critical information only inside the banner image.
All text fields support Liquid variables, so you can personalise the message with contact, reward, booking, or Touchpoint data. See Liquid templates and variable bindings.
CTA label and link
Use a CTA only when the email needs a clear next action, such as opening a landing page, viewing booking details, or starting redemption.
Rules:
Email CTA LabelandEmail CTA Linkmust be used together.Email CTA Linkmust start withhttp://orhttps://.- Use action-based labels such as
View my booking,Redeem my reward, orOpen campaign.
If the email is purely informative, leave both CTA fields empty.
Mobile, dark mode, and readability
Most notification emails are read on phones, so optimise for quick scanning:
- keep the most important information above the fold
- avoid long image-heavy layouts
- make sure links and CTAs are understandable out of context
- test the message in your email platform before launch, especially if you use strong brand colours or image-led banners
Common validation cues
| Message | What it means | Fix |
|---|---|---|
Email subject line is missing for {{notification_type}} notification | The email has no subject. | Fill Email Subject Line. |
{{notification_type}} notification has no email preheader text | The email can still send, but the inbox preview is weaker. | Add Email Preheader. |
Email banner image is missing for {{notification_type}} notification | The banner field is empty. | Upload an Email Banner. |
Email content is missing for {{notification_type}} notification | The message body is empty. | Fill Email Content. |
{{notification_type}} notification has invalid CTA link '{{invalid_url}}' | The button link is malformed. | Use a valid URL beginning with http:// or https://. |
Related
Configure notifications globally
Apply one email setup everywhere a notification type can send.
Configure notifications by touchpoint
Create different messages for different rewards or Touchpoints.
Liquid templates and variable bindings
Personalise notification content with supported Liquid variables.
Notification types reference
Check which notification types your message design needs to cover.