Concern Over Smartlead Default Community Bounce List Setting

Mike Roth · 2025-02-19 21:35:17.942599+00

FYI - I think 99% of users would agree this Smartlead setting default should be the opposite or at a minimum don't default this at all, keep it as an option because no Smartlead users want to use the Community Bounce List (it isn't accurate and will block 90% of leads being added to Smartlead). It's going to cause all your Clay users to have to manually update every single table they use to turn this off.

Concern Over Smartlead Default Community Bounce List Setting | Clay

10 comments

· Sorted by Oldest

Channeled
APP
·
·
We don't have a specific setting to disable the Community Bounce List by default in Clay's Smartlead integration. However, you can manage this when setting up your Smartlead campaigns within Clay. When using the "Add Lead to Campaign" or "Update Lead in Campaign" actions, you can configure the run settings to suit your needs. To ensure you're not using the Community Bounce List, you can: 1. Use conditional formulas in the run settings to control when leads are added or updated. 2. Set up a lookup action to check if a lead exists before adding them. 3. Use SmartLead's own duplicate checking features if you prefer to manage this on their end. Could you clarify which specific Smartlead action in Clay you're trying to modify? This would help me provide more targeted advice on managing the Community Bounce List setting.
Source: Smartlead integration overview | Documentation | Clay University
Channeled
APP
·
·
Looks like you're still looking for help.
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!
Bo (Clay)
·
·
Hi Mike! Thanks for pointing this out. I'm going to share this feedback with our product team so they can evaluate adjusting the default behavior. Let me know if you need anything else!
Mike Roth
·
·
Thanks Bo, can you update this thread if they fix it before I go update all my tables? Feel free to ask Eric N or any big SmartLead user you know and they’ll give you the same feedback 👍
Bo (Clay)
·
·
Hey Mike - Yes ! I'll let you know 💪💪 Thanks again. Always great to read your feedback Mike.
Bo (Clay)
·
·
Hi Mike! Could you clarify if you'd like to see the default setting changed for both the Community Bounce list and duplicate across campaigns, or just the Community Bounce list specifically? Let me know!
Mike Roth
·
·
Hey Bo! I believe the current default for duplicate across campaigns is correctly defaulted as it stands so the main change would just be to community bounce list (I assume most users weren’t aware of this Clay update for the SL integration as I assume it was somewhat recent but sharing since some people in different groups were upset by this causing them to change every Clay table to revert this setting since they noticed 90% of their leads not being added after validating them in Clay before adding to SL)
Bo (Clay)
·
·
Thanks! I've added this feedback to the previous one. Let me know if you have any other suggestions!
Henry Jefferies
·
I had this same problem today - thanks @Mike and Bo for clearing it up!
Channeled
APP
·
·
Hi Mike Roth! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
We don't have a specific setting to disable the Community Bounce List by default in Clay's Smartlead integration. However, you can manage this when setting up your Smartlead campaigns within Clay. When using the "Add Lead to Campaign" or "Update Lead in Campaign" actions, you can configure the run settings to suit your needs. To ensure you're not using the Community Bounce List, you can: 1. Use conditional formulas in the run settings to control when leads are added or updated. 2. Set up a lookup action to check if a lead exists before adding them. 3. Use SmartLead's own duplicate checking features if you prefer to manage this on their end. Could you clarify which specific Smartlead action in Clay you're trying to modify? This would help me provide more targeted advice on managing the Community Bounce List setting.
Source: Smartlead integration overview | Documentation | Clay University
Channeled
APP
·
·
Looks like you're still looking for help.
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!
Bo (Clay)
·
·
Hi Mike! Thanks for pointing this out. I'm going to share this feedback with our product team so they can evaluate adjusting the default behavior. Let me know if you need anything else!
Mike Roth
·
·
Thanks Bo, can you update this thread if they fix it before I go update all my tables? Feel free to ask Eric N or any big SmartLead user you know and they’ll give you the same feedback 👍
Bo (Clay)
·
·
Hey Mike - Yes ! I'll let you know 💪💪 Thanks again. Always great to read your feedback Mike.
Bo (Clay)
·
·
Hi Mike! Could you clarify if you'd like to see the default setting changed for both the Community Bounce list and duplicate across campaigns, or just the Community Bounce list specifically? Let me know!
Mike Roth
·
·
Hey Bo! I believe the current default for duplicate across campaigns is correctly defaulted as it stands so the main change would just be to community bounce list (I assume most users weren’t aware of this Clay update for the SL integration as I assume it was somewhat recent but sharing since some people in different groups were upset by this causing them to change every Clay table to revert this setting since they noticed 90% of their leads not being added after validating them in Clay before adding to SL)
Bo (Clay)
·
·
Thanks! I've added this feedback to the previous one. Let me know if you have any other suggestions!
Henry Jefferies
·
I had this same problem today - thanks @Mike and Bo for clearing it up!
Channeled
APP
·
·
Hi Mike Roth! This thread was recently closed by our Support team. If you have a moment, please share your feedback: