Discrepancy in Linkedin Reactors Count vs Clay Integration

Guillermo C. · 2025-10-22 09:09:01.862495+00

Good morning. I am using the Linkedin integration to track brand mention posts and get commenters and reactors. Hoewever the number of retrieved reactors in Clay does not match does actually reacting in Linkedin. https://app.clay.com/workspaces/476313/workbooks/wb_0t3tkpvC8iW7oXGp45U/tables/t_0t3tmcjgMKKd6dXiK5e/views/gv_0t3tmckjqaAEsw3yCVk See row 9: 0 reactors retrieved in Clay but actually 11 reactors in Linkedin. Could you explain me why?

Discrepancy in Linkedin Reactors Count vs Clay Integration | Clay

12 comments

· Sorted by Oldest

Clay Support
APP
·
·
The mismatch occurs because our data providers don't use your session cookies or aren't logged in as you, so results might not reflect real-time visibility—some entries can be missed.
Try reloading those rows to see if the provider returns more complete results. For more control, you can connect tools like PhantomBuster or Apify in Clay to run searches using your own LinkedIn session, which can improve accuracy.
Clay Support
APP
·
·
Was that helpful?
Guillermo C.
·
·
I am re-running the Linkedin research daily and still does not return the actual reactors. Anyone searching for this post can see the actual number of reactors so I do not understand why there would be a cookies issue...
Clay Support
APP
·
·
The issue persists because our data providers don't use your active LinkedIn session or cookies when retrieving reactor data. Even though the post is publicly visible, LinkedIn restricts certain engagement data (like detailed reactor lists) based on login status and permissions—our providers access this data differently than when you're logged in directly.
This is a known limitation with our LinkedIn integration. The data might not always reflect real-time visibility, and some entries can be missed even with daily re-runs.
For more reliable results, consider using tools like PhantomBuster or Apify connected in Clay, which run searches using your own LinkedIn session and can improve accuracy.
Clay Support
APP
·
·
Was that helpful?
Guillermo C.
·
·
Not much...
Clay Support
APP
·
·
I'm sorry to hear that the information wasn't helpful. I'll connect you to a human agent who can assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments
Guillermo C.
·
·
The URL is at the beggining of the chat
Guillermo C.
·
·
Thank you!
Quentin R.
·
·
Hi Guillermo, I wish I could explain what happens but even after looking to our logs, it's hard to tell. I reported a bug to our engineering team. From experience, similar issues often come from LinkedIn, so not much we can do. Anything else we could help with?
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
The mismatch occurs because our data providers don't use your session cookies or aren't logged in as you, so results might not reflect real-time visibility—some entries can be missed.
Try reloading those rows to see if the provider returns more complete results. For more control, you can connect tools like PhantomBuster or Apify in Clay to run searches using your own LinkedIn session, which can improve accuracy.
Clay Support
APP
·
·
Was that helpful?
Guillermo C.
·
·
I am re-running the Linkedin research daily and still does not return the actual reactors. Anyone searching for this post can see the actual number of reactors so I do not understand why there would be a cookies issue...
Clay Support
APP
·
·
The issue persists because our data providers don't use your active LinkedIn session or cookies when retrieving reactor data. Even though the post is publicly visible, LinkedIn restricts certain engagement data (like detailed reactor lists) based on login status and permissions—our providers access this data differently than when you're logged in directly.
This is a known limitation with our LinkedIn integration. The data might not always reflect real-time visibility, and some entries can be missed even with daily re-runs.
For more reliable results, consider using tools like PhantomBuster or Apify connected in Clay, which run searches using your own LinkedIn session and can improve accuracy.
Clay Support
APP
·
·
Was that helpful?
Guillermo C.
·
·
Not much...
Clay Support
APP
·
·
I'm sorry to hear that the information wasn't helpful. I'll connect you to a human agent who can assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments
Guillermo C.
·
·
The URL is at the beggining of the chat
Guillermo C.
·
·
Thank you!
Quentin R.
·
·
Hi Guillermo, I wish I could explain what happens but even after looking to our logs, it's hard to tell. I reported a bug to our engineering team. From experience, similar issues often come from LinkedIn, so not much we can do. Anything else we could help with?
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!