Salesforce Marketing-Cloud-Account-Engagement-Specialist Salesforce Marketing Cloud Account Engagement Specialist (SU24) Exam Practice Test

Dynamic lists are lists that automatically add or remove prospects based on criteria that you define. Prospects can be “unmatched” from a dynamic list if they no longer meet the criteria. For example, if you have a dynamic list of prospects who have opened an email in the last 30 days, and a prospect does not open any email for 31 days, they will be removed from the list. Automation rules and segmentation rules do not “unmatch” prospects, they only apply actions to prospects that match the criteria

 According to the Salesforce documentation, the explanation for why the completion actions did not occur when the client submitted their Marketing Cloud Account Engagement form to test the form’s completion actions is: A) The client has a visitor filter set up to filter activities from their IP address. Completion actions do not occur on filtered visitors. A visitor filter is a feature that allows users to exclude certain visitors from being tracked and reported in Marketing Cloud Account Engagement. A visitor filter can be based on IP address, location, or domain. A visitor filter can help users to avoid tracking their own activities or those of their competitors. A completion action is an automation tool that can be used to perform an action after a prospect successfully completes a marketing element, such as submitting a form, clicking a link, or visiting a web page. A completion action can be used to perform actions such as adding a prospect to a list, assigning a prospect to a user, sending an autoresponder email, or adjusting a prospect’s score. However, completion actions do not occur on filtered visitors, as they are not tracked or reported in Marketing Cloud Account Engagement. Therefore, if the client has a visitor filter set up to filter activities from their IP address, the completion actions will not occur when they submit the form. The ‘email’ form field being set up to exclude free email addresses, the client not un-pausing the completion actions, or kiosk mode being enabled on the form are not the explanations for why the completion actions did not occur when the client submitted their Marketing Cloud Account Engagement form to test the form’s completion actions, as they are either irrelevant, incorrect, or nonexistent options for the form or the completion actions. References: Salesforce documentation

When investigating an odd field value on a prospect's record in Pardot, the first course of action should be to view the prospect's Audit tab. This tab provides a comprehensive log of all changes made to the prospect’s record, including information on what changes were made, who made them, and when they were made. This approach allows users to quickly ascertain the source of the odd field value, whether it was updated through a form submission, manually edited by another user, or changed through some other process. It is a more direct and reliable method than contacting assigned users or reviewing individual form submissions, which may not conclusively reveal the origins of the specific change.

The way that a visitor can convert to a prospect is by submitting a Marketing Cloud Account Engagement form. A visitor is an anonymous person who visits a website that has Marketing Cloud Account Engagement tracking code installed. A visitor can be identified by their IP address, location, browser, device, and pages viewed. A visitor can also be tracked by Marketing Cloud Account Engagement cookies if they have visited the website before. A visitor can convert to a prospect when they provide their email address to Marketing Cloud Account Engagement through a form, a form handler, a landing page, or a custom redirect. A prospect is a known person who has a record in Marketing Cloud Account Engagement and can be associated with a lead or a contact in Salesforce. A prospect can be tracked by their email address, activities, score, grade, and other fields. A prospect can also be segmented, nurtured, and qualified by Marketing Cloud Account Engagement5. Option A is not correct because downloading an eBook does not necessarily convert

The prospect’s Audits tab shows the history of changes made to the prospect’s record, such as field updates, list changes, and assignment dates. These data points can help determine what updates were made during the database clean-up project and how they affected the prospects. The Lifecycle Report, the amount of time the prospect spent viewing the website, and the unique clicks are not data points that can be found in the Audits tab, but they can be found in other reports or tabs in Marketing Cloud Account Engagement. References Prospect Audits

According to the Salesforce documentation, the two Marketing Cloud Account Engagement form actions that would accomplish enabling bot protection on their forms are honeypot technique and reCaptcha. Bot protection is a feature that helps prevent automated bots from submitting forms and creating fake prospects. Honeypot technique is a method that uses a hidden field in the form that is not visible to human users, but can be detected by bots. If the hidden field is filled out, the form submission is rejected as a bot submission. reCaptcha is a service that uses a challenge-response test to verify that the form submitter is a human and not a bot. The user can enable either or both of these options in the form settings to add bot protection to their forms. Enabling HTTPS, or Hypertext Transfer Protocol Secure, is a method that encrypts the communication between the user’s browser and the web server, but it does not prevent bots from submitting forms. Dependent fields are fields that are displayed or hidden based on the value of another field, but they do not prevent bots from submitting forms either. References: Salesforce documentation

 According to the Salesforce documentation, the information that the tooltip above each step on the engagement studio program report provides is high-level metrics only for prospects who have completed the step. An engagement studio program report is a report that shows the performance and results of an engagement program, such as the number of prospects, emails, and conversions. The tooltip above each step on the program report shows the number and percentage of prospects who have completed that step, as well as the number and percentage of prospects who have taken the positive, negative, or neutral path after that step. The tooltip does not show the metrics for prospects who are waiting to complete, who have left, or who have skipped each step, as these are shown in other sections of the report. References: Salesforce documentation

An autoresponder is a type of email that is automatically sent to a prospect when they perform a specific action, such as filling out a form, downloading a file, or registering for an event. To send an autoresponder, a marketer must create an email template using the classic email builder in Marketing Cloud Account Engagement. An email template is a reusable email design that can be customized with dynamic content and personalization. A test email, a one-to-one email, and a list email are not suitable for sending an autoresponder, as they are either not reusable, not automated, or not personalized. References: : Create an Autoresponder Email

According to the Salesforce documentation, the actions that can be done with the gear icon on the prospect list are: B) Assign, C) Delete, and D) Edit. The gear icon is a feature that allows users to perform different actions on a prospect or a group of prospects from the Prospect List. The gear icon can be accessed from the Prospects tab in Marketing Cloud Account Engagement, and it can show different options for the selected prospect or prospects, such as assign, delete, or edit. The assign option allows the user to assign the prospect or prospects to a user, a group, or a queue. The delete option allows the user to delete the prospect or prospects from Marketing Cloud Account Engagement. The edit option allows the user to edit the prospect or prospects’ information, such as name, email, or custom fields. The copy option is not an action that can be done with the gear icon on the prospect list, as it is not an available option for the prospect or prospects. References: Salesforce documentation

The key difference between an email template and an email content record in the enhanced email experience within Pardot lies in their usability across different Salesforce platforms. An email template, once created in Pardot, can be utilized by users across Pardot, Sales Cloud, and Service Cloud. This allows for a consistent messaging and branding experience across various customer-facing platforms within the Salesforce ecosystem. In contrast, an email content record in Pardot is specific to Pardot and designed for use within the platform's email marketing campaigns, focusing on specific layouts and elements tailored to Pardot's capabilities.

 The metrics in the list email report that could help the Account Engagement user understand how these prospects may have become unmailable are Total Opt Outs and Hard Bounces (D). These metrics show the number and percentage of prospects who either opted out of receiving future emails or had their emails bounced back due to a permanent error, such as an invalid email address. These prospects are marked as Do Not Email and cannot be emailed again unless they opt back in. The other metrics (A, B, C) are not directly related to the prospects’ mailable status, but rather to the email delivery, performance, and tracking. References: List Email Report Metrics

