AD0-E559 Questions and Answers

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.

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.

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.

To limit the intern’s access to work strictly to the APJ Workspace, Michael must create a User for the intern that grants access only to the APJ Workspace. This can be done by selecting the APJ Workspace from the Workspaces drop-down menu when creating the User. The User will then only be able to view and edit programs and assets within that Workspace.

 Sally would set communication limits in the Admin to stop any over-communication by the Marketing Team across all regions at a global level. Communication limits are settings that control how many emails a person can receive within a certain time frame. They can be applied at the account level, workspace level, or program level. Setting communication limits in the Admin will affect all workspaces and programs in the account. Requesting a custom Duplicate Key from Support or disabling program communication limits will not help Sally achieve her goal.

The marketer should wait 24 hours for the updated period cost to be reflected in RCE. This is because RCE data is refreshed once a day, usually at night. Therefore, any changes made to the period cost or other program attributes will not be visible in RCE until the next day. RCE does not update in real time, and the updated period cost will be reflected in RCE eventually.

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

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.

A person would not appear on this smart list if the email sent to them last week bounced. This is because a bounced email is not considered as a sent email in Adobe Marketo Engage. Therefore, the person would not meet the criteria of the Was Sent Email filter and would be excluded from the smart list. The person would appear on the smart list if they were last sent an email 6 months ago or if they unsubscribed from the email they received last month, as long as they met the date of activity constraint

A reason why the webhook failed is that webhooks can only be used successfully once they are approved. Webhooks are like assets that need to be approved before they can be used in smart campaigns. If a webhook is not approved, it will fail when called by a smart campaign. Webhooks can be used successfully in conjunction with the Member of List filter, in batch campaigns, and without approval.