Operations
Part of Designing marketing automation around identity, consent and triggers
6 marketing automation checks before signing off
Six checks for journey mechanics, PECR mail consent and DebugView tag faults, so a journey goes live with real evidence instead of assumption.
What to take away
- Write the entry rule, every branch, each wait, the timeout, and the re-entry rule before build, not after the first duplicate send.
- Under PECR, electronic mail needs consent or a narrow soft-opt-in test; the ICO guidance is UK-scoped and does not travel.
- A DebugView tag confirms a tag fired. It says nothing about consent, identity, downstream systems or revenue.
- Every wait needs a timeout path and every timeout needs an owner, or contacts sit in limbo indefinitely.
- Close the review only when each defect has an owner, acceptance evidence and a retest date.
A marketing automation sign-off fails in the same three places: a journey nobody can describe, a consent record nobody can evidence, and a tag test mistaken for proof the whole chain works. The six checks below cover those three.
1. Journey mechanics
A journey is five decisions, not a canvas. Entry, branches, waits, timeouts, re-entry. Write all five down before anyone opens the builder.
Five journey decisions
- Entry: qualifying event, fields, exclusions
- Branches: every split needs a default
- Waits: set a maximum timeout
- Timeouts: name the exit and checker
- Re-entry: interval and loop stop
Entry is a rule, not a list. State the qualifying event, the fields it reads, and the exclusions. A contact who bought yesterday should not enter a win-back flow, and that exclusion belongs in the entry rule where a reviewer can see it.
Branches need a default. Every split should say what happens to the contact who matches neither side, because in practice that is most of them.
Waits need a maximum. A wait with no timeout holds a contact until something else moves them, and nothing else will. Set the timeout, name the exit, and say who checks the queue when the timeout fires.
Re-entry is the check teams skip. Decide whether a contact can re-enter, after how long, and what stops a loop when the entry event fires again from the journey's own send.
2. Electronic mail consent under PECR
The UK Information Commissioner's Office sets out electronic-mail marketing rules under PECR. These rules cover channel scope, consent, and soft-opt-in conditions. They also cover sender identity, opt-out, and suppression.
Read the electronic-mail marketing guidance as UK guidance only. Other markets set their own rules, and a soft-opt-in that works in one does not transfer. Take qualified advice for each market, channel and purpose.
Consent records raise the common marketing automation questions teams ask before launch: what counts as evidence, how long it holds, and what happens when someone withdraws mid-journey.
PECR consent evidence
- Store basis, timestamp, source, exact wording
- Propagate withdrawal to every connected system
- Keep suppression lists separate from segments
- Read ICO guidance as UK-only
- Take qualified advice per market
3. Identity and data readiness
- Name the identifier, the authoritative source, and the fallback when it is missing.
- Define merge and split behaviour for duplicate profiles, and who stewards them.
- Record field definitions, quality rules, sensitivity, and how late or duplicate events are handled.
4. Content, integrations and handoffs
Content, integrations and handoffs
- Check claims, rights, accessibility, fallback content, sender, reply handling and approval date.
- Test each integration for source, transform, latency, retry, reconciliation and outage behaviour.
- Define the sales handoffpayload, queue, owner, response expectation, rejection reason and return path.
5. Tag troubleshooting with Analytics DebugView
Google's DebugView shows events and user properties from one user in real time, which makes it a tag diagnostic. It also notes that client-side privacy controls can stop events appearing, so an empty DebugView is not proof a tag is broken.
Use the DebugView tag to answer one question: did this event reach Analytics from this browser? It cannot tell you whether the journey sent the right message, whether consent was recorded, or whether the CRM accepted the lead.
6. Release evidence and monitoring
Release evidence and monitoring
- Run controlled records through ordinary, edge, failure, opt-out, pause and replay paths, and save expected against actual.
- Monitor entrants, branch counts, timeouts, errors, delivery, complaints, suppressions and handoffs.
- Publish alert thresholds, pause authority and the review cadence with named owners.
Release evidence and monitoring
| Check | Evidence required | Closure test |
|---|---|---|
| Journey mechanics | Entry, branch, wait, timeout, re-entry rules | A reviewer can trace one contact end to end |
| PECR consent | Basis, timestamp, source, wording, suppression | Withdrawal propagates to every system |
| Tag test | DebugView session and event log | Result matches the expected event list |
Common questions
When should the six checks be run?
Before launch, after any material change to entry or consent logic, and on a scheduled basis for live journeys. A migration counts as material change even when the logic is copied unchanged.
Does a passing checklist prove compliance?
No. It records an operating review. Qualified advisers assess the current law against the actual facts, markets, messages and data.
What happens to a journey with no owner?
Pause it and decide whether a current purpose, reliable data and a named owner can be restored. If not, retire it. Marketing workflow management practices keep that decision from stalling.
The W3C Privacy Principles statement gives designers shared privacy concepts and warns against shifting privacy work onto individuals. The CISA software acquisition fact sheet adds supply-chain and vulnerability questions worth asking of any vendor. Neither replaces local review.
