Free Practice Questions for the Salesforce Marketing Cloud Consultant MC-Con-201 Exam (2026 Updated)

Omni-Channel routing is the Salesforce architecture used to assign inbound conversations to Agentforce Service Agents or human service representatives. Conversational Email integrates Marketing Cloud Next with Agentforce and Service Cloud so that customer replies can remain within the same conversation thread and be routed appropriately.

Salesforce documents Omni-Channel flows as the mechanism for routing conversation-associated records to Agentforce. In general Agentforce channel architecture, the inbound Omni-Channel flow receives the conversation record and routes work to the configured Service Agent. For Conversational Email specifically, Salesforce also documents routing types such as Omni-Flow for directing a reply to a Service Agent.

A generic record-triggered flow on Email Message doesn't provide the complete channel-routing behavior required for Agentforce ownership. A platform-event trigger likewise isn't the prescribed Conversational Email routing architecture.

The uploaded master bank identifies B.

Study Guide Reference: Agentforce and AI Innovation → Conversational Email → Omni-Channel and Agentforce Routing.

===============

Salesforce provides the Device to Known Identity Resolution rule specifically to associate anonymous tracked visitors with known Unified Individual profiles.

Current Marketing Cloud Next setup documentation states that an Individual Identity Resolution ruleset should include an Identity Match DMO match criterion where Identity Match Type is matched exactly to device-to-known. Salesforce explains that this recommended rule attributes web-tracking activity to the correct Unified Individual.

This architecture exists because anonymous website engagement initially contains a device or visitor identity rather than ordinary CRM identity attributes. Once the visitor becomes identifiable—for example, through a recognized interaction—the Identity Match relationship enables Data 360 to stitch that visitor identity to the known Individual.

Option A incorrectly proposes manually altering identity relationships with Flow. Option B assumes Website Engagement should be directly matched to Individual using email, which bypasses the specialized identity-stitching mechanism Salesforce provides.

The uploaded master bank identifies C.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Identity Match DMO and Device-to-Known Matching.

===============

The Email Engagement dashboard is the purpose-built dashboard for analyzing standard email performance metrics across Marketing Cloud Next sends. Salesforce's Marketing Performance Intelligence package includes preconfigured Email Engagement reports and dashboard components for common KPIs including Total Emails Sent, Open Rate, Click-Through Rate, Bounce Rate, and Opt-Out Rate.

The dashboard provides visualizations such as status bar graphs, time-based activity graphs, campaign click-engagement rankings, email-send-status views, and detailed activity tables. This allows marketers to evaluate messaging performance without having to construct a custom analytics model.

Campaign Performance is broader and focuses on campaign-level outcomes across associated marketing activity rather than being the specialized email KPI view requested here. Unified Engagement History serves another purpose: it surfaces marketing engagement alongside CRM records such as Contacts, Leads, Accounts, and Opportunities for sales and service users.

Therefore, B precisely matches the requirement for an easy-to-use, cross-send email analytics dashboard.

The uploaded master bank also identifies B. Salesforce's 2026 Marketing Cloud Next reporting documentation explicitly lists Open Rate, Click-Through Rate, Bounce Rate, and related metrics in the Email Engagement dashboard.

Study Guide Reference: Analytics and Performance Insights → Marketing Performance Intelligence → Email Engagement Dashboard.

===============

A Contact Point Selection Rule implemented through an activation template is specifically designed to determine which email address, phone number, or other messaging contact point should be used when an individual has multiple available values. Salesforce documents activation templates as reusable configurations containing contact point selection, source priority, filtering, enrichment, and membership rules.

For example, an activation template can prioritize a primary CRM email over another email address, filter invalid contact points, and apply consent criteria. Segment-triggered marketing flows can then reference that activation template and use its stored logic to choose one appropriate contact point. Salesforce specifically notes that this capability helps ensure recipients don't receive duplicate messages.

A Decision element isn't intended to reproduce Data 360 contact-point selection logic manually. Identity Resolution also doesn't simply merge multiple legitimate contact points into one. A Unified Individual may correctly retain multiple email addresses belonging to the same person; activation logic determines which address should actually be used.

The uploaded master keys A. Official Salesforce documentation directly supports contact-point selection through activation templates.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Activation Templates → Contact Point Selection.

===============

The source bank recommends starting with a single lean Data Graph and expanding it as additional campaign requirements emerge . This approach avoids building unnecessary relationships and processing large datasets before an actual personalization use case requires them.

Current Salesforce guidance supports the underlying principle. Marketing Cloud Next personalization begins with a Unified Individual-based Data Graph containing required identity/contact fields plus the additional objects and fields required for personalization . Salesforce also notes that Data Graph cost and processing depend on data-model structure, participating records, refresh frequency, and fields updated. It recommends filters so that only records required for the use case are included.

Option A risks creating an oversized graph based on speculative future requirements. Option B introduces two graphs immediately even though the first campaign doesn't establish a requirement for separate demographic and transactional graphs. In the standard Marketing Cloud Next configuration without additional Personalization capabilities, Salesforce also notes that only one default Data Graph is used at a time.

Therefore, begin with the smallest useful graph, validate the campaign, and expand the graph as real personalization requirements develop.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Data Graph Design → Use-Case-Driven Personalization Architecture.

Marketing Cloud Next evaluates consent at the intersection of a contact point, engagement channel, and communication subscription . Salesforce's consent model is deliberately granular so that customers can make different decisions for different channels and categories of marketing content.

For example, the same customer might opt in to the "Weekly Deals" subscription by SMS while declining the same subscription by email. They might simultaneously remain opted in to a separate "Product Updates" email subscription. Salesforce explicitly states that customers give consent for each channel type associated with a communication subscription.

The contact point is also significant. Consent is tied to contact-point values—such as a particular email address or telephone number—rather than simply being stored as one global preference on the Unified Individual. Salesforce notes that a Unified Individual can contain multiple contact points and that consent checks evaluate those contact points during sending.

Options B and C incorrectly describe consent as globally shared.

The source bank correctly identifies A.

Study Guide Reference: Consent → Consent Evaluation → Contact Point, Channel, and Communication Subscription.

===============

An Automation Event-Triggered Flow is the Marketing Cloud Next-native architecture for responding near real time to CRM record changes associated with a Prospect, Lead, or Contact. Salesforce provides the Prospect, Lead, Contact, or Related Record Change automation event specifically for this purpose. It can start a flow when a qualifying related record is created or updated and meets configured conditions.

A Case associated with a Contact can therefore serve as the related object. The consultant can configure the entry condition so the automation executes when Case Status changes to Closed, identify the related Contact, and then send the customer-satisfaction email.

A generic Salesforce record-triggered flow can react to Case changes, but option C uses the purpose-built Marketing Cloud Next automation-event model for marketing communications. An Audience Flow is better suited to scheduled or segment/list-based audiences rather than immediate reaction to an individual CRM record update.

The uploaded source also identifies C.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Automation Event-Triggered Flows → Prospect, Lead, Contact, or Related Record Change.

===============

Salesforce supports additive edits to an existing Data Graph , including adding related DMOs and adding fields to existing DMOs. When an active Data Graph is edited and the consultant chooses Save and Build , Salesforce processes the new version while keeping the currently active version available.

Salesforce explicitly states that during processing, the existing Data Graph remains active . Once processing completes successfully, the newly built version becomes active. If the build fails, the existing graph continues to operate. This design protects downstream consumers from unnecessary interruption during an additive update.

Cloning is useful when a genuinely separate Data Graph configuration is required, but it isn't necessary merely because an active graph needs additional data. Option B incorrectly claims that editing automatically invalidates dependencies. Option C adds unnecessary operational disruption by pausing segments and flows.

There are limits: once a Data Graph is active, changes are generally additive; existing objects and fields can't simply be removed as they can from a draft.

The master bank correctly keys A. Salesforce's current Data Graph editing documentation directly confirms this version-processing behavior.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Data Graph Management → Editing, Building, and Version Processing.

===============

An Actionable List is the correct audience mechanism when marketers need to target a fixed, specifically selected collection of existing Leads or Contacts without building a Data 360 segment. Salesforce describes Actionable Lists as static collections suited to known individuals, such as imported event attendees or other deliberately selected contacts. An Audience Flow can use a List as its audience source.

For personalization, Content Variables provide dynamic placeholders whose values can be populated by Flow at runtime. Salesforce allows content variables to map to data sources available to Flow, including Salesforce records and other connected data. This makes it possible to supply attributes such as First Name and Account information during message execution.

A Data Graph is designed primarily as a personalization data source and isn't itself the appropriate fixed-list audience source described here. Option A unnecessarily introduces a marketing object and AMPscript when the records already exist as Contacts.

The uploaded master bank identifies C. Salesforce confirms that Audience Flows support List sources and that Actionable Lists represent fixed audiences.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Audience Flows → Actionable Lists and Content Variables.

===============

Marketing Cloud Next provides Consent Banner as a dedicated Salesforce CMS content type . Therefore, the first step is to create a CMS content item of type Consent Banner. Salesforce describes this content type specifically as a banner for marketing landing pages and external websites that collects visitor consent for web-activity tracking.

Once the Consent Banner asset exists, it can be configured for the appropriate tracking environment. Salesforce's web-tracking requirements explicitly state that landing pages with consent-based tracking require a consent banner created in Salesforce CMS , along with the relevant Data 360 web-tracking integration.

Option A is incorrect because an ordinary CMS content block isn't the specialized Consent Banner content type. Option B reverses the required sequence: enabling or applying tracking to a landing-page environment doesn't itself create the consent-banner asset.

This architecture separates reusable consent content from individual landing-page design, allowing administrators to manage tracking-compliance experiences consistently.

The uploaded master bank correctly keys C.

Study Guide Reference: Consent → Web Tracking Consent → Salesforce CMS Consent Banner Content Type.

===============

Salesforce's current Conversational Email implementation guide lists essentially the same five activities shown in option C . First, configure the human representative escalation experience in Service Cloud and Omni-Channel. Second, configure an Agentforce Service Agent capable of handling email conversations. Third, enable and configure Conversational Email in Unified Messaging for the applicable sending address. Fourth, create the Conversational Email campaign and its flow. Finally, monitor engagement, routing, resolutions, and agent escalation outcomes.

Salesforce emphasizes that the human escalation experience should be configured before Conversational Email is enabled, because customers must have a supported path to a human representative when the AI agent can't resolve an inquiry. Service Agents are likewise a formal prerequisite because Agentforce provides the automated interpretation and response capability.

Option A introduces a transactional API endpoint that isn't a standard implementation requirement. Option B relies on Journey Builder and Marketing Cloud Connect concepts that aren't part of the Marketing Cloud Next Conversational Email setup sequence.

The uploaded source correctly identifies C.

Study Guide Reference: Agentforce and AI Innovation → Conversational Email → Agentforce, Service Cloud, Escalation, and Monitoring.

Conversational Email provides the most direct and autonomous solution. Rather than forcing customers to navigate to another web experience or create conventional support cases, NTO can make the existing Order Confirmation and Tracking emails conversational. Customers can simply reply to the email with a question such as "Where is my order?"

Salesforce states that Conversational Email integrates with Agentforce, Digital Engagement, and Data 360. The platform analyzes inbound replies, determines intent, and can route the conversation to an Agentforce agent or human representative while preserving the complete email-thread context.

Salesforce specifically lists Order Management and tracking-information requests as a Conversational Email use case. This makes C particularly strong: Agentforce can resolve repetitive tracking requests without generating unnecessary low-value support workload.

Option A adds friction by sending the customer to a separate chatbot page. Option B only automates routing after a support ticket already exists, whereas the requirement is to reduce or eliminate those cases through autonomous handling.

The uploaded source also keys C.

Study Guide Reference: Agentforce and AI Innovation → Conversational Email → Autonomous Service and Order Management.

===============

Einstein Send Time Optimization (STO) is designed to determine the best time to deliver an email to each individual based on predicted engagement behavior. Salesforce describes STO as a predictive AI capability that analyzes historical data and estimates the send time at which each subscriber is most likely to engage. This makes it the appropriate feature when a global campaign needs individualized delivery timing rather than one fixed send time for the whole audience.

