Pass the Salesforce Marketers Marketing-Cloud-Account-Engagement-Specialist Questions and answers with ValidTests

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

 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

Form reports show the performance and activity of your Marketing Cloud Account Engagement forms, which are web forms that capture prospect information. You can use form reports to see how many prospects have viewed, completed, or started but not completed your forms, as well as the conversion rate and average time to complete. You can also drill down into individual form submissions and view the prospect’s details and activities. References: [Form Reports], [View Form Reports]

 A repeating automation rule is a type of automation rule that allows prospects to match the rule more than once, as long as they meet the criteria again. When creating a repeating automation rule, two considerations must be made: setting how many days must pass before a prospect can match the repeating automation rule again ©, and setting the number of times a prospect can match the repeating automation rule in total (D). These settings help prevent prospects from being over-marketed or receiving duplicate actions. Setting how many prospects are allowed to match the repeating automation rule (A) or setting a date for when prospects can no longer match the repeating automation rule (B) are not available options for repeating automation rules. References: Using Account Engagement Automation Rules vs. Salesforce Flows

According to the Salesforce documentation, when a prospect is added to a suppression list in an engagement studio program, the prospect is paused from receiving any further emails or actions from the program. However, the prospect’s progress in the program is not reset or removed. If the prospect is removed from the suppression list, the prospect will resume the program from where they left off, which is the next step after the last completed step. In this case, the prospect will continue on the engagement studio program onto step 6. References: Salesforce documentation

According to the Salesforce documentation, the correct steps to access a Prospect Record are: B) Mouseover Prospects, C) Click Prospect List, and A) Select Prospect. A Prospect Record is a feature that shows the detailed information and activity history of a prospect in Marketing Cloud Account Engagement. A Prospect Record can be accessed from the Prospects tab in Marketing Cloud Account Engagement, and it can show different sections of information for the prospect, such as details, insights, activities, or custom fields. To access a Prospect Record, the user needs to follow these steps:

Mouseover Prospects: The user needs to move the cursor over the Prospects tab in the navigation bar in Marketing Cloud Account Engagement. This will open a drop-down menu with different options, such as Prospect List, Add Prospect, or Import Prospects.

Click Prospect List: The user needs to click on the Prospect List option in the drop-down menu. This will open the Prospect List page, which shows a list of prospects in Marketing Cloud Account Engagement. The user can customize, sort, filter, search, or export the Prospect List, and they can also perform different actions on the prospects, such as assign, delete, or edit.

Select Prospect: The user needs to select the prospect that they want to access from the Prospect List. This will open the Prospect Record page, which shows the detailed information and activity history of the prospect. The user can view, edit, or update the Prospect Record, and they can also perform different actions on the prospect, such as sending an email, adding to a list, or changing the score or grade.

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 automation tool that should be used to increase a prospect’s score an additional five points every time a specific form is completed is completion action. A completion action is an automated task that is triggered by a certain element in Marketing Cloud Account Engagement, such as a form, a form handler, a custom redirect, a page action, or a file download17. A completion action can perform various actions, such as adjusting score, adding to list, assigning to user, sending autoresponder email, and so on18. A completion action can be added to a form in the fourth step of the form builder tool, and it can be customized to execute only on prospects who meet specific criteria19. A completion action is not retroactive and will only apply to prospects who complete the chosen action moving forward

 According to the Salesforce documentation, the asset that needs to be created first in order for a user to send a prospect a one-to-one email is an email template. A one-to-one email is an email that is sent to an individual prospect, such as a follow-up or a confirmation email. A one-to-one email can be sent from the prospect record, a list, a report, or a campaign. To send a one-to-one email, the user needs to have an email template that defines the content and layout of the email. An email template can be created in Email Studio or Content Builder, and it can be personalized with variable tags or dynamic content. An autoresponder, an engagement studio program email, or a list email are not assets that need to be created first in order for a user to send a prospect a one-to-one email, as they are related to other types of email sends, such as automated responses, program emails, or mass emails. References: Salesforce documentation

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