Certified Marketing Cloud ConsultantDemo

The Scope by User configuration evaluates Sales Cloud data access using the integrated Marketing Cloud Connect user who initiates the action. Reports, campaigns, and returned subscriber records are therefore limited to data that user is permitted to view in Salesforce.

Marketing Cloud Engagement’s Event Notification Service delivers transactional “not sent” events to a callback endpoint. An external system is required to receive those callbacks and complete the subscription-confirmation process, enabling real-time handling of failed transactional sends.

MobileConnect SMS personalization can use customer attributes in the MobileConnect Demographics table. Salesforce documentation states that MobileConnect replaces personalization strings with applicable customer attributes and directs users to link applicable data extensions to the MobileConnect Demographic attribute group.

A Refresh Mobile Filtered List activity recalculates the birthday-based audience before each weekly run. A Send SMS activity then sends the existing MobileConnect outbound message to that refreshed list; importing contacts is not needed because the contacts and filtered list have already been created.

In Automation Studio, File Transfer decrypts the incoming encrypted file, and Import File loads that external subscriber data into a Marketing Cloud list or data extension. An SQL Query can use data extensions and system data views, including send and open history, to construct an engagement-based audience before the Send Email activity runs.

The _Click data view contains email click-tracking records and retains them for six months. An SQL Query activity can query that data view, filter click events to the required time period, and select distinct subscriber identifiers for the loyalty-program audience.

A separate data extension preserves the independently updated dataset while Data Designer relationships associate it with the existing contact-related data extensions. Data Designer supports linking data extensions to the contact record or to other data extensions, enabling related data to be used without changing the contact record itself.

An Automation Studio Import Activity can automatically load a file from the SFTP and overwrite or update an auto-suppression list, providing a scheduled no-code maintenance process. Salesforce documents that auto-suppression lists can be modified by an Import Activity in Automation Studio.

A Subscriber Key uniquely identifies a subscriber, determines which subscriber record is unsubscribed, and permits the same email address to be associated with different Subscriber Keys. Marketing Cloud Connect stores Salesforce Contact, Lead, or User IDs as Subscriber Keys; therefore, a previous send keyed by Email Address can create a separate subscriber record whose unsubscribe status does not apply to the MCC record.

The Complaint data view stores spam-complaint events at the subscriber level. An automation that queries this data view can identify the affected subscribers and provide their records for flagging in the customer service database.

A Salesforce Campaign supports manually adding both leads and contacts as campaign members. With Marketing Cloud Connect, Email Studio can target Salesforce campaigns as recipient sources for sends, including through Send Flow.

Marketing Cloud Connect can use the record owner as the sender through the Send From Record Owner option. A custom Send Classification can apply the associated sender profile, including dynamic sender information sourced from Sales Cloud. Delivery Profiles control delivery configuration rather than the From identity, and an Organization-Wide Email Address represents an organizational sender rather than the record owner.

AMPscript can use HTTPGet() to retrieve and parse an RSS feed during email send processing, so the message can include current feed entries. An External Content block can be configured with Send Time retrieval, which fetches URL content when the email is processed for sending. Personalization Strings substitute attributes, and Dynamic Content applies rule-based content variations; neither is an RSS retrieval mechanism.

A Random Split distributes contacts across the three creative versions. After each version is sent and sufficient time is allowed for responses, an Engagement Split can route non-engaged contacts. A Join combines those non-engaged paths so they receive a single follow-up email.

A dedicated IP must send at least 100,000 emails per month to remain warm and maintain its sender reputation. Sending below that amount can cause delivery problems such as deferrals, bulk-folder placement, or blocking. At approximately 300,000 monthly emails, this volume meets the minimum requirement.

Marketing Cloud Connect triggered sends can be created on objects that have a lookup to a Contact ID or Lead ID, so the Shipments custom object needs a lookup to a Lead or Contact. Each enabled object also requires an Apex trigger for after-insert and after-update events that calls the Marketing Cloud Connect trigger automation utility.

The _Sent data view provides email-send records and subscriber identifiers, and the _Subscriber data view provides the associated email address. Joining these data views supports troubleshooting by email address while avoiding storage of a duplicate email address in every SendLog record. The _Sent data view is retained for the last six months and is not real-time.

Data extensions are the table-based data objects used by Contact Builder to store and relate contact information. They support the relational data model needed to augment contact records with related tables; lists are not a substitute for that Contact Builder data model.

For bulk reactivation, export the Held (Undeliverable) subscribers, change each exported Status value to Active, and import the file into All Subscribers with an update option. Salesforce documents this as the process for changing Held subscribers back to Active; reactivation should be done only after confirming the addresses are deliverable, because it can otherwise increase future bounces and harm sender reputation.

Marketing Cloud Connect uses an Apex trigger to evaluate Lead insert or update events, and the Lead object must be enabled for triggered sends in the connector configuration. The triggered send is created from Sales Cloud; Marketing Cloud Engagement creates the corresponding triggered-send definition, while Sales Cloud can display aggregate tracking data across the connected clouds.

A Decision Split should evaluate the current activation Boolean immediately before each reminder. Waiting 24 hours before each evaluation places the sends at 24 and 48 hours after registration and prevents a subscriber who activated during either wait period from receiving the corresponding reminder. Journey Builder Decision Splits evaluate contact data against configured filter criteria, while Wait activities hold contacts for the configured duration.

LookupOrderedRows() retrieves a rowset from a data extension, so one call can return multiple records for a SubscriberKey and expose the fields in those records. A single Lookup() call returns one requested column value and, when multiple records match, returns only the first matching value; it therefore does not meet the multi-record, 25-column requirement. The Server-Side JavaScript LookupOrderedRows() function is the correctly named rowset lookup option.

A Triggered Send Data Extension supports an API-initiated, event-driven email send and stores the submitted recipient data for use in personalization. The triggered send and its email content can be configured in Marketing Cloud, allowing marketers to update the creative without changing the website’s API integration. Hourly Automation Studio activities do not satisfy the near-immediate delivery requirement.

Google Analytics 360 provides the Google Analytics audience and Journey Builder GA entry source needed to create a segment of purchasers who have not submitted a review and automatically admit its members to the journey. The Web Analytics Connector is for tracking and analyzing Marketing Cloud Engagement send data, not for injecting a Google Analytics audience into Journey Builder.