Rest API Need for multi-Field LookUp

Rest API Need for multi-Field LookUp


We provide a solution which helps identify new leads and enrich leads with social identities and lead scores. We have just released an integration to import and export leads  between Marketo and our solution. In the current release of the Rest API framework from Marketo, we can only match the lead data using a look up field that we call ‘Custom Marketo ID’ (which checks to see if a lead already exists in Marketo with a given Marketo ID)We would like the capability to do the matching based on multi-field lookup (e.g., twitter handle, LinkedIn ID etc). An example scenario would be:

 

New Lead in NextPrinciples:

- First Name: Joe
- Last Name: Smith
- Marketo ID: ‘’
- Twitter ID: ‘joesmith’
- LinkedIn ID: ‘jsmith1’
- email: ‘joe@np.com

Only Lead in Marketo:

- LinkedIn ID: ‘jsmith1’

 

When this lead is exported from NextPrinciples to Marketo, it first checks to see if there is a Marketo ID in the lead record. Since the value is null, it then looks to see if there is a Twitter ID. In this case, it finds ‘joesmith’ and uses the Marketo API call to look up the field ‘Twitter ID’ in Marketo to see if a lead exists with the field’s value as ‘joesmith’. Since there is no lead found with this Twitter ID in Marketo, our call to Marketo then looks up the LinkedIn ID and checks if a lead exists in Marketo with the LinkedIn ID value of ‘jsmith1’. It finds a match and therefore updates the existing lead in Marketo and does not create a new lead.

Furthermore, can we define logic among "lookupFields"? For example, can we define "email" OR “twitter ID", (alternately)  "email" AND “twitter ID"?

Can we define a precedence? For example, if more than one lead was matched,  then we get the lead that has a matched “twitter ID”, instead of another lead that has a match based on  “linkedIn ID” only.
 

5 Comments
Anonymous
Not applicable
I get some of the general uses for a more complex way to query, but what is the specific issue you're dealing with here? In your example, there is an email address- why not just use that?
Anonymous
Not applicable

Erik,

We are bringing new leads identified & scored on social channels and sending it to Marketo. Since social channels don't share email IDs, we need to use other fields to check on Marketo. 

Does this help answer your question?
 

Anonymous
Not applicable
Could you do this with multiple calls today then? Try and look up with one, then look up with the other?
Anonymous
Not applicable
Erik,
Good insight.

In our case, we create or update multiple leads in the call. We use lookupField(s) match to decide whether to create or update each lead, thus multi lookup fields would be a good fit.
http://developers.marketo.com/documentation/rest/createupdate-leads/

On the other hand, if to make mutiple calls mutiple times, there could be limitations in addition to extra code to make extra calls, e.g. if we are to create/update more than a hundred leads then we need to work around considering the 100 filter value limit:
http://developers.marketo.com/documentation/rest/get-multiple-leads-by-filter-type/


Community Manager
Status changed to: Open Ideas