Complete Marketing-Cloud-Account-Engagement-Specialist Salesforce Materials

According to the Salesforce documentation, when a visitor clicks on a custom redirect with an action of adding a tag, and then fills out a form and becomes a prospect, the following three things will happen to the prospect: A) The prospect activities will show that the form was successfully completed, B) The prospect will be added to the list, and D) The prospect will be tagged. A custom redirect is a trackable URL that can be used to measure and report on the clicks of any online content, such as banner ads, social media posts, or third-party websites. A custom redirect can also have completion actions, such as adding a tag, which are performed when a visitor clicks on the custom redirect. A tag is a label that can be used to categorize and segment prospects. A form is a web form that can be used to collect information from prospects and store it in Marketing Cloud Account Engagement. A form can also have completion actions, such as adding to a list, which are performed when a prospect successfully submits the form. A list is a collection of prospects that can be used for segmentation and email sending. When a visitor clicks on a custom redirect and then fills out a form, the visitor becomes a prospect, and the completion actions of both the custom redirect and the form are applied to the prospect. The prospect activities will show both the custom redirect click and the form submission, the prospect will be added to the list specified in the form completion action, and the prospect will be tagged with the tag specified in the custom redirect completion action. The newly converted prospect will be affected by both the custom redirect and the form completion actions, as they are not dependent on the prospect’s previous submissions or activities. References: Salesforce documentation

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

A designer can control the CSS styling for two assets in Marketing Cloud Account Engagement: landing pages and forms. Landing pages are web pages that capture visitor information and generate leads. Forms are web forms that collect visitor information and convert them to prospects. Both landing pages and forms can be customized with CSS to match the branding and design of LenoxSoft. Form handlers and social posts are not assets that can be controlled by CSS in Marketing Cloud Account Engagement. Form handlers are connectors that allow Marketing Cloud Account Engagement to use external forms on your website. Social posts are messages that can be sent to your social media accounts from Marketing Cloud Account Engagement. References Customize Landing Pages with CSS Customize Forms with CSS

 If a non-repeating automation rule has matched 100 prospects, and a user pauses the automation rule, edits the rules criteria, and resumes the rule, the 100 prospects who previously matched the rule will be marked as unmatching the updated rule. This means that they will not receive any new actions from the rule, and any actions that were already applied to them will not be undone11. However, if the rule is set to repeat, the prospects who previously matched the rule can match the rule again if they meet the new criteria