Skip to main content
A
Anonymous
August 12, 2014
Question

Mismatch in Number of Records Extarcted from API Vs. Records Found on Marketo UI.

  • August 12, 2014
  • 4 replies
  • 866 views
Hi All,

Please pardon me if this question has already been posted on Community.

We are using Marketo API 2.4 version for extracting data from one of our Test Account.

We are using getMultipleLeads call to get Lead object from the Marketo Data Source. As per the convenience provided by the recent updates we are applying Date Range criteria while extracting the records.

The criteria is applied using LastUpdateAtSelector object and setting its setOldestUpdatedAt , setLatestUpdatedAt utility methods to set the date range.

Now if we apply the criteria for smaller date ranges like a month or weeks we get data with permissible range of deviation in the result returned by the API and data available on the Marketo for the verification.

But as soon as we apply larger date ranges like months or year, the data returned shows substantial difference between the number of records available on Marketo UI. API returns larger number of results, most of them are outside the date range.

Is this a known behavior?

Please do let us know as it can be a show stopper if user is applying larger date ranges higher than a year.

Any help is much appreciated.

Regards
Anil.
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

A
Anonymous
August 12, 2014
This sounds like a bug. 

What was the date range when the call returned the right leads? And what was the date range when it did not? 
A
Anonymous
August 14, 2014
Hi Murtza,

Please find the part of response XML .

<paramsGetMultipleLeads xmlns="marketo.com/mktows/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <leadSelector xsi:type="mkt:LastUpdateAtSelector" xmlns:mkt="marketo.com/mktows/" xmlns="">
    <latestUpdatedAt>2014-07-10T17:45:00.000+05:30</latestUpdatedAt>
    <oldestUpdatedAt>2013-07-25T20:34:00.000+05:30</oldestUpdatedAt>
  </leadSelector>
  <includeAttributes xmlns="">
    <stringItem>FirstName</stringItem>
    <stringItem>LeadID</stringItem>
  </includeAttributes>
</paramsGetMultipleLeads>
<paramsGetMultipleLeads xmlns="marketo.com/mktows/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <leadSelector xsi:type="mkt:LastUpdateAtSelector" xmlns:mkt="marketo.com/mktows/" xmlns="">
    <latestUpdatedAt>2014-07-10T17:45:00.000+05:30</latestUpdatedAt>
    <oldestUpdatedAt>2013-07-25T20:34:00.000+05:30</oldestUpdatedAt>
  </leadSelector>
  <includeAttributes xmlns="">
    <stringItem>FirstName</stringItem>
    <stringItem>LeadID</stringItem>
  </includeAttributes>
</paramsGetMultipleLeads>


Regards,
Prathamesh
A
Anonymous
August 14, 2014
Hi Murtza,

Can you please hand over me the Bug # if Marketo is already working on the same issue?

If not, Can you please create one and do let mek now the bug number so that we can help our partners track it accordingly.

We are working with Birst Inc. and working on POC of Marketo Version 2.4 API.

Regards,
Anil.
A
Anonymous
August 14, 2014
This is not a known behavior that I am aware of. Until we get this resolved, I would recommend making more API calls with smaller date ranges as a workaround.

Partners can now file bug reports. Can you file a bug report about this? 

https://community.marketo.com/MarketoSupportHome
Terms & ConditionsAccessibility statement

Loading footer...