Rules
Part of Designing marketing automation around identity, consent and triggers
Nine marketing automation journeys worth building before the rest
Marketing automation examples for 2027 show nine adaptable journeys for resources, events, onboarding, B2B nurture, renewal, re-engagement, and feedback.
What to take away
- Build the journey a customer already asks for, that fails visibly, and that your data can support today.
- Frequency, consequence, data readiness and a named owner decide the order, not the length of a platform feature list.
- HubSpot, Klaviyo, Eventbrite, Delighted and Zapier publish list pricing. Cvent, Marketo, Gainsight, ChurnZero and Totango sell by quote only.
- Test the failure case first, keep a manual route during the pilot, and retire the automation when the supporting service disappears.
Marketing automation examples earn their place by running a service a customer or colleague notices. Each journey below pairs one service pattern with the platform feature behind it. The marketing automation design guide explains why identity, consent and triggers outrank message copy.
The nine patterns and the platform feature behind each
1. Requested-resource follow-up, HubSpot Workflows. Enrollment runs on list membership or property value. A booked meeting ends the flow. Paid seats typically list around $15 to $20 monthly as of 2026.
2. Event journey, Cvent with Eventbrite. Cvent holds registration, sessions, reminders and check-in on one attendee record. It sells by quote, while Eventbrite charges per paid ticket only.
3. New-customer onboarding, Intercom Series. Series fires when a customer completes a product event and pauses when the step is done. Seat pricing means a stalled signup still needs a named owner.
4. Feature adoption, Braze Canvas with Pendo. Canvas branches on behavior and caps frequency so prompts do not repeat. Pendo targets people who skipped one action and records completion.
5. B2B nurture, Marketo Engage Smart Campaigns. A smart list feeds flow steps with waits and choices, and scoring combines fit with behavior. Adobe prices it by quote, with no public rate.
6. Renewal preparation, Gainsight. Health scores, renewal dates and risk playbooks sit with named account owners. Gainsight sells by quote, and ChurnZero and Totango match on the same basis.
7. Lapsed-customer re-engagement, Klaviyo win-back flow. It starts a set number of days after a last purchase and stops on a new order. The free plan covers 250 contacts and 500 monthly sends as of 2026.
8. Feedback and recovery, Delighted with Zendesk. Surveys fire from a trigger event, detractors are flagged, and billing runs on surveyed contacts. A low score opens a Zendesk ticket for a person close.
9. Internal campaign operations, Zapier filters and paths. Paths create tasks in Asana or Jira and flag missing evidence. Campaign operations shows how to keep those review loops clear of customer messaging.
Example: trigger, wait, branch and exit for three journeys
Trigger, wait, branch and exit
| Journey | Trigger | Wait | Branch | Exit |
|---|---|---|---|---|
| HubSpot resource follow-up | Gated asset form submission | One business day before the delivery task | No download in 48 hours, resend once | Booked meeting meets the goal and ends enrollment |
| Marketo nurture | Score crosses threshold or list add | Four days between touches | High fit adds a sales task; high behavior sends a case study | Opportunity created or unsubscribe |
| Klaviyo win-back | Set days after the last order | Five days after the first reminder | Opened but not clicked switches variant | New order placed or frequency cap reached |
Those values are illustrative settings, not vendor defaults. Copy the shape, then set the numbers from your own send history and service hours.
Which journey to build first
Rank candidates on frequency, consequence, data readiness and owner. The highest score with a named owner wins.
Frequency is how often the need appears. A missed renewal handoff costs more than a late newsletter, so consequence outranks volume. Data readiness decides feasibility, since the trigger event, identity match and permission must already work. Ownership decides who answers when the journey misfires.
| Need | Candidate journey | Acceptance evidence |
|---|---|---|
| Requested help arrives late | HubSpot requested-resource workflow | Timely delivery and completed task |
| Sales follow-up is inconsistent | Marketo nurture or Cvent event journey | Accepted, worked handoff |
| Customers stall | Braze or Pendo feature adoption | Barrier cleared without excess contact |
| Renewal risk surfaces late | Gainsight health score playbook | Risk logged and owned |
| Complaints close without follow-up | Delighted and Zendesk recovery | Issue resolved and customer informed |
| Campaign QA repeats | Zapier internal operations | Correct record and human approval |
Settle the common marketing automation questions about triggers, data minimums and ownership before you commit to the first build.
The rules each journey must carry
Platform capability does not supply your rules, staffing or accountability. Write these fields down before a journey runs unattended.
- Entry and exclusions, including who must never be enrolled
- Identity and permission, plus the preference that overrides both
- Data and content sources, with a named field owner
- Branch, priority and frequency limits
- Handoff, success, timeout and error handling
- Pause, recovery, owner and measure
Define each journey's rules
- Entry, exclusions, identity, permission
- Preference, data, content, branch
- Priority, frequency, handoff, success
- Timeout, error, pause, recovery
- Owner and measure
The NIST Privacy Framework starting guide outlines a voluntary process for identifying and managing privacy risk. Use it to assign data and response owners, and treat it as planning input rather than legal clearance.
Consent duties differ by market. The FTC CAN-SPAM compliance guide covers US opt-out and identification rules, while Canadian sends run under PIPEDA and CASL.
Testing and retirement
- Baseline the manual processvolume, response time and outcome.
- Test duplicate events, missing identifiers, changed customer state and revoked permission.
- Keep a manual route open for the pilot population and send uncertain context to a person.
Pilot one journey safely
- Test failure casesduplicates, missing IDs, revoked permission
- Use neutral fallback when context is uncertain
- Select frequent demand with observable outcome
- Establish baseline and guardrails
- Keep manual route during pilot
- Retire if need, owner, or service disappears
Retire the automation when the customer need, the owner or the downstream service disappears. A flow that keeps sending after the service is gone inflates contact volume and erodes trust.
Output is still a page or a message. The W3C explanation of information and relationships says visual structure should also be programmatically available, so test rendered output with the users and assistive technology in scope. Log the findings in the marketing operations checklist before launch.
Common questions
Which journey should a team build first?
One with frequent demand, an observable consequence, dependable permission and data, and a named owner. Bound the pilot and keep a manual fallback.
Are these proven case studies?
No. They are patterns that need testing against your market, data and staffing.
Why do some platforms publish no price?
Cvent, Marketo Engage, Gainsight, ChurnZero and Totango bundle modules, seats and services into quotes. Ask for a three-year total with implementation.
Can an internal workflow count as marketing automation?
Yes, when it repeatably supports marketing work such as routing, records, deadlines or QA while accountable decisions stay with people.
