• Cert++
  • Practice
  • Certle
  • Review
  • Tracks
  • Checklist
  • Guides
  • Upgrade
Cert++
  1. Home
  3. Marketing Cloud Engagement Consultant

Marketing Cloud Engagement Consultant

Checklist progress

0/130Learned

Marketing Cloud Engagement Consultant

Study Checklist

  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Architect

Checklist progress

0/130Learned

  • Identifying missing requirements needed to recommend the right Marketing Cloud account structure when a customer describes multi-brand or multi-region sending needs
  • Determining which additional data points are necessary before recommending a contact identity strategy when a customer's CRM and email list structures are misaligned
  • Recognizing which deliverability-related questions must be answered before designing a high-volume sending architecture
  • Assessing what compliance and consent information is required from a customer before designing a data ingestion and audience strategy under GDPR or CAN-SPAM constraints
  • Designing a segmentation strategy using Data Extensions vs. Lists based on customer data volume and query complexity requirements
  • Translating business segmentation requirements (e.g., 'send to recent purchasers only') into a Marketing Cloud data model design using filtered or query-based data extensions
  • Recommending the right data intake method (import, API, Automation Studio import activity) based on the customer's data freshness requirements and technical capabilities
  • Identifying whether a customer's segmentation requirements can be met with out-of-the-box filtered data extensions or require SQL Query Activities
  • Gathering requirements around suppression lists and exclusion logic to ensure compliant audience segmentation
  • Determining when a customer should use a native Marketing Cloud feature versus a custom API integration based on their internal developer resources
  • Assessing a customer's readiness for self-service administration of Marketing Cloud business units versus centralized management by a single team
  • Recommending Journey Builder vs. Automation Studio based on a customer team's technical skill level and ongoing campaign maintenance requirements
  • Recommending AMPscript vs. Content Blocks vs. dynamic content rules based on a marketer's coding proficiency and content reuse needs
  • Advising a non-technical marketing team on whether to use drag-and-drop Content Builder features or custom HTML/AMPscript templates for scalable content management
  • Recommending whether a customer with a small marketing team and limited IT support should use a preference center built with CloudPages vs. a Profile Center hosted by Marketing Cloud
  • Determining whether Marketing Cloud Connect is the appropriate integration approach given a customer's Salesforce org edition and data syncing requirements
  • Explaining the prerequisites and configuration steps required to establish Marketing Cloud Connect between a Salesforce org and Marketing Cloud
  • Explaining the role of the Marketing Cloud Connect user and the permission sets required on the Salesforce CRM side
  • Explaining how synchronized data extensions are created via Marketing Cloud Connect and which standard CRM objects are available (Contacts, Leads, Campaigns, Cases)
  • Explaining how field mappings and filter rules are configured for synchronized data extensions in Marketing Cloud Connect
  • Understanding the difference between a triggered send from Sales/Service Cloud and a journey-based send using Marketing Cloud Connect's Journey Builder integration
  • Describing how CRM campaign membership is used as a Journey Builder Salesforce Data entry source and the implications for contact injection timing and volume
  • Identifying the Journey Builder Sales/Service Cloud activities (Create Task, Create Case, Convert Lead, Update Record)
  • Determining when to include Journey Builder Sales/Service Cloud activities in a journey to automate CRM follow-up
  • Troubleshooting a Marketing Cloud Connect sync failure where contact records are not appearing in synchronized data extensions
  • Diagnosing why a Send Logging data extension is not capturing send records after configuring Marketing Cloud Connect
  • Troubleshooting a connected send where tracking data (opens, clicks) is not flowing back to the CRM campaign member record
  • Identifying the impact of a multi-org Marketing Cloud Connect configuration on data isolation and business unit segmentation
  • Determining how the All Subscribers list and data extensions interact when selecting audiences for a personalized send
  • Evaluating when to use Contact Builder attributes vs. data extension columns to store subscriber data used for personalization
  • Explaining the role of Contact Builder's Data Designer in linking data extensions to the contact record and making those relationships available as journey decision criteria
  • Recommending the appropriate data model to support send-time personalization when a customer has a one-to-many relationship between subscribers and purchase records
  • Explaining how AMPscript LookupRows and Lookup functions retrieve data from relational data extensions to personalize email content at send time
  • Designing a relational data model using linked data extensions to support personalized product recommendation emails
  • Recommending the appropriate Marketing Cloud extension product when a customer needs to manage mobile push notifications alongside email in a cross-channel journey
  • Recommending Advertising Studio vs. Journey Builder Advertising Activities for a customer who wants to suppress recent email openers from a paid social campaign
  • Recommending an Enterprise 2.0 account structure with multiple business units versus a single business unit when a customer has distinct brands with separate subscriber lists
  • Explaining the implications of shared All Subscribers list vs. business-unit-level subscriber management within an enterprise account hierarchy
  • Determining when a customer's multi-region or multi-brand requirements necessitate separate Marketing Cloud accounts vs. business units within a single enterprise account
  • Describing the roles and permissions model in Marketing Cloud and the difference between standard system roles and custom roles
  • Identifying how roles and permissions cascade from a parent account to child business units and where overrides are appropriate
  • Explaining how to assign the minimum required access to a business unit user in Marketing Cloud
  • Advising whether a child business unit should have its own SAP or inherit the parent account's SAP based on branding and deliverability requirements
  • Explaining how Lock and Publish (template locking) is used in a parent business unit to enforce brand standards while allowing child business units to edit permitted regions
  • Explaining the relationship between Reply Mail Management and the envelope from address in transactional vs. commercial sends
  • Configuring Reply Mail Management to auto-delete, auto-reply, or forward replies to a designated inbox based on a customer's operational requirements
  • Troubleshooting a scenario where reply emails from subscribers are not being processed by Reply Mail Management as expected
  • Explaining what the Sender Authentication Package (SAP) includes (private domain, dedicated IP, link wrapping)
  • Explaining the deliverability implications of the Sender Authentication Package (SAP)
  • Explaining how SAP affects the from address, reply-to address, and physical mailing address displayed to subscribers
  • Determining the relationship between SAP and link wrapping/tracking domain configuration and the effect on subscriber trust and click tracking
  • Describing the IP warming process required after provisioning a dedicated IP through SAP and the risk of skipping or shortcutting the warm-up schedule
  • Analyzing the impact of applying SAP to a child business unit when the parent account already uses a shared IP and different from-domain
  • Identifying the components of Mobile Studio (MobileConnect, MobilePush)
  • Determining when to use MobileConnect vs. MobilePush based on customer use case
  • Configuring a MobileConnect keyword and short code to support an inbound SMS campaign with STOP/HELP compliance handling
  • Troubleshooting an SMS opt-in flow configured in MobileConnect that is not correctly double-opting in subscribers
  • Distinguishing between Automation Studio and Journey Builder as orchestration tools based on whether the use case is batch/scheduled or event-driven/real-time
  • Explaining the difference between a triggered send (classic) and a Journey Builder transactional message and when each is preferred
  • Recommending a file drop automation vs. a scheduled automation in Automation Studio based on the upstream data delivery pattern
  • Selecting the correct Automation Studio activity (SQL Query, Import, Send, Filter, Data Extract, Transfer) for each step in a nightly data refresh and send workflow
  • Identifying the appropriate Journey Builder entry source (Data Extension, Salesforce Data, API Event, CloudPages Form, Audience) for a given customer acquisition scenario
  • Identifying which Journey Builder activities are available in the Activities panel (Email, SMS, Push, Ad Audience, Update Contact, Sales/Service Cloud activities)
  • Determining when to use a Wait activity vs. an Engagement Split vs. a Decision Split in a Journey Builder journey based on business logic requirements
  • Recommending the use of Salesforce Data Entry events in Journey Builder when a customer wants to trigger a journey based on a CRM record change
  • Determining when to use an Einstein Split vs. a Decision Split in Journey Builder based on whether the branching logic is rules-based or AI-driven engagement prediction
  • Designing a multi-step re-engagement journey that uses engagement splits, wait periods, and exit criteria to prevent over-messaging inactive subscribers
  • Designing a post-purchase journey that branches based on product category using Decision Splits backed by data from a relational data extension
  • Evaluating journey goal configuration and its effect on contact exit and reporting in a conversion-focused email series
  • Configuring Journey Builder exit criteria and exit conditions so that contacts who convert or unsubscribe are removed from the journey before receiving subsequent messages
  • Handling a scenario where contacts must re-enter an active journey when a qualifying event occurs again, and configuring re-entry settings appropriately
  • Explaining how to manage Journey Builder version transitions without disrupting in-progress contacts
  • Explaining what happens to contacts already in a running journey when a new version of that journey is activated
  • Using Path Optimizer in Journey Builder to statistically test multiple message paths and automatically direct remaining contacts to the winning path
  • Troubleshooting a Journey Builder journey where contacts are entering but not receiving emails due to suppression, send classification, or contact status issues
  • Architecting an Automation Studio workflow that refreshes a filtered audience, executes a SQL query for suppression, and triggers a send in the correct sequence
  • Combining Journey Builder and Automation Studio in a hybrid architecture where Automation Studio prepares data and a Journey Builder API event entry source fires the journey
  • Designing an automation that uses the Data Extract activity and File Transfer activity to export tracking data to an SFTP for downstream reporting
  • Explaining the error-handling behavior in Automation Studio when a step fails mid-automation
  • Identifying the options for configuring notifications and restart behavior when an Automation Studio step fails

Given a customer scenario, demonstrate the ability to differentiate when to use standard reports, data views, and tracking extracts.

0/7

  • Explaining the difference between Marketing Cloud standard email reports, data views, and tracking extracts in terms of data freshness, scope, and use cases
  • Describing the available system data views in Marketing Cloud (_Sent, _Open, _Click, _Bounce, _Unsubscribe, _Complaint, _Job, _ListSubscribers)
  • Identifying the key fields each Marketing Cloud system data view exposes for SQL-based analytics
  • Recommending data views (e.g., _Sent, _Open, _Click, _Bounce) over standard reports when a customer needs custom cross-send analytics via SQL queries
  • Determining when to use a tracking extract vs. a data view query to populate a reporting data extension with send-level engagement metrics
  • Using the _Subscribers data view to identify and report on subscribers whose status has changed to Unsubscribed or Bounced
  • Identifying the data view retention window limitations and the impact on reporting queries that reference historical sends

Explain the various data objects in Marketing Cloud.

0/14

Comparing Marketing Cloud data objects: Lists, Data Extensions, Measures, and Groups — explaining the structural and functional differences

Learn this concept
Unseen

Explaining when to use a Sendable Data Extension vs. a non-sendable Data Extension and the required subscriber relationship field

Learn this concept
Unseen

