AD0-E556 Exam Dumps : Adobe Marketo Engage Architect

The three recommendations that the Consultant should make are to create two workspaces: A prospect workspace and a customer workspace, to create a naming convention that tags customer vs prospect campaigns, and to reduce the access for the demand generation manager and IT manager to a limited role that cannot create fields. These recommendations will help the company to achieve their goals of pulling quick reports for prospect programs and customer programs from a reporting tool like Tableau, and changing the operating model from de-centralized to centralized. Creating two workspaces: A prospect workspace and a customer workspace will enable the company to segment and organize their programs based on their target audience, as well as to leverage their existing workspaces feature. Creating a naming convention that tags customer vs prospect campaigns will enable the company to standardize and identify their programs based on their purpose, as well as to facilitate reporting and analysis. Reducing the access for the demand generation manager and IT manager to a limited role that cannot create fields will enable the company to centralize and control their field management process, as well as to avoid field duplication or inconsistency.

References:

The way that the Marketo Engage Architect should approach the platform integration is to use Email Scripting for scenario 1 and REST API for scenario 2. These methods will help the Architect to automate and optimize the processes of cloning existing default programs, building emails using RSS feed, scheduling emails, deleting records on Marketo, and pushing data to Donor System. Using Email Scripting for scenario 1 will allow the Architect to dynamically generate email content based on the RSS feed of blog section, instead of manually creating email assets. Using REST API for scenario 2 will allow the Architect to programmatically delete records on Marketo and push data to Donor System, instead of relying on manual or offline methods.

References:

The two actions that the Marketo Engage Architect should recommend to meet these requirements are to create a webinar email asset in the program template that uses Velocity Scripting to populate region and industry and to create a regional webinar program template with a consistent naming convention. These actions will help the Architect to quickly scale the volume of webinars from once a month for North America to three times a month globally, as well as to vary the content of assets for different combinations of region and industry. Creating a webinar email asset in the program template that uses Velocity Scripting to populate region and industry will enable the Architect to dynamically insert content based on the lead’s region and industry segmentation fields, instead of creating separate email assets for each segment. Creating a regional webinar program template with a consistent naming convention will enable the Architect to easily clone and customize the program for each region, as well as to report on the results of each webinar at the global and regional level.

References: