Salesforce Marketing-Cloud-Consultant Salesforce Certified Marketing Cloud Consultant Exam (SP23) Exam Practice Test

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

A Verification Activity can be used to prevent emails from being sent if they exceed a certain number of contacts. A Verification Activity checks the number of records in a data extension or list and stops the automation if the number is above or below a specified threshold. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_verification_activity.htm &type=5

To capture open-ended feedback from customers via SMS and write it to a data extension, Northern Trail Outfitters should use a text-response message template with embedded AMPscript to capture the response. A text-response message template is a template that allows marketers to send a text message to a mobile number and receive a reply. AMPscript is a scripting language that allows marketers to perform complex tasks within messages, such as inserting data into a data extension. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_text_response.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_ampscript_overview.htm &type=5

To capture and categorize email Not Sent events and insert them into a data extension using Automation Studio, Northern Trail Outfitters should use the following order of activities:

• Data Extract with the Tracking Extract type. This activity will extract tracking data, such as Not Sent events, from Marketing Cloud and place a zipped file in the Safehouse.
• File Transfer from Safehouse. This activity will move the zipped file from the Safehouse to an Enhanced FTP location.
• File Transfer unzip. This activity will unzip the file and place it in an Enhanced FTP location.
• Import File. This activity will import the file into a data extension.

Data Extension Extract is not a valid extract type for tracking data. SQL Query is not an activity that can insert data into a data extension from a file. Data Factory Utility is not a valid activity in Automation Studio. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_data_extract_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_file_transfer_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_import_file_activity.htm &type=5

To make sure the decision splits reflect the correct tent for each customer, Northern Trail Outfitters should use Entry Data as the type of data in the decision splits. Entry Data is the data that is captured at the time of entry into a journey and remains static throughout the journey. Entry Data can include data from data extensions, Salesforce objects, or API events. Using Entry Data will ensure that the decision splits are based on the tent that each customer bought at the time of entry, and not affected by any subsequent purchases or data changes. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_entry_data.htm &type=5

 Import File activity can be used to import the unsub file from the SFTP to a data extension. Query activity can be used to query the data extension and update the status of the subscribers in All Subscribers list to Unsubscribed. Data Extract and File Transfer activities are not needed for this process. References: https://help.salesforce.com/articleView?id=sf.mc_as_import_file_activity.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_as_query_activity.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 options that could be recommended for localizing email content to speak to subscribers in their own language are:

• Leverage AMPscript within an email template to lookup subscriber language and personalize the email based on the value. AMPscript is a scripting language that allows marketers to perform complex tasks within messages, such as looking up data from data extensions, applying conditional logic, or displaying dynamic content based on subscriber attributes or behaviors.
• Leverage enhanced dynamic content blocks within Content Builder to create language-specific emails. Enhanced dynamic content blocks are blocks that allow marketers to create personalized content based on rules and filters without coding.

Leveraging personalization strings within the email template will not help with localization, as they are used for inserting simple subscriber attributes or system information into messages. Leveraging Content Builder to create email templates for each individual language will not be efficient or scalable, as it will require creating and maintaining multiple templates for each message. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_ampscript_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_ceb_enhanced_dynamic_content_blocks.htm &type=5

To provide near real-time data in a 30-day welcome journey, Northern Trail Outfitters should use contact data using synchronized data sources. This will allow them to access the most up-to-date data from their CRM system in decision splits and other journey activities. Journey data is static and based on the entry source data extension, which may not reflect recent changes in CRM. Contact data mapped through profile attributes or imported from CRM reports may not be as timely or accurate as synchronized data sources. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_synchronized_data_sources.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_decision_split.htm &type=5

Publication List and Auto-Suppression List can be used to control what content is available to certain users and business units based on their preferences and send volume. A Publication List allows subscribers to opt in or out of different types of communications, while an Auto-Suppression List automatically excludes subscribers from receiving certain messages based on criteria such as frequency or content category. References: https://help.salesforce.com/articleView?id=sf.mc_es_publication_lists.htm &type=5 https://help.salesforce.com/articleView?id=sf.mc_es_auto_suppression_lists.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

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 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

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 inform NTO’s marketing manager if more than 1,000 records are ever imported through this automation, and prevent the sendable data extension from being updated that day, the consultant should place a Verification Activity between the import and SQL Query activity. A Verification Activity is an activity that allows marketers to verify if certain conditions are met before proceeding with the next activity in an automation. For example, a Verification Activity can check if the number of records in a data extension is above or below a specified threshold, and send an email notification or stop the automation based on the result. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_verification_activity.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

