Hi, is there an issue with Clay campaign feature? My leads don’t seem to enter the campaign, even though they appear on Campaign sheet..
That's frustrating—let me help fix this. Several things can prevent leads from entering campaigns:
Most common causes:
• Need to sync lead data - Run the "Sync lead data" enrichment in your parent table
• Leads on global blocklist
• Duplicate email addresses within the campaign
• Sender account connection issues
Quick fix: Check your Sender Accounts tab and Schedule settings first. The "Send Table Data" action is crucial—it syncs your lead data from your parent table into the campaign. [1]
Try running the sync lead data enrichment and let me know if that resolves it.
Is that what you were looking for?
If you still need help with your campaign issue, I’m here to assist further. Would you like to provide more details about what you’re trying to resolve or understand?
No, not working. I’m used to creating Clay campaigns, and usually the leads sent to campaign appear in the analytics tab. Currently, no lead appear and no email has sent, despite sending thresholds not being attained.
I'm sorry to hear this is causing trouble. I'll connect you to a human agent who can assist you further.
Our support team has got your message and we'll get back to you soon!
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!

thks
Hi Alexis, thanks for reaching out and thanks so much for reporting this. Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Hey Alexis, it looks like the campaign was deleted from the workbook. Do you have another campaign that is stuck? If so, can you send me the link? Our engineers have been looking into this and believe they have a fix for new campaigns moving forward. But if you have a stuck campaign now before the fix is released, let us know + send the link and we can manually fix it on the backend.