Explaining the Contact model in Contact Builder and the concept of contact key

Learn this concept
Unseen

Explaining identity resolution in the Marketing Cloud Contact model

Learn this concept
Unseen

Explaining the relationship between the All Subscribers list and data extensions, including how an unsubscribe from a data extension send affects the All Subscribers status

Learn this concept
Unseen

Describing the role of Publication Lists and Suppression Lists in managing subscriber consent and exclusion within Marketing Cloud

Learn this concept
Unseen

Explaining attribute groups in Contact Builder

Learn this concept
Unseen

Understanding the purpose of Data Designer in Contact Builder for linking data extensions into the contact model for use in Journey Builder

Learn this concept
Unseen

Describing the differences between Filtered Data Extensions and Query-based Data Extensions, including refresh limitations and maintenance considerations

Learn this concept
Unseen

Describing the purpose and structure of Synchronized Data Extensions created via Marketing Cloud Connect and how they differ from standard data extensions

Learn this concept
Unseen

Describing how the Import Activity in Automation Studio maps source file columns to data extension fields

Learn this concept
Unseen

Identifying common Import Activity failure causes such as field type mismatches or missing required fields

Learn this concept
Unseen

Explaining how data extension retention settings work and what happens to records when the retention period expires

Learn this concept
Unseen

Explaining the implications of data extension retention for journey audiences

Learn this concept
Unseen

Evaluate implications on data model when choosing contact identity.

0/9

  • Analyzing the impact of using subscriber key vs. email address as the contact identifier when a customer sends to the same person from multiple business units
  • Determining how the choice of contact key (Salesforce Contact ID vs. email vs. custom ID) affects unsubscribe behavior across business units
  • Explaining how duplicate subscriber keys in a sendable data extension affect deliverability and send outcomes
  • Explaining how All Contacts count is determined in Marketing Cloud and which actions cause a contact to be counted
  • Explaining why All Contacts count matters for contract and billing
  • Determining when a consultant would recommend using Contact Delete to reduce All Contacts count
  • Describing the Contact Delete process in Marketing Cloud and what data is removed vs. retained
  • Assessing the downstream data model consequences of changing the contact identity field after a Marketing Cloud account is already in production
  • Evaluating the risk of contact key collisions when integrating a legacy email platform with a new Marketing Cloud account that uses a different subscriber identity field
  • Comparing personalization strings, AMPscript, and dynamic content rules as methods for individualizing email content
  • Selecting the appropriate personalization approach (personalization strings, AMPscript, or dynamic content rules) based on complexity and marketer skill level
  • Designing a dynamic content rule in Content Builder to show different email sections based on subscriber attribute values (e.g., loyalty tier, region)
  • Using AMPscript Lookup and LookupRows functions to retrieve related data from a linked data extension to populate personalized product or account details in an email
  • Applying conditional AMPscript (IF/ELSEIF/ELSE) to render different message copy based on subscriber data fields without creating multiple separate campaigns
  • Implementing Einstein Send Time Optimization to automate send-time individualization for large subscriber volumes
  • Implementing Einstein Content Selection to automate content individualization at scale
  • Describing the CAN-SPAM and CASL requirements for commercial emails (physical address, unsubscribe mechanism, honor period)
  • Determining whether to use a transactional send classification vs. a commercial send classification based on message content and CAN-SPAM/CASL compliance requirements
  • Explaining the components of a Send Classification (Delivery Profile and Sender Profile)
  • Explaining how Delivery Profile and Sender Profile control the from name, from address, physical address, and unsubscribe method applied to a send
  • Explaining how Marketing Cloud's one-click unsubscribe and Profile Center satisfy CAN-SPAM and CASL requirements
  • Designing a preference center using CloudPages that allows subscribers to manage subscription preferences at the publication list level rather than performing a global unsubscribe
  • Selecting between a standard commercial email send, a triggered send, and a Journey Builder send based on a customer's real-time transaction notification requirement
  • Choosing the appropriate sending domain and IP strategy (shared vs. dedicated) based on a customer's sending volume, brand reputation, and deliverability history
  • Recommending SMS via MobileConnect vs. push notification via MobilePush based on whether the customer's subscribers are app users or non-app mobile audiences
  • Evaluating when to use A/B testing in Email Studio vs. Path Optimizer in Journey Builder for a customer who wants to test subject lines on a batch promotional send
  • Identifying when a customer should use Content Builder's A/B test feature (subject line, content, from name, send time)
  • Interpreting Content Builder A/B test winner-selection criteria options
  • Recommending the use of a CloudPages SmartCapture form vs. an API-triggered journey entry for collecting new subscriber opt-ins based on the customer's technical implementation constraints

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Marketing Cloud Engagement Consultant studiers.

Go to Discord

Explaining the implications of data extension retention for journey audiences

Explainer

Learn More

Practice Question

Keep going

Next conceptAnalyzing the impact of using subscriber key vs. email address as the contact identifier when a customer sends to the same person from multiple business units

Checklist progress

0/130 (0%)

0 of 130 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Marketing Cloud Engagement Consultant studiers.

Go to Discord

Explainer

Data extension retention policies control how long contact records persist in Marketing Cloud to maintain clean profiles and manage storage. These policies directly impact journeys because they rely on Contact Builder attributes sourced from these data extensions.

Core information
  • Retention policies in Contact Builder manage data extensions by removing outdated data to maintain clean customer profiles.
More details and nuances
  • Journey Builder expressions reference Contact Builder attributes, so deleting a data extension invalidates the attribute set used in the journey.