The API user created in Marketing Cloud for Marketing Cloud Connect should have the API User checkbox selected and the Administrator & Marketing Cloud Administrator roles applied. This ensures that the user has access to all features and functions in Marketing Cloud and can perform API calls between Marketing Cloud and Sales Cloud. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_create_a_marketing_cloud_api_user.htm &type=5

To integrate a new dataset with pre-existing contacts, Northern Trail Outfitters should create a new data extension and link it to the other data extension. A data extension is a table that stores data in Marketing Cloud, such as contact information or purchase history. Data extensions can be linked by common fields or attributes using Contact Builder or SQL queries. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_data_extensions.htm &type=5

Two best practices that should be utilized for configuring customer data for long-term cleanliness and maintainability are:

• When using an external database of record, utilize that system’s identifier as the contact key. This will ensure that contacts can be identified and tracked across different channels and platforms using a consistent and persistent value.
• Define the subscriber key as a unique value that does not relate to a specific channel. This will allow contacts to change their email or mobile device without affecting their subscriber key or losing their tracking history.

Configuring Contact Builder to automatically generate a unique subscriber key is not recommended, as it may create duplicate or inconsistent records if contacts already have an identifier in another system. Regularly merging duplicate contacts is not a best practice, but rather a remedial action that should be avoided by using proper data hygiene techniques. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htm &type=5

To send an SMS message and capture the responses in a data extension using AMPscript, Northern Trail Outfitters should use two MobileConnect templates: Text Response and Data Capture. Text Response is a template that allows marketers to send a text message to a mobile number and receive a reply. Data Capture is a template that allows marketers to use AMPscript to insert the reply into a data extension. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_text_response.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_moc_data_capture.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

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

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

The Contact ID field name should be included in the report in addition to email address when using a Send Flow in Content Builder. The Contact ID is a unique identifier for each contact in Sales Cloud and Marketing Cloud. It is required for sending emails to contacts using a Send Flow. The other field names are not required for this purpose. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_send_flow.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_contact_id.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

Three questions that are relevant to determining a solution for automating a process of importing data from a data warehouse into Marketing Cloud are:

• Is the data file a delta or a historical file? This question will help determine how to handle existing records and avoid duplication or overwrite. A delta file contains only new or updated records, while a historical file contains all records regardless of changes.
• Will the data file be placed on the SFTP at the same time daily? This question will help determine how to schedule an automation or trigger an event based on file drop. If the data file is placed on the SFTP at different times, then a File Drop Automation may be more suitable than a Scheduled Automation.
• Does someone need to be notified if an error happens on import? This question will help determine how to handle errors and exceptions during import. If someone needs to be notified, then an email notification activity or a verification activity may be added to the automation.

Whether the data extension has a data relationship or not is not relevant to determining a solution for importing data, as it is only used for creating relationships between data extensions in Email Studio. Whether the file has more than 5,000 rows or not is not relevant to determining a solution for importing data, as it does not affect how data is imported or processed. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_file_drop_automation_studio_triggers.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_import_file_activity.htm &type=5

Creating and enabling a BLOCKOUT window in MobileConnect can be used to prevent SMS messages from being sent during certain hours of the day. A BLOCKOUT window is a time period during which no messages are sent or received by MobileConnect, regardless of when they were scheduled or triggered. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_blockout_window.htm &type=5

Supporting inbound messages in each country would require additional long code implementation for MobileConnect. A long code is a standard phone number that can send and receive SMS messages. Each country has its own regulations and requirements for long codes, so a single long code cannot be used for all markets. The other functionalities do not tie to additional long code implementation. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_long_codes.htm &type=5

Using RMM personalization strings to render the email reply body can be used to include the body of marketing email replies captured by Reply Mail Management (RMM) within auto-forwarded messages to their Customer Success team. RMM personalization strings are variables that can be inserted into auto-forwarded messages to display information from the original reply message, such as subject line, sender address, or reply body. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_reply_mail_management_personalization_strings.htm &type=5

 To integrate Marketing Cloud with their existing point-of-sale system in order to email purchase receipts to their customers, Northern Trail Outfitters should use MuleSoft Anypoint Platform. MuleSoft Anypoint Platform is a tool that allows marketers to connect and integrate different systems and applications using APIs and connectors. MuleSoft Anypoint Platform can help transform and map data between different formats and protocols, such as JSON and SOAP. References: https://www.mulesoft.com/platform/anypoint-platform

 A File Drop Automation can be used to trigger an automation when a file is uploaded to the Marketing Cloud FTP. A SQL Query can be used to segment the audience based on the data inside the file and populate a data extension for each segment. The data extensions can then be used as entry sources for different journeys. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_define_a_triggered_automation.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_query_activity.htm &type=5

