QuestionQ37

VerifiedSection 3: Reporting and Attribution

An Adobe Marketo Engage Consultant has been asked to audit an existing Marketo Engage instance that has been running for 10 years. Due to high turnover on the Marketing Operations team, the MQL assignment process is not documented, and Marketing Operations does not have access to Salesforce.

The Sales team reports receiving only about 10 MQLs per week, while the Marketing team's reporting shows an average of 50 MQLs per week. Sales team members do not receive any MQL alert from Marketo Engage — they only see lead assignments when leads are placed into the "Sales Queue" in Salesforce. The Marketo Engage–Salesforce sync is confirmed to be properly configured and has write access to all standard objects and fields.

During the audit, the consultant identifies the following issues:

  • On average, 40 leads are graduating to MQL status but are not syncing that update to Salesforce. These lead records already exist in Salesforce's Lead object and belong to the Hospitality industry.
  • The Web-Message field on the Marketo Engage form is not updating on Salesforce's Lead and Contact objects, even though the Marketo Engage sync user has read and write access to the "Web-Message" field on the Lead, Contact, and Account objects.

Which two steps should the consultant take to identify the root cause?

Choose two
Explanation

A Custom Sync Rule (Custom Sync Filter) in Marketo Engage designates a field that controls whether a given lead/contact record is allowed to sync between Marketo and Salesforce. If such a rule exists and excludes or mishandles records tied to a particular segment (here, Hospitality industry leads that already exist in Salesforce), those records' status changes — such as graduating to MQL — will fail to sync to Salesforce even though the overall connector and standard write access are configured correctly. This explains why only a subset of MQLs (the non-excluded ones) reach Salesforce and trigger Sales Queue assignment.

Separately, because the sync user already has full read/write access to the Web-Message field on Lead, Contact, and Account, the failure to update Lead and Contact records is not a permissions problem but a field-mapping problem. Marketo field mappings tie a single Marketo field to specific corresponding Salesforce object fields; if the Web-Message field was mapped only to the Account object instead of to the Lead and Contact objects, form submissions would write to Account and never appear on the Lead or Contact records, despite adequate access rights.

Learn more

Community Discussion

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