All of the above options could cause standard sync actions from occurring. A large sync queue means that there are many prospects waiting to be synced between Marketing Cloud Account Engagement and Salesforce, which could delay or prevent the sync process. A connector that is not verified or has become unverified means that the authentication between Marketing Cloud Account Engagement and Salesforce has failed, which could interrupt the sync process. A Salesforce API limit that has been reached means that the number of API calls that Salesforce allows per day has been exceeded, which could stop the sync process34 References: 3: Salesforce Marketing Cloud Account Engagement Consultant Certification Flashcards4: Salesforce Certified Marketing Cloud Account Engagement Consultant Exam Flashcards

A form handler setting that allows prospects to receive multiple autoresponders from form submissions within a 24-hour period is Disable Visitor Activity Throttling and send autoresponder emails after every submission. This setting overrides the default behavior of Marketing Cloud Account Engagement, which is to throttle visitor activity and send only one autoresponder email per prospect per form per day2. This setting can be useful for forms that are used for multiple purposes, such as event registration, content download, or contact request

The preview matches feature in Pardot's automation rule setup is an essential tool for ensuring that the criteria set for a rule accurately targets the intended prospects. Before activating the rule, this feature allows the administrator to verify which prospects currently match the specified criteria without affecting the database or running the rule prematurely. This method is effective for refining and confirming criteria to avoid unintended targeting and to refine the selection process.

The fastest way for an Administrator to create a one-time list of prospects who match specific criteria is to use a segmentation rule. A segmentation rule is a rule that runs once and matches prospects based on the criteria you set. You can use a segmentation rule to perform actions on the matched prospects, such as adding them to a list, assigning them to a user, or changing their field values. A segmentation rule is useful when you want to segment your prospects quickly and easily without creating a dynamic list or an automation rule

 The reason why the reporting metrics of Email Template A are not changing as a result of the new list email send is that the metrics would be attributed to Email Template B. When a user creates a copy of an email template, makes changes and saves it as a new email template, the new email template becomes a separate entity from the original email template. The new email template has its own name, ID, and reporting metrics. The reporting metrics of an email template include the number of sends, total opens, unique opens, total clicks, unique clicks, opt-outs, and spam complaints. These metrics are calculated based on the emails that use the email template. Therefore, when the user sends a list email using Email Template B, the reporting metrics of Email Template B are updated, but the reporting metrics of Email Template A are not affected1. Option A is not correct because an email template’s metrics do change after the template is used one time. An email template’s metrics are updated every time an email that uses the template is sent, opened, clicked, opted out, or marked as spam1. Option B is not correct because Email Template A should not have been deleted after creating the copy. Deleting an email template does not affect the reporting metrics of the template or the emails that use the template. Deleting an email template only prevents the template from being used for new emails1. Option D is not correct because the user should not have made Email Template A the primary template. There is no concept of a primary template in Marketing Cloud Account Engagement. Each email template is independent and can be used for different types of emails. Making Email Template A the primary template would not change the reporting metrics of the template or the emails that use the template

According to the Salesforce documentation, the user should resolve the issue of not being able to choose the specific email template when sending a new list email by editing the email template to make it available for “List Emails”. An email template is a reusable design that defines the content and layout of an email. An email template can be configured to be available for different types of email sends, such as one-to-one emails, list emails, or autoresponders. A list email is an email that is sent to a specific list of prospects, such as a newsletter or a promotion. To use an email template for a list email, the user must edit the email template and check the box for “List Emails” in the email template settings. This will make the email template available to choose when sending a new list email. Editing the list to be available for “Email Sending”, “Email Templates”, or editing the email template and choosing the appropriate list are not the correct ways to resolve the issue of not being able to choose the specific email template when sending a new list email, as they are either irrelevant or incorrect options for the list or the email template settings. References: Salesforce documentation

According to the Salesforce documentation, the answer is true. Administrators can reset passwords for users. An administrator is a user who has the highest level of permissions and access in Marketing Cloud Account Engagement, and who can create and manage other users, roles, and settings. An administrator can reset passwords for users in the Admin tab in Marketing Cloud Account Engagement, and they can use different methods, such as:

• Reset password for a single user: An administrator can reset the password for a single user by accessing the user record in the User List, and clicking on the Reset Password button. The administrator can then enter a new password for the user, or generate a random password. The administrator can also choose to send an email notification to the user with the new password.
• Reset password for multiple users: An administrator can reset the password for multiple users by selecting the users from the User List, and clicking on the Reset Password option in the table actions. The administrator can then enter a new password for the users, or generate a random password. The administrator can also choose to send an email notification to the users with the new password.

References: Salesforce documentation

According to the Salesforce documentation, a prospect’s score can be changed through automation rules, scoring model changes, or completion actions. A prospect’s score is a numerical value that indicates the level of interest and engagement of a prospect, based on their activities, such as opening an email, clicking a link, or submitting a form. A prospect’s score can be changed by using different methods, such as:

• Automation rules: An automation rule is an automation tool that can be used to update a prospect’s score when the prospect meets certain criteria, such as prospect field values, activities, or scores. For example, an automation rule can be created to increase a prospect’s score by 10 points when the prospect visits a specific web page.
• Scoring model changes: A scoring model is a feature that allows users to customize the scoring rules for different types of activities, such as email opens, form submissions, or custom redirects. A scoring model can be changed by editing the default scoring model in Marketing Cloud Account Engagement, or by creating a custom scoring model for a specific group of prospects. For example, a scoring model can be changed to assign more points to an email open, or to create a different scoring model for prospects from a certain industry.
• Completion actions: A completion action is an automation tool that can be used to adjust a prospect’s score after the prospect successfully completes a marketing element, such as submitting a form, clicking a link, or visiting a web page. A completion action can be used to increase or decrease a prospect’s score by a specific amount, or to reset a prospect’s score to zero. For example, a completion action can be created to decrease a prospect’s score by 5 points when the prospect unsubscribes from an email.

References: Salesforce documentation

The correct way to use a custom account field in Salesforce for segmentation in Marketing Cloud Account Engagement is to create a custom account field in Marketing Cloud Account Engagement and map it to the account field in Salesforce. This will allow you to sync the data between the two systems and use the custom field as a segmentation criterion in Marketing Cloud Account Engagement. You can create a custom account field in Marketing Cloud Account Engagement by going to Settings > Object and Field Configuration > Prospect Account Fields > Add Custom Field. Then, you can map it to the corresponding account field in Salesforce by selecting it from the drop-down menu

The only required field for a record in Salesforce to be synced or created as a prospect record in Marketing Cloud Account Engagement is the email address. Marketing Cloud Account Engagement uses the email address as the unique identifier for prospects, so it is mandatory for any record to sync between the two platforms. Other fields, such as name, company, or phone, are optional and can be mapped between Marketing Cloud Account Engagement and Salesforce, but they are not required for the sync to happen. For more details —> 123

The way the marketer can satisfy the request to permanently delete a prospect from Marketing Cloud Account Engagement is by archiving the prospect and then selecting “Permanently Delete” from the recycle bin. Archiving a prospect removes them from the active prospect database and places them in the recycle bin, where they can be restored or permanently deleted. Permanently deleting a prospect removes them from Marketing Cloud Account Engagement and Salesforce completely and cannot be undone. The marketer cannot archive the prospect without permanently deleting their data, as the archived prospects still count towards the database limit and can be restored. The marketer cannot delete the prospect in Salesforce, as this will only archive the prospect in Marketing Cloud Account Engagement, not permanently delete them. The marketer cannot go to the prospect record and choose the “Permanently Delete” menu option, as this option is not available on the prospect record, only on the recycle bin. References Deleting Prospects

