Adobe AD0-E559 Adobe Marketo Engage Business Practitioner Expert Exam Practice Test

A field that can give some indication of where the leads came from is Original Source Info. This is a system-managed field that captures the first known referrer URL for a person. It can helpidentify the source of web traffic that led to the person’s creation in the database. Lead Source and Acquisition Program are not system-managed fields and may not be populated or accurate for all leads

To find a comprehensive list of actions that users have taken within the Adobe Marketo Engage instance in the last six months, Ajay can use Audit Trail. Audit Trail is a feature that tracks all user activities within an Adobe Marketo Engage instance, such as creating, updating, or deleting programs, assets, fields, users, roles, etc. Audit Trail also shows who updated the Webinar registration landing page in the last month by filtering by user name, date range, and activity type.

The conclusion that the marketer can make about these A/B test results is that their test hypothesis was invalidated and they should test again. This means that their assumption about what would improve their email performance was not supported by the data and they should try a different variation or element to test. The test was not erroneous or too short, as long as it was set up correctly and ran for a sufficient time period to reach statistical significance

Garrin did not set up the campaign correctly to achieve his desired results. The campaign will fire if a person fills out a form or clicks a link in an email, not both. This is because he used an “or” filter logic for his triggers, which means that any one of them will qualify a person for the campaign. To make sure that a person fills out a form and clicks a link in an email, he should use an “and” filter logic instead

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 marketer would include a Program Member Custom Field on the registration form to capture this information without the risk of the information being overwritten. A Program Member Custom Field is a field that is specific to a program and a person, and it can store different values for different programs. This way, the person can indicate their preferred break-out session for each event they register for, without affecting their previous or future choices. A Visibility Rule is not a field, but a way to show or hide fields based on other fields. A Program Member Token is not a field, but a way to reference a Program Member Custom Field value in an email or landing page

The field ‘Is Customer’ is required on the form so she can use it as a choice with the Thank You Page in Form Settings. This will allow her to redirect existing customers and new leads to different thank you pages based on the value of the field. The field is not needed to alert the Sales Owner or to use it in a Smart Campaign, as those actions can be done based on other criteria.

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.

One new benefit Bhaskar will gain by implementing this new naming convention is that he will be able to create a global product-specific scoring program that triggers off Program Status Changes with a Program Name constraint. This will help him score leads based on their engagement with different product lines across different programs. For example, he can create a trigger that fires when Program Status is Changed and Program Name contains PROD1, and then add a flow step that increases the score for PROD1 by a certain amount. Creating product-specific dynamic content or nurtures does not require this naming convention. 

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.

To find the list of people who received the losing email, they would use the Was Sent Email filter with the Test Variant constraint. This filter allows them to specify which email and which test variant they want to target. The Was Sent A/B Test filter does not have a Variant constraint, and it is not possible to see who received which test variant without using a constraint. 

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.

Option C is the correct smart list section for their data management smart campaign. This option uses the Visits Web Page trigger with the Min. Number of Times constraint set to 3 and the Date of Activity constraint set to in past 90 days. This will ensure that only people who have visited any web page at least three times within the last 90 days will qualify for the campaign. Option A uses filters instead of triggers, which means that it will not run automatically and instantaneously. Option B uses an incorrect filter logic, which means that it will not require three web page visits within 90 days

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