With the increasing amount of Marketo records being created and modified by external services/plugins bolted into Marketo using the REST API it is becoming very difficult to flow, classify and troubleshoot leads coming in through these channels. We can create multiple users with an API role and create multiple named key sets but we are unable to filter data by these more granular distinguishers.
For example, if we use the Marketo API to collect leads from our webinar provider as well as our survey solution or through an external community site or WordPress instance we cannot run these leads through different flows or simply count the monthly totals separately.
Adding filters (or relevant constraints) allowing the API Role or Service Name to add granularity to an increase in API activity is not only convenient but increasingly necessary. Especially when 'Lead Source' may not be useful as the lead is created elsewhere but modified by the API.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.