By default, if the information in Salesforce differs from the information in Marketing Cloud Account Engagement, the information in Salesforce will override the information in Marketing Cloud Account Engagement. This means that Salesforce is the master source of truth for most fields, and any changes made in Salesforce will overwrite the values in Marketing Cloud Account Engagement. However, this behavior can be customized for each field in Marketing Cloud Account Engagement, by choosing one of the following options: Use Marketing Cloud Account Engagement’s value, Use Salesforce’s value, or Use the most recently updated record. You can also prevent a field from syncing at all by choosing Do not sync. For more details —> 45

Completion actions are actions that Marketing Cloud Account Engagement executes after a prospect successfully completes a desired activity, such as submitting a form or clicking a custom link. Completion actions only affect prospects, not visitors, because visitors are anonymous and have not been identified by Marketing Cloud Account Engagement yet

To troubleshoot why a prospect did not receive an email from a drip program, an Administrator should check the following tabs in Marketing Cloud Account Engagement:

• The Audits tab to see if the prospect was on the correct lists when the email was sent. This tab shows the list membership changes and email sends for the prospect.
• The Overview tab to determine whether the prospect is unmailable. This tab shows the prospect’s email status, which could be opt-out, hard bounce, or do not email.
• The Lists tab to determine whether the prospect is on the recipient list or any suppression lists. This tab shows the lists that the prospect belongs to, including any lists that are used to exclude prospects from receiving emails. References: Marketing Cloud Account Engagement Audits Tab, Marketing Cloud Account Engagement Email Statuses, Marketing Cloud Account Engagement Lists

The best way to understand how many prospects are currently waiting on a step in an engagement program is to look at the tooltip above that step. The tooltip will show you the number of prospects that are currently on that step, as well as the number of prospects that have completed that step. You can also see the percentage of prospects that have taken a specific action or followed a specific path from that step. The tooltip is a quick and easy way to get an overview of the performance of each step in your program

The two activities that trigger a prospect record to sync from Marketing Cloud Account Engagement to the CRM are landing page submission and form submission. A prospect record is a record that contains the information and activities of a potential customer in Marketing Cloud Account Engagement. A sync is a process that updates the data between Marketing Cloud Account Engagement and your CRM system, such as Salesforce or Microsoft Dynamics. A sync can be initiated from Marketing Cloud Account Engagement to the CRM, or from the CRM to Marketing Cloud Account Engagement, depending on the activity or the data change. A landing page submission is an activity that occurs when a prospect fills out a form on a landing page, which is a web page that you create and host in Marketing Cloud Account Engagement to showcase your products or services, offer content, or register for events. A form submission is an activity that occurs when a prospect fills out a form, which is a web element that allows you to collect information from your prospects, such as their name, email, or company. Both landing page submission and form submission trigger a prospect record to sync from Marketing Cloud Account Engagement to the CRM, because they create or update the prospect data in Marketing Cloud Account Engagement, and Marketing Cloud Account Engagement pushes the data to the CRM

 If a Marketing Cloud Account Engagement administrator wants to know how many unique submissions they have for a form on a landing page, they should check the landing page report. The landing page report shows the performance metrics of a landing page, such as views, submissions, conversion rate, and cost per submission. The landing page report also shows the number of unique submissions, which is the number of prospects who submitted the form for the first time. The landing page report can be accessed from the landing page table or from the landing page details page6. References: Marketing Cloud Account Engagement Landing Page Reports

 According to the [Salesforce documentation], in order to set up an automated grading model in Marketing Cloud Account Engagement, two components are required: profile and automation rule. A profile is a set of criteria that defines an ideal prospect for a specific product or service. A profile can include information such as industry, job title, location, company size, etc. An automation rule is a logic-based action that can be triggered when a prospect meets certain criteria. An automation rule can be used to assign a grade to a prospect based on their profile match. A Marketing Cloud Account Engagement score is a numerical value that indicates the level of interest and engagement of a prospect, but it is not required for setting up an automated grading model. A dynamic list is a list of prospects that is updated automatically based on certain criteria, but it is not required for setting up an automated grading model either. References: [Salesforce documentation]

Marketing Cloud Account Engagement forms are the best option if you need data de-duplication in the CRM, such as Salesforce. Marketing Cloud Account Engagement forms can automatically match and update existing records in the CRM based on the email address or other unique identifiers4. Marketing Cloud Account Engagement forms can also create new records in the CRM if the prospect does not exist yet4. Form handlers, on the other hand, do not have this functionality, and may create duplicate records in the CRM if the prospect already exists

By default, Marketing Cloud Account Engagement writes to two objects in Salesforce: contact records and lead records. These are the two objects that store information about individual prospects in Salesforce. Marketing Cloud Account Engagement syncs with these objects based on the email address field, which is the unique identifier for prospects. Marketing Cloud Account Engagement can create new contact or lead records in Salesforce, or update existing ones, depending on the sync settings and rules. Marketing Cloud Account Engagement does not write to case records, opportunity records, or account records by default, but it can read from them and use their information for segmentation and reporting purposes. References Marketing Cloud Account Engagement and Salesforce Sync Behavior

 An engagement studio program is a tool that allows the Marketing Manager to create and automate a series of steps that guide prospects through a marketing journey. An engagement studio program consists of three types of elements: actions, triggers, and rules. An action is something that the program does to or for the prospect, such as sending an email, adding them to a list, or notifying a user. A trigger is something that the program checks for or waits for the prospect to do, such as opening an email, clicking a link, or submitting a form. A rule is something that the program evaluates about the prospect, such as their score, grade, or field value8

Among the possible actions that can be taken in an engagement studio program, three of them are:

• Add prospect to list. This action adds the prospect to a specified list in Account Engagement. This action is useful for segmenting prospects based on their engagement or moving them to a different list for further marketing8
• Send email to prospect. This action sends an email to the prospect using an Account Engagement email template. This action is useful for delivering relevant and personalized content to the prospect based on their stage in the journey8
• Notify a user. This action sends an email notification to a specified user or user group in Account Engagement or Salesforce. This action is useful for alerting the sales team or other stakeholders about the prospect’s engagement or readiness

According to the Salesforce documentation, the answer is true. You can see the score, grade, assigned user and recent interaction within the Insight section of the Prospect Record. The Insight section is a feature that shows the key information and metrics of a prospect in Marketing Cloud Account Engagement. The Insight section can be accessed from the Prospects tab in Marketing Cloud Account Engagement, and it can show different data for the prospect, such as score, grade, assigned user, or recent interaction. The score is a numerical value that indicates the level of interest and engagement of a prospect, based on their activities, such as opening an email, clicking a link, or submitting a form. The grade is a letter value that indicates the level of fit of a prospect, based on their attributes, such as industry, job title, location, or company size. The assigned user is the user who is responsible for the prospect, and who can view and edit the prospect’s information. The recent interaction is the latest action or event that the prospect has performed or received, such as opening an email, clicking a link, or registering for a webinar. The Insight section can help users to quickly and easily view the most important information and metrics of a prospect, and to take actions based on the data. References: Salesforce documentation

The user role that a Marketing Cloud Account Engagement user must have in order to verify the Salesforce connector is Administrator. A Salesforce connector is a feature that allows you to connect your Marketing Cloud Account Engagement account with your Salesforce CRM system, and enable bi-directional data sync and alignment between sales and marketing. To verify the Salesforce connector, you need to have the Administrator user role in Marketing Cloud Account Engagement, which gives you full access to all features and settings in Marketing Cloud Account Engagement, including the connectors. You also need to have the appropriate permissions in Salesforce, such as the API Enabled and Modify All Data permissions

When a user creates and resumes a new automation rule, the rule will continuously look for prospects who match the criteria (B) and evaluate their entire prospect database for matches ©. These are the characteristics of automation rules in Account Engagement, which are different from segmentation rules that run only once. The rule will not run once and must be re-run for prospects to match again (A), nor will it unmatch prospects that no longer match the criteria (D). Unmatching prospects is only possible with dynamic lists, not automation rules. References: Using Account Engagement Automation Rules vs. Salesforce Flows

According to the Salesforce documentation, the two prospect activities that trigger a sync from Marketing Cloud Account Engagement to Salesforce are: A) Submitting a form, and B) Opening an email. A form submission is an activity that occurs when a prospect fills out and submits a Marketing Cloud Account Engagement form or a form handler. An email open is an activity that occurs when a prospect opens an email sent from Marketing Cloud Account Engagement. These two activities will trigger a sync from Marketing Cloud Account Engagement to Salesforce, meaning that the prospect’s information and activity data will be updated in Salesforce. A sync from Marketing Cloud Account Engagement to Salesforce happens when a prospect is created or updated in Marketing Cloud Account Engagement, or when a prospect performs a significant activity in Marketing Cloud Account Engagement. Clicking a custom redirect or unsubscribing from email are not activities that trigger a sync from Marketing Cloud Account Engagement to Salesforce, as they are not considered significant activities in Marketing Cloud Account Engagement. A custom redirect is a trackable URL that can be used to measure and report on the clicks of any online content. An unsubscribe is an action that occurs when a prospect opts out of receiving emails from the sender. These two activities will not trigger a sync from Marketing Cloud Account Engagement to Salesforce, unless they are combined with other activities that do trigger a sync, such as submitting a form or opening an email. References: Salesforce documentation

 If a LenoxSoft marketer selects the option “Redirect the prospect instead of showing the form’s Thank You Content” when creating a new Account Engagement landing page, the expected behavior when a prospect submits a form designed to show Thank you Content is that the prospect will be redirected to another webpage ©. This option overrides the form’s Thank you Content and sends the prospect to the specified URL instead. The prospect will not continue to see the form upon submission (A), nor will the discrepancy between the two assets cause an error (B). The form’s Thank you Content will not display (D), as it is replaced by the redirect option. References: Redirect Account Engagement Forms to a Success Page

The [[crm_deleted]] flag is a system field that indicates whether a prospect record has been deleted in Salesforce. The only action that removes this flag from a prospect record is undeleting the record in Salesforce. Re-submitting a form by a prospect, unchecking “CRM Deleted” on the prospect record, or removing the prospect from the Marketing Cloud Account Engagement recycle bin will not remove the flag, as the prospect will still be deleted in Salesforce2. References: 2: [System Fields]

In order to have both a Lead and a Contact field sync with the same Marketing Cloud Account Engagement prospect field, two requirements must be met. They are:

• The Lead and Contact fields must have the same API name. The API name is the unique identifier of a field in Salesforce, and it must match exactly between the Lead and Contact objects. For example, if the Lead field has an API name of Lead_Source__c, the Contact field must also have the same API name4
• The Marketing Cloud Account Engagement field must be mapped to the Salesforce field. The mapping is the connection between the fields in Account Engagement and Salesforce, and it allows the data to sync between the two systems. The mapping can be done manually or automatically, depending on the field type and the connector version

 Marketing Cloud Account Engagement can sync with Salesforce custom fields that are on the Lead, Contact, or Account objects. Custom Prospect fields in Marketing Cloud Account Engagement can be mapped to custom Lead or Contact fields in Salesforce. Custom Account fields in Marketing Cloud Account Engagement can be mapped to custom Account fields in Salesforce. Custom Opportunity fields in Marketing Cloud Account Engagement can be mapped to custom Opportunity fields in Salesforce. Custom Record Type fields are not supported by Marketing Cloud Account Engagement and cannot be synced

 Drip programs are automated email campaigns that send a series of messages to prospects based on predefined criteria and triggers. If a prospect is removed from a drip program, they will stop receiving any emails from that program. However, if they are added back to the same drip program, they will resume the drip where they left off, unless the drip program has been reset or modified. References: [Drip Programs], [Add Prospects to Drip Programs]

 The feature that the Marketing Cloud Account Engagement administrator should use to gather a prospect’s company name and job title, but only once they have captured the prospect’s first name, last name, and email address in a previous form submission, is progressive profiling. Progressive profiling is a feature that allows the administrator to display different fields on a form based on the information that the prospect has already provided. This way, the administrator can avoid asking the same questions repeatedly and collect more information gradually. Progressive profiling can be enabled on a form by selecting the option “Always display even if previously completed” for the fields that are required, such as first name, last name, and email address, and selecting the option “Only display if progressive profiling is enabled and the field is blank” for the fields that are optional, such as company name and job title. This way, the form will only show the optional fields once the required fields are filled out. Always display even if previously completed, reCaptcha, and dependent fields are not features that can achieve the same goal as progressive profiling. Always display even if previously completed is an option that can be used to enable progressive profiling, but it is not a feature by itself. reCaptcha is a feature that can be used to prevent spam submissions on a form, but it does not affect the fields that are displayed on the form. Dependent fields are fields that are displayed or hidden based on the value of another field, but they do not depend on whether the prospect has already provided the information or not. References Progressive Profiling

The best way to configure a thank you email to be sent after the form on the “Request a Demo” landing page is submitted is to configure an autoresponder email to send as a completion action when the “Request a Demo” form has been submitted. An autoresponder email is an email that is automatically sent to a prospect after they complete a desired activity, such as submitting a form or clicking a custom link. You can use autoresponder emails to thank your prospects, confirm their actions, or provide them with additional information or content. A completion action is an action that Marketing Cloud Account Engagement executes after a prospect successfully completes a desired activity, such as submitting a form or clicking a custom link. You can use completion actions to perform actions on the prospects who complete the activity, such as adding them to a list, assigning them to a user, or changing their field values. To configure an autoresponder email to send as a completion action when the “Request a Demo” form has been submitted, you need to go to Marketing > Forms > Forms > Request a Demo > Completion Actions > Add New Action > Send Autoresponder Email, and select the email that you want to send. 

The HML merge field that should be included in an email to allow prospects to manage their email preferences is {{OptOut}} or {{EmailPreferenceCenter}}. The {{OptOut}} merge field inserts a link that allows prospects to opt out of receiving emails from the sender. The {{EmailPreferenceCenter}} merge field inserts a link that allows prospects to choose which types of emails they want to receive from the sender. The {{Unsubscribe}} merge field is not valid in HML, as it is only used in PML. The {{ReportSpam}} merge field is not recommended, as it can negatively affect the sender’s reputation. The {{Opt_Out}} merge field is not valid in HML, as it uses an underscore instead of a camel case1. References: 1: HML Merge Fields

The two events that allow for a prospect’s Marketing Cloud Account Engagement campaign to be set are:

