Marketing-Cloud-Consultant Salesforce Certified Marketing Cloud Consultant Exam (SP23) Questions and Answers

A limitation that the consultant should consider when recommending Field-Level Encryption is that Field-Level Encryption doesn’t support segmenting, filtering, or querying encrypted fields. Field-Level Encryption is a feature that allows marketers to encrypt sensitive data in Marketing Cloud using encryption keys and algorithms. However, encrypted fields cannot be used for segmenting subscribers using filters or queries, as they cannot be evaluated or compared with other values. References: https://help.salesforce.com/s/articleView?id=sf.mc_overview_field_level_encryption.htm &type=5

To configure a sending domain in Marketing Cloud, the customer needs to delegate a subdomain to Marketing Cloud and modify their DNS entries to point to Marketing Cloud’s servers. These questions will help determine if the customer has the authority and ability to do so. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm &type=5

To use the Ad Campaign Activity in a Journey Builder journey, Northern Trail Outfitters should enable Advertising Studio. Advertising Studio is a tool that allows marketers to create and manage advertising campaigns on different platforms, such as Facebook, Google, or Twitter. The Ad Campaign Activity is a feature of Advertising Studio that allows marketers to add contacts from a journey to an advertising audience and target them with relevant ads. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_advertising_studio.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_ad_campaign_activity.htm &type=5

To enable data extensions for sending SMS messages from MobileConnect, Northern Trail Outfitters should add two fields to their data extensions: a field of Locale type containing the country code and a field of Phone type containing the mobile number. These fields are required for MobileConnect to identify and send messages to mobile subscribers. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_create_a_data_extension_for_mobileconnect.htm &type=5

To diagnose the issue of failed Salesforce Triggered Sends, the consultant should ensure the System User is assigned the Standard User Profile. The System User is a user account that Marketing Cloud Connect uses to communicate with Sales Cloud. The System User needs to have the Standard User Profile or a custom profile with similar permissions to enable Salesforce Triggered Sends. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_troubleshoot_marketing_cloud_connect_configuration_issues.htm &type=5

To recommend a scalable business unit hierarchy for Northern Trail Outfitters and its three subsidiaries, the consultant should suggest one parent BU and three child BUs with their own Sender Authentication Packages. This will allow each subsidiary business to have their own branding, content, and subscribers, as well as access to aggregate reporting and shared subscribers from the parent BU. Each child BU should have its own Sender Authentication Package to authenticate its email sends with its own domain and branding. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_business_unit_setup.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm &type=5

To send emails to loyalty members based on recent activity, a contact data entry source can be used to segment the data based on attributes and filters configured in Contact Builder. This allows for more flexibility and scalability than using a data extension entry source with an applied filter. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_entry_sources.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_attribute_groups.htm &type=5

To automate a weekly SMS message to contacts who have a birthday that week, the Refresh Mobile Filtered List activity can be used to update the filtered list based on the birth date criteria. The Outbound Send activity can then be used to send the SMS message to the contacts in the filtered list. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_refresh_mobile_filtered_list.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_moc_outbound_send.htm &type=5

To allow for long-term self-sufficiency in segmentation, Northern Trail Outfitters should use data filters. Data filters are a user-friendly tool that allows marketers to segment their data based on criteria and conditions without coding. Data filters can also be refreshed and reused for different campaigns. Attribute groups are used to link data sources in Contact Builder, not for segmentation. Publication lists are used to manage opt-in preferences, not for segmentation. Query activities require SQL knowledge and coding skills, which the marketing team lacks. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_data_filters.htm &type=5

To format the JSON payload from their commerce platform within the email, Northern Trail Outfitters should use the BuildRowSetFromJSON() AMPscript function. The BuildRowSetFromJSON() AMPscript function is a function that allows marketers to parse a JSON string and return a rowset object that can be used to display data within an email message. The BuildRowSetFromJSON() AMPscript function can handle nested JSON objects and arrays. References: https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-programmatic-content.meta/mc-programmatic-content/buildrowsetfromjson.htm

To export a data file to its SFTP containing all subscribers who did not receive their intended email in the last 24 hours, Northern Trail Outfitters should use a Data Extract Activity in their automation. A Data Extract Activity is an activity that allows marketers to extract data from Marketing Cloud and place it in a file on an Enhanced FTP location or an external SFTP location. The Data Extract Activity can use different extract types, such as Tracking Extract or Data Extension Extract, to export different types of data. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_data_extract_activity.htm &type=5

A contact is a person who interacts with a brand across one or more channels, such as email, mobile, web, etc. A contact is identified by a contact key, which is usually the same as the subscriber key in Marketing Cloud or the contact or lead ID in Sales Cloud. When users register with the mobile app, they will create new contacts in Marketing Cloud with their device IDs as contact keys. However, these contacts will not be associated with their contact keys in Sales Cloud until they are synchronized through Marketing Cloud Connect, which can take up to 24 hours. Therefore, newly registered users will create additional contacts in Marketing Cloud until they are matched with their existing contacts in Sales Cloud. References: https://help.salesforce.com/articleView?id=sf.mc_co_what_is_a_contact.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_co_implementing_contacts_in_the_marketing_cloud.htm &type=5

To capture customer feedback via email and create a new case in Service Cloud if a customer indicates they are unhappy with the service they have received, Northern Trail Outfitters should use an Engagement Split to capture positive or negative responses, and a Case Activity to create a new case in Service Cloud. An Engagement Split is an activity that allows marketers to route contacts based on their engagement with email messages, such as opens or clicks. A Case Activity is an activity that allows marketers to create cases in Service Cloud based on contact attributes or journey data. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_engagement_split.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_case_activity.htm &type=5

To manually create a segment of both lead and contact records that can be targeted through the Send Flow in Content Builder, Northern Trail Outfitters should use a Salesforce Campaign. A Salesforce Campaign is an object in Sales Cloud that allows marketers to group leads or contacts for a specific marketing initiative, such as an email campaign. A Salesforce Campaign can be used as a target audience in Marketing Cloud using the Send Flow in Content Builder. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_send_flow.htm &type=5

To send SMS messages to contacts located in the United States using a Salesforce entry event in a journey, NTO should format the phone field in Salesforce as +l[phonenumber], where +1 is the country code for the United States and [phonenumber] is the 10-digit phone number without any spaces or dashes. This format ensures that Marketing Cloud can correctly identify and validate the mobile numbers for SMS sending. Normalizing phone numbers in journey settings only applies to mobile numbers stored in MobileConnect or MobilePush demographics tables, not to mobile numbers from Salesforce entry events. Selecting ‘US’ as the sending country in SMS activity only affects how opt-out keywords are processed, not how mobile numbers are validated. Configuring the phone field in Salesforce as US locale only affects how phone numbers are displayed in Salesforce, not how they are formatted for Marketing Cloud. References: https://help.salesforce.com/articleView?id=sf.mc_rn_june_2020_moc_normalize_phone_number_journey_setting.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_moc_country_code_processing_for_opt_out_keywords.htm &type=5 https://help.salesforce.com/articleView?id=admin_phoneformat.htm &type=5

• The Shipment object requires a Lookup to Lead or Contact1. This is because triggered sends can only be sent to Salesforce contacts, leads, or person accounts when object records are created or updated1.
• An Apex Trigger is created on the Shipment object2. This is because a trigger is Apex code that executes before or after certain operations on an object2, and it can be used to invoke the Marketing Cloud integration action that triggers the email send3.

To send an email with personalized fields from multiple data extensions without coding experience, Northern Trail Outfitters should combine the data outside of Marketing Cloud and upload it into a sendable data extension. This will allow them to have all the required fields for personalization in one data source and avoid using complex scripting or queries to join and filter data from multiple data extensions.

Establishing data relationships and creating data filters would not help with personalization, as they are used for segmentation purposes. Creating SQL query activities would require coding skills and experience with SQL syntax. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_send_email_using_a_data_extension.htm &type=5

A synchronized data extension is a data extension that is automatically populated with data from Sales Cloud objects using Marketing Cloud Connect. A query activity is an automation studio activity that allows querying data from data extensions or data views using SQL statements. A Salesforce data extension is a type of data extension that stores data imported from Sales Cloud reports or campaigns using Marketing Cloud Connect. By querying synchronized data extensions using a query activity to a Salesforce data extension, the customer can segment contacts based on complex criteria without relying on Sales Cloud reports or campaigns. Then, by sending via Email Studio Send Flow to the Salesforce data extension, the customer can leverage tracking and reporting features of Marketing Cloud Connect. References: https://help.salesforce.com/articleView?id=sf.mc_co_data_integration_synchronized_data_sources.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_send_email_send_flow.htm &type=5

To utilize a Retention Policy for a data extension that stores web behavior data, two methods are possible. One is to delete data from the data extension prior to twelve months ago, then configure a Retention Period via Contact Builder. This will allow the data extension to keep only the data from the previous twelve months and delete any older data automatically. The other method is to replace the current data extension with a new data extension configured with a Retention Period. This will create a new data extension with the same fields and settings as the old one, but with a Retention Period enabled. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_data_retention_policies.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_create_a_new_data_extension_from_an_existing_data_extension.htm &type=5

A random split activity is an automation studio activity that randomly splits a data extension into multiple groups based on percentage or number of records. It can be used to create test groups for different messaging strategies or to segment a large audience into smaller batches for sending. It can handle up to 12 groups and up to 50 million records per group. References: https://help.salesforce.com/articleView?id=sf.mc_as_random_split_activity.htm &type=5

The email address that would appear as the From Address for the automatic reply to the customer is reply@marketingcloud.com. This is because Northern Trail Outfitters has configured their Reply Mail Management settings to forward replies to customerservice@nto.com and send an auto-reply message to the customer’s email address. The From Address for the auto-reply message is always reply@marketingcloud.com, regardless of the original From Address or the forwarding address. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_reply_mail_management.htm &type=5

A query activity is an automation studio activity that allows querying data from data extensions or data views using SQL statements. A data extension entry source is a journey builder entry source that allows injecting contacts into a journey based on a data extension. Journey activities are actions that occur within a journey, such as sending an email or updating a contact attribute. By using a query activity to filter contacts who have not made a purchase in the last six months from their order data extension, NTO can create a sendable data extension with those contacts and use it as a data extension entry source for their journey. Then, by using journey activities, they can communicate the same message across all channels to those contacts. References: https://help.salesforce.com/articleView?id=sf.mc_as_sql_query_activity.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_jb_data_extension_entry_source.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_jb_journey_activities.htm &type=5

A random split activity is an automation studio activity that randomly splits a data extension into multiple groups based on percentage or number of records. It can be used to create test groups for different messaging strategies or to segment a large audience into smaller batches for sending. It can handle up to 12 groups and up to 50 million records per group. References: https://help.salesforce.com/articleView?id=sf.mc_as_random_split_activity.htm &type=5

To target all customers who have registered to receive push notifications, Northern Trail Outfitters can use two ways to create this segment:

• Using Mobile Studio, create a Mobile Push Filtered List then filter on the MobilePush Demographics attribute group. This is a user-friendly tool that allows marketers to segment their mobile push audience based on criteria and conditions without coding.
• Using Automation Studio, query the _MobilePushDemographics Data View and save this to a data extension. This is a more advanced tool that allows marketers to segment their mobile push audience using SQL queries and data views.

Using Journey Builder or Contact Builder are not ways to create segments for mobile push audiences, as they are used for different purposes. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_create_a_filtered_list.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_query_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_data_view_mobilepushdemographics.htm &type=5

Two considerations that should be made when using a File Drop Automation are:

• They may utilize an external FTP site. A File Drop Automation can be configured to use an external SFTP location as well as an Enhanced FTP location for file triggers.
• The directory is unable to be used by another File Drop Automation. A File Drop Automation can only use one directory for file triggers, and that directory cannot be used by another File Drop Automation.

