AD0-E559 Adobe Marketo Engage Business Practitioner Expert Questions and Answers

Two benefits to using global forms versus local forms are that global forms allow for consistent scoring and reporting and data standardization, and that global forms offer a scalable solution especially when there are universal changes that need to be made, saving time and resources. Global forms are forms that are created in Design Studio and can be used across multiple programs and landing pages. They help maintain data quality and consistency, as well as reduce duplication and errors. Global forms do not natively offer custom stylization or tracking without additional constraints.

A reason for this data value change is that this email was already part of the Adobe Marketo Engage database in the past as an unsubscribe. This is because Adobe Marketo Engage maintains a global unsubscribe list that applies to all workspaces and partitions. If an email address is unsubscribed in one workspace or partition, it will be unsubscribed in all others as well. Therefore, when a new person is created with an email address that was previously unsubscribed, Adobe Marketo Engage will automatically mark them as unsubscribed as well. A trigger campaign or a system flow action would not cause this data value change

To time-stamp a custom field with the current date and time, David would use a System token in the “Change Data Value” flow step. System tokens are tokens that reference system-level information, such as date, time, IP address, etc. The System token for date and time is {{system.dateTime}}. Person/Lead tokens and Trigger tokens are not suitable for this purpose, as they reference person-level information or trigger-specific information.

Miri will receive an email with apple pie messaging. Jacinda will receive an email with tiramisu messaging. Indira will receive an email with sticky toffee pudding messaging. This is because the segmentation is based on dessert preferences, and each segment has only one dessert assigned to it. Therefore, each person will receive the message that corresponds to their first dessert preference in alphabetical order. For example, Miri likes apple pie and sticky toffee pudding, but apple pie comes before sticky toffee pudding in alphabetical order, so she will receive the apple pie message. The other options are incorrect because they do not follow this logic

A best practice for A/B testing is to run a combination of many tests sequentially and methodically. This will help the marketer optimize their email performance by testing one element at a time and measuring its impact on key metrics such as open rate, click rate, conversion rate, etc. Varying as many elements as possible in each test or ending the test as soon as one version surpasses the other are not best practices for A/B testing, as they can lead to inaccurate or inconclusive results.

Two things that Jay could try to identify the issue are to go into the Members tab of the webinar program and check if any person has the program status of Registration Error, and to go into the Members tab of the webinar program and check that the webinar url column is populated using a custom view. These steps can help Jay troubleshoot if there was any problem with the registration process or the webinar provider integration. Changing the program status manually or looking in field management will not help Jay solve the issue.

Two fields that David would use for this purpose are Person Source and Original Source Type. These are system-managed fields that capture information about how a person was created in the database. Person Source indicates which channel or method was used to create the person, such as Web Service API, List Import, Sales Insight, etc. Original Source Type indicates which type of source was used to create the person, such as Web Page Visit, Web Form Fillout, Sales Generated, etc. These fields can give David a high-level view of the lead sources without relying on user input or smart campaign logic. Registration Source Type and Acquisition Program are not system-managed fields and may not be populated or accurate for all leads.

The fields First Name, Last Name, Email Address, and Company Name will pre-fill for only people already known in the database. Pre-fill is a feature that populates form fields with data from a known lead’s record. If a person is not known in the database, such as someone who clicks the link from social media, the fields will not pre-fill

A Company Web Activity report can be used to get this company level view. This report type shows metrics such as number of visits, number of people, average pages per visit, etc. for each company in the database. The marketer can filter the report by vertical and date range to see how many unique companies by vertical are in their Adobe Marketo Engage database. A People Performance Report or an Account Performance Report will not show company-level metrics or allow filtering by vertical.

A Program Performance Report with all content programs selected can be built and analyzed to show the most engaging content. This report type shows metrics such as new names, success, cost per success, etc. for each program in a selected channel or folder. The marketer can filter the report by the content channel and the date range of the financial year to see how many form fills have been created from each content program. A Smart List or a People Performance Report will not show program-level metrics or allow filtering by channel or folder.

A possible reason the email has not been launched is that the new email has not been activated. An email must be approved and activated before it can be sent out by an Engagement Program. If the email is not activated, it will be skipped by the cast. The stream and the content do not need to be activated for the email to be launched.

The best practice steps that must be taken when embarking on developing such a process are to create a folder within the Marketing Activities to store all data management processes, containing a Default Program with a default Data Management Channel with nested Smart Campaigns. This will help organize and standardize the data management processes and make them easy to find and report on. The Data Management Channel is designed for operational programs that do not generate revenue or influence pipeline. Creating a folder within the Design Studio or using an Operational Channel will not achieve the same result.