Refer to the case study.
UNICORN FINTECH COMPANY PROFILE
Unicorn Fintech is a mobile-only financial-services startup created by a consortium of consumer banks to resell savings, checking, loan, transfer/remittance, and other services from a secure smartphone app. The company is venture-funded, and plans to reach profitability before a planned IPO in two years.
Business issues and requirements
Marketing is responsible for acquiring new customers 0 through online, television advertising, and email campaigns, and for cross-selling new services to customers through IM, email, and in-app campaigns. Evaluating the success of these campaigns has been a persistent problem: although the company can track revenue by product line, it can’t attribute those revenues to campaigns: for example, did a new loan come from onboarding a new customer, or by cross-selling a savings-account customer? Marketing currently uses crude, manual tools and guesswork to evaluate the quality and lifespan of new leads, and even the deliverability of emails in its external campaigns. As a result, the department can’t allocate spending to the most productive campaigns, or decide how much different touchpoints in multi-stage campaigns contribute to revenue. Operational processes to connect lead data to CRM and other databases are entirely manual.
Staffing and leadership
Unicorn has fewer than 200 employees, and roles aren’t always defined in traditional ways. Since customer acquisition and cross-selling are primarily through electronic channels, Marketing and IT roles especially often overlap. The traditional Sales role falls entirely to Marketing, and IT is responsible for the Salesforce CRM system, Google Analytics, and a handful of third-party integrations. The CMO and CIO work closely together on most initiatives, and budgets are typically project-driven rather than fixed annually. Individual contributors to Marketing campaigns include the Marketing Operations Manager, responsible for lead scoring and analytics. Key IT contacts include the CRM Administrator and Web Developer. Incidental contributors are the Corporate Attorney, who signs off on opt-in/out and DMARC policies.
Revenue sources
Unicorn earns commissions on financial services delivered by the banking consortium through its apps, including fixed finders’ fees for what the company calls "skips"-customers who initially engage with Unicorn, but then "skip" to receive services directly from a consortium bank. Unicorn needs to attribute revenue from these customers to its own campaigns; currently, it’s impossible to attribute ROI to individual campaigns, or provide documentation to claim commissions on "skips."
Current and aspirational marketing technology
Current Marketing technology consists of Marketable,an open-source lead management solution supported by a set of spreadsheets and scripts developed in-house. Marketable offers lead tracking and source attribution, but not multi-touch source attribution. Unicorn Fintech Marketing has difficulty linking the different stages of customer campaign journeys, and relies on scripts to translate Marketable’s "sales alerts" into next steps it could use in multi-touch campaigns. IT has worked out scripts to input Marketable qualified leads into Salesforce, but the system is brittle and often requires manual intervention.
Current campaign management processes
A typical email campaign:
• Addresses a purchased (for customer acquisition) or0 in-house (for cross-sell) list. Purchased lists range from 300,000 to 1.5 million addresses
• Is sent from multiple data centers in the US and Canada
• Includes an "unsubscribe" opt-out below the message
• Is static; there are no formula fields
• Uses no deliverability authentication, nor integration 0 with any email management platform.
All campaigns to date direct respondents to a single 0 landing page with the company’s "all markets" message. More sophisticated targeting is a high priority.
Current lead management and attribution
Unicorn’s lead-management process follows
Marketable’s "out of the box" defaults: lead evaluation levels 1 through 3, lifecycle stages "unqualified" and "qualified." The qualification processes are manual, and highly subjective: Marketing staff classify leads according to prospect email responses, including free-form comments. "Sales" followup is by email forms prompting higher levels of engagement. The company intends to phase out Marketable and replace spreadsheets and scripts with native features of whatever solution set it adopts.
Attribution processes are binary: response to a campaign email or web visit is rated a success if it results in a sale: there is no success rating assigned to TV ads that result in web visits, for example. Cost are not allocated to individual campaigns.
The Marketing department plans to expand outreach to social media (Facebook, Twitter, Instagram, in-house and third-party financial blogs), and wants to make sure it can assess the ROI of these channels, and the overall social media program.
Current governance processes
Currently, the Marketing department assigns content development and campaign management duties to team members on a campaign-by-campaign basis. All team members (and IT) have access to all assets and tools, which sometimes leads to duplication and conflicts. The CMO realizes that a more specialization will be necessary to support the social media campaigns, but hasn’t decided on the optimal organizational model.
Input of qualified leads from Marketable into
Salesforce is by manual cut-and-paste, assisted by scripts; inconsistency of input practices across Marketing team members is a known problem; individual members have their own "go-to" fields: where one member might check "TV ad" as Lead Source, another would put that in the comments field.
CMO
The CMO’s most important concerns are:
• The current solution has too many manual steps to scale with anticipated growth
• Without more sophisticated attribution, the company will overinvest in less productive campaigns, and underinvest in better ones
• In general, analytics integrations are manual, slow, and unreliable
• The current system completely misses "skips"-customers switching from the Unicorn app to consortium banks-an important source of revenue
• Documenting the value of Unicorn’s Marketing processes is essential to the success of the planned IPO, and millions of dollars in stock valuation hangs in the balance.
CIO
The CIO is concerned primarily with:
• The amount of time his team spends patching up Marketing campaigns and CRM data transfers, at the expense of other, critical initiatives
• Quality and reliability of the Analytics information his team provides to Marketing
MARKETING STAFF
Marketing Operations staff concerns:
• Campaigns require so much work that they can’t run as many of them as they need to
• Multi-touch cross-selling campaigns (for example, savings accounts to loans) with excellent margins, but no way to know which campaign touches perform best
• Getting swamped with manual record-keeping; for example, spreadsheet mistakes take hours to find and
fix
• Poor integration with third-party tools for preparing, sending, and evaluating campaign materials, for
Example.
o Webhook not firing,
o Reaching API limit
o Synchronization errors with third-party tools and Salesforce
• Inadequate number of lead stages and qualification levels, making it difficult to evaluate lead value, especially in multi-touch campaigns
Despite the absence of an external Sales team,
Marketing Operations would like to improve the granularity of their lead tracking, including both lifecycle stages and quality levels, with "no score" and negative levels.
Unicorn Fintech is using Salesforce and Adobe Marketo Engage. They want to change their lead sync and lead routing rules for new leads that are generated through Marketo Engage forms. The Marketing Operations Manager needs to help them build new automation. Leads must reach a minimum lead score of 50 prior to being synced for Inside Sales to follow up. Prior to syncing to Salesforce, they want to make sure that each lead has a minimum data set of lead source and country. The Inside Sales Managers in each region cannot agree on a single global process for which leads should be assigned to which Inside Sales reps once the leads are created in Salesforce. They want the flexibility to decide at the country level.
What is the most appropriate, scalable process for the Marketing Operations Manager to build?
- A . Include country as a form field, use a hidden field to populate lead source, trigger the sync immediately, and assign to a country lead queue
- B . Include country as a form field, use a hidden field to populate lead source, trigger the sync when the person reaches 50 points, and assign to a country lead queue
- C . Use inferred data to populate the country field, use a hidden field to populate lead source, trigger the sync when the person reaches 50 points, and assign to an Inside Sales rep
- D . Use inferred data to populate the country and lead source fields, trigger the sync immediately, and assign directly to the Inside Sales Managers in each region
B
Explanation:
Including country as a form field, using a hidden field to populate lead
source, triggering the sync when the person reaches 50 points, and assigning to a country lead queue is the most appropriate, scalable process for the Marketing Operations Manager to build. This way, the process ensures that each lead has a minimum data set of lead source and country, that the lead score is high enough to indicate interest and readiness, and that the lead routing is flexible enough to accommodate different regional preferences. Using inferred data to populate the country field or the lead source field would not be reliable or accurate, as inferred data can be incorrect or missing. Triggering the sync immediately would not respect the lead score threshold of 50 points. Assigning to an Inside Sales rep or an Inside Sales Manager directly would not allow for flexibility or load balancing. Assigning to a country lead queue would allow for more control and visibility over the lead distribution
Refer to the case study.
UNICORN FINTECH COMPANY PROFILE
Unicorn Fintech is a mobile-only financial-servicesstartup created by a consortium of consumer banks to resell savings, checking, loan, transfer/remittance, and other services from a secure smartphone app. The company is venture-funded, and plans to reach profitability before a planned IPO in two years.
Business issues and requirements
Marketing is responsible for acquiring new customers 0 through online, television advertising, and email campaigns, and for cross-selling new services to customers through IM, email, and in-app campaigns. Evaluating the success of these campaigns has been a persistent problem: although the company can track revenue by product line, it can’t attribute those revenues to campaigns: for example, did a new loan come from onboarding a new customer, or by cross-selling a savings-account customer? Marketing currently uses crude, manual tools and guesswork to evaluate the quality and lifespan of new leads, and even the deliverability of emails in its external campaigns. As a result, the department can’t allocate spending to the most productive campaigns, or decide how much different touchpoints in multi-stage campaignscontribute to revenue. Operational processes to connect lead data to CRM and other databases are entirely manual.
Staffing and leadership
Unicorn has fewer than 200 employees, and roles aren’t always defined in traditional ways. Since customer acquisition and cross-selling are primarily through electronic channels, Marketing and IT roles especially often overlap. The traditional Sales role falls entirely to
Marketing, and IT is responsible for the Salesforce CRM system, Google Analytics, and a handful of third-party integrations. The CMO and CIO work closely together on most initiatives, and budgets are typically project-driven rather than fixed annually. Individual contributors to Marketing campaigns include the Marketing Operations Manager, responsible for lead scoring and analytics. Key IT contacts include the CRM Administrator and Web Developer. Incidental contributors are the Corporate Attorney, who signs off on opt-in/out and DMARC policies.
Revenue sources
Unicorn earns commissions on financial services delivered by the banking consortium through its apps, including fixed finders’ fees for what the company calls "skips"-customers who initially engage with Unicorn, but then "skip" to receive services directly from a consortium bank. Unicorn needs to attribute revenue from these customers to its own campaigns; currently, it’s impossible to attribute ROI to individual campaigns, or provide documentation to claim commissions on "skips."
Current and aspirational marketing technology
Current Marketing technology consists of Marketable,an open-source lead management solution supported by a set of spreadsheets and scripts developed in-house. Marketable offers lead tracking and source attribution, but not multi-touch source attribution. Unicorn Fintech Marketing has difficulty linking the different stages of customer campaign journeys, and relies on scripts to translate Marketable’s "sales alerts" into next steps it could use in multi-touch campaigns. IT has worked out scripts to input Marketable qualified leads into Salesforce, but the system is brittle and often requires manual intervention.
Current campaign management processes
A typical email campaign:
• Addresses a purchased (for customer acquisition) or0 in-house (for cross-sell) list. Purchased lists range from 300,000 to 1.5 million addresses
• Is sent from multiple data centers in the US and Canada
• Includes an "unsubscribe" opt-out below the message
• Is static; there are no formula fields
• Uses no deliverability authentication, nor integration 0 with any email management platform.
All campaigns to date direct respondents to a single 0 landing page with the company’s "all markets" message. More sophisticated targeting is a high priority.
Current lead management and attribution
Unicorn’s lead-management process follows
Marketable’s "out of the box" defaults: lead evaluation levels 1 through 3, lifecycle stages "unqualified" and "qualified." The qualification processes are manual, and highly subjective: Marketing staff classify leads according to prospect email responses, including free-form comments. "Sales" followup is by email forms prompting higher levels of engagement. The company intends to phase out Marketable and replace spreadsheets and scripts with native features of whatever solution set it adopts.
Attribution processes are binary: response to a campaign email or web visit is rated a success if it results in a sale: there is no success rating assigned to TV ads that result in web visits, for example. Cost are not allocated to individual campaigns.
The Marketing department plans to expand outreach to social media (Facebook, Twitter, Instagram, in-house and third-party financial blogs), and wants to make sure it can assess the ROI of these channels, and the overall social media program.
Current governance processes
Currently, the Marketing department assigns content development and campaign management duties to team members on a campaign-by-campaign basis. All team members (and IT) have access to all assets and tools, which sometimes leads to duplication and conflicts. The CMO realizes that a more specialization will be necessary to support the social media campaigns, but hasn’t decided on the optimal organizational model.
Input of qualified leads from Marketable into
Salesforce is by manual cut-and-paste, assisted by scripts; inconsistency of input practices across Marketing team members is a known problem; individual members have their own "go-to" fields: where one member might check "TV ad" as Lead Source, another would put that in the comments field.
CMO
The CMO’s most important concerns are:
• The current solution has too many manual steps to scale with anticipated growth
• Without more sophisticated attribution, the company will overinvest in less productive campaigns, and underinvest in better ones
• In general, analytics integrations are manual, slow, and unreliable
• The current system completely misses "skips"-customers switching from the Unicorn app to consortium banks-an important source of revenue
• Documenting the value of Unicorn’s Marketing processes is essential to the success of the planned IPO, and millions of dollars in stock valuation hangs in the balance.
CIO
The CIO is concerned primarily with:
• The amount of time his team spends patching up Marketing campaigns and CRM data transfers, at the expense of other, critical initiatives
• Quality and reliability of the Analytics information his team provides to Marketing
MARKETING STAFF
Marketing Operations staff concerns:
• Campaigns require so much work that they can’t run as many of them as they need to
• Multi-touch cross-selling campaigns (for example, savings accounts to loans) with excellent margins, but no way to know which campaign touches perform best
• Getting swamped with manual record-keeping; for example, spreadsheet mistakes take hours to find andfix
• Poor integration with third-party tools for preparing, sending, and evaluating campaign materials, for Example.
o Webhook not firing,
o Reaching API limit
o Synchronization errors with third-party tools and Salesforce
• Inadequate number of lead stages and qualification levels, making it difficult to evaluate lead value, especially in multi-touch campaigns
Despite the absence of an external Sales team,
Marketing Operations would like to improve the granularity of their lead tracking, including both lifecycle stages and quality levels, with "no score" and negative levels.
Some of Unicorn’s customers use their financial products and services. Marketing wants to roll out a "Weekly rollup" email to customers who are opted in for email. This email will show a quick snapshot of how each product/service those customers have with Unicorn perform.
The data to send these emails must be set up to sync to the Adobe Marketo Engage instance for each customer. Each customer can own multiple of the same product, or a number of products/services.
How should this data be pushed into Marketo Engage to be used most effectively?
- A . Sync this data on the "Person’ Level in a number of fields for "Product" or "Service" Build Segmentations for Product and Service
Add Segments into the Email as Dynamic content for personalization - B . Create a maximum of 3 fields for each piece of data for both Products and Services onto the "Person" Level
Add each field into Email Scripting tokens then use to turn the module on or off if they have less than 3 products - C . Build two Custom Objects, one called "Products" and one called "Services" to link onto Person with relevant fields
Use an Email Scripting token in the email so it can be personalized for each email recipient
C
Explanation:
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.
https://nation.marketo.com/t5/product-blogs/custom-objects-best-practices-tips-and-tricks/ba-p/244199
A company has a meeting with a third party that wants to begin submitting leads captured through various channels. These leads are aware that the third party will share their information with the company and have provided consent through their engagement. The third party will send the leads through a REST API.
Which steps should the Adobe Marketo Engage Architect take to make sure that the REST API is set up correctly?
- A . Create API User Role, Use an existing API User, Create new Launchpoint Service, Run a Call test with Identity and Endpoint
- B . Create API User Role, Create a new API User, Create new Launchpoint Service, Run a Call test with Identity and Endpoint
- C . Create API User Role, Create a new API User, Create new Launchpoint Service, Run a Call test with Token and Endpoint
- D . Create API User Role, Use an existing API User, Create new Launchpoint Service, Run a Call test with Token and Identity
B
Explanation:
The steps that the Adobe Marketo Engage Architect should take to make sure that the REST API is set up correctly are to create API User Role, create a new API User, create new Launchpoint Service, and run a Call test with Identity and Endpoint. These steps will allow the Architect to configure and test the REST API integration with Marketo Engage. Creating API User Role will enable the Architect to define the permissions and access level for the API User. Creating a new API User will enable the Architect to generate a unique Client ID and Client Secret for authentication. Creating new Launchpoint Service will enable the Architect to register and manage the third-party service in Marketo Engage. Running a Call test with Identity and Endpoint will enable the Architect to verify that the API calls are working properly and that leads can be submitted through various channels.
References:
https://developers.marketo.com/rest-api/
https://docs.marketo.com/display/public/DOCS/Create+an+API+Only+User+Role
https://docs.marketo.com/display/public/DOCS/Create+a+Custom+Service
https://docs.marketo.com/display/public/DOCS/Webhooks
A company has a Contact Us form that contains a text field called "Comments" where prospects describe their needs to provide sales with context for follow-up. When this form is completed, a Marketing Qualified Lead (MQL) is generated and sent to sales. The "Comments" field is a custom text field. Leads often write lengthy descriptions that exceed 140 characters. The "Comments" field is not synced to CRM. Another field called "Notes" is synced to CRM. This is also a text field. The "Notes" field is often used by Sales and is commonly overwritten by Sales. Both Sales and Marketing agree that the "Comments" field is important and want to give the prospect space to describe their needs.
An Adobe Marketo Engage Architect needs to set up an interesting moment that is triggered upon the Contact Us form fill that contains the "Comments" value to give Sales immediate context of the inquiry.
Which two actions must the Marketo Engage Architect take to fulfill this request? (Choose
two.)
Which two actions must the Marketo Engage Architect take to fulfill this request? (Choose two.)
- A . Use a token in the Interesting Moment to populate info from the "Comments" field
- B . Change the "Comments" field type from text to string to capture longer comments
- C . Have Marketo Support re-map the "Comments" field in Marketo to the "Notes" CRM field
- D . Create the "Comments" field in CRM, sync it to Marketo, and have Marketo Support remap it
- E . Switch the field mapping on the Marketo form from "Comments" to "Notes"
A,D
Explanation:
The two actions that the Marketo Engage Architect must take to fulfill this request are to use a token in the Interesting Moment to populate info from the “Comments” field and to create the “Comments” field in CRM, sync it to Marketo, and have Marketo Support remap it. These actions will allow the Architect to set up an interesting moment that is triggered upon the Contact Us form fill that contains the “Comments” value to give Sales immediate context of the inquiry. Using a token in the Interesting Moment will enable the Architect to dynamically insert the value of the “Comments” field into the interesting moment description. Creating the “Comments” field in CRM, syncing it to Marketo, and having Marketo Support remap it will enable the Architect to preserve the value of the “Comments” field in both systems and avoid overwriting the “Notes” field that is used by Sales.
References:
https://docs.marketo.com/display/public/DOCS/Interesting+Moments
https://docs.marketo.com/display/public/DOCS/Use+Tokens+in+Interesting+Moments
https://docs.marketo.com/display/public/DOCS/Field+Mapping
The VP of Marketing is concerned about the workload of the marketing team and wants to hire an agency to assist the team by building campaigns and programs within their Adobe Marketo Engage instance. The biggest concern is adding users who may be able to access and accidentally break established templates, nurture campaigns, and scoring. Therefore, the users will only be able to work in the Marketing Activities area.
The agency will have access to building programs, campaigns, emails, and landing pages.
What is the best set of user role permissions for the agency users?
- A . Web Campaign Editor, Access Email, Activate Trigger Campaign, Clone Marketing Asset
- B . Edit Marketing Asset, Edit Campaign, Activate Trigger Campaign, Clone Marketing Asset
- C . Access Email, Access Landing Page, Web Campaign Editor, Edit Marketing Asset
- D . Edit Marketing Asset, Access Email, Access Landing Page, Export Analytics Data
A company has the native Adobe Marketo Engage sync with Microsoft Dynamics in place. The business consistently exceed their database limits. It needs to limit database growth and remove certain records from Marketo Engage.
Which two actions should the Marketing Operations team recommend to solve this issue? (Choose two.)
- A . Delete any Leads or Contacts from Marketo Engage in the sync with no email address or invalid ‘-‘ email address
- B . Work with the Dynamics CRM admin to hide certain records that should not be in the sync using ‘-‘ the Dynamics "inactive" functionality
- C . Design an inactive monitoring process using scoring and have them removed from the sync by ‘-‘ Dynamics using the Custom Sync Filter functionality
- D . Block unwanted Leads and Contacts from the sync based on a set criteria using the Custom *-* Sync Filter functionality
- E . Block inactive Leads and Contacts from the sync using the Custom Sync Filter functionality
A,D
Explanation:
The two actions that the Marketing Operations team should recommend to solve this issue are to delete any Leads or Contacts from Marketo Engage in the sync with no email address or invalid ‘-’ email address and to block unwanted Leads and Contacts from the sync based on a set criteria using the Custom – Sync Filter functionality. This is because these actions will help limit database growth and remove certain records from Marketo Engage by eliminating records that are not valid or useful for marketing purposes
and preventing records that do not meet certain criteria from being synced. The other options are not as effective as these two, because they either rely on Dynamics functionality that may not be available or consistent, or they do not address the issue of database limits.
References:
https://docs.marketo.com/display/public/DOCS/Microsoft+Dynamics+Sync%3A+Overview
https://docs.marketo.com/display/public/DOCS/Custom+Sync+Filter
An Adobe Marketo Engage Consultant is reviewing all programs in an instance.
Each campaign in each program contains at least three flow steps:
• If Acquisition Program is Empty, change Acquisition Program to the current program’s name
• Change the status in the program (based on the action)
• Write an Interesting Moment
These flow steps happen in almost every campaign.
How can the Consultant edit the programs for scalability and efficiency?
- A . Create global Interesting Moments campaigns based on specific triggers and using tokens
- B . Create a global program and coordinating campaigns to update the acquisition program to the latest program touched
- C . Remove the program status change because this will be handled by the Acquisition Program update
A
Explanation:
This would allow you to manage Interesting Moments centrally rather than having to repeat the same flow steps in multiple campaigns. By using tokens, you can easily change the content of Interesting Moments based on the specific trigger without having to manually edit the flow step in each campaign.
Tokens are pieces of code that represent a certain value, such as the name of a program or the date of an event. When the campaign runs, the token will be replaced with the actual value it represents, which can change dynamically based on the context.
Moreover, to handle the acquisition program and program status update tasks efficiently, it would be better to do these tasks in the specific campaigns where the lead first interacts rather than in every campaign. This would reduce the amount of redundant processing in the system.
Note: While option B – Create a global program and coordinating campaigns to update the acquisition program to the latest program touched, seems to provide scalability, it does not align with Marketo’s recommended best practices. The acquisition program should be the first program that resulted in the person being created in Marketo and should not be updated to the latest program touched. This allows you to track the initial source of the lead effectively.
An enterprise software company sells its products directly to its B2B customers but also sells their product through third-party sellers. The company runs marketing campaigns directly to their B2B target audience. They also provide funds to the third-party sellers to run campaigns on the company’s behalf. In return, the leads and engagement are provided by the third-party seller when a campaign is complete. Any data must be passed to Salesforce due to reporting being done in Salesforce.
Programs and channels should be set up to report on the efficacy of direct marketing and investment to third-party seller/partner marketing to determine how budget should be spent the following year.
How should this requirement be met?
- A . Two sets of event based channels should be created: one set for direct marketing and the otherfor third-party seller marketing
- B . One set of channels should be created, and separate program statuses should be used to designate Direct or Partner
- C . One set of channels should be created, and a tag should be used to determine Direct or Partner
A
Explanation:
This approach would allow the company to separately track and report on the performance of its direct marketing campaigns and those run by third-party sellers. Each channel would have its own progression statuses, allowing the company to define specific stages in the customer journey for both types of campaigns. This level of granularity can provide a better understanding of where leads are coming from and how they’re interacting with the marketing efforts, whether it’s direct or through third-party sellers.
In Marketo, channels define the progression statuses that leads can achieve as they interact with your campaigns. Creating separate channels for direct and third-party seller marketing would mean you can customize these statuses for each type of marketing, giving you more accurate data on how your campaigns are performing.
Remember that using different channels for different types of marketing efforts is a best practice in Marketo as it allows for better organization, reporting, and analysis of your marketing activities. Channels provide a way to categorize your programs based on the tactics and goals used, and they help you track the success of these different tactics in achieving your marketing goals.
Refer to the case study.
UNICORN FINTECH COMPANY PROFILE
Unicorn Fintech is a mobile-only financial-services startup created by a consortium of consumer banks to resell savings, checking, loan, transfer/remittance, and other services from a secure smartphone app. The company is venture-funded, and plans to reach profitability before a planned IPO in two years.
Business issues and requirements
Marketing is responsible for acquiring new customers 0 through online, television advertising, and email campaigns, and for cross-selling new services to customers through IM, email, and in-app campaigns. Evaluating the success of these campaigns has been a persistent problem: although the company can track revenue by product line, it can’t attribute those revenues to campaigns: for example, did a new loan come from onboarding a new customer, or by cross-selling a savings-account customer? Marketing currently uses crude, manual tools and guesswork to evaluate the quality and lifespan of new leads, and even the deliverability of emails in its external campaigns. As a result, the department can’t allocate spending to the most productive campaigns, or decide how much different touchpoints in multi-stage campaigns contribute to revenue. Operational processes to connect lead data to CRM and other databases are entirely manual.
Staffing and leadership
Unicorn has fewer than 200 employees, and roles aren’t always defined in traditional ways. Since customer acquisition and cross-selling are primarily through electronic channels, Marketing and IT roles especially often overlap. The traditional Sales role falls entirely to Marketing, and IT is responsible for the Salesforce CRM system, Google Analytics, and a handful of third-party integrations. The CMO and CIO work closely together on most initiatives, and budgets are typically project-driven rather than fixed annually. Individual contributors to Marketing campaigns include the Marketing Operations Manager, responsible for lead scoring and analytics. Key IT contacts include the CRM Administrator and Web Developer. Incidental contributors are the Corporate Attorney, who signs off on opt-in/out and DMARC policies.
Revenue sources
Unicorn earns commissions on financial services delivered by the banking consortium through its apps, including fixed finders’ fees for what the company calls "skips"-customers who initially engage with Unicorn, but then "skip" to receive services directly from a consortium bank. Unicorn needs to attribute revenue from these customers to its own campaigns; currently, it’s impossible to attribute ROI to individual campaigns, or provide documentation to claim commissions on "skips."
Current and aspirational marketing technology
Current Marketing technology consists of Marketable,an open-source lead management solution supported by a set of spreadsheets and scripts developed in-house. Marketable offers lead tracking and source attribution, but not multi-touch source attribution. Unicorn Fintech Marketing has difficulty linking the different stages of customer campaign journeys, and relies on scripts to translate Marketable’s "sales alerts" into next steps it could use in multi-touch campaigns. IT has worked out scripts to input Marketable qualified leads into Salesforce, but the system is brittle and often requires manual intervention.
Current campaign management processes
A typical email campaign:
• Addresses a purchased (for customer acquisition) or0 in-house (for cross-sell) list. Purchased lists range from 300,000 to 1.5 million addresses
• Is sent from multiple data centers in the US and Canada
• Includes an "unsubscribe" opt-out below the message
• Is static; there are no formula fields
• Uses no deliverability authentication, nor integration 0 with any email management platform.
All campaigns to date direct respondents to a single 0 landing page with the company’s "all markets" message. More sophisticated targeting is a high priority.
Current lead management and attribution
Unicorn’s lead-management process follows
Marketable’s "out of the box" defaults: lead evaluation levels 1 through 3, lifecycle stages "unqualified" and "qualified." The qualification processes are manual, and highly subjective: Marketing staff classify leads according to prospect email responses, including free-form comments. "Sales" followup is by email forms prompting higher levels of engagement. The company intends to phase out Marketable and replace spreadsheets and scripts with native features of whatever solution set it adopts.
Attribution processes are binary: response to a campaign email or web visit is rated a success if it results in a sale: there is no success rating assigned to TV ads that result in web visits, for example. Cost are not allocated to individual campaigns.
The Marketing department plans to expand outreach to social media (Facebook, Twitter, Instagram, in-house and third-party financial blogs), and wants to make sure it can assess the ROI of these channels, and the overall social media program.
Current governance processes
Currently, the Marketing department assigns content development and campaign management duties to team members on a campaign-by-campaign basis. All team members (and IT) have access to all assets and tools, which sometimes leads to duplication and conflicts. The CMO realizes that a more specialization will be necessary to support the social media campaigns, but hasn’t decided on the optimal organizational model.
Input of qualified leads from Marketable into
Salesforce is by manual cut-and-paste, assisted by scripts; inconsistency of input practices across Marketing team members is a known problem; individual members have their own "go-to" fields: where one member might check "TV ad" as Lead Source, another would put that in the comments field.
CMO
The CMO’s most important concerns are:
• The current solution has too many manual steps to scale with anticipated growth
• Without more sophisticated attribution, the company will overinvest in less productive campaigns, and underinvest in better ones
• In general, analytics integrations are manual, slow, and unreliable
• The current system completely misses "skips"-customers switching from the Unicorn app to consortium banks-an important source of revenue
• Documenting the value of Unicorn’s Marketing processes is essential to the success of the planned IPO, and millions of dollars in stock valuation hangs in the balance.
CIO
The CIO is concerned primarily with:
• The amount of time his team spends patching up Marketing campaigns and CRM data transfers, at the expense of other, critical initiatives
• Quality and reliability of the Analytics information his team provides to Marketing
MARKETING STAFF
Marketing Operations staff concerns:
• Campaigns require so much work that they can’t run as many of them as they need to
• Multi-touch cross-selling campaigns (for example, savings accounts to loans) with excellent margins, but no way to know which campaign touches perform best
• Getting swamped with manual record-keeping; for example, spreadsheet mistakes take hours to find and fix
• Poor integration with third-party tools for preparing, sending, and evaluating campaign materials, for Example.
o Webhook not firing,
o Reaching API limit
o Synchronization errors with third-party tools and Salesforce
• Inadequate number of lead stages and qualification levels, making it difficult to evaluate lead value, especially in multi-touch campaigns
Despite the absence of an external Sales team,
Marketing Operations would like to improve the granularity of their lead tracking, including both lifecycle stages and quality levels, with "no score" and negative levels.
Unicorn Fintech launches a new paid subscription app where users can sign up to read financial advice. Access to Unicorn Fintech’s new app is renewed each year, and the App User Expiry Date is a date field that is updated hourly from CRM to Adobe Marketo Engage. Another string type field called App User Status changes to a status of "Current" in Marketo Engage when the App User’s access becomes valid, and changes to "Lapsed" if the App User fails to renew.
The Marketing team wants to add App Users who have not yet renewed to an Engagement Program to nurture them 2 months prior to their App User Expiry Date, and then remove the App User from the nurture if they renew.
Which smart campaign setup is the most efficient to manage adding the App User to the nurture?
- A . Build a scheduled batch Smart Campaign, use a Wait Step with a Date Token, and then Add to Engagement Program
- B . Build a scheduled batch Smart Campaign, use a Wait Step with a specific date, and then Change Engagement Program Cadence
- C . Build a triggered Smart Campaign, use a Wait Step with a Date Token, and then Add to Engagement Program
- D . Build a triggered Smart Campaign, use a Wait Step with a specific date, and then Change Engagement Program Cadence
C
Explanation:
Building a triggered Smart Campaign, using a Wait Step with a Date Token, and then Add to Engagement Program is the most efficient way to manage adding the App User to the nurture. This way, the Smart Campaign will trigger whenever the App User Status changes to “Lapsed”, and then wait until two months before the App User Expiry Date to add the App User to the Engagement Program. Building a scheduled batch Smart Campaign would require running the Smart Campaign periodically to check for new App Users who have not renewed, which is less efficient. Using a Wait Step with a specific date would not work for different App Users who have different expiry dates. Changing Engagement Program Cadence would not add or remove the App User from the nurture.
An Adobe Marketo Engage Architect is integrating a Marketo Engage instance for a nonprofit client with two different third-party platforms.
The requirements are outlined below:
Scenario 1: Automatically clone existing default programs on Marketo, build the email using the RSS feed of blog section, and schedule the email on every Thursday.
Scenario 2: Before deleting any record on Marketo, push the data to "Donor System".
How should the Marketo Engage Architect approach the platform integration?
- A . Scenario 1 – Use Webhook and Scenario 2 – Use REST API
- B . Scenario 1 – Use Email Scripting and Scenario 2 – Use REST API
- C . Scenario 1 – Use JavaScript API and Scenario 2 – Use REST API
- D . Scenario 1 – Use REST API and Scenario 2 – Use Webhook
B
Explanation:
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:
https://docs.marketo.com/display/public/DOCS/Email+Scripting
https://developers.marketo.com/rest-api/
An Adobe Marketo Engage Consultant is assigned to audit an existing Marketo Engage instance. This is a 10-year-old instance. Due to high turnover within the Marketing Operations team, the team does not have the MQL assignment process documented. Marketing Operations does not have access to Salesforce. The sales team reports that they receive only 10 MQLs in a week. The Marketing team shows on average 50 MQLs in a week. The Sales team members do not get any MQL alert from Marketo Engage. They see the lead assignment only when the leads are assigned to "Sales Queue" on Salesforce. The Marketo Engage sync on Salesforce is properly configured and has write access to all standard objects and fields.
While auditing Marketo Engage instance, the consultant finds the following issues:
• An average 40 leads are getting graduated to MQLs but not syncing with Salesforce. These records are already in Salesforce’s lead object and belong to Hospitality Industry.
• The web-message field on the Marketo Engage form is not getting updated to Salesforce’s Lead and Contact objects. The Marketo Engage Sync user has read and write access to "Web-Message" field on Lead, Contact, and Account objects.
Which two steps should the consultant perform to find the root cause? (Choose two.)
- A . Check if Marketo’s Custom Object is in place
- B . Check if the Web-Message form field is mapped to Account object
- C . Check if the Custom Activities are configured properly
- D . Check if the Behavior Scoring is configured properly
- E . Check if the Custom Sync Rule is in place
B,E
Explanation:
The two steps that the consultant should perform to find the root cause are to check if the Web-Message form field is mapped to Account object and to check if the Custom Sync Rule is in place. These steps will help the consultant to identify and resolve the issues that are causing leads not syncing with Salesforce or fields not getting updated.
Checking if the Web-Message form field is mapped to Account object will help the consultant to verify that the field mapping is correct and consistent between Marketo Engage and Salesforce, as well as between Lead, Contact, and Account objects. Checking if the Custom Sync Rule is in place will help the consultant to verify that there are no filters or conditions that are blocking leads from syncing with Salesforce based on their industry or other criteria.
References:
https://docs.marketo.com/display/public/DOCS/Salesforce+Sync%3A+Overview
https://docs.marketo.com/display/public/DOCS/Field+Mapping
https://docs.marketo.com/display/public/DOCS/Custom+Sync+Filter
An Adobe Marketo Engage Consultant is assigned to audit an existing Marketo Engage instance. This is a 10-year-old instance. Due to high turnover within the Marketing Operations team, the team does not have the MQL assignment process documented. Marketing Operations does not have access to Salesforce. The sales team reports that they receive only 10 MQLs in a week. The Marketing team shows on average 50 MQLs in a week. The Sales team members do not get any MQL alert from Marketo Engage. They see the lead assignment only when the leads are assigned to "Sales Queue" on Salesforce. The Marketo Engage sync on Salesforce is properly configured and has write access to all standard objects and fields.
While auditing Marketo Engage instance, the consultant finds the following issues:
• An average 40 leads are getting graduated to MQLs but not syncing with Salesforce. These records are already in Salesforce’s lead object and belong to Hospitality Industry.
• The web-message field on the Marketo Engage form is not getting updated to Salesforce’s Lead and Contact objects. The Marketo Engage Sync user has read and write access to "Web-Message" field on Lead, Contact, and Account objects.
Which two steps should the consultant perform to find the root cause? (Choose two.)
- A . Check if Marketo’s Custom Object is in place
- B . Check if the Web-Message form field is mapped to Account object
- C . Check if the Custom Activities are configured properly
- D . Check if the Behavior Scoring is configured properly
- E . Check if the Custom Sync Rule is in place
B,E
Explanation:
The two steps that the consultant should perform to find the root cause are to check if the Web-Message form field is mapped to Account object and to check if the Custom Sync Rule is in place. These steps will help the consultant to identify and resolve the issues that are causing leads not syncing with Salesforce or fields not getting updated.
Checking if the Web-Message form field is mapped to Account object will help the consultant to verify that the field mapping is correct and consistent between Marketo Engage and Salesforce, as well as between Lead, Contact, and Account objects. Checking if the Custom Sync Rule is in place will help the consultant to verify that there are no filters or conditions that are blocking leads from syncing with Salesforce based on their industry or other criteria.
References:
https://docs.marketo.com/display/public/DOCS/Salesforce+Sync%3A+Overview
https://docs.marketo.com/display/public/DOCS/Field+Mapping
https://docs.marketo.com/display/public/DOCS/Custom+Sync+Filter
An Adobe Marketo Engage Consultant is assigned to audit an existing Marketo Engage instance. This is a 10-year-old instance. Due to high turnover within the Marketing Operations team, the team does not have the MQL assignment process documented. Marketing Operations does not have access to Salesforce. The sales team reports that they receive only 10 MQLs in a week. The Marketing team shows on average 50 MQLs in a week. The Sales team members do not get any MQL alert from Marketo Engage. They see the lead assignment only when the leads are assigned to "Sales Queue" on Salesforce. The Marketo Engage sync on Salesforce is properly configured and has write access to all standard objects and fields.
While auditing Marketo Engage instance, the consultant finds the following issues:
• An average 40 leads are getting graduated to MQLs but not syncing with Salesforce. These records are already in Salesforce’s lead object and belong to Hospitality Industry.
• The web-message field on the Marketo Engage form is not getting updated to Salesforce’s Lead and Contact objects. The Marketo Engage Sync user has read and write access to "Web-Message" field on Lead, Contact, and Account objects.
Which two steps should the consultant perform to find the root cause? (Choose two.)
- A . Check if Marketo’s Custom Object is in place
- B . Check if the Web-Message form field is mapped to Account object
- C . Check if the Custom Activities are configured properly
- D . Check if the Behavior Scoring is configured properly
- E . Check if the Custom Sync Rule is in place
B,E
Explanation:
The two steps that the consultant should perform to find the root cause are to check if the Web-Message form field is mapped to Account object and to check if the Custom Sync Rule is in place. These steps will help the consultant to identify and resolve the issues that are causing leads not syncing with Salesforce or fields not getting updated.
Checking if the Web-Message form field is mapped to Account object will help the consultant to verify that the field mapping is correct and consistent between Marketo Engage and Salesforce, as well as between Lead, Contact, and Account objects. Checking if the Custom Sync Rule is in place will help the consultant to verify that there are no filters or conditions that are blocking leads from syncing with Salesforce based on their industry or other criteria.
References:
https://docs.marketo.com/display/public/DOCS/Salesforce+Sync%3A+Overview
https://docs.marketo.com/display/public/DOCS/Field+Mapping
https://docs.marketo.com/display/public/DOCS/Custom+Sync+Filter
An Adobe Marketo Engage Consultant is assigned to audit an existing Marketo Engage instance. This is a 10-year-old instance. Due to high turnover within the Marketing Operations team, the team does not have the MQL assignment process documented. Marketing Operations does not have access to Salesforce. The sales team reports that they receive only 10 MQLs in a week. The Marketing team shows on average 50 MQLs in a week. The Sales team members do not get any MQL alert from Marketo Engage. They see the lead assignment only when the leads are assigned to "Sales Queue" on Salesforce. The Marketo Engage sync on Salesforce is properly configured and has write access to all standard objects and fields.
While auditing Marketo Engage instance, the consultant finds the following issues:
• An average 40 leads are getting graduated to MQLs but not syncing with Salesforce. These records are already in Salesforce’s lead object and belong to Hospitality Industry.
• The web-message field on the Marketo Engage form is not getting updated to Salesforce’s Lead and Contact objects. The Marketo Engage Sync user has read and write access to "Web-Message" field on Lead, Contact, and Account objects.
Which two steps should the consultant perform to find the root cause? (Choose two.)
- A . Check if Marketo’s Custom Object is in place
- B . Check if the Web-Message form field is mapped to Account object
- C . Check if the Custom Activities are configured properly
- D . Check if the Behavior Scoring is configured properly
- E . Check if the Custom Sync Rule is in place
B,E
Explanation:
The two steps that the consultant should perform to find the root cause are to check if the Web-Message form field is mapped to Account object and to check if the Custom Sync Rule is in place. These steps will help the consultant to identify and resolve the issues that are causing leads not syncing with Salesforce or fields not getting updated.
Checking if the Web-Message form field is mapped to Account object will help the consultant to verify that the field mapping is correct and consistent between Marketo Engage and Salesforce, as well as between Lead, Contact, and Account objects. Checking if the Custom Sync Rule is in place will help the consultant to verify that there are no filters or conditions that are blocking leads from syncing with Salesforce based on their industry or other criteria.
References:
https://docs.marketo.com/display/public/DOCS/Salesforce+Sync%3A+Overview
https://docs.marketo.com/display/public/DOCS/Field+Mapping
https://docs.marketo.com/display/public/DOCS/Custom+Sync+Filter
An Adobe Marketo Engage Consultant is assigned to audit an existing Marketo Engage instance. This is a 10-year-old instance. Due to high turnover within the Marketing Operations team, the team does not have the MQL assignment process documented. Marketing Operations does not have access to Salesforce. The sales team reports that they receive only 10 MQLs in a week. The Marketing team shows on average 50 MQLs in a week. The Sales team members do not get any MQL alert from Marketo Engage. They see the lead assignment only when the leads are assigned to "Sales Queue" on Salesforce. The Marketo Engage sync on Salesforce is properly configured and has write access to all standard objects and fields.
While auditing Marketo Engage instance, the consultant finds the following issues:
• An average 40 leads are getting graduated to MQLs but not syncing with Salesforce. These records are already in Salesforce’s lead object and belong to Hospitality Industry.
• The web-message field on the Marketo Engage form is not getting updated to Salesforce’s Lead and Contact objects. The Marketo Engage Sync user has read and write access to "Web-Message" field on Lead, Contact, and Account objects.
Which two steps should the consultant perform to find the root cause? (Choose two.)
- A . Check if Marketo’s Custom Object is in place
- B . Check if the Web-Message form field is mapped to Account object
- C . Check if the Custom Activities are configured properly
- D . Check if the Behavior Scoring is configured properly
- E . Check if the Custom Sync Rule is in place
B,E
Explanation:
The two steps that the consultant should perform to find the root cause are to check if the Web-Message form field is mapped to Account object and to check if the Custom Sync Rule is in place. These steps will help the consultant to identify and resolve the issues that are causing leads not syncing with Salesforce or fields not getting updated.
Checking if the Web-Message form field is mapped to Account object will help the consultant to verify that the field mapping is correct and consistent between Marketo Engage and Salesforce, as well as between Lead, Contact, and Account objects. Checking if the Custom Sync Rule is in place will help the consultant to verify that there are no filters or conditions that are blocking leads from syncing with Salesforce based on their industry or other criteria.
References:
https://docs.marketo.com/display/public/DOCS/Salesforce+Sync%3A+Overview
https://docs.marketo.com/display/public/DOCS/Field+Mapping
https://docs.marketo.com/display/public/DOCS/Custom+Sync+Filter
An Adobe Marketo Engage Consultant is assigned to audit an existing Marketo Engage instance. This is a 10-year-old instance. Due to high turnover within the Marketing Operations team, the team does not have the MQL assignment process documented. Marketing Operations does not have access to Salesforce. The sales team reports that they receive only 10 MQLs in a week. The Marketing team shows on average 50 MQLs in a week. The Sales team members do not get any MQL alert from Marketo Engage. They see the lead assignment only when the leads are assigned to "Sales Queue" on Salesforce. The Marketo Engage sync on Salesforce is properly configured and has write access to all standard objects and fields.
While auditing Marketo Engage instance, the consultant finds the following issues:
• An average 40 leads are getting graduated to MQLs but not syncing with Salesforce. These records are already in Salesforce’s lead object and belong to Hospitality Industry.
• The web-message field on the Marketo Engage form is not getting updated to Salesforce’s Lead and Contact objects. The Marketo Engage Sync user has read and write access to "Web-Message" field on Lead, Contact, and Account objects.
Which two steps should the consultant perform to find the root cause? (Choose two.)
- A . Check if Marketo’s Custom Object is in place
- B . Check if the Web-Message form field is mapped to Account object
- C . Check if the Custom Activities are configured properly
- D . Check if the Behavior Scoring is configured properly
- E . Check if the Custom Sync Rule is in place
B,E
Explanation:
The two steps that the consultant should perform to find the root cause are to check if the Web-Message form field is mapped to Account object and to check if the Custom Sync Rule is in place. These steps will help the consultant to identify and resolve the issues that are causing leads not syncing with Salesforce or fields not getting updated.
Checking if the Web-Message form field is mapped to Account object will help the consultant to verify that the field mapping is correct and consistent between Marketo Engage and Salesforce, as well as between Lead, Contact, and Account objects. Checking if the Custom Sync Rule is in place will help the consultant to verify that there are no filters or conditions that are blocking leads from syncing with Salesforce based on their industry or other criteria.
References:
https://docs.marketo.com/display/public/DOCS/Salesforce+Sync%3A+Overview
https://docs.marketo.com/display/public/DOCS/Field+Mapping
https://docs.marketo.com/display/public/DOCS/Custom+Sync+Filter
An Adobe Marketo Engage Consultant is assigned to audit an existing Marketo Engage instance. This is a 10-year-old instance. Due to high turnover within the Marketing Operations team, the team does not have the MQL assignment process documented. Marketing Operations does not have access to Salesforce. The sales team reports that they receive only 10 MQLs in a week. The Marketing team shows on average 50 MQLs in a week. The Sales team members do not get any MQL alert from Marketo Engage. They see the lead assignment only when the leads are assigned to "Sales Queue" on Salesforce. The Marketo Engage sync on Salesforce is properly configured and has write access to all standard objects and fields.
While auditing Marketo Engage instance, the consultant finds the following issues:
• An average 40 leads are getting graduated to MQLs but not syncing with Salesforce. These records are already in Salesforce’s lead object and belong to Hospitality Industry.
• The web-message field on the Marketo Engage form is not getting updated to Salesforce’s Lead and Contact objects. The Marketo Engage Sync user has read and write access to "Web-Message" field on Lead, Contact, and Account objects.
Which two steps should the consultant perform to find the root cause? (Choose two.)
- A . Check if Marketo’s Custom Object is in place
- B . Check if the Web-Message form field is mapped to Account object
- C . Check if the Custom Activities are configured properly
- D . Check if the Behavior Scoring is configured properly
- E . Check if the Custom Sync Rule is in place
B,E
Explanation:
The two steps that the consultant should perform to find the root cause are to check if the Web-Message form field is mapped to Account object and to check if the Custom Sync Rule is in place. These steps will help the consultant to identify and resolve the issues that are causing leads not syncing with Salesforce or fields not getting updated.
Checking if the Web-Message form field is mapped to Account object will help the consultant to verify that the field mapping is correct and consistent between Marketo Engage and Salesforce, as well as between Lead, Contact, and Account objects. Checking if the Custom Sync Rule is in place will help the consultant to verify that there are no filters or conditions that are blocking leads from syncing with Salesforce based on their industry or other criteria.
References:
https://docs.marketo.com/display/public/DOCS/Salesforce+Sync%3A+Overview
https://docs.marketo.com/display/public/DOCS/Field+Mapping
https://docs.marketo.com/display/public/DOCS/Custom+Sync+Filter
An Adobe Marketo Engage Consultant is assigned to audit an existing Marketo Engage instance. This is a 10-year-old instance. Due to high turnover within the Marketing Operations team, the team does not have the MQL assignment process documented. Marketing Operations does not have access to Salesforce. The sales team reports that they receive only 10 MQLs in a week. The Marketing team shows on average 50 MQLs in a week. The Sales team members do not get any MQL alert from Marketo Engage. They see the lead assignment only when the leads are assigned to "Sales Queue" on Salesforce. The Marketo Engage sync on Salesforce is properly configured and has write access to all standard objects and fields.
While auditing Marketo Engage instance, the consultant finds the following issues:
• An average 40 leads are getting graduated to MQLs but not syncing with Salesforce. These records are already in Salesforce’s lead object and belong to Hospitality Industry.
• The web-message field on the Marketo Engage form is not getting updated to Salesforce’s Lead and Contact objects. The Marketo Engage Sync user has read and write access to "Web-Message" field on Lead, Contact, and Account objects.
Which two steps should the consultant perform to find the root cause? (Choose two.)
- A . Check if Marketo’s Custom Object is in place
- B . Check if the Web-Message form field is mapped to Account object
- C . Check if the Custom Activities are configured properly
- D . Check if the Behavior Scoring is configured properly
- E . Check if the Custom Sync Rule is in place
B,E
Explanation:
The two steps that the consultant should perform to find the root cause are to check if the Web-Message form field is mapped to Account object and to check if the Custom Sync Rule is in place. These steps will help the consultant to identify and resolve the issues that are causing leads not syncing with Salesforce or fields not getting updated.
Checking if the Web-Message form field is mapped to Account object will help the consultant to verify that the field mapping is correct and consistent between Marketo Engage and Salesforce, as well as between Lead, Contact, and Account objects. Checking if the Custom Sync Rule is in place will help the consultant to verify that there are no filters or conditions that are blocking leads from syncing with Salesforce based on their industry or other criteria.
References:
https://docs.marketo.com/display/public/DOCS/Salesforce+Sync%3A+Overview
https://docs.marketo.com/display/public/DOCS/Field+Mapping
https://docs.marketo.com/display/public/DOCS/Custom+Sync+Filter
Won: Leads that are attached to opportunities that we have closed and Won
In a meeting to discuss how to increase the amount of sales leads, someone suggests scoring leads who have clicked a link in an email with +35 points.
As the Adobe Marketo Engage Consultant, what are the effects of the lifecycle if this suggestion is implemented? (Choose two.)
- A . Conversion from Lead -> Sales Lead would increase
- B . Conversion from Opportunity -> Won would increase
- C . Conversion from Known -> Engaged would decrease
- D . Conversion from Sales Lead -> Opportunity would decrease
- E . Conversion from Sales Lead -> Opportunity would increase
A,D
Explanation:
The effects of the lifecycle if this suggestion is implemented are that the conversion from Lead -> Sales Lead would increase and the conversion from Sales Lead -> Opportunity would decrease. This is because scoring leads who have clicked a link in an email with +35 points would make them jump from Known to Sales Lead in one step, bypassing the Engaged and Lead stages. This would increase the number of leads sent to Sales, but it would also decrease the quality and readiness of those leads, as they may not be truly interested or qualified for the product or service. This would result in lower conversion rates from Sales Lead to Opportunity, as well as lower sales efficiency and effectiveness.
References:
https://docs.marketo.com/display/public/DOCS/Success+Path+Analyzer
https://docs.marketo.com/display/public/DOCS/Best+Practices%3A+Lead+Scoring
An Adobe Marketo Engage Architect is working for Too Big to Fail Co., an enterprise company that has an 8-year-old Marketo Engage instance (A). Too Big to Fail Co. recently purchased start up Treat Snack LTD, which has 100 employees and its own Marketo Engage instance (B). The Architect needs to merge the two instances and maintain business continuity. No additional budget, funding, or resources are available for the merger and migration.
The Architect needs to determine the most important actions to take for the minimum viable solution to meet the business needs. The two instances need to be merged in 3 months.
Which actions should the Architect take?
- A . • Dedupe the instance (B) database and import the leads into instance (A)
• Determine the highest-performing assets and rebuild the campaigns relevant to those assets
• Audit the instance for critical business functions
• Rebuild in instance (A) - B . • Dedupe instance (A) database and import the leads into instance (B)
• Determine the highest-performing assets and rebuild the campaigns relevant to those assets
• Audit the instance for critical business functions
• Rebuild in instance (B) - C . • Spin up a new instance (C)
• Dedupe leads across both instances (A and B) and import into the new instance (C)
• Audit highest-performing assets and key critical campaigns in both instances
• Rebuild in the new instance (C)
A
Explanation:
The most important actions to take for the minimum viable solution are to dedupe the instance (B) database and import the leads into instance (A), determine the highest-performing assets and rebuild the campaigns relevant to those assets, audit the instance for critical business functions, and rebuild in instance (A). This is because instance (A) is older and likely has more data, assets, and integrations than instance (B), and it would be easier and faster to migrate the smaller instance into the larger one. Deduping the leads and determining the highest-performing assets are essential steps to avoid data quality issues and maintain campaign performance. Auditing the instance for critical business functions and rebuilding them in instance (A) are necessary steps to ensure business continuity and alignment. The other options are not as feasible or efficient as this one, because they involve creating a new instance or migrating the larger instance into the smaller one, which would require more time, resources, and complexity.
References:
https://docs.marketo.com/display/public/DOCS/Instance+Migration+Guide
https://docs.marketo.com/display/public/DOCS/Best+Practices%3A+Data+Management
An Adobe Marketo Engage Architect needs to audit an existing Marketo Engage instance. Upon inspection, more than 1000 fields that only live in Marketo Engage were created for a single use to collect information for a specific event, or ask a specific question during the registration of an event.
What should the Architect recommend to their client regarding field creation best practices?
- A . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained.
- B . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. No additional action is needed to retain the data.
- C . Create a set of temporary person fields (temp_string 1, temp.string 2, temp.date 1, temp.date 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained. Clear the data from the temporary fields at the end of the event for utilization by another program.
A
Explanation:
Creating a set of temporary program member fields and using them on local forms for every event that requires custom questions is a good way to avoid creating too many fields that only live in Marketo Engage. Adding the leads to a static list can help retain the data if needed.
https://experienceleague.adobe.com/docs/marketo/using/home.html
An Adobe Marketo Engage Architect needs to audit an existing Marketo Engage instance. Upon inspection, more than 1000 fields that only live in Marketo Engage were created for a single use to collect information for a specific event, or ask a specific question during the registration of an event.
What should the Architect recommend to their client regarding field creation best practices?
- A . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained.
- B . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. No additional action is needed to retain the data.
- C . Create a set of temporary person fields (temp_string 1, temp.string 2, temp.date 1, temp.date 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained. Clear the data from the temporary fields at the end of the event for utilization by another program.
A
Explanation:
Creating a set of temporary program member fields and using them on local forms for every event that requires custom questions is a good way to avoid creating too many fields that only live in Marketo Engage. Adding the leads to a static list can help retain the data if needed.
https://experienceleague.adobe.com/docs/marketo/using/home.html
An Adobe Marketo Engage Architect needs to audit an existing Marketo Engage instance. Upon inspection, more than 1000 fields that only live in Marketo Engage were created for a single use to collect information for a specific event, or ask a specific question during the registration of an event.
What should the Architect recommend to their client regarding field creation best practices?
- A . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained.
- B . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. No additional action is needed to retain the data.
- C . Create a set of temporary person fields (temp_string 1, temp.string 2, temp.date 1, temp.date 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained. Clear the data from the temporary fields at the end of the event for utilization by another program.
A
Explanation:
Creating a set of temporary program member fields and using them on local forms for every event that requires custom questions is a good way to avoid creating too many fields that only live in Marketo Engage. Adding the leads to a static list can help retain the data if needed.
https://experienceleague.adobe.com/docs/marketo/using/home.html
An Adobe Marketo Engage Architect needs to audit an existing Marketo Engage instance. Upon inspection, more than 1000 fields that only live in Marketo Engage were created for a single use to collect information for a specific event, or ask a specific question during the registration of an event.
What should the Architect recommend to their client regarding field creation best practices?
- A . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained.
- B . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. No additional action is needed to retain the data.
- C . Create a set of temporary person fields (temp_string 1, temp.string 2, temp.date 1, temp.date 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained. Clear the data from the temporary fields at the end of the event for utilization by another program.
A
Explanation:
Creating a set of temporary program member fields and using them on local forms for every event that requires custom questions is a good way to avoid creating too many fields that only live in Marketo Engage. Adding the leads to a static list can help retain the data if needed.
https://experienceleague.adobe.com/docs/marketo/using/home.html
An Adobe Marketo Engage Architect needs to audit an existing Marketo Engage instance. Upon inspection, more than 1000 fields that only live in Marketo Engage were created for a single use to collect information for a specific event, or ask a specific question during the registration of an event.
What should the Architect recommend to their client regarding field creation best practices?
- A . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained.
- B . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. No additional action is needed to retain the data.
- C . Create a set of temporary person fields (temp_string 1, temp.string 2, temp.date 1, temp.date 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained. Clear the data from the temporary fields at the end of the event for utilization by another program.
A
Explanation:
Creating a set of temporary program member fields and using them on local forms for every event that requires custom questions is a good way to avoid creating too many fields that only live in Marketo Engage. Adding the leads to a static list can help retain the data if needed.
https://experienceleague.adobe.com/docs/marketo/using/home.html
An Adobe Marketo Engage Architect needs to audit an existing Marketo Engage instance. Upon inspection, more than 1000 fields that only live in Marketo Engage were created for a single use to collect information for a specific event, or ask a specific question during the registration of an event.
What should the Architect recommend to their client regarding field creation best practices?
- A . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained.
- B . Create a set of temporary program member fields (PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2) and utilize those fields on a local form for every event that requires custom questions. No additional action is needed to retain the data.
- C . Create a set of temporary person fields (temp_string 1, temp.string 2, temp.date 1, temp.date 2) and utilize those fields on a local form for every event that requires custom questions. Add them to a static list if data needs to be retained. Clear the data from the temporary fields at the end of the event for utilization by another program.
A
Explanation:
Creating a set of temporary program member fields and using them on local forms for every event that requires custom questions is a good way to avoid creating too many fields that only live in Marketo Engage. Adding the leads to a static list can help retain the data if needed.
https://experienceleague.adobe.com/docs/marketo/using/home.html
People who search the web for wholesale suppliers of gourmet treats
In which order should the different types of scoring be rolled out?
- A . Predictive, Behavior Demographic, Intent, Product
- B . Behavior, Demographic, Predictive, Product, Intent
- C . Behavior, Intent, Demographic, Product, Predictive
B
Explanation:
The order of the different types of scoring should be based on the priority and feasibility of the traits that the Sales team identified. Behavior scoring should be rolled out first, because it captures the most helpful trait of attending a webinar, as well as other actions that indicate interest and engagement. Demographic scoring should be rolled out next, because it captures the second most helpful trait of title and company size, as well as other attributes that indicate fit and qualification. Predictive scoring should be rolled out third, because it captures the third most helpful trait of working for similar companies, as well as other factors that indicate propensity and likelihood to buy. Product scoring should be rolled out fourth, because it captures the fourth most helpful trait of having a high interest in their chocolate tasting line of products, as well as other preferences and needs that indicate product fit and value. Intent scoring should be rolled out last, because it captures the fifth most helpful trait of searching the web for wholesale suppliers of gourmet treats, as well as other signals that indicate buying intent and readiness.
References:
https://docs.marketo.com/display/public/DOCS/Scoring+Overview
https://docs.marketo.com/display/public/DOCS/Best+Practices%3A+Lead+Scoring