QuestionQ26

VerifiedSection 4: Advanced Marketo Governance

An Adobe Marketo Engage Consultant has been assigned to audit an existing Marketo Engage instance. The instance is two years old and follows a de-centralized model for program execution, meaning all marketers in the organization have been trained to operate and build in the instance independently.

During the audit, the consultant discovers the following:

  1. No naming convention exists, so all program names are arbitrary.
  2. There are four Marketo Engage Admins — the marketing operations manager, the demand generation manager, the CRM administrator, and the IT manager. All four admins have access to everything and have been creating fields on their own to fit individual business needs.
  3. There is only one workspace for the entire instance, even though the company has paid for additional workspaces.
  4. There are two Revenue Lifecycle Models: a prospect lifecycle and a customer lifecycle.

The CMO wants to prioritize the following goals:

  1. The ability to pull quick reports for prospect programs and customer programs from a reporting tool such as Tableau.
  2. Changing the operating model from de-centralized to centralized, so that the marketing operations manager and the CRM administrator are the only two people managing the operational side of the Marketo Engage instance, while a new agency manages campaign execution on behalf of marketing.

Which three recommendations should the consultant make?

Choose three
Explanation

Splitting the instance into a prospect workspace and a customer workspace mirrors the two existing Revenue Lifecycle Models and gives structural separation of assets for the two audience types. Pairing this with a naming convention that explicitly tags each program or campaign as prospect or customer allows an external reporting tool such as Tableau to quickly filter and report on prospect versus customer activity, since such tools typically query by naming/attribute values rather than by folder or workspace location alone. To centralize governance so that only the marketing operations manager and CRM administrator control the operational side of the instance, the demand generation manager and IT manager (who had been creating custom fields independently, causing field sprawl and inconsistency) need to have their roles reduced to a limited permission set that removes field-creation rights, using Marketo Engage's granular role-based permission model (e.g., removing 'Access Field Management' access) rather than granting them broader admin rights.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!