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

An identified visitor is a visitor who has provided their contact information in a Marketing Cloud Account Engagement form. This means that the visitor has converted into a prospect and has a record in Marketing Cloud Account Engagement. Marketing Cloud Account Engagement can track the activities and behavior of identified visitors using a cookie that is placed on their browser when they fill out a form. Identified visitors are different from anonymous visitors, who have not provided any contact information and are only tracked by their IP address, and from visitors whose organization has been identified using a reverse IP lookup, who may or may not have a prospect record in Marketing Cloud Account Engagement

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

 According to the Salesforce documentation, the types of fields that are not supported by the Marketing Cloud Account Engagement sync are: B) Formula fields, D) Geolocation fields, and E) Text Area (rich) fields. A Marketing Cloud Account Engagement sync is a feature that allows users to connect and exchange data between Marketing Cloud Account Engagement and Salesforce fields, such as name, email, score, or grade. A Marketing Cloud Account Engagement sync can be configured by the administrator in the connector settings, and it can be customized for different objects, fields, or actions. A Marketing Cloud Account Engagement sync can support different types of fields, such as text, number, date, checkbox, picklist, or lookup fields. However, a Marketing Cloud Account Engagement sync cannot support some types of fields, such as formula, geolocation, or text area (rich) fields. A formula field is a field that calculates a value based on a formula or an expression. A geolocation field is a field that stores the latitude and longitude coordinates of a location. A text area (rich) field is a field that allows users to enter formatted text, images, or links. These types of fields are not supported by the Marketing Cloud Account Engagement sync, as they are either incompatible, complex, or large for the data exchange. A record type field is a type of field that is supported by the Marketing Cloud Account Engagement sync, as it is a field that defines different business processes, page layouts, or picklist values for different users. A number field is also a type of field that is supported by the Marketing Cloud Account Engagement sync, as it is a field that stores numerical values. References: Salesforce documentation

The two ways that a Marketing Cloud Account Engagement prospect syncs with a Salesforce Lead or Contact record are shared CRM ID and shared email address. A CRM ID is a unique identifier that is assigned to a Lead or Contact record in Salesforce and is synced with the corresponding prospect record in Marketing Cloud Account Engagement. A CRM ID ensures that the prospect data is matched with the correct Lead or Contact data and prevents duplicates. A CRM ID is created when a prospect is created or updated in Marketing Cloud Account Engagement and a matching Lead or Contact is found or created in Salesforce, or when a Lead or Contact is created or updated in Salesforce and a matching prospect is found or created in Marketing Cloud Account Engagement5. An email address is a required field for both a prospect in Marketing Cloud Account Engagement and a Lead or Contact in Salesforce. An email address is used to identify and associate a prospect with a Lead or Contact, and to trigger a sync between Marketing Cloud Account Engagement and Salesforce. An email address is also used to track the prospect’s activities, such as email opens, clicks, form submissions, and page views5. Option B is not correct because a shared assigned user ID is not a way that a Marketing Cloud Account Engagement prospect syncs with a Salesforce Lead or Contact record, but a result of the sync. An assigned user ID is the ID of the user who owns the prospect in Marketing Cloud Account Engagement or the Lead or Contact in Salesforce. The assigned user ID is synced between Marketing Cloud Account Engagement and Salesforce to ensure that the same user owns the prospect and the Lead or Contact, unless there are custom assignment rules in place5. Option D is not correct because a shared tracking pixel is not a way that a Marketing Cloud Account Engagement prospect syncs with a Salesforce Lead or Contact record, but a method of tracking the prospect’s activities. A tracking pixel is a hidden image that is embedded in an email or a web page and sends a request to Marketing Cloud Account Engagement’s server when the email or the web page is opened. A tracking pixel allows Marketing Cloud Account Engagement to record the prospect’s email opens, page views, and other actions

To post a form directly to a third-party platform as well as Marketing Cloud Account Engagement upon submission, LenoxSoft should use the form handler tool in Marketing Cloud Account Engagement. This tool allows them to use their own forms while still sending the data to Marketing Cloud Account Engagement. They can specify the third-party platform’s URL as the post URL in the form handler settings and map the form fields to Marketing Cloud Account Engagement fields. References: [Marketing Cloud Account Engagement Form Handler]

Form handlers allow you to use your own forms to post your data to Marketing Cloud Account Engagement. A form handler is a great alternative to use instead of Marketing Cloud Account Engagement forms. They allow you to fully customize the look of your form and submit data to more than one database. However, form handlers do not support progressive profiling, which is a feature that allows you to display new fields for known prospects and collect more information about them. To use progressive profiling, you need to create a Marketing Cloud Account Engagement form and enable it in the form settings

The event that would make the Salesforce connector become unverified is the connector user’s Salesforce password was changed. 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 a connector user, which is a Salesforce user that Marketing Cloud Account Engagement uses to access your Salesforce data and perform actions on your behalf. The connector user needs to have the appropriate permissions and settings in Salesforce, such as the API Enabled and Modify All Data permissions, and the security token2. If the connector user’s Salesforce password was changed, the security token would also change, and Marketing Cloud Account Engagement would not be able to authenticate with Salesforce. This would cause the Salesforce connector to become unverified, and the data sync between Marketing Cloud Account Engagement and Salesforce would stop. To fix this, you need to update the connector user’s password and security token in Marketing Cloud Account Engagement, and re-verify the Salesforce connector

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

 According to the Salesforce documentation, an automation rule is an automation tool that can be used to send an email to a prospect when a form is submitted and a specific field value is selected on that form. An automation rule can be configured to trigger an action (such as sending an email) when a prospect meets certain criteria (such as submitting a form and having a specific field value). The criteria can be set to Match All or Match Any, depending on the logic required. In this case, the Match All option should be used, as the prospect needs to meet both conditions (form submission and field value) to receive the email. A completion action is another automation tool that can be used to perform an action after a prospect successfully completes a form, but it cannot be used to check for a specific field value. A dynamic list is a list of prospects that is updated automatically based on certain criteria, but it cannot be used to send an email directly. A list email is an email that is sent to a specific list of prospects, but it cannot be triggered by a form submission or a field value. References: Salesforce documentation

According to the Salesforce documentation, when a prospect is permanently deleted from Marketing Cloud Account Engagement, all the associated data and activities are also deleted and cannot be restored. However, if the prospect fills out a new Marketing Cloud Account Engagement form and submits their information, a new prospect record will be created with the same email address as the deleted one, but without any of the previous data and activities. The new prospect will have a new unique ID and will not be linked to the deleted one in any way. References: Salesforce documentation