Skip to content
Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryMMarketing Automation
MarketingIntermediate

Marketing Automation

Marketing Automation in Salesforce is the category of products and tools that run marketing tasks on a schedule or in response to behavior, without a person clicking send each time.

§ 01

Definition

Marketing Automation in Salesforce is the category of products and tools that run marketing tasks on a schedule or in response to behavior, without a person clicking send each time. It covers email and SMS campaigns, drip and nurture sequences, lead scoring and grading, multi-step customer journeys, and real-time web personalization.

Salesforce does not ship one product called Marketing Automation. It ships a family. Marketing Cloud Engagement handles high-volume B2C and B2B messaging and journeys. Marketing Cloud Account Engagement (the product formerly named Pardot) handles B2B lead nurturing tied to CRM. Marketing Cloud Personalization decides what each web visitor sees in real time, and Data Cloud supplies the unified profile underneath. Which products a company runs depends on its business model and budget.

§ 02

How the Salesforce marketing-automation family fits together

Marketing Cloud Engagement and Journey Builder

Marketing Cloud Engagement is the high-volume messaging platform, descended from the product once called ExactTarget. It sends email, SMS, push, in-app, WhatsApp, and LINE messages, and it stores audience data in Data Extensions rather than standard CRM objects. The automation centerpiece is Journey Builder, a canvas where you drag activities to define how and when each contact gets a message. Contacts enter a journey from an entry source such as a Data Extension, an event, an API call, a mobile event, an audience, or a CloudPage. From there the canvas evaluates each contact continuously and moves them forward when conditions are met. Activity types include send activities (email, SMS, push), wait activities that pause a contact for a duration or until a date, decision splits that route contacts by data or engagement, join activities that merge paths, and update-contact activities that change data mid-journey. Marketing Cloud Engagement is licensed separately from Sales Cloud, and pricing scales with contact and send volume. It is the right tool when the program is high-volume and channel-heavy rather than tightly bound to opportunity records.

Marketing Cloud Account Engagement (formerly Pardot)

Marketing Cloud Account Engagement is the B2B side of the family, and most teams still call it Pardot. It is built for a sales motion where marketing hands qualified leads to reps, so it lives close to the CRM. Prospects come in through landing pages, forms, and form handlers. Two qualification signals run side by side. Scoring measures behavior, so a prospect earns points for opening emails, visiting pricing pages, or downloading assets. Grading measures fit against your ideal profile using letter grades from demographic and firmographic data. The nurture engine is Engagement Studio, where you build multi-step programs from three pieces: triggers that decide when a prospect enters or branches, rules that evaluate prospect data at a decision point, and actions that do the work such as sending an email or updating a field. Programs support wait steps so you control cadence, plus suppression lists so the wrong people never receive a send. Einstein adds lead scoring, campaign insights, and attribution on top. Account Engagement is licensed separately from Marketing Cloud Engagement, and the two are frequently run together.

Marketing Cloud Personalization for real-time decisions

Marketing Cloud Personalization, formerly Interaction Studio, is the real-time layer. Where Journey Builder and Engagement Studio plan messages ahead of time, Personalization decides what a single visitor sees at the moment a page loads. It tracks behavior across web and app, stitches that activity into a unified profile, and then picks the content, offer, or product to show that specific person. The decision happens in milliseconds, so the same homepage can greet a first-time visitor and a loyal repeat buyer differently. This matters because batch campaigns assume you know the audience in advance, while web traffic is anonymous and changes by the second. Personalization closes that gap by reacting to live signals such as the page being viewed, items in a cart, or a segment the visitor just entered. It is most valuable on high-traffic properties where a small lift in relevance compounds across many sessions. In a full stack, Personalization is the activation point that turns the profile data managed by Data Cloud and the other Marketing Cloud products into a tailored on-site experience.

Data Cloud as the shared profile foundation

Data Cloud is Salesforce's customer data platform, and it is the strategic center of newer marketing-automation thinking. Historically each product kept its own copy of the customer. Marketing Cloud Engagement had Data Extensions, Account Engagement had prospects, Personalization had visitor profiles, and the CRM had Leads and Contacts. That fragmentation made it hard to know that one human spanned all of them. Data Cloud ingests data from every Salesforce cloud plus outside sources such as web analytics, ad platforms, and warehouses, then resolves it into one unified profile per person. Marketing tools increasingly read segments and attributes from Data Cloud instead of maintaining separate silos. The practical payoff is consistency: a suppression you set in one place can hold everywhere, and a segment built on combined service and purchase history is available to messaging tools. Anyone planning a new marketing deployment should map Data Cloud in from the start, because retrofitting a shared profile after the silos are entrenched is far more work than designing for it on day one.

Marketing Cloud Intelligence and cross-channel reporting