• When new prospects are imported into Marketing Cloud Account Engagement via a .csv file. A Marketing Cloud Account Engagement campaign is a marketing initiative that you use to track the first touch point with your prospects, such as a trade show, a webinar, or a Google Ad. You can assign a Marketing Cloud Account Engagement campaign to your prospects when you import them into Marketing Cloud Account Engagement via a .csv file, which is a file that contains the prospect data in a comma-separated format. You can use the Marketing Cloud Account Engagement campaign field in the .csv file to specify the campaign that you want to associate with the prospects, or you can use the default campaign that you select when you upload the file4.
• When the Google Analytics connector is enabled within Marketing Cloud Account Engagement, which will associate prospects with third-party campaigns. The Google Analytics connector is a feature that allows you to connect your Marketing Cloud Account Engagement account with your Google Analytics account, and sync the campaign data between them. You can use the Google Analytics connector to append UTM parameters to your Marketing Cloud Account Engagement tracked links, and associate prospects with third-party campaigns, such as Google Ads, Facebook Ads, or Twitter Ads. UTM parameters are tags that you can add to the end of a URL to track the source, medium, campaign, term, and content of your web traffic. When a prospect clicks on a Marketing Cloud Account Engagement tracked link that contains UTM parameters, Marketing Cloud Account Engagement will set the prospect’s Marketing Cloud Account Engagement campaign to the value of the utm_campaign parameter, if it exists. 

 A prospect’s first touch campaign is the campaign that is associated with the prospect when they are created in Marketing Cloud Account Engagement. This campaign can be set using completion actions, which are actions that Marketing Cloud Account Engagement executes after a prospect successfully completes a desired activity, such as submitting a form or clicking a custom link1. Completion actions can be configured to change the prospect’s campaign to the one that is associated with the form or custom link

The recommended way to create this type of list is to use an automation rule where prospects who complete the form will match the rule once and be added to the list. An automation rule is a rule that runs continuously in the background and matches prospects based on the criteria you set. You can use an automation rule to perform actions on the matched prospects, such as adding them to a list, assigning them to a user, or changing their field values. However, an automation rule can only match a prospect once in its lifetime, even if the prospect meets the criteria again later. This prevents duplicate or conflicting actions from being applied to the same prospect3. Therefore, an automation rule is ideal for creating a list of prospects who complete the Contact Us form but only want them to be added the first time they complete the form. If a prospect is ever removed from the list, they will not be able to get added back to it, because they will not match the automation rule again.

The best way to accomplish the goal of sending the same email template again this week to the same list, but make sure that the prospects that received it last week do not get it again, is to create a new list of the prospects that received the email last week and then use it as a suppression list when sending the email template to the “Hot Prospects” list ©. This way, the prospects who already received the email will be excluded from the recipient list, and only the new prospects who match the dynamic criteria will receive the email. Creating a new dynamic list using the criteria “Prospect email template”, the template name, and “was not received” (A) is not a valid option, as there is no such criteria available for dynamic lists. Sending the email template to the “Hot Prospects” list, but selecting the “deduplicate” option (B) is not a valid option, as the deduplicate option only removes duplicate prospects within the same list, not across different lists. Sending the email template to the “Hot Prospects” list like last time (D) is not a valid option, as the prospects that received it before will not be automatically suppressed from receiving the same email template, unless the email template has the option “Do not send to prospects who have already received this email” enabled. References: Create a Dynamic List, Send a List Email

The best way to run an A/B test in Marketing Cloud Account Engagement is to set up an A/B test that automatically sends the two versions to a single list and then determines a winner based on clicks or opens. This way, you can compare the performance of the two versions on the same audience and avoid any bias or timing issues that might affect the results. Option A is not a good way to run an A/B test because sending the same list two different emails at different times might skew the results due to factors such as email fatigue, inbox clutter, or changing preferences. Option B is not a good way to run an A/B test because event signups might not be the best metric to measure the effectiveness of an email, especially if the event is not directly related to the email content or offer. Option C is not a good way to run an A/B test because sending the two versions to two different lists might introduce variability in the results due to differences in the list composition, quality, or behavior. References: How to Run an A/B Test in Marketing Cloud Account Engagement: A Step by Step Guide (2022), The Basics of A/B Testing in Marketing Cloud Account Engagement - The Spot

 A trigger step is a type of step in an Engagement Studio program that allows marketers to check whether a prospect has completed a specific activity, such as submitting a form, clicking a link, or opening an email. The trigger step that a user would place in an Engagement Studio program to look for a Marketing Cloud Account Engagement form submission that is on an Account Engagement landing page is a landing page trigger. A landing page trigger checks whether a prospect has viewed or submitted a landing page that is hosted by Marketing Cloud Account Engagement. A custom redirect trigger, a form trigger, or an activity trigger are not suitable for looking for a Marketing Cloud Account Engagement form submission that is on an Account Engagement landing page, as they either check for different types of activities, or require a different type of form or landing page3. References: 3: Engagement Studio Triggers

The two list types that could be used as a recipient list on a list email send are static list and dynamic list. A static list is a list of prospects that can be manually added or removed, or updated by automation tools. A static list does not change unless the user or the automation tool modifies it13. A dynamic list is a list of prospects that automatically updates based on the criteria that the user defines. A dynamic list adds or removes prospects who match or do not match the criteria in real time14. Both static and dynamic lists can be used to segment prospects and send targeted email campaigns to them15. The other list types, such as archived list, test list, public list, and CRM visible list, are not suitable for sending list emails, as they have different purposes and limitations

An automation rule is a criteria-based action that is triggered when a prospect matches the rule. By default, an automation rule will only affect a prospect one time, unless you enable the Repeat Rule option. If you enable the Repeat Rule option, the automation rule can match a prospect more than once, as long as they meet the criteria each time. Automation rules do not run every time, since they are evaluated based on a schedule that you can set. References: [Automation Rules], [Repeat Automation Rules]

A good bounce rate is less than 10%. Bounce rate is the percentage of visitors who leave a website after viewing only one page. It indicates how frequently users visit your site without interacting or exploring further. A high bounce rate may indicate that your content is unsatisfactory or poorly optimized. A low bounce rate may indicate that your content is engaging or useful. However, bounce rate can also vary depending on the industry, page type, and traffic source. For example, a blog may have a higher bounce rate than an ecommerce site, because users may only read one article and then leave. Similarly, a landing page may have a lower bounce rate than a home page, because users may be more likely to click on a call-to-action. Therefore, it is important to compare your bounce rate with industry benchmarks, page types, and traffic sources. As a general rule, a good bounce rate is around 40% or lower, while a bounce rate of 60% or higher may be an indication that you need to evaluate your page content and make it more helpful and engaging for users. For more details —> 14151617

The prospects that will process through the new step once the program is started again are all prospects new to the program. When a user edits a running and non-repeating engagement studio program by pausing it and adding a new Send Email step at the beginning of the program, the new step will apply only to the prospects who enter the program after the program is resumed. The prospects who are already in the program will not go back to the new step, but will continue from their current position in the program. This is because a non-repeating engagement studio program allows prospects to go through the program only once and does not allow them to repeat any steps or actions. Therefore, the new step will not affect the prospects who have already processed through the program7. Option A is not correct because not all prospects on the recipient list will process through the new step once the program is started again. The recipient list is the list of prospects who are eligible to enter the program. However, some of the prospects on the recipient list might have already entered and completed the program before the new step was added. Those prospects will not process through the new step, as they have already exited the program7. Option B is not correct because not all prospects in the program will process through the new step once the program is started again. The prospects in the program are the prospects who have entered the program and are either active or paused in the program. However, some of the prospects in the program might have already passed the position where the new step was added. Those prospects will not process through the new step, as they have already moved forward in the program7. Option D is not correct because none of the prospects on the suppression list will process through the new step once the program is started again. The suppression list is the list of prospects who are excluded from entering the program. The suppression list can be used to prevent prospects who are already customers, competitors, or partners from receiving marketing emails. The prospects on the suppression list will never enter or process through the program, regardless of the new step

There are three ways the Marketing Manager can create a new prospect in Marketing Cloud Account Engagement. They are:

• Click the “Send to Account Engagement” button on a Salesforce Lead. This option allows the Marketing Manager to send a one-to-one email to a lead in Salesforce using an Account Engagement email template. If the lead does not already exist as a prospect in Account Engagement, it will be created automatically and synced with Salesforce1
• Manually add a prospect in Marketing Cloud Account Engagement. This option allows the Marketing Manager to create a new prospect record in Account Engagement by entering the prospect’s email address and other information. The prospect can then be added to lists, campaigns, or engagement programs2
• Import a .CSV file with the prospect’s email address. This option allows the Marketing Manager to import a list of prospects from a .CSV file into Account Engagement. The file must contain the prospect’s email address as the first column, and can also include other fields. The imported prospects can then be assigned, tagged, or added to lists or campaigns

 A CNAME or vanity alias is used to provide a seamless transition for your prospects when visiting pages and forms that you host on your site and Marketing Cloud Account Engagement hosted campaign elements such as landing pages, search results and individually tracked links sent in your emails. This is true because a CNAME allows you to use your own domain name instead of the default go.Marketing Cloud Account Engagement.com domain name, which enhances your branding and trustworthiness.

To see why the email was not sent to the prospect, the marketing manager should refer to the list email send report to see if a suppression list was used. A suppression list is a list of prospects who should not receive a specific email, even if they are on the recipient list. If the prospect was on a suppression list, they would not receive the email. The other options are not likely to explain why the email was not sent, as the prospect was already on the recipient list and was mailable

Email, First Name, and Last Name are not required fields in order for GoToWebinar to register a new user to an event. GoToWebinar is a web conferencing platform that allows you to host and join online meetings, webinars, and trainings. You can integrate Marketing Cloud Account Engagement with GoToWebinar using the GoToWebinar connector, which allows you to register prospects for GoToWebinar events from Marketing Cloud Account Engagement forms, landing pages, or completion actions. However, the only required field for GoToWebinar registration is Email. You can also include other fields, such as First Name, Last Name, Phone, or Company, but they are not mandatory. If you do not include these fields, Marketing Cloud Account Engagement will use the default values from the prospect’s record or the connector settings.

Answer A is incorrect because Email, First Name, and Last Name are not required fields in order for GoToWebinar to register a new user to an event, as explained above. References: [GoToWebinar Connector], [Set Up the GoToWebinar Connector]

According to the Salesforce documentation, the marketer can accomplish the goal of creating different Marketing Cloud Account Engagement lists to correspond with the different stages of the buying cycle and automatically updating the prospect list membership based on the opportunity stage change in Salesforce by using a dynamic list. A dynamic list is a list of prospects that is updated automatically based on certain criteria, such as prospect field values, activities, or scores. A dynamic list can be used to segment prospects based on their opportunity stage in Salesforce, and to add or remove prospects from the list when the opportunity stage changes. For example, a dynamic list can be created for prospects whose opportunity stage is Negotiations, and another dynamic list can be created for prospects whose opportunity stage is Closed Won. When an opportunity moves from Negotiations to Closed Won in Salesforce, the prospect associated with that opportunity will be removed from the Negotiations list and added to the Closed Won list in Marketing Cloud Account Engagement. A completion action, a page action, or an automation rule are not the best tools to accomplish the goal of creating different Marketing Cloud Account Engagement lists to correspond with the different stages of the buying cycle and automatically updating the prospect list membership based on the opportunity stage change in Salesforce, as they are related to other aspects of automation, such as performing actions after a prospect completes a marketing element, visits a web page, or meets certain criteria, but not segmenting prospects based on their opportunity stage in Salesforce. References: Salesforce documentation

The recommended way for the user to accomplish this is to set the page action URL as https://www.lenoxsoft.com/products/B. This will create a wildcard page action that will match any URL that starts with https://www.lenoxsoft.com/products/B, including the three URLs mentioned. A wildcard page action allows you to apply the same completion action to multiple pages that share a common prefix.  This way, the user can notify a specific user when a prospect visits any page under the products/B section of their website

According to the Salesforce documentation, the answer is false. There are some restrictions on how you assign custom users abilities. A custom user is a user who has a custom role assigned to them in Marketing Cloud Account Engagement. A custom role is a feature that allows users to create and assign custom permissions and access levels to other users in Marketing Cloud Account Engagement. A custom role can be created and managed by the administrator in the Admin tab in Marketing Cloud Account Engagement, and it can be assigned to new or existing users. A custom role can be assigned to a user by using different methods, such as editing an existing default role, assigning new users during the import process, or adding a batch of existing users using table actions. However, there are some restrictions on how you assign custom users abilities, such as:

• You cannot assign a custom user the ability to create or edit other users, roles, or connectors. This ability is reserved for the administrator only, and it cannot be delegated to a custom user.
• You cannot assign a custom user the ability to access or edit the data or settings of another user, unless the custom user is the manager of that user. A manager is a user who is responsible for overseeing and managing other users, and who can view and edit their data or settings. A manager can be assigned to a user in the user record, and they can have a custom role or a default role.
• You cannot assign a custom user the ability to access or edit the data or settings of a prospect, unless the custom user is the owner or the assigned user of that prospect. An owner is a user who created the prospect in Marketing Cloud Account Engagement, and who can view and edit their data or settings. An assigned user is a user who is assigned to the prospect in Marketing Cloud Account Engagement, and who can view and edit their data or settings. An owner or an assigned user can be assigned to a prospect in the prospect record, and they can have a custom role or a default role.

References: Salesforce documentation

 The way a visitor can convert to a prospect is by submitting a form on a landing page. A visitor is an anonymous person who visits your website, while a prospect is a known person who has an identified email address. A visitor becomes a prospect when they fill out a Marketing Cloud Account Engagement form, which captures their email address and other information. A landing page is a web page that contains a form and a call to action, such as downloading a file or registering for an event. When a visitor submits a form on a landing page, they become a prospect and can be tracked and nurtured by Marketing Cloud Account Engagement. Viewing an embedded form, visiting a tracked website, or receiving a marketing email are not ways to convert a visitor to a prospect, as they do not capture the visitor’s email address or identify them as a prospect. References [Visitors and Prospects] [Landing Pages and Forms]

 When working on a list email, the Marketing Manager has three options that are not available when working on an Account Engagement email template. They are:

• Ability to send the email immediately. This option allows the Marketing Manager to send the list email to the selected recipients as soon as the email is ready, without scheduling it for a later date or time. This option is useful for urgent or time-sensitive messages6
• Ability to schedule the email. This option allows the Marketing Manager to choose a specific date and time to send the list email to the selected recipients. This option is useful for planning ahead or aligning with the best time to reach the audience6
• Recipient and suppression lists. This option allows the Marketing Manager to select which lists of prospects will receive the list email, and which lists of prospects will be excluded from receiving the list email. This option is useful for targeting and segmenting the audience based on their attributes or behaviors6

The number that would display on the Report Card for the email send statistic is 100. This is because the Report Card shows the total number of prospects that have reached a specific step in the program, regardless of the date range that you filter by. The date range filter only affects the data that is shown in the Engagement History table, which shows the number of prospects that have taken a specific action on a specific date. Therefore, even if the user filters the program to show a date range of Tuesday through Friday of last week, the Report Card will still show that 100 emails were sent on Monday, as that is the total number of prospects that reached the first step of the program

By default, Pardot integrates closely with Salesforce CRM to synchronize data primarily with two key standard objects: Lead and Contact records. This integration allows Pardot to write marketing data directly to these objects, enabling a seamless flow of information about prospects' activities and engagement. This capability is foundational for maintaining updated and relevant data within Salesforce, facilitating more targeted and effective sales and marketing efforts. Case, Account, and Opportunity records, while important within Salesforce, do not receive direct writes from Pardot by default, although they can be involved in more advanced, customized integrations.

When an engagement studio action step is scheduled to send an email on a specific date, it means that the email will be sent to all prospects who reach that step on or after that date. Therefore, a prospect arriving after the send date will be sent the email (D). The prospect will not remain on the step until a new send date is set (A), skip the Send Email step (B), or be removed from the program ©. References: Work with Time and Pauses in Engagement Studio

The difference between a dynamic list and a static list is that you cannot manually update list membership of a dynamic list but you can manually update list membership of a static list. A list is a collection of prospects that you can use to segment your audience, send emails, or perform other actions. A dynamic list is a list that automatically populates with prospects who match the criteria you set. A static list is a list that you manually populate with prospects or import from a file. A dynamic list is constantly updated, so prospects are added or removed from the list as they meet or no longer meet the criteria. A static list is not updated automatically, so you can add or remove prospects from the list as you wish. You cannot manually update list membership of a dynamic list, because the list is controlled by the criteria. You can manually update list membership of a static list, because the list is controlled by you

According to the Salesforce documentation, the first step the user must take in order to change which email template is used in a running engagement program is to pause the program. A running engagement program is a program that is actively sending emails and performing actions to the prospects in the program. To make any changes to a running program, such as changing the email template, the user must first pause the program to stop the email sends and actions. After making the changes, the user can resume the program and continue the email sends and actions. Copying the original engagement program, changing the wait time for the template, or deleting the old sent email are not the first steps the user must take, as they will not allow the user to change the email template in the running program. References: Salesforce documentation

The recommended way to identify the prospects who purchased a certain product within the last year and export them to a .csv file is to create a segmentation rule based on the Product Name field. A segmentation rule is a one-time rule that matches prospects based on certain criteria and performs certain actions. You can create a segmentation rule that matches prospects who have the specific product name in the Product Name field and the action to export them to a .csv file. This way, you can get a one-time export of all the prospects who have the product name before it changes. An automation rule, a completion action, or a dynamic list are not suitable for this goal, as they are either recurring, real-time, or based on an activity, not a one-time export based on a field value. References [Segmentation Rules Overview]

In order to send an autoresponder email, you need to create an email template in Marketing Cloud Account Engagement and select the option “Autoresponder emails” under “Available For”. An email template is a preformatted email that you can use to create and send emails quickly and easily. An autoresponder email is an email that is triggered automatically whenever a prospect engages with your marketing assets, such as filling out a form or downloading a file

Conditional completion actions in Pardot allow for a more targeted approach in executing actions based on specific criteria met by prospects. A key behavior of these actions is that both standard (apply to all prospects) and conditional (apply only if certain conditions are met) completion actions can coexist on the same marketing asset. This dual functionality enhances the asset's ability to engage with different segments of the audience differently, based on their interactions or demographic information, thus allowing for more personalized and effective marketing tactics.

A good way in Salesforce to verify that a record is syncing to a prospect in Marketing Cloud Account Engagement is to check that the Marketing Cloud Account Engagement URL field is not empty. The Marketing Cloud Account Engagement URL field is a custom field that is added to the lead or contact object in Salesforce when you connect your Marketing Cloud Account Engagement account with your Salesforce CRM. The Marketing Cloud Account Engagement URL field contains the link to the prospect record in Marketing Cloud Account Engagement that corresponds to the lead or contact record in Salesforce. The Marketing Cloud Account Engagement URL field is populated when a prospect record is synced from Marketing Cloud Account Engagement to Salesforce, or when a lead or contact record is synced from Salesforce to Marketing Cloud Account Engagement. Therefore, if the Marketing Cloud Account Engagement URL field is not empty, it means that the record is syncing to a prospect in Marketing Cloud Account Engagement.

By default, Marketing Cloud Account Engagement will sync with contact accounts in Salesforce. Contact accounts are the standard account type in Salesforce, where each account can have multiple contacts related to it. Marketing Cloud Account Engagement can sync with contact accounts and their related contacts, leads, and opportunities. However, Marketing Cloud Account Engagement can also sync with person accounts in Salesforce, if they are enabled in your org. Person accounts are a special account type in Salesforce, where each account is also a contact. Marketing Cloud Account Engagement can sync with person accounts and their related opportunities, but not with leads. To sync with person accounts, you need to enable the option in the Salesforce connector settings in Marketing Cloud Account Engagement. For more details —> 121314

 According to the Salesforce documentation, the default scoring model in Marketing Cloud Account Engagement assigns points to prospects based on their activities, such as clicking a link in an email, submitting a form, or visiting a landing page. These activities indicate the level of interest and engagement of the prospects, and help prioritize them for sales follow-up. Converting a lead to a contact or sending an email to the assigned user are not activities that automatically increase the prospect’s score, unless they are customized in the scoring rules. References: Salesforce documentation

 If a marketing manager wants to view list email engagement metrics in Engagement History in Salesforce, they will not be able to see the Total Replies metric (A). This metric is not supported by Engagement History, which only shows the following metrics for list emails: Total Delivered, Unique Opens, Unique Clicks, Hard Bounces, Soft Bounces, Opt Outs, and Spam Complaints. The other metrics (B, C, D) are supported by Engagement History and can be viewed in Salesforce. References: Salesforce Engagement History: A Complete Overview

Express Export is a feature that allows you to export a list of prospects with only the default fields, such as email, name, company, score, and grade. This option is faster and simpler than the full export, which includes all the custom fields as well. You can use the Express Export option by selecting a list of prospects and clicking on the “Tools” button, then choosing “Express Export”. References: [Export Prospects], [Express Export]

A lead qualification model based on implicit prospect interest and explicit information provided by prospects requires the feature of Marketing Cloud Account Engagement Score and Grade. The score is a numerical value that measures the implicit interest of a prospect based on their engagement with marketing activities, such as opening emails, clicking links, and visiting landing pages. The grade is a letter value that measures the explicit fit of a prospect based on the information they provide, such as industry, company size, and job title. By combining the score and grade, marketers can segment and prioritize their prospects more effectively3. References: 3: Scoring and Grading Prospects

