A consultant conducts an audit on a company's Adobe Marketo Engage instance and discovers:
The instance hits its API limit twice a month, affecting leads from multiple third-party integrations from being consistently created or updated automatically.
The field "Country" is set as a text field, which results in inconsistent variations and mis-spellings of the country value, leading to the inability to route leads to the proper regional sales team.
There is a Segmentation called "Region", which is defined by the "Country" field values; due to the inconsistency of the field, a majority of the person records sit in the "Default" segment.
Lead routing is based on the "Region" segment, and there is no logic set in the routing to account for the "Default" leads.
After sharing these findings with a group of stakeholders, the stakeholders share:
The Data Science team uses the Marketo Engage API to pull data out of the instance twice a month for an executive dashboard that tracks quarterly goals.
The Sales team is extremely below target for qualified leads because the volume routed to them is so low.
The Web team has reported on below-average form conversions because too many fields are open text.
The Marketing team wants to send nurture emails that are localized based on the "Region" Segmentation.
A consultant conducts an audit on a company's Adobe Marketo Engage instance and discovers: