Marketo Smart List Count Doesn't Match UI Export or Bulk Extract API Export | Community
Skip to main content
Y
Yogesh_Kumar300
Level 1
July 31, 2026
Question

Marketo Smart List Count Doesn't Match UI Export or Bulk Extract API Export

  • July 31, 2026
  • 3 replies
  • 120 views

Hi everyone,

We're experiencing an issue where a Smart List shows a higher record count than what is returned by both the Marketo UI Export and the Bulk Extract API.

For example:

  • Smart List Count: 30k records
  • Marketo UI Export: 13k records
  • Bulk Extract API: Also returns fewer records than the Smart List count.

Has anyone encountered this behavior before? If so, were you able to identify the root cause or find a workaround?

Any insights would be greatly appreciated. Thanks!

3 replies

SanfordWhiteman
SanfordWhiteman
Level 10
July 31, 2026

That’s quite a delta and suggests an indexing bug which support can clear up, but we need more info.

 

 Is the Bulk Extract rowcount like the UI export rowcount? Are there filters that make it so even the accurate results are always changing? 

Y
Yogesh_Kumar300Author
Level 1
July 31, 2026

Hi Sanford,

Thanks for your response.

The Smart List is static at the time of validation, so the results are not changing during the export. We also verified that there are no concurrent updates or filters that would cause records to be added or removed while the export is running.

We've already opened a support case with Adobe, and the support engineer confirmed that different processors were returning different evaluation results for the same Smart List. The issue was subsequently escalated to Engineering.

I was mainly curious if anyone else in the community has encountered a similar indexing or processor inconsistency and whether there were any temporary workarounds before Engineering resolved it.

SanfordWhiteman
SanfordWhiteman
Level 10
August 1, 2026

I was mainly curious if anyone else in the community has encountered a similar indexing or processor inconsistency and whether there were any temporary workarounds before Engineering resolved it.

Yes, on rare occasions. A possible workaround is creating a new SL with the same criteria plus an additional filter to make the query unique (like <a string field> [is not] <some unique value>).

Terms & ConditionsAccessibility statement

Loading footer...