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

The acquisition program will be captured for the person automatically because the Content Form is local to this program. This is because Adobe Marketo Engage automatically sets the acquisition program for a person when they fill out a form that is local to a program for the first time. The Change Program Status flow step does not set program membership or acquisition program, but only changes the status of an existing member. The program does not contain any other mechanism to set the acquisition program for the person. 

A trigger token cannot successfully be used within a batch smart campaign. This is because a trigger token references a value that is specific to a trigger event, such as {{trigger.web page}} or {{trigger.email name}}. A batch smart campaign does not have any trigger events, so the trigger token will not have any value. A different smart campaign must be used for each web page or a custom field must be used to accomplish this. It is possible to customize what is shown in an interesting moment view

A reason for creating a form in Design Studio rather than within a program in Marketing Activities is that the form can be used across multiple programs. This allows for reusability and consistency of forms. Creating a form in Design Studio does not offer more design options or enable sharing across workspaces

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

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 reason the Activity Log tab is empty is that the person activity is filtered. This can happen when a filter is applied to the activity log, such as by date range, activity type, primary attribute, etc. To see all activities for a person, the filter should be cleared or adjusted. The activity log would not be exported by an API or emptied by an anonymous lead.

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.

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.

The administrator needs to add all stages to the success path to correct the model validation error. This is because a revenue model must have at least one stage on the success path, and the success path must be continuous and sequential. The administrator cannot leave any gaps or jumps between stages on the success path. Adding triggers or SLA stages is not required to validate the model.

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 tokens have been set up in this folder so they will be available in all programs inside the folder. Tokens are inherited from the parent folder to the child folder or program, so any tokens set up at the folder level can be used by any program within that folder. This allows for consistency and efficiency when creating programs and assets that use the same token values

 A best practice when creating a scoring model is to look at previous wins or gather sales feedback to identify shared characteristics of the people that became customers. This will help the marketer understand which behaviors and attributes are most indicative of sales readiness and assign appropriate scores accordingly. Asking the marketing team or importing a template may not reflect the unique needs and goals of the business.