The directory used by the file trigger can be inside or outside the import directory, as long as it is not used by another File Drop Automation. The directory can contain more than five file triggers, but only one file trigger can start an automation at any given time. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_file_drop_automation_studio_triggers.htm &type=5

To choose a subscriber key for Marketing Cloud, Northern Trail Outfitters should use a value that is unique, persistent, and channel-agnostic. A CRM ID or a loyalty program number are both good options, as they meet these criteria and can be used to identify and track subscribers across different channels and platforms. Email and mobile device ID are not good options, as they are not unique or persistent (subscribers can change their email or device) and they are specific to one channel (email or mobile). References: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htm &type=5

To configure specific data extensions, like Product Information, that are used by several business units (BU), Northern Trail Outfitters should share data extensions from the top-level BU. Sharing data extensions from the top-level BU allows marketers to grant access to common data sources across multiple child BUs without creating local copies or duplicating data. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_share_data_extensions_across_business_units.htm &type=5

A Sender Authentication Package (SAP) is a set of features that authenticate an email sender’s identity and reputation, such as a private domain, a dedicated IP address, a link customization, and a reply mail management. By having an additional SAP for the new domain comms.nto.com.au, NTO can send emails from their new domain without impacting deliverability. An additional IP address is not required if they already have one for their SAP. An additional private domain is not enough to authenticate their sender identity and reputation. Registering the new domain in From Address Management is not necessary if they have an SAP for the new domain. References: https://help.salesforce.com/articleView?id=sf.mc_es_sender_authentication_package.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_from_address_management.htm &type=5

Synchronized data extensions are data extensions that are automatically populated with data from Sales Cloud objects using Marketing Cloud Connect. They can be configured with filters to limit the records that are imported based on criteria such as field values or record types. By using synchronized data extensions with a filter on the consent checkbox field, NTO can import their Sales Cloud data into Marketing Cloud and leverage it within Journey Builder. Synchronized data extensions can be refreshed as frequently as every 15 minutes, which meets the requirement of having no more than 30 minutes delay. References: https://help.salesforce.com/articleView?id=sf.mc_co_data_integration_synchronized_data_sources.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_co_implement_synchronized_data_sources_best_practices.htm &type=5

To know the number of contacts in their account and email it to their Chief Marketing Officer on a weekly basis, Northern Trail Outfitters should schedule the Contacts Counts Standard Report. This report shows how many contacts are in Marketing Cloud across different channels and platforms. The report can be scheduled to run at a recurring interval and emailed to one or more recipients. References: https://help.salesforce.com/s/articleView?id=sf.mc_rn_contacts_count_report.htm &type=5

To automate exclusion of identified email addresses from all future sends that use specific sender profiles, Northern Trail Outfitters should use an auto-suppression list. An auto-suppression list is a tool that allows marketers to exclude subscribers from email sends based on their email address and sender profile. The email addresses can be added to the auto-suppression list using a SQL query or an import activity. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_create_an_auto_suppression_list.htm &type=5

SOAP API calls updating objects and CreateSalesforceObject() AMPscript are both types of API calls that are counted against the rolling 24-hour limit in Salesforce. Login calls and bulk API calls are not counted against this limit. References: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_api_concepts_limits.htm https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-programmatic-content.meta/mc-programmatic-content/createsalesforceobject.htm

Creating an installed package in Marketing Cloud with Read and Write permissions for data extensions should be used to facilitate the functionality of upserting rows into a data extension using a REST API endpoint. An installed package is a container for one or more API integrations that provides authentication credentials and permissions for accessing Marketing Cloud resources. Read and Write permissions for data extensions allow the API integration to retrieve and modify data in data extensions. References: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/create_a_package.html https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/data-extensions.html

To limit subscriber records by BU based on the ‘Region’ profile attribute, Northern Trail Outfitters should select ‘Define Subscriber Filter’ for each BU on the BU Setup page and configure a condition to match the corresponding profile attribute. This will allow users who are assigned to a BU to only view and send to subscribers who have the same region value as their BU. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_business_unit_setup.htm &type=5

Two considerations that should be made about tokenized sending are:

• Personalization strings still allow PII to be displayed within an email. Tokenized sending does not encrypt or mask PII within an email, it only prevents it from being stored in Marketing Cloud. Therefore, personalization strings should be used with caution and only when necessary.
• Service Level Agreements for email sends are unsupported with the inclusion of outside servers. Tokenized sending relies on an external server to provide PII at send time, which may introduce latency or errors that affect the delivery time and performance of emails.

Journey Builder decision splits do not provide a method to access tokenized data natively, but they can be configured with custom activities or API calls to do so. Tokenized sending does not require field-level data encryption for additional security, as PII is never stored in Marketing Cloud. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_tokenized_sending.htm &type=5

This personalization string is used to direct a subscriber to a web version of the email, allowing them to view the email online even if their email client does not support HTML. For more information on personalization strings, please see the documentation here: https://help.salesforce.com/articleView?id=mc_es_personalization_strings.htm &type=5.

The %%view_email_url%% personalization string is a system-generated link that allows subscribers to view a web page version of an email. It can be included as the href attribute in a ‘view online’ link in an email template to enable users to view the email in a browser if they have trouble viewing it in their email client. The %%view_as_webpage%% personalization string is deprecated and should not be used. The %%vawp%% personalization string is an alias for %%view_as_webpage%% and should not be used either. The %%view_online%% personalization string does not exist. References: https://help.salesforce.com/articleView?id=sf.mc_es_view_email_url_personalization_string.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_view_as_web_page_personalization_string.htm &type=5

To send SMS and push notifications together with emails as part of a new customer onboarding journey, Northern Trail Outfitters should use a GUID or another generated ID for Contact Key. A Contact Key is a unique identifier for each contact in Marketing Cloud across different channels and platforms. A GUID or another generated ID is recommended as a Contact Key because it is persistent, consistent, and channel-agnostic. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htm &type=5

The _ListSubscribers data view contains information about subscribers who belong to a specific list, including publication lists. It can be used to query subscribers based on their list ID, status, and date joined or unsubscribed. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_data_view_listsubscribers.htm &type=5

A limitation that the consultant should consider when recommending Field-Level Encryption is that Field-Level Encryption doesn’t support segmenting, filtering, or querying encrypted fields. Field-Level Encryption is a feature that allows marketers to encrypt sensitive data in Marketing Cloud using encryption keys and algorithms. However, encrypted fields cannot be used for segmenting subscribers using filters or queries, as they cannot be evaluated or compared with other values. References: https://help.salesforce.com/s/articleView?id=sf.mc_overview_field_level_encryption.htm &type=5

Before disconnecting the sandbox instance and connecting the production instance in the Cloud Kicks business unit, NTO should remove any existing user mappings, attribute mappings, and tracking subscriptions that are associated with the sandbox instance. User mappings define which Marketing Cloud users can access which Sales Cloud users’ data. Attribute mappings define which Sales Cloud fields are used as subscriber attributes in Marketing Cloud. Tracking subscriptions define which Sales Cloud objects receive tracking data from Marketing Cloud sends. These settings should be removed before changing the CRM connection to avoid errors or conflicts. Additionally, NTO should update any query activities that reference the synchronized data extensions from the sandbox instance, as these will be different from the production instance synchronized data extensions. References: https://help.salesforce.com/articleView?id=sf.mc_co_disconnect_a_salesforce_org_from_a_business_unit.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_co_map_marketing_cloud_users_to_salesforce_users.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_co_create_attribute_mappings_for_your_account.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_co_set_up_tracking_information_to_send_to_salesforce.htm &type=5

A consideration that should be made when building dynamic content rules is that rules should be built before uploading the respective content. Dynamic content rules are rules that define what content should be displayed based on subscriber attributes or behaviors. Dynamic content rules should be created before uploading content blocks or images into Content Builder, as they cannot be edited after content is uploaded. References: https://help.salesforce.com/s/articleView?id=sf.mc_ceb_dynamic_content_rules.htm &type=5

To target all customers who have registered to receive push notifications, Northern Trail Outfitters can use two ways to create this segment:

• Using Mobile Studio, create a Mobile Push Filtered List then filter on the MobilePush Demographics attribute group. This is a user-friendly tool that allows marketers to segment their mobile push audience based on criteria and conditions without coding.
• Using Automation Studio, query the _MobilePushDemographics Data View and save this to a data extension. This is a more advanced tool that allows marketers to segment their mobile push audience using SQL queries and data views.

Using Journey Builder or Contact Builder are not ways to create segments for mobile push audiences, as they are used for different purposes. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_create_a_filtered_list.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_query_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_data_view_mobilepushdemographics.htm &type=5

To send emails to loyalty members based on recent activity, a contact data entry source can be used to segment the data based on attributes and filters configured in Contact Builder. This allows for more flexibility and scalability than using a data extension entry source with an applied filter. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_entry_sources.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_attribute_groups.htm &type=5

To process the correct subscribers who are added to a data extension via API for a monthly payment reminder journey, Northern Trail Outfitters should use Contact Evaluation > Evaluate new records only. Contact Evaluation is a setting that defines how contacts are evaluated for entry into a journey based on their entry source. Evaluate new records only is an option that allows only new records that are added to the entry source after the journey is activated to enter the journey. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_contact_evaluation.htm &type=5

An auto-suppression list populated with the known email addresses can be used to ensure none of these competitors receive their emails. An auto-suppression list is a type of exclusion list that prevents subscribers from receiving certain types of messages based on criteria such as email address, subscriber key, or domain. References: https://help.salesforce.com/articleView?id=sf.mc_es_auto_suppression_lists.htm &type=5

To track clicks on Contact records in Salesforce, two requirements must be met:

• The subscriber key must match the ContactID field in Salesforce.
• The individual level tracking option must be selected in Marketing Cloud configuration.

If either of these requirements is not met, clicks will not show up on Contact records. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_marketing_cloud_connect_configuration.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_guidelines_for_marketing_cloud_connect.htm &type=5

Performing large-scale segmentation in Automation Studio before admitting contacts into Journey Builder can help reduce the amount of contacts admitted into the journey, thereby increasing the performance of the journey.

Creating prefiltered, sendable copies of data extensions for each journey instead of using the same entry source can also help optimize journey performance as it reduces the number of contacts that have to be processed for each journey. This can help with performance as the data extension is already filtered and therefore the journey has to do less work in terms of filtering the participants. For more information, see the Salesforce Certified Marketing Cloud Consultant Exam Study Guide[1] or the Salesforce documentation on Journey Performance[2].

[1] https://trailhead.salesforce.com/content/learn/certifications/marketing-cloud-consultant/marketing-cloud-consultant-exam-study-guide  [2] https://help.salesforce.com/articleView?id=mc_jb_improve_journey_performance.htm &type=5

Two potential reasons for SMS responses getting the default keyword response rather than the appropriate next keyword response are:

• Responses are not sent within the Conversation Window. The Conversation Window is a setting that defines how long MobileConnect waits for a response from a subscriber after sending an outbound message. If a subscriber responds after the Conversation Window expires, MobileConnect treats their response as a new inbound message rather than part of an ongoing conversation.
• Next keyword was not specified on the outbound message. The Next Keyword is a setting that defines what keyword MobileConnect expects from a subscriber after sending an outbound message. If a subscriber responds with a different keyword than what MobileConnect expects, MobileConnect treats their response as a new inbound message rather than part of an ongoing conversation.

Responses containing “stop” in the message content will not get the default keyword response, but rather an opt-out confirmation message. Responses sent with AMPscript in body will not affect how MobileConnect handles responses, as AMPscript is only evaluated at send time. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_conversation_window.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_moc_next_keyword.htm &type=5

To send an email to one million contacts in Sales Cloud using 10+ fields to segment contacts, Northern Trail Outfitters should send to a Salesforce Report from Marketing Cloud using Email Studio Send Flow. Sending to a Salesforce Report allows marketers to use existing reports in Sales Cloud as target audiences in Marketing Cloud without importing or syncing data. Using Email Studio Send Flow allows marketers to select an audience, an email message, and other options for sending an email campaign. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_send_flow.htm &type=5

To query Marketing Cloud for send data across SMS, Push, and email, Northern Trail Outfitters should use _Send Data Views. Data Views are system-generated tables that store tracking and system data for different channels and platforms in Marketing Cloud. _Send Data Views contain information about email sends, SMS sends, and push sends across different business units and accounts. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_data_view_send.htm &type=5

To send a welcome email to contacts when a contact record is added as a campaign member to a ‘Loyalty Member’ campaign in Sales Cloud, Northern Trail Outfitters should create a journey with a Salesforce Data entry source and an email activity. A Salesforce Data entry source allows marketers to inject contacts into a journey based on changes or events in Sales Cloud objects, such as campaign members. An email activity allows marketers to send an email message to contacts in a journey. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_salesforce_data_event.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_email.htm &type=5

The LookupRows AMPscript function returns a rowset from a data extension that matches the specified criteria. It can be used to retrieve multiple rows of data from a data extension based on one or more column values. For example, NTO can use the LookupRows function to retrieve all rows from the second data extension that have the same session ID as the subscriber in the sendable data extension, and then loop through the rowset to display the product data for each abandoned cart item in the email. References: https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-programmatic- content.meta/mc-programmatic-content/lookuprows.htm

Three tasks that a consultant would suggest for using Journey Builder instead of Automation Studio are:

• Building simple segmented campaigns without SQL queries. Journey Builder allows marketers to create simple segmented campaigns using filters and rules without writing SQL queries. Automation Studio requires SQL queries for creating complex segments using data extensions.
• Designing decision logic via an intuitive user interface. Journey Builder allows marketers to design decision logic using activities such as decision splits, engagement splits, or random splits via an intuitive user interface. Automation Studio requires scripting or coding for creating decision logic using activities such as script activities or verification activities.
• Setting behavior-based goals. Journey Builder allows marketers to set behavior-based goals using criteria such as email opens, clicks, conversions, or custom events. Automation Studio does not have a feature for setting behavior-based goals.

Processing zipped encrypted files containing subscriber data is a task that a consultant would suggest for using Automation Studio instead of Journey Builder, as Automation Studio has activities such as file transfer activities or import file activities that can handle zipped encrypted files. Creating customer segments from multiple data extensions is a task that a consultant would suggest for using Automation Studio instead of Journey Builder, as Automation Studio has activities such as query activities or filter activities that can create customer segments from multiple data extensions. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_journey_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_automation_studio.htm &type=5

To create a task on Contact and Lead records for follow up when someone has not opened five emails in a row, a scheduled automation can be used to run a SQL query activity that selects the subscribers who meet this criteria from the _Open data view and inserts them into a data extension. The data extension can then be used as an entry source for a journey that has a task activity to create the task in Sales Cloud. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_data_view_open.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_task_activity.htm &type=5

To send out a biweekly newsletter with personalized property listings for new contacts added to a newsletter campaign in Salesforce CRM, a real estate agency should use Automation Studio to prepare personalization data and initiate journey. Automation Studio can run a scheduled automation that imports new contacts from Salesforce CRM into a data extension, runs query activities to join and filter property data based on contact criteria, and injects contacts into a journey that sends the newsletter with personalized content. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_import_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_query_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_journey_builder_audience.htm &type=5

Two options that would prevent the customer from duplicating records when implementing a Sales Cloud instance are:

• Get existing records updated with new Keys sourced from Sales Cloud instance. This option will allow the customer to update their existing records in Marketing Cloud with new keys that match their Sales Cloud records, such as Contact ID or Lead ID. This will ensure data consistency and avoid duplication across both systems.
• Continue as normal, as Marketing Cloud Contact Models will dedupe keys by Email Address. This option will allow the customer to continue using Email Address as their primary key in Marketing Cloud, and rely on Marketing Cloud Contact Models to dedupe keys by Email Address when syncing data from Sales Cloud. This will ensure data accuracy and avoid duplication within Marketing Cloud.

Uploading CSV with Migrated Subscriber Keys to All Subscribers will not prevent duplication, as it will create new records in Marketing Cloud with different keys than the existing records. Purging the current records and carrying on with new keys sourced from Sales Cloud will result in data loss and potential compliance issues. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_contact_key.htm &type=5

A journey with CRM date based entry source can be used to trigger emails based on a date field in the CRM object, such as the reminder date. The journey can also use the Update Contact activity to update the record in CRM after sending the reminder email. References: https://help.salesforce.com/articleView?id=sf.mc_jb_date_based_events.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_jb_update_contact.htm &type=5

Synchronized data extensions are data extensions that are automatically populated with data from Sales Cloud objects using Marketing Cloud Connect. They can be configured with filters to limit the records that are imported based on criteria such as field values or record types. By using synchronized data extensions with a filter on the consent checkbox field, NTO can import their Sales Cloud data into Marketing Cloud and leverage it within Journey Builder. Synchronized data extensions can be refreshed as frequently as every 15 minutes, which meets the requirement of having no more than 30 minutes delay. References: https://help.salesforce.com/articleView?id=sf.mc_co_data_integration_synchronized_data_sources.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_co_implement_synchronized_data_sources_best_practices.htm &type=5

A verification activity is an automation studio activity that allows checking the record count or field value of a data extension and sending a notification email if it meets certain criteria. A filter activity is an automation studio activity that allows filtering records from a source data extension into a target data extension based on filter criteria. By using these two activities in an automation, NTO can monitor available coupon codes in their coupon data extension and send a notification email to their email specialist if the available coupon count falls below 500. An import activity is used to import data from an external file or data source into a data extension, which is not relevant for this use case. A data extract activity is used to extract data from a data extension or data view into a file, which is also not relevant for this use case. References: https://help.salesforce.com/articleView?id=sf.mc_as_verification_activity.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_as_filter_activity.htm &type=5

The Transactional Messaging API can be used to send email to customers who log in for the first time on a new IP. The Transactional Messaging API allows for fast and reliable delivery of transactional messages, such as password resets, order confirmations, or account alerts. The message can include information related to the login IP by using personalization strings or AMPscript variables. References: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/transactional-messaging-api.html https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/transactional-messaging-personalization.html

A Sender Authentication Package (SAP) is a set of features that authenticate an email sender’s identity and reputation, such as a private domain, a dedicated IP address, a link customization, and a reply mail management. By having an additional SAP for the new domain comms.nto.com.au, NTO can send emails from their new domain without impacting deliverability. An additional IP address is not required if they already have one for their SAP. An additional private domain is not enough to authenticate their sender identity and reputation. Registering the new domain in From Address Management is not necessary if they have an SAP for the new domain. References: https://help.salesforce.com/articleView?id=sf.mc_es_sender_authentication_package.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_from_address_management.htm &type=5

This allows you to specify the exact name of the file when running the automation. The File Drop Starting Source is an automation activity that allows you to specify the source of the File Drop as either a Scheduled or Manual event. This allows you to control when the data is imported from the Enhanced FTP file.

To set up their automation to import the data from the file on a nightly basis, Northern Trail Outfitters should use two ways to start their automation:

• File Drop Starting Source. This is a trigger that starts an automation when a file is dropped in an Enhanced FTP folder or an external SFTP location.
• Scheduled Starting Source. This is a trigger that starts an automation at a specified date and time or at recurring intervals.

%%BASEFILENAME_FROM_TRIGGER%% and %%BASEFILENAME_FROM_FILEDROP%% are not starting sources, but variables that can be used in file transfer or import activities to reference file names. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_automation_studio_triggers.htm &type=5