The score is a numerical value that indicates how interested a prospect is in your products or services based on their activities, such as email opens, clicks, form submissions, etc. The score helps marketers prioritize leads and identify prospects who are ready to buy. Lenoxsoft is interested in following up with IT professionals who are actively engaging with their marketing materials, so the score is the best indicator of their interest level. The grade is a letter value that indicates how well a prospect matches your ideal customer profile based on their attributes, such as industry, job title, location, etc. The grade helps marketers segment leads and target prospects who are a good fit for your business. The profile reflects Lenoxsoft’s ideal customer, but it does not show how engaged the prospect is. The campaign is the first touch point that brought the prospect to your website, such as a Google ad, an email, or a social media post. The campaign helps marketers track the source and effectiveness of their marketing channels, but it does not show how engaged the prospect is. References [Scoring and Grading Overview]

 The best method to create a Marketing Cloud Account Engagement landing page that matches the exact look and feel of your website is to import a layout using a URL from your website. This method allows you to use an existing web page as a template for your landing page, and Marketing Cloud Account Engagement will automatically copy the HTML code, CSS styles, and images from the URL. You can then edit the layout as needed and add Marketing Cloud Account Engagement elements, such as forms or dynamic content

 When a marketer deletes a list and a prospect from Marketing Cloud Account Engagement, the list is archived to the Recycle Bin, but the two remaining prospects are not deleted. The list can be restored from the Recycle Bin within 30 days, but the deleted prospect cannot be restored unless it is manually re-imported or re-created. The two remaining prospects are still active in Marketing Cloud Account Engagement and can be found in the All Prospects list or other lists they belong to. Option A is not correct because deleting a list does not restore a deleted prospect. Option B is not correct because a list can be deleted even if it contains active prospects. Option C is not correct because deleting a list does not delete the prospects in the list. References: Marketing Cloud Account Engagement Recycle Bin 101 – Salesforce Dani, Go Green with Marketing Cloud Account Engagement’s Recycle Bin · Nebula Consulting

Default roles are included with Marketing Cloud Account Engagement and cannot be edited or deleted2. Custom roles can be edited and deleted, and can be created from scratch or from a default role2. Custom roles allow you to customize the access and permissions for different types of users in your organization2

 When an engagement studio program is created with an Email Send action step immediately followed by an Email Open trigger step with a 3 day wait, it means that the program will wait for up to 3 days for the prospect to open the email. If the prospect opens the email within the 3 day period, they will immediately progress down the “Yes” path (A). The prospect will not wait for any additional time after opening the email (B), nor will they progress down the “No” path (C, D). References: Engagement Studio Overview

 According to the Salesforce documentation, the variable tag that must be included in an email to allow prospects to manage their email preferences is %%unsubscribe%% or %%email_preference_center%%. A variable tag is a placeholder that is replaced with a specific value when the email is sent. The %%unsubscribe%% variable tag is replaced with a link that allows the prospect to unsubscribe from all emails from the sender. The %%email_preference_center%% variable tag is replaced with a link that allows the prospect to opt in or out of specific email lists or categories. Either of these variable tags can be used to enable prospects to manage their email preferences, and they are required by law in some countries. %%opt_out%% or %%email_preference_center%%, %%opt_out%% report_spam%%, and %%unsubscribe%% or %%opt_out%% are not valid variable tags that can be used to allow prospects to manage their email preferences, as they are either incorrect or nonexistent. References: Salesforce documentation

Creating or marking an opportunity as lost will result in the change of a prospect’s score. This is because opportunities are one of the factors that affect the scoring of prospects in Marketing Cloud Account Engagement. Scoring is a numerical value that indicates the level of interest or engagement of a prospect in your products or services. Scoring is based on the actions and activities of prospects, such as opening emails, clicking links, filling out forms, visiting landing pages, and creating or updating opportunities. When an opportunity is created or marked as lost, the prospect’s score will change accordingly. For example, if you have a scoring rule that adds 50 points to a prospect’s score when an opportunity is created, and subtracts 25 points when an opportunity is lost, then creating or marking an opportunity as lost will affect the prospect’s score by those amounts.

Answer B is incorrect because creating or marking an opportunity as lost will not result in no change of a prospect’s score, as explained above. References: Scoring, Opportunities

In Pardot, the best tool to use for assigning prospects to a group of users based on specific criteria is an automation rule with rule groups. Automation rules allow for the creation of complex criteria that prospects must meet to trigger certain actions. In this scenario, the rule would check for prospects with a score greater than 100, a grade greater than B, completion of any form on a landing page, and a “Product of Interest” field value of either A or B. Once a prospect meets these conditions, the automation rule can then assign them to the specified group of users. This method is efficient for processing large numbers of prospects automatically and continuously, which is not as feasible with completion actions on forms or landing pages, or with a one-time use segmentation rule.

The reason why the email link www.lenoxsoft.com was not re-written for tracking is that the link should start with http or https to be automatically re-written. Marketing Cloud Account Engagement automatically re-writes links in emails to track the clicks and measure the engagement of the recipients. However, Marketing Cloud Account Engagement only re-writes links that start with http or https, as these are the protocols that indicate a web address. The link www.lenoxsoft.com does not have a protocol, so Ma rketing Cloud Account Engagement does not recognize it as a web address and does not re-write it for tracking. The other options are not relevant for link re-writing. The link does not need to contain a wildcard, point to go.Marketing Cloud Account Engagement.com, or be populated with variable tags to be automatically re-written. These are features that can be used to create dynamic or custom links, but they are not required for link re-writing. References [Link Click Tracking]

Mailable Database usage is the number of prospects in an account that are opted in and can receive emails. It does not include prospects that are opted out, in the recycle bin, or have a hard bounce or do not email status. Therefore, the Mailable Database usage for the marketer with 4,000 total prospects, 3,000 of which are opted in, 500 of which are opted out, and 500 of which are in the recycle bin, is 3,000 (A). The other options (B, C, D) are incorrect because they either include prospects that are not mailable or exclude prospects that are mailable. References: Marketing Cloud Account Engagement - Salesforce.com

By default (using business accounts), Marketing Cloud Account Engagement creates new records as leads in Salesforce. This means that when a prospect is assigned to a user in Marketing Cloud Account Engagement, and there is no matching lead or contact in Salesforce, Marketing Cloud Account Engagement will create a new lead record in Salesforce and sync with it. However, you can also configure Marketing Cloud Account Engagement to create new records as contacts or person accounts in Salesforce, depending on your preference. To do this, you need to enable the option in the Salesforce connector settings in Marketing Cloud Account Engagement, and make sure that the connector user has the appropriate permissions in Salesforce. For more details —> 151617

According to the Salesforce documentation, the feature in Salesforce that can be enabled to show landing page engagement data on a Salesforce Campaign page layout is Engagement History. Engagement History is a feature that allows users to view and report on how prospects interact with Marketing Cloud Account Engagement marketing assets, such as emails, forms, landing pages, and custom redirects. Engagement History can be enabled for Salesforce Campaigns, Leads, Contacts, Accounts, and Opportunities, and it can display metrics such as views, clicks, submissions, and conversions. Advanced Dynamic Content, Marketing Cloud Account Engagement Activities Visualforce page, and B2B Marketing Analytics are not features that can show landing page engagement data on a Salesforce Campaign page layout, as they are related to other aspects of marketing automation, such as personalization, activity tracking, and analytics. References: Salesforce documentation