MobileConnect Demographics is a data source that is supported to personalize SMS messages. MobileConnect Demographics is a system-generated attribute group that contains information about mobile subscribers, such as phone number, locale, status, keyword, and source. This information can be used to insert personalization strings or AMPscript variables into SMS messages. References: https://help.salesforce.com/s/articleView?id=sf.mc_moc_mobileconnect_demographics.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_moc_personalize_an_sms_message.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 file naming pattern is a setting in the import activity that specifies how to identify the file to import. If the file name changes every time, but has a consistent prefix, the %%BASEFILENAME_FROM_TRIGGER%% variable can be used to match the file name based on the prefix. For example, if the file naming pattern is set to thankyou_customers_%%BASEFILENAME_FROM_TRIGGER%%.csv, it will match any file that starts with thankyou_customers_ and ends with .csv. References: https://help.salesforce.com/articleView?id=sf.mc_as_import_file_naming_conventions.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 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 pull data from the SendLog for troubleshooting based on email address without coding experience, Northern Trail Outfitters should filter data using a Filter Activity on SendLog Data Extension. A Filter Activity is an activity that allows marketers to create filtered data extensions based on criteria and conditions without coding. A SendLog Data Extension is a custom data extension that captures send-time values for each subscriber in an email send. References: https://help.salesforce.com/s/articleView?id=sf.mc_as_filter_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_create_a_sendlog_data_extension.htm &type=5

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

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

This setting allows the consultant to verify the sender's identity and configure the incoming email settings. Reference: https://help.salesforce.com/articleView?id=mc_es_sap_overview.htm &type=5

To redirect its emails to Marketing Cloud servers for processing, Northern Trail Outfitters should use a Sender Authentication Package. A Sender Authentication Package is a feature that allows marketers to authenticate their email sends with their own domain and branding, instead of using Marketing Cloud’s default domain and branding. This will improve email deliverability and reputation, as well as provide more control over email settings and preferences. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm &type=5

Journey Builder can be used to send a weekly coupon campaign with a reminder three days later at the subscribers’ optimized send time. Journey Builder allows users to create cross-channel customer journeys that deliver personalized messages at the right time and on the right channel. Journey Builder can use Einstein Send Time Optimization to determine the optimal time to send an email based on each subscriber’s past engagement behavior. 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_jb_einstein_send_time_optimization.htm &type=5

The subscriber key is a unique identifier for each subscriber in Marketing Cloud. It is used to track subscriber preferences, behaviors, and attributes across channels and business units. If the previous send used email address as a subscriber key, it would not match the subscriber key in Sales Cloud, which is usually the contact or lead ID. Therefore, the email opt out status would not be synchronized between Marketing Cloud and Sales Cloud, and the customer could receive an email through MCC even after unsubscribing from the previous send. References: https://help.salesforce.com/articleView?id=sf.mc_co_subscriber_key.htm &type=5

Two solutions that could pull in the RSS feed at the time of send for Northern Trail Outfitters’ weekly email newsletter are:

• AMPscript. AMPscript is a scripting language that can be used to retrieve and display dynamic content from external sources, such as RSS feeds, in emails.
• External Content. External Content is a feature that allows marketers to create blocks of content from external sources, such as RSS feeds, in Content Builder.

Dynamic Content is not a solution for pulling in RSS feeds, as it is used to display different content based on subscriber attributes or rules. Personalization Strings are not a solution for pulling in RSS feeds, as they are used to display subscriber or account information in emails. References: https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-programmatic-content.meta/mc-programmatic-content/ampscriptUseCasesRetrieveRSSFeed.htm https://help.salesforce.com/s/articleView?id=sf.mc_ceb_external_content_blocks.htm &type=5

To troubleshoot the connection between Sales Cloud and Marketing Cloud, a consultant should start by validating Marketing Cloud and Sales Cloud permissions for the connecting users. The connecting users are the users who authenticated Marketing Cloud Connect in both systems. They need to have certain permissions and roles in both systems to enable full functionality of Marketing Cloud Connect. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_troubleshoot_marketing_cloud_connect_configuration_issues.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