Engagement Frequency addresses a different optimization problem. It determines how frequently a customer should receive email and is primarily intended to reduce fatigue and unsubscribes caused by over-messaging. Engagement Scoring predicts behaviors such as likelihood to open, click, or unsubscribe, allowing marketers to segment or branch audiences according to engagement propensity.

Neither of those features directly schedules each recipient's email for their predicted optimal engagement time.

The master question bank identifies A as the answer. Salesforce's STO model documentation likewise states that the feature maximizes email engagement by optimizing individual send times.

Study Guide Reference: Agentforce and AI Innovation → Einstein Predictive AI → Send Time Optimization.

===============

The most appropriate pattern is Get Records followed by Decision . The flow needs information from a related CRM object—the Case object—that isn't inherently part of the current audience-flow record. A Get Records element can retrieve a matching Case for the customer using criteria such as Contact ID and an open Case status. The subsequent Decision element evaluates whether an open Case was returned and routes the customer accordingly.

Customers with an open case can be diverted away from the Send Email Message path, while those without a matching open Case proceed through the promotional sequence. This structure keeps the suppression condition explicit and maintainable within the flow.

An "Exclusion Filter" isn't the standard Flow Builder element presented for this type of CRM-record lookup and routing. A Decision element alone also can't simply assume access to arbitrary related Case data; the related records first need to be retrieved or otherwise supplied to the flow.

Salesforce lists both Get Records and Decision as supported Flow Builder elements for marketing automation. The supplied master bank likewise keys option A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Flow Elements → Get Records and Decision.

===============

A Salesforce CRM connector in Data 360 is a foundational prerequisite for bringing CRM data into Marketing Cloud Next. Salesforce's setup documentation lists creating a Salesforce CRM connector as one of the required tasks during initial Marketing Cloud Next configuration. The Sales Data Kit then deploys CRM data streams for objects such as Accounts, Contacts, Leads, and Opportunities.

An Identity Resolution ruleset isn't required before deploying the Sales Data Kit. In fact, Salesforce explains that deploying the Sales Data Kit provides a faster path to subsequently building Identity Resolution rulesets because the required CRM objects and mappings are already available.

Option C is plausible in a generic deployment failure, because deployment does require System Administrator plus Data Cloud Architect and Marketing Cloud Admin permissions. However, the question's provisioning context and guided deployment dependency point specifically to the missing CRM connector. The master bank likewise identifies B.

Therefore, before deploying the Sales Data Kit, the consultant should ensure Data 360 is enabled and its Salesforce CRM connector has been established.

Study Guide Reference: Platform Setup and Governance → Marketing Cloud Next Setup → CRM Connector and Sales Data Kit Deployment.

===============

Handlebars is the appropriate method because the scenario specifically requires conditional logic against values supplied by the Data Graph. Marketing Cloud Next's Handlebars implementation provides comparison and control helpers such as if, else if, equals, compare, and, or, and iif. These functions allow message content to change according to profile values such as Loyalty Tier or Points balance.

Marketing Cloud Next exposes the profile Data Graph through Handlebars, allowing deeply related profile attributes to be referenced and evaluated programmatically. Salesforce's developer documentation describes $dataGraph as the profile data graph loaded with marketing content and shows how nested attributes can be traversed.

Simple merge fields are appropriate when the requirement is only to print an attribute. They don't by themselves provide the richer branching logic requested here. Dynamic content variations can also implement marketer-configured targeting, but when the explicit requirement is conditional expression logic against Data Graph values, Handlebars is the more direct technical answer.

The uploaded source keys B.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Personalization → Handlebars Conditional Logic and Data Graph Data.

===============

A Calculated Insight is designed for aggregations across multiple Data 360 records. The requested values aren't simple attributes stored on one ecommerce order. "Total Items" requires aggregation across the customer's purchase history, while "Favorite Category" requires grouping purchase activity by category and identifying the dominant result.

Salesforce Calculated Insights support aggregate metrics such as sums and counts together with dimensions that enable more granular analysis. Salesforce also supports calculated insight metrics in activations and downstream personalization scenarios.

