Discrepancy in Record Count: Clay vs. SF Report

Priyanka L. · 2025-12-03T15:03:32.234Z

Hi @Clay S., I have a report linked into Clay. On SF this report has 669 records but Clay is only pulling in 429 records. The SF report is tabular, and has less than 2000 total rows, I also refreshed the Clay test. Please can someone help me understand why this is happening?

Discrepancy in Record Count: Clay vs. SF Report | Clay

Clay Support
APP
·
·
That's frustrating—let me help troubleshoot this discrepancy.
The most likely cause is your uniqueness fields configuration. When importing Salesforce reports, Clay uses uniqueness fields to prevent duplicates. [1] If you haven't selected specific fields, Clay uses the entire row content as the unique identifier, which can cause issues with duplicate detection.
To fix this:
1.
Check your Clay import settings for the uniqueness fields configuration
2.
Select specific fields (like Record ID or Email) as unique identifiers instead of using the entire row
3.
Trigger a manual refresh using the "Run now" button
Also verify your Salesforce report contains the expected accounts and filters, and confirm the correct report is linked in Clay.
If the issue persists after adjusting uniqueness fields, the report format might need verification—ensure it's truly tabular without any hidden groupings.
Clay Support
APP
·
·
Is that what you were looking for?
Priyanka L.
·
·
there is opportunity ID within this report which is a unique indicator
Clay Support
APP
·
·
Perfect! Set Opportunity ID as your uniqueness field in the Clay import settings. This should resolve the record count mismatch. [1]
Go to your Salesforce import configuration and select Opportunity ID in the "Uniqueness fields" section, then trigger a manual refresh using "Run now." [2] This will prevent Clay from treating rows as duplicates and should pull in all 669 records.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help resolving the record count issue or have any other questions, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other challenges you’re facing?
Priyanka L.
·
·
where do I find clay import setting?
Clay Support
APP
·
·
For your existing Salesforce import, click Actions > Import in your table (the Actions button is just below the top navigation bar). [1]
In the import configuration, you'll find the Uniqueness fields section where you can select Opportunity ID as your unique identifier. [2]
Clay Support
APP
·
·
Did this help?
Clay Support
APP
·
·
If you still need assistance finding the import settings or configuring the uniqueness fields, I’m happy to help. Would you like to share more about what you’re trying to set up or any other issues you’re encountering?
Priyanka L.
·
·
opp id is already a unique identifier
Loading attachments
Clay Support
APP
·
·
Since Opportunity ID is already set as your uniqueness field, the issue might be elsewhere. Check if your Salesforce report has any hidden filters or groupings that could be limiting the data. [1]
Also verify that all 669 records in Salesforce actually contain values in the OPPORTUNITY_ID field—empty or null values in this field could cause Clay to skip those records during import. [2]
Try refreshing the import by clicking "Submit" again to see if that pulls in the missing records.
Clay Support
APP
·
·
Is that what you were looking for?
Priyanka L.
·
·
no this still returns 429 rows and there are no groupings or filters in the report
Clay Support
APP
·
·
I'm sorry this is still frustrating. I'll connect you to one of our human agents who can assist further.

19 comments