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 efficient measure that should be taken to make sure leads from the right countries are synced to the correct queues in the CRM is to build program in each region workspace. When the score reaches 60, trigger the Salesforce sync and assign to lead queues based on country. For example, “If Country is USA, Assign to USA lead queue”. This measure will help the organization to improve its lead routing to its team across regions, as well as to use their new lead scoring to mark leads as MQLs. Building program in each region workspace will allow the organization to segment and target leads based on their region and country, as well as to leverage their existing workspaces and partitions. Triggering the Salesforce sync and assigning to lead queues based on country will allow the organization to sync leads that reach MQL status based on their score and assign them to the appropriate sales team queue in CRM.

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: