Salesforce Marketing-Cloud-Account-Engagement-Specialist - Salesforce Marketing Cloud Account Engagement Specialist (SP25)

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]

The daily system generated emails are: daily prospect activity emails (for all prospects), daily prospect activity emails (for my prospects), daily visitor activity emails, and daily prospect assignment emails. These are the emails that Marketing Cloud Account Engagement sends to users based on their preferences, which provide a summary of the activities and actions of prospects and visitors on a daily basis. Daily prospect activity emails (for all prospects) show the activities of all prospects in your Marketing Cloud Account Engagement account. Daily prospect activity emails (for my prospects) show the activities of the prospects that are assigned to you. Daily visitor activity emails show the activities of the anonymous visitors on your website. Daily prospect assignment emails show the prospects that have been assigned to you or to other users910 References: 9: Auto generated email – How to guide10: Customizing the System Generated Emails

Completion actions are not retroactive and will only apply to prospects who complete the chosen action moving forward. Completion actions will fire each and every time a prospect takes the chosen action, except for when changing the prospect’s Marketing Cloud Account Engagement score

 According to the Marketing Cloud Account Engagement Email Basics, there are three mandatory components for an email to be saved in Marketing Cloud Account Engagement: a text version, a sender, and an unsubscribe link. A text version is required for accessibility and deliverability reasons, as some email clients or recipients may not support HTML emails. A sender is required to identify the source of the email and comply with the CAN-SPAM Act. An unsubscribe link is required to allow recipients to opt out of future emails and comply with the GDPR and other privacy regulations. Variable tags, dynamic content, and social posts are optional components that can enhance the personalization and interactivity of the email, but they are not required for saving the email draft. 

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

A good default sales ready lead score is 100, as this indicates a high level of interest and engagement from the prospect. Lead scoring is a way of assigning a numerical value to each prospect based on their behavior and profile, such as visiting your website, opening your emails, filling out forms, etc. The higher the score, the more likely the prospect is to buy from you. A lead score of 100 means that the prospect has met all the criteria you have set for a sales ready lead, such as viewing a specific page, requesting a demo, or downloading a white paper. You can customize your lead scoring criteria and thresholds according to your business needs and goals. For more details —> 12

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