An Adobe Marketo Engage Consultant is assigned to audit an existing Marketo Engage instance. The instance is 2 years old and follows a de-centralized model for program execution. Therefore, all marketers within the organization have been trained to operate and build in the Marketo Engage instance independently. During the audit, the consultant discovers:
1. Naming convention does not exist. Therefore, all program names are named arbitrarily.
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 one workspace for the entire instance. However, 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. Ability to pull quick reports for prospect programs and customer programs from a reporting tool like Tableau.
2. Change the operating model from de-centralized to centralized so the marketing operations manager and CRM administrator are the only two people managing the operational side of the Marketo Engage instance and a new agency will manage the campaign execution on the behalf of marketing.
Which three recommendations should the Consultant make? (Choose three.)
Building two Custom Objects, one called ''Products'' and one called ''Services'' to link onto Person with relevant fields is the best way to push the data into Marketo Engage. This way, you can store multiple records of products and services for each person, and use an Email Scripting token in the email to personalize it for each recipient. Syncing this data on the ''Person'' level in a number of fields for ''Product'' or ''Service'' would limit the number of products and services you can store for each person, and would require building Segmentations for Product and Service and adding Segments into the Email as Dynamic content for personalization. Creating a maximum of 3 fields for each piece of data for both Products and Services onto the ''Person'' level would also limit the number of products and services you can store for each person, and would require adding each field into Email Scripting tokens then use to turn the module on or off if they have less than 3 products.
Currently there are no comments in this discussion, be the first to comment!