Strategy
Part of Marketing automation strategy: platform control tests to run
A six-block marketing automation strategy framework, from problem to measurement
A six-block marketing automation strategy framework that links one customer problem to evidence, operating choices, controls and review gates in England.
A marketing automation strategy framework should force a small number of decisions before anyone selects a channel or builds a workflow. This six-block method is an editorial planning tool. It does not predict an outcome or guarantee compliance.
What to take away
- A six-block framework forces decisions on problem, audience and intervention before any channel or workflow is built.
- Separate output from outcome so a send count is not mistaken for impact.
- One bounded intervention per planning period keeps failure diagnosable.
- Every metric needs a defined event, numerator, denominator, period and owner.
- Named reviewers must approve data protection, PECR and other rules before a pilot starts.
Block 1: problem definition
Owner: the person accountable for the customer process.
Problem Definition Gate
Can you show where the problem occurs?
Proceed to Block 2
Stop and gather evidence
Input: a recent workflow map, service evidence and unresolved exceptions. Output: one observable problem statement, a population and a time boundary. "Improve engagement" fails this block. A defined delay or incorrect hand-off can be investigated.
Gate: stop if the team cannot show where the problem occurs or who has authority to alter the process.
Block 2: intended change
Map inputs, the proposed automated activity, its immediate output and the later outcome. List the assumptions connecting each step. HM Treasury's Magenta Book uses theory-of-change work to surface causal steps, evidence weaknesses and alternative explanations. The guidance concerns government evaluation, but the separation between output and outcome prevents a send count from being mistaken for impact.
Intended Change Chain
- Inputs
- Automated activity
- Immediate output
- Later outcome
- Assumptions connecting steps
Gate: reject any chain that jumps directly from a platform action to revenue without an evidenced mechanism.
Block 3: audience boundary
Owner: research or insight lead, working with the process owner.
Audience Boundary Checklist
- Eligible account described
- Workflow users and approvers listed
- Important exclusions noted
- Source, geography, sample, date retained
- Recruitment and eligibility screen
- Uncertainty log
Describe the eligible account, the people who use or approve the workflow, and important exclusions. Retain the source, geography, sample and date behind each audience claim. A UK technology statistic may shape a question; it does not prove an England buyer segment.
Output: a recruitment and eligibility screen plus an uncertainty log.
Block 4: strategic choice
Write what the team will do and what it will defer. Select one problem, one primary audience and one bounded intervention for the planning period. Tactics, channels, tools and rules follow from this choice; they are not substitutes for it.
Gate: pause when the proposal depends on several untested changes at once. Reduce the scope until failure can be diagnosed.
Block 5: operating design and authority
The operations owner writes a rule card. It covers trigger, eligibility, exclusions, source data and action. It also covers timing, frequency, suppression and exception queue. Manual override, pause control and retirement date complete the card. The tool owner then checks whether the current system can implement and log those requirements.
Do not assume a capability because a platform uses "automation". Save dated first-party evidence or run a disclosed test. HubSpot's paid Marketing Hub tiers include workflow automation, but its free tier is limited.
Mailchimp's Standard plan includes customer journey builder and prices by contacts. Salesforce Marketing Cloud offers Journey Builder for enterprise teams and prices by edition and contacts.
Klaviyo focuses on ecommerce flows and prices by active profiles. Customer.io triggers messages from product events and prices by profiles.
For a platform review, put the same six questions to each of these five products, using the rule card as the test:
- Can it trigger on the event in the card, such as a form, a purchase or a product event?
- Can it apply the eligibility rule and the exclusions before a send?
- Can it enforce the frequency cap and suppression across every journey?
- Can it route failures to an exception queue?
- Can an authorised person pause one journey without stopping all others?
- Does it log who changed a rule, and when?
Record pass, fail or not tested for each product, with the edition and the date. Event-led products such as Customer.io and Klaviyo tend to start from the trigger; Mailchimp, HubSpot and Salesforce Marketing Cloud tend to start from the audience. Check which fits your problem statement.
The block's final gate lists named reviewers for data protection, PECR and advertising claims. It also lists accessibility, security, AI and commercial terms as applicable. Each reviewer records approve, reject or approve with a condition. A blank field means the pilot cannot start.
The ICO's direct marketing guidance says organisations should identify the activity, plan protection, collect information fairly and respect preferences. Qualified review must apply the current rules to the proposed audience and channel.
Block 6: measurement and review
The analyst defines each metric's event, numerator, denominator and period. Then exclusions, system and owner. The GOV.UK Service Manual recommends planning performance data from the beginning and explains the difference between a measurement and a rate in its performance-data introduction.
Use an outcome measure, a harm or workload guardrail, and enough diagnostics to explain failures. These are categories, not universal KPIs. Baselines and thresholds must come from the organisation's approved evidence.
Review the framework
Meet at a fixed interval and whenever a trigger occurs. Triggers include a new data source, channel, supplier or model. They also include a new audience, legal update or unexplained guardrail movement. For each block, record what changed, who owns the action and whether the rule continues.
If another team cannot identify the current assumption, denominator and stop control, the work is not ready to automate.
Before you act
- Write one observable problem statement with a population and time boundary.
- Map the causal chain and list the assumptions connecting each step.
- Select one problem, one audience and one bounded intervention.
- Write a rule card covering trigger, exclusions, suppression and pause control.
- Define each metric's event, numerator, denominator, period and owner.
- List named reviewers and record approve, reject or approve with a condition.
Common questions
What makes a problem statement pass block one?
It must be observable, naming where the problem occurs, a population and a time boundary. A vague aim such as improve engagement fails. A defined delay or incorrect hand-off can be investigated. The team must also show who has authority to alter the process, or the block stops.
Why separate output from outcome in the intended change?
The Magenta Book's theory-of-change work surfaces causal steps, evidence weaknesses and alternative explanations. Keeping output and outcome apart stops a send count being mistaken for impact. Any chain jumping from a platform action straight to revenue without an evidenced mechanism should be rejected.
When should the framework be reviewed?
At a fixed interval and whenever a trigger occurs. Triggers include a new data source, channel, supplier or model. They also include a new audience, legal update or unexplained guardrail movement. For each block, record what changed, who owns the action and whether the rule continues. The finished framework is a decision record, not a presentation.
