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

It is not possible to create a dynamic list of all prospects who have accessed a certain file in Marketing Cloud Account Engagement. Dynamic lists are based on criteria that match prospect fields, not prospect activities. Therefore, you cannot use a dynamic list to segment prospects based on whether they have downloaded a file, watched a video, or visited a page. Option A is not correct because field value mapping has nothing to do with dynamic lists or file access. Option C is not correct because match type is irrelevant for this question, as there is no valid criterion for file access. Option D is not correct for the same reason as option C. References: Marketing Cloud Account Engagement Dynamic Lists for Faster Segmentation (+ 10 Examples), Create a Dynamic List - Salesforce

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

The limitations of connecting Marketing Cloud Account Engagement to a Salesforce Sandbox account are: if connected to a sandbox first, when you create your production connector, all prospects will not automatically queue to sync, and Marketing Cloud Account Engagement can’t “wipe” data, so you will need to manually delete any prospects and data that is brought into your Marketing Cloud Account Engagement account from the sandbox connector before enabling the connector for your production instance. A Salesforce Sandbox account is a copy of your production environment that you can use for testing and development purposes. Marketing Cloud Account Engagement Sandboxes are test versions of a Marketing Cloud Account Engagement Business Unit that you can provision within a Salesforce Sandbox. However, Marketing Cloud Account Engagement Sandboxes have some limitations that you need to be aware of before using them. One limitation is that if you connect Marketing Cloud Account Engagement to a Salesforce Sandbox first, and then create a production connector, the prospects in your Marketing Cloud Account Engagement account will not automatically sync with the production environment. You will need to manually sync them or use an automation tool to do so. Another limitation is that Marketing Cloud Account Engagement cannot erase the data that is brought into your Marketing Cloud Account Engagement account from the sandbox connector, such as prospects, fields, and assets. You will need to manually delete them before enabling the connector for your production instance, or else you will end up with duplicate or unwanted data in your Marketing Cloud Account Engagement account1112 References: 11: Marketing Cloud Account Engagement Sandboxes: What They Can, and Can’t Do12: Use Marketing Cloud Account Engagement Sandboxes

 According to the Salesforce documentation, the issue of none of the lead’s Marketing Cloud Account Engagement information (score/grade) transferring over when Jim, a sales manager, converted a lead to a contact in Salesforce can be addressed by making sure that the administrator has mapped the lead fields to the contact fields in Salesforce. A field mapping is a feature that allows users to sync the data between Marketing Cloud Account Engagement and Salesforce fields, such as name, email, score, or grade. A field mapping can be configured by the administrator in the connector settings, and it can be customized for different objects, such as leads, contacts, or accounts. When a lead is converted to a contact in Salesforce, the Marketing Cloud Account Engagement information (score/grade) should transfer over to the contact record, as long as the lead fields and the contact fields are mapped correctly in the connector settings. If the fields are not mapped correctly, the Marketing Cloud Account Engagement information (score/grade) will not transfer over, and the contact record will not reflect the Marketing Cloud Account Engagement data. Therefore, the administrator needs to make sure that the lead fields and the contact fields are mapped correctly in the connector settings, and that the sync between Marketing Cloud Account Engagement and Salesforce is working properly. Marketing Cloud Account Engagement only showing this information on the lead record, this information showing on the account record and not the contact, or the administrator needing to create lookup fields on the contact to see this from the lead are not the correct ways to address the issue of none of the lead’s Marketing Cloud Account Engagement information (score/grade) transferring over when Jim, a sales manager, converted a lead to a contact in Salesforce, as they are either inaccurate, irrelevant, or unnecessary options for the field mapping or the data sync. References: Salesforce documentation

 The best way to track the number of visitors who access a file on a web page that the company does not own on the company website is to use custom redirects ©. Custom redirects are used to track links such as banner ad clicks, links to third-party sites, links on social media, and access to files hosted outside of Account Engagement. Link clicks appear as activity on a prospect’s record. Page actions (A) are not a valid option, as they are used to track and automate actions based on a prospect’s page views, not link clicks. Account Engagement form (B) is not a valid option, as it is used to capture and update prospect information, not track link clicks. Account Engagement tracking code (D) is not a valid option, as it is used to track and cookie visitors on the company website, not on a third-party site. References: Custom Redirects

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.

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 scenario that would convert an anonymous visitor into an identified prospect is submitting a Web2Lead form that is linked to Account Engagement via a form handler ©. This is because a form handler captures the visitor’s information and passes it to Account Engagement, where a new prospect record is created. Creating a Lead in Salesforce which syncs to Account Engagement as a new prospect record (A) will not convert an anonymous visitor, as it does not involve any interaction with the visitor. Scanning the badge of someone who visited a booth at a recent event (B) will not convert an anonymous visitor, as it does not involve any online activity that can be tracked by Account Engagement. Opening an email sent by a sales rep using the Send Account Engagement Email functionality in Salesforce (D) will not convert an anonymous visitor, as it requires the visitor to already have a prospect record in Account Engagement. References: Anonymous Visitors

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]

 Prospects sync to your CRM when they have been assigned to a user or queue. A CRM is a customer relationship management platform that allows you to manage your sales and customer service operations. You can integrate Marketing Cloud Account Engagement with your CRM using the Salesforce connector, which allows you to sync data, activities, and campaigns between Marketing Cloud Account Engagement and Salesforce. However, not all prospects in Marketing Cloud Account Engagement are synced to Salesforce. Only prospects that have been assigned to a user or queue in Marketing Cloud Account Engagement are synced to Salesforce as leads or contacts. You can assign prospects manually, through automation rules, or through lead assignment rules.

Answer A, C, D, and E are incorrect because prospects do not sync to your CRM when they fill out a form on a landing page, when they have a lead score greater than 50, when they visit a landing page, or when they are created manually in the Marketing Cloud Account Engagement database, unless they are also assigned to a user or queue, as explained above. References: [Salesforce Connector], [Sync Prospects with Salesforce]