Clay Announces Waterfall Data Feature Across 10 Providers for Email Optimization

Yash T. · 2024-02-27 18:47:21.752378+00

keeping the announcements coming - *you can now waterfall data across up to 10 providers in Clay* :ocean::ocean::ocean: this is most useful for emails - because you don’t spend a credit unless you _find_ the email – and sometimes the initial batch of 5 isn’t good enough to maximize coverage. See the screenshot below. hope this helps you all get that extra mileage out of all the providers we connect to!

Clay Announces Waterfall Data Feature Across 10 Providers for Email Optimization | Clay

10 comments

· Sorted by Oldest

Amit S.
·
·
I would love for a configuration option where I can select which service providers' emails need to be validated too. For instance, Nimbler only returns validated emails. So I don't have to validate Nimbler emails with Zerobounce.
Rubi S.
·
·
Clay can see it all now...they're coming for you(r email)
Yash T.
·
·
Amit S. we’ll work on that, but often data providers will return a “valid” email that hasn’t been properly checked, so it’s best practice to double-verify. but we’ve logged this in feedback! Rubi S. you know it 😉
:elmoonfire:1
Ludovic V.
·
·
Yash T. the more the better! However I wonder if you plan to revise your 30 enrichment column limit per table. Personally, with the way we use Clay, we'll never benefit from such a feature as we're already blocked by the limit. Since it's about table performance, I wonder if instead of putting a separate limit of enrichment columns (30), total columns (70) and rows (50k) you could do a limit per cell for example. Our tables won't go beyond 10% of the row limit. A theoretical table of 80 columns with 5k lines, should be smaller and work faster than a table of 70 columns with 50k lines. Just sharing an idea!
Mike J.
·
·
do you find the best strategy is to "validate" every waterfalled email with "Only Safe To Send Emails" turned on? or does that produce false positives and screw up the idea of the waterfall: maybe wrong channel for this:)
Clay S.
·
·
i leave it as the default Mike J. -- just try to keep your bounce rate < 3% and you should be okay
Mike J.
·
·
thanks Clay S.!
Mahdi G.
·
·
Nice work Yash T., are you looking at adding custom data and validation providers into the mix soon?
Luke M.
·
·
Ludovic V. - If we really need to get past the column limit we will link multiple tables together. You could run a 10 column waterfall in 1 table and then write the final email into another table. Totally understand that having it all in 1 table is ideal, but if you ever need this before they increase that column limit there's a solution 😉
:thumbsup_all:2
Mahdi G.
·
·
Luke M. great idea! That could be resolved by adding respond to webhook column to the waterfall table (isn't currently possible)

Loading comments

Amit S.
·
·
I would love for a configuration option where I can select which service providers' emails need to be validated too. For instance, Nimbler only returns validated emails. So I don't have to validate Nimbler emails with Zerobounce.
Rubi S.
·
·
Clay can see it all now...they're coming for you(r email)
Yash T.
·
·
Amit S. we’ll work on that, but often data providers will return a “valid” email that hasn’t been properly checked, so it’s best practice to double-verify. but we’ve logged this in feedback! Rubi S. you know it 😉
:elmoonfire:1
Ludovic V.
·
·
Yash T. the more the better! However I wonder if you plan to revise your 30 enrichment column limit per table. Personally, with the way we use Clay, we'll never benefit from such a feature as we're already blocked by the limit. Since it's about table performance, I wonder if instead of putting a separate limit of enrichment columns (30), total columns (70) and rows (50k) you could do a limit per cell for example. Our tables won't go beyond 10% of the row limit. A theoretical table of 80 columns with 5k lines, should be smaller and work faster than a table of 70 columns with 50k lines. Just sharing an idea!
Mike J.
·
·
do you find the best strategy is to "validate" every waterfalled email with "Only Safe To Send Emails" turned on? or does that produce false positives and screw up the idea of the waterfall: maybe wrong channel for this:)
Clay S.
·
·
i leave it as the default Mike J. -- just try to keep your bounce rate < 3% and you should be okay
Mike J.
·
·
thanks Clay S.!
Mahdi G.
·
·
Nice work Yash T., are you looking at adding custom data and validation providers into the mix soon?
Luke M.
·
·
Ludovic V. - If we really need to get past the column limit we will link multiple tables together. You could run a 10 column waterfall in 1 table and then write the final email into another table. Totally understand that having it all in 1 table is ideal, but if you ever need this before they increase that column limit there's a solution 😉
:thumbsup_all:2
Mahdi G.
·
·
Luke M. great idea! That could be resolved by adding respond to webhook column to the waterfall table (isn't currently possible)