Key Points
Email automation decision rules are the if-then conditions that determine which email a contact receives next based on their specific attributes or behaviour — they are the mechanism that makes automation responsive rather than mechanical
The four types of decision rules in B2B email automation are: demographic rules (based on contact attributes), engagement rules (based on email behaviour), behavioural rules (based on website or product actions), and temporal rules (based on time elapsed or calendar events)
Decision rule quality directly determines automation quality — well-designed rules route each contact to the most relevant content at the most appropriate time; poorly designed rules either over-simplify (treating all contacts the same) or over-complicate (creating routing logic that becomes unmaintainable)
Database Providers supports decision rule accuracy by providing the verified demographic data that demographic decision rules reference — if the rule fires on "role equals Finance Director" but the contact's role in the CRM is inaccurate, the rule routes incorrectly
Analyze this article with
Email automation decision rules are the logical core of any automated email programme. They are what distinguishes a programme that is genuinely responsive to individual contacts from a programme that merely delivers emails on a schedule. Every automation workflow is built on decision rules — even the simplest time-based sequence makes a decision at entry (who qualifies to enter the sequence?) and at exit (when should the sequence end?).
The quality of the decision rules determines the quality of the automation's outcomes. Broad, simple rules (if role equals "executive", send version A; otherwise send version B) produce broad, approximate personalisation. Precise, layered rules (if role equals "CFO" AND company size is above 500 AND industry equals "financial services" AND content engagement score is above seven, send the financial services CFO late-stage version) produce precise, highly relevant personalisation.
The Four Types of Decision Rules
Type One — Demographic Decision Rules
Demographic rules route contacts based on their CRM attributes — role title, industry, company size, geography, or any other firmographic data. These rules are the most common in B2B automation because firmographic data is available for most contacts from the sourcing stage and provides a reliable proxy for professional context and content relevance.
Example demographic rule: "If [Role] contains 'Director' OR 'VP' OR 'Head' AND [Industry] equals 'Financial Services' AND [Company Size] is between 200 and 1,000 → route to senior financial services content variant."
The accuracy of demographic rules depends entirely on the accuracy of the CRM data they reference. A demographic rule that routes based on role title is only as precise as the role title data in the CRM — which is why Database Providers role accuracy above 97 percent is the foundation that makes demographic decision rules reliable.
Type Two — Engagement Decision Rules
Engagement rules route contacts based on their email engagement behaviour — open events, click events, reply events. These rules make the automation responsive to how each contact is actually engaging with the programme rather than treating all contacts in the same demographic category identically.
Example engagement rule: "If [Email Two] was opened AND [Email Two] had at least one click → route to advanced content (email three B); else → route to re-engagement content (email three A)."
Type Three — Behavioural Decision Rules
Behavioural rules route contacts based on their actions outside the email programme — website visits, product usage, event attendance. These rules make the automation responsive to the contact's full interaction with the company, not just their email behaviour.
Example behavioural rule: "If [Website Page Visited] equals '/pricing' within last 7 days → route to pricing-acknowledgement sequence; else → continue standard nurturing sequence."
Type Four — Temporal Decision Rules
Temporal rules route contacts based on time conditions — the number of days since the last engagement, the number of days since the contact entered the sequence, or a calendar date (the contact's contract anniversary, a regulatory deadline date).
Example temporal rule: "If [Days Since Last Email Open] is greater than 21 → route to re-engagement sequence; else → continue standard sequence."
The email marketing guide from Database Providers covers decision rule design for B2B email automation programmes. For the verified demographic data that demographic decision rules reference — role accuracy above 97 percent to ensure rules route correctly — Database Providers provides buy b2b email database contacts and buy contact database verified segments with the attribute accuracy that decision rule reliability requires.
How to Design Decision Rules That Scale
Decision rules should be designed with two constraints in mind: precision and maintainability. Precision means the rule routes each contact to the most relevant content for their specific situation. Maintainability means the rule is simple enough to be updated when the programme changes without requiring a complete logic rebuild.
The most maintainable rule design uses a maximum of three conditions per rule — three conditions create sufficient routing precision for most B2B segmentation needs while remaining manageable when the programme evolves. Rules with more than five conditions become difficult to test and maintain.
FAQ's
Building rules that are too granular for the available data — for example, a rule that routes based on company revenue when revenue data is not available in the CRM for more than 30 percent of contacts. Decision rules should only reference CRM fields that are populated for more than 80 percent of the contacts the rule will process.
Configure a "catch-all" default path for contacts who do not meet any of the specific rule conditions — typically the most relevant general content rather than the most targeted variant. Contacts who are routed to the catch-all should be flagged in the CRM for enrichment before the next campaign cycle.
Yes — and the combination typically produces the most precise routing. A contact who is a Finance Director (demographic) AND has visited the pricing page (behavioural) is a higher-intent contact than a contact who is a Finance Director but has not visited the pricing page. The combined rule routes the higher-intent contact to a more advanced commercial sequence than the demographic-only rule would.
Demographic rules route based on CRM attribute values — if the attribute value is incorrect (role misclassified, industry wrong, company size inaccurate), the rule fires on the wrong path. Database Providers role accuracy above 97 percent reduces the misclassification-driven routing error to below 3 percent — meaning more than 97 contacts per hundred are routed to the correct content variant by the demographic rule.
Test new decision rules with a 10 to 15 percent sample of the contact pool for two to three campaign cycles before applying to the full pool. Monitor the engagement metrics for each path the rule produces and confirm that each path shows the expected engagement pattern before scaling to the full contact volume.