Marketing Cloud Intelligence, formerly Datorama, is the analytics layer of the family. A mature program rarely spends only inside Salesforce. Budget flows to paid search, social ads, display, and other channels, and each platform reports performance in its own format. Intelligence connects to those sources plus Marketing Cloud and pulls the numbers into one model so you can compare cost, reach, and return across channels in a single dashboard. Without that consolidation, marketers stitch spreadsheets together by hand and the picture is always stale. Intelligence is licensed separately, and most programs that run several channels add it once reporting by hand stops scaling. The point is not prettier charts. It is being able to answer which channel actually drove pipeline when spend is spread across many platforms that each claim credit. Intelligence sits beside the execution tools rather than inside any one of them, which is why it can report on activity that started outside Salesforce entirely.

AI and the move toward Marketing Cloud Next

AI now runs through the whole family rather than sitting in one product. Einstein generative AI drafts subject lines and body copy inside Content Builder, and it powers scoring, campaign insights, and attribution in Account Engagement. The newer direction is Marketing Cloud Next, which rebuilds marketing on the core Salesforce platform. There a campaign starts with a Flow that automates content and data collection, audiences are built from unified Data Cloud data, and Agentforce can draft and refine a multichannel campaign from a written brief. Marketing Cloud Growth is the entry edition of this platform-native approach, aimed at smaller teams who want curated campaign templates and generative AI without standing up the full enterprise stack. None of this replaces the established products overnight. Engagement, Account Engagement, and Personalization still run most enterprise programs today. The AI features and the platform-native editions augment those workflows, so the safe read is that the capability set keeps growing while the older product names stay in service for years.

Choosing and combining the products

There is no single right stack, only the right stack for a business model. A pure B2B company with a rep-led sales motion usually starts with Account Engagement, because lead scoring, grading, and tight CRM sync are exactly what hand-off to sales needs. A high-volume B2C brand starts with Marketing Cloud Engagement for the channel breadth and send scale. Many companies run both, because nurturing a sales pipeline and sending a million-record promotion are genuinely different jobs. Personalization joins when a high-traffic website justifies real-time on-site tailoring. Data Cloud belongs in any new build that expects to grow past one product. Intelligence comes in once spend spans channels and manual reporting breaks. The recurring failure mode is the big-bang launch, where a company buys several products and tries to switch them all on at once. Phased rollouts that prove return between phases tend to succeed, because each phase funds the next and the team learns one product before adding another.

§ 03

How to stand up an automated marketing program

Marketing automation is a category, so you do not create one record called a marketing automation. You stand up an automated program inside a specific product. The most common first build is an automated nurture in Engagement Studio (Account Engagement) or a multi-step journey in Journey Builder. The high-level path below applies to either. Confirm you have the product license and the right user permissions before you start.

  1. Pick the product and define the goal

    Decide whether the program belongs in Account Engagement (B2B nurture toward a sales hand-off) or Marketing Cloud Engagement (high-volume or multichannel journey). Write down the single outcome the program should drive before you touch the canvas.

  2. Build the audience and entry

    In Account Engagement, define the list or rule that adds prospects. In Marketing Cloud Engagement, pick an entry source such as a Data Extension, event, or API call. This decides who enters and when.

  3. Lay out steps with waits and branches

    Add the messages, then the wait steps that set cadence, then the rules or decision splits that send different people down different paths based on their data or engagement.

  4. Add suppression and exit logic

    Attach suppression or exclusion lists so the wrong contacts never receive a send, and define how a contact leaves the program when the goal is met.

  5. Test, then activate

    Run a test send to a seed audience, verify the branching with sample prospects, then start the program and watch the first cohort move through before scaling volume.

Entry sourceremember

What adds a contact to the program: a list or scoring threshold in Account Engagement, or a Data Extension, event, or API call in Journey Builder.

Wait stepremember

A pause that holds a contact for a set duration or until a date, used to control how fast messages go out.

Rule or decision splitremember

A branch point that evaluates contact data or engagement and routes each person down the matching path.

Suppression listremember

An exclusion set that prevents specific contacts from receiving sends even if they otherwise qualify.

Gotchas
  • Engagement Studio and Journey Builder are different tools in different products. A program built in one does not run in the other.
  • Audiences live in different stores. Account Engagement uses prospects and lists, while Marketing Cloud Engagement uses Data Extensions, so plan the data flow before building.
  • Without suppression rules, an automated program will happily message people you meant to exclude. Set exclusions before activating, not after.
  • Test branches with real sample data. A decision split that looks correct on the canvas can still route contacts the wrong way if the underlying field is empty.

Prefer this walkthrough as its own page? How to Marketing Automation in Salesforce, step by step

§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Marketing Automation.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Test your knowledge

Q1. What does Marketing Automation describe as a discipline and toolset?

Q2. Which Salesforce product is the B2B-focused entry in the Marketing Automation family?

Q3. How does Marketing Automation connect marketing teams to sales teams in the revenue model?

§

Discussion

Loading…

Loading discussion…