A streaming insight is unnecessary because the campaign runs monthly and doesn't require second-by-second recalculation. Using a standard formula field as proposed in C also doesn't solve multi-record ecommerce aggregation: formula expressions aren't a substitute for analytical rollups across transaction history.

The uploaded source keys B. One wording issue exists in option B: it says "aggregate the purchase volume for the account," while the scenario ultimately requires values associated with each Unified Individual. The underlying architectural principle remains correct—use a Calculated Insight grouped appropriately to the customer/profile dimension.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Calculated Insights → Metrics, Dimensions, and Aggregations.

===============

Unified Engagement History is designed to give Salesforce users a consolidated view of marketing engagement directly within CRM record pages. Salesforce instructs administrators to turn on Unified Engagement History Dashboards and then add the appropriate dashboard component to Account, Lead, Contact, and Opportunity record pages.

This provides sales and marketing users with contextual engagement information without requiring them to leave the CRM record. Marketing engagement can include the individual's interactions with emails, forms, web activity, campaigns, and other Marketing Cloud Next touchpoints represented through the unified engagement model.

The Email Engagement dashboard is useful for aggregate email-performance analysis, but it isn't the specialized CRM-record-level engagement-history experience requested here. Similarly, the Website Engagement DMO alone only represents one class of behavior and wouldn't provide the combined email, form, and page-view history required by the scenario.

The uploaded master bank identifies B. Salesforce's current setup documentation explicitly states that Unified Engagement History components should be added to Contact and other CRM record pages to expose marketing engagement data to users.

Study Guide Reference: Analytics and Performance Insights → Unified Engagement History → CRM Record Page Integration.

===============

Conversational Email is explicitly designed for two-way email interactions in Marketing Cloud Next. Salesforce states that customers can reply directly to outbound emails and that the platform evaluates those replies to determine intent. The resulting conversation can then trigger automated actions, route to an Agentforce agent, or escalate to a human representative while maintaining the original email thread and conversation context.

This precisely matches the requirement for order-notification replies. Salesforce also integrates Conversational Email with Agentforce, Digital Engagement, Service Cloud, Omni-Channel, and Data 360 , allowing AI handling and seamless human escalation. Human representatives can access the complete conversation history when an Agentforce agent escalates the interaction.

Reply Mail Management isn't the complete solution for an AI-driven, contextual conversational experience. Engagement Scoring is predictive marketing functionality based on engagement behavior; it doesn't analyze free-form customer email replies for service intent.

The uploaded document correctly identifies B. Salesforce's current Conversational Email documentation explicitly describes intent analysis, AI/human routing, and contextual thread preservation.

Study Guide Reference: Agentforce and AI Innovation → Conversational Email → Agentforce and Human Escalation.

===============

The correct data source is Event because the required Order Number belongs to the purchase event that initiated the marketing interaction. Marketing Cloud Next supports Event as a personalization data source for Email, SMS, and WhatsApp messages . Event-based personalization makes attributes carried by the triggering event available as merge fields within the message.

In this scenario, when the purchase occurs, the triggering event contains contextual transaction information such as the Order Number. The WhatsApp template can reference that event attribute directly without requiring the value to be separately persisted and retrieved through a Data Graph.

A Data Graph is more appropriate when personalization requires persistent customer-profile information or attributes from related Data 360 objects. A Salesforce Record source is appropriate when the content specifically needs fields from a CRM record supplied to the personalization context. Neither is necessary when the desired information originates directly from the event that triggered the message.

The uploaded master bank identifies option C. Salesforce's personalization reference confirms that Event is supported for WhatsApp and can supply event-based attributes to marketing content.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Content Personalization → Event Data Sources and WhatsApp Messaging.

===============

The critical word is initial . Marketing Cloud Next Business Units provide organizational separation for regions, brands, product lines, or other marketing divisions, but their data isolation is enforced through Data 360 Data Spaces. Salesforce establishes a one-to-one relationship between a Business Unit and a Data Space: a Business Unit can map to only one Data Space, and that Data Space can't be associated with another Business Unit.

More importantly, Salesforce's Business Unit setup instructions specify that before creating the initial Business Units, the organization must already have two or more Data Spaces . Therefore, for North American and European environments requiring segregation, the consultant first establishes the separate Data Spaces. The Business Units can then be created and mapped to those unique Data Spaces, with their associated marketing workspaces and content.

Option B represents an important subsequent configuration but isn't the prerequisite initial step. Option C addresses content organization but by itself doesn't establish the required data boundary.

The master bank likewise identifies A.

Study Guide Reference: Platform Setup and Governance → Business Units in Marketing Cloud Next → Data Spaces and Business Units.

===============

A Data Graph is the correct source because it combines a primary Data Model Object with related objects into a structure optimized for personalization. For Marketing Cloud Next profile personalization, Salesforce typically configures the Data Graph with Unified Individual as the primary DMO , then adds related objects such as Individual, Contact Point Email, purchases, service records, loyalty data, or other associated profile information.

This differs from using the Unified Individual DMO alone. The Unified Individual provider can expose attributes directly stored on that object, but it doesn't provide the same ability to traverse and expose attributes from multiple related DMOs. The requirement specifically states that the content block needs data from related objects , making the Data Graph necessary.

A Personalization Recommender is designed to generate individualized recommendations rather than simply expose relational customer attributes for ordinary email personalization.

Salesforce explicitly states that Data Graphs used for Marketing Cloud Next personalization are typically based on Unified Individual and can include related data such as purchases or service cases. The uploaded bank also keys A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Personalization → Data Graphs and Related Data.

===============

After the initial Identity Resolution processing, Data 360 uses incremental processing so that unchanged source records don't need to be repeatedly rematched. Salesforce's current Identity Resolution documentation explicitly states that preprocessing identifies records that are new or changed and sends only those records into Identity Resolution.

Salesforce determines whether a record changed by converting source records to hash values and comparing those hashes with the values from previous Identity Resolution runs. Records whose current hash indicates no change can be excluded from unnecessary reprocessing.

This behavior has direct credit-consumption implications. Salesforce explains that preprocessing prevents credits from being consumed by repeatedly running Identity Resolution over records that have already been unified in their current form. Even when a source performs a full refresh, preprocessing can protect unchanged records from unnecessary identity-processing work.

Option A is incomplete because an existing record that has been modified must also be reprocessed. Option B incorrectly assumes that every subsequent run rematches the entire source population.

The uploaded master correctly keys C.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Incremental Processing and Credit Consumption.

===============

The Communication Subscription DMO defines the category of marketing content that customers can subscribe to, such as Weekly Deals, Product Updates, or Event Notifications. The Communication Subscription Channel Type DMO then associates that subscription with each supported engagement channel. Therefore, when Weekly Deals is available through both email and SMS, the subscription is represented by Communication Subscription and its channel relationships are represented through Communication Subscription Channel Type.

Communication Subscription Consent performs a different function: it represents customer-level consent associated with the subscription. It doesn't define which channels are supported by the subscription itself. Engagement Channel Type defines available channels such as Email or SMS, but the question specifically asks for the objects used to define the subscription and map it to communication channels . The linking DMO is therefore Communication Subscription Channel Type.

Salesforce explicitly states that each communication subscription contains at least one channel type and can contain several channels. The uploaded master bank also identifies C.

Study Guide Reference: Consent → Communication Subscription Data Model → Communication Subscription and Communication Subscription Channel Type.

===============

An Event Data Provider is appropriate because the email is triggered by a discrete event—specifically, a landing-page form submission—and the email must use values contained in that event payload. Salesforce categorizes Event as a supported Marketing Cloud Next personalization data source and describes events as activities such as order confirmations and subscription signups that trigger flows.

A form submission can launch an Automation Event-Triggered Flow. Data associated with the triggering event can then be exposed to message content through the Event Data Provider, allowing submitted values such as first name, selected product, event choice, or form responses to appear as merge fields.

A Data Graph is better suited to persistent profile and related Data 360 information. It isn't necessary when the desired values are already available from the triggering event. Activation Data Provider is used when personalization attributes come from a Data 360 segment activation.

Salesforce documentation demonstrates the same pattern: event-triggered emails can use event values through Event Data Provider merge fields. The uploaded bank keys A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Event-Triggered Marketing → Event Data Provider Personalization.

===============