What is marketing automation?

Marketing automation is software that carries out marketing actions off rules and behaviour rather than a person deciding to press send. Someone downloads a guide, and a sequence starts. A score crosses a threshold, and a record is handed to sales. A customer goes quiet, and a win-back runs. The defining feature is that the software executes a predefined rule or workflow on its own, often in response to an event, condition or customer behaviour, rather than a person deciding to send each time. Automations can run on schedules too; what makes them automation is that the rule is set in advance and fires without anyone initiating each action.

Four jobs recur in the B2B-rooted automation work buyers describe. It captures and routes records, moving a form fill from a landing page into the CRM. It scores them, ranking who is worth a salesperson's time. It nurtures, running multi-step sequences that respond to what someone does or does not do. And it reports on the result back to pipeline. One buyer summarises the middle of that as lead scoring plus a whole host of things around lead capture, with leads routed from landing pages into the CRM by the platform.

Less than the product names suggest, and more than buyers' shortlists suggest. Around half the products buyers describe as marketing automation platforms also appear as email platforms in the same corpus, so the software overlaps heavily. But the buyers barely overlap: very few people in market for marketing automation are simultaneously in market for an email platform. They are treated as different purchases, because they answer different questions. An email platform is asked to send well; an automation platform is asked to move someone through a predefined journey or funnel.

Listen for the vocabulary, because it separates the two far more cleanly than the vendor list does. Buyers in market for marketing automation use lead, nurture, scoring and funnel language at close to double the rate of buyers in market for an email platform. If the problem you are describing is about who gets handed to sales and when, you are buying automation whatever the product is called. If it is about getting a campaign out reliably to a large list, you are buying an email platform.

No, though the vocabulary comes from there. The lead-and-nurture framing is most associated here with businesses that have sales teams and longer consideration cycles, and the platforms most associated with the term were built for that. But the same mechanics run consumer lifecycle programmes — abandoned carts, win-backs, replenishment reminders — and buyers describe using one platform for campaign email, nurture and outreach depending on the use case. The trigger-based mechanic is what makes it automation, not the presence of a salesperson at the end.

A CRM primarily stores and manages the relationship record — accounts, contacts, deals and sales activity. Marketing automation uses rules, behaviour and timing to decide what marketing action should happen next: nurture a lead, score it, route it, or trigger a lifecycle message. The two often integrate tightly and may be sold in the same suite, but one is primarily the record and the other the workflow around it.

A welcome or nurture sequence that starts when someone fills in a form. Lead scoring that ranks records by behaviour. Routing a record to a salesperson once it crosses a threshold. On the consumer side: abandoned-cart messages, win-back campaigns for lapsed customers, replenishment reminders, and triggered messages that follow someone across email, push and SMS. What they share is a rule defined in advance that fires on its own.

It depends what the CRM already does and who operates it. The two are tightly coupled: the CRM typically holds the relationship record, while the automation layer uses rules and behaviour to decide what marketing action happens next, and often writes engagement or lead status back to the CRM. Several major suites sell both halves together. The question worth answering is whether the automation you need can run inside the CRM suite you already have, or whether a separate automation layer is justified — the handover between the two systems can become a source of friction.