Email conditions and provider syntax reference
You'll find the rules and comparisons you can use to tailor an email, plus what to check in your email platform before sending.
Use email conditions to show each contact the passage that fits them. RightMessage checks an ordered set of branches and uses the default content when none match. The fields you can use come from your connected email platform and question mappings.
Question mapping
Choose Question mapping when your question is already mapped to a field in your email platform. Having the question in your RightMessage library isn't enough.
| If you'd like to... | Use |
|---|---|
| Choose a mapped question | The question picker, which lists the question wording and answer options. |
| Choose a different question | Change Question. |
| Write for contacts who don't match | Default content (shown if no conditions match):. Your selected passage becomes the starting fallback. |
| Match the saved answer exactly | Equals (exact match). It compares the field with the mapped segment value. |
| Find an answer within a longer value | Contains (partial match). Check that this fits how your platform stores the data. |
| Write each alternative | The content editor for each segment. The answer wording visitors see may differ from the value stored in your platform. |
New conditions start with Equals (exact match). Existing conditions keep their saved operator. Before switching to Contains (partial match), check the stored value in your platform. When you save, only alternatives with both content and a mapped value become branches.
Advanced rules
You can use Advanced rules with available email-platform fields even without a mapped question. The field picker groups mapped RightMessage questions, native fields, custom fields, and tags when your integration provides them.
| Control | What it does |
|---|---|
| Default content (shown if no branches match): | Supplies the fallback outside the ordered branches. |
| Branch | Holds rules and the content to show when they match. The first matching branch supplies the content. |
| All rules must match (AND) | Requires every rule in the branch to match. This is the default. |
| Any rule may match (OR) | Requires only one rule in the branch to match. |
| Choose a field... | Selects the email-platform field or mapped question to compare. |
| Operator | Offers equality, inequality, contains, greater than, less than, greater than or equal, or less than or equal, depending on the field. |
| Value | Lets you choose a catalog value or type one. Supported values include strings, numbers, and booleans. |
| Add conditions | Adds another rule to the branch. |
| Rule removal | Appears when the branch has more than one rule. |
| Add branch | Adds another content alternative at the end. |
| Branch removal | Appears when there is more than one branch. |
The available operators follow the field's type:
| Field type | Available comparisons |
|---|---|
| Mapped question or text field | Equals (==), does not equal (!=), and contains. |
| Numeric field | The text comparisons above, plus greater than (>), less than (<), greater than or equal (>=), and less than or equal (<=). |
| Boolean field | Equals and does not equal. |
| Tags | Contains only. |
Choose the comparison that fits your stored value. Finding digits inside text is different from comparing numbers.
Complete every rule you intend to use before saving. RightMessage removes rules with no field token or an empty value. It also removes branches with no remaining rules or no content. If no complete branch remains, the editor asks you to complete one.
Put specific branches before broader ones if both could match. Add branch adds to the end. There isn't a drag or move control. To reorder existing branches, edit the rules and content in their current positions.
Saving, editing, and removal
Use Add Conditional Content for a new condition and Update Conditional Content for an existing one. Cancel closes the dialog without applying your edits. Remove puts the condition's default content back into the email.
You can still edit a condition if its original field disappears from the current catalog. Check that field and its mapping before sending.
The editor shows separate messages for fields that are loading, missing mappings, and request errors. A missing question mapping blocks Question mapping and AI personalization. It doesn't block Advanced rules when email-platform fields are available.
Check your email platform's syntax
RightMessage uses field information from your connected platform to construct tokens. Common object names include subscriber for Kit and Drip, customer for Customer.io, visitor for Bento, and user for Userlist, Encharge, and Braze. Several CRM integrations use contact. Some platforms use field tokens without an object prefix.
Email platforms don't all accept the same Liquid, filters, tag checks, or numeric comparisons. A template can render in RightMessage but still be incompatible with your platform's sending engine.
For example, website Liquid that uses ActiveCampaign data isn't automatically valid inside an ActiveCampaign email. Use ActiveCampaign's supported personalization and conditional-content syntax. Copy doesn't translate every expression into the sending platform's language.
For Kit, paste into your intended draft, check its subscriber fields and conditions, then use Kit's preview and test send. Include a contact with no mapped answer to check the fallback. Repeat this check after changing mappings or switching integrations.
Create and export a personalized email covers the complete workflow.