Issue with Clay Campaign: Excess Credits and No Emails Found | Clay

Issue with Clay Campaign: Excess Credits and No Emails Found

Hi everyone, I have been running Clay campaigns for this one workbook and it has successfully found work emails for the last few months. Two notes:

1.
The estimate was 2000 credits but it consumed 8000 credits
2.
0 emails were found and I don't understand why. I can't tell if this was a big coincidence since this table has always produced many emails. Any ideas?

20 comments

Channeled
APP
·
·
Credits are charged for each email finding attempt (2 credits per cell) regardless of whether an email is found. The 8000 credit consumption suggests you had approximately 4000 rows processed. Normally, if no email is found, the credits should be refunded. To investigate: 1. Check your credit usage dashboard (Settings > Credit usage) to see the detailed breakdown by table 2. Use "View Table History" at the bottom of your table to see which columns used credits For the lack of emails found, this could be a technical issue or data quality problem. Consider running a smaller test batch to troubleshoot.
Sources: How Clay Credits Work Credit usage | Documentation | Clay University
Mathew M.
·
·
No
Mathew M.
·
·
https://app.clay.com/workspaces/90784/tables/t_KqPuzVTSvmpj/views/gv_h4eCZSc3pamc
Mathew M.
·
·
https://app.clay.com/workspaces/90784/tables/t_pjRxNAvhgFrj/views/gv_CrvAhk8kTGqp
Channeled
APP
·
·
Hello Matthew! Thanks for reaching out and being super patient while we got back to you. 1. Could you give me some more context into what these credit spends are? Are they for a few enrichments specifically or all for a specific time window? 2. Just to make sure we are ruling everything out, did you make any changes in the filters for the Find People search? Another reason could be that since you have been finding people based on these filters for a while, the ones being pulled up now do not have as much information about them on the web as the ones you previously pulled in. Recorded this loom outlining my thought process. Suggestions: 1. Change to Clay credits for the Prospeo data provider or add a valid api key to maximise data coverage. You can also add data providers to increase chances of getting emails. 2. About 11k rows have not run at all so the number of 14k emails not being found is not a true number. Effectively 3k emails were not found as the rest 11k rows were not run. You can figure this by filtering through Find work email is empty for the first data provider. Hope this gives you something to work off of! Do let me know more about the credit spend!
Mathew M.
·
·
It was for emails but the estimate was 2000 credits for two tables
Mathew M.
·
·
Is there a way we can have a refund on these credits?
Mathew M.
·
·
My issue is:
1.
We ran two tables for 2000 credits each (4000 credits total)
2.
Emails were not found for almost all leads which doesn't make sense
3.
Nothing else in our tables were triggered since we couldn't find work emails
Channeled
APP
·
·
Was this run done yesterday? Would like to know how many rows you approximately ran to get an idea. I can see from the setup it should spend about 2-3 credits per row. 1-2 credits depending on which data provider ends up finding the email and 1 credit for the validation. That brings total up to 2-3 credits per row. Once you let me know the date I can pull up more details on my end and talk to the team regarding the refund policy.
Mathew M.
·
·
We ran this on Tuesday around 9 am EST for both tables
Mathew M.
·
·
It depleted 8000 credits
Channeled
APP
·
·
Hey Mathew! Took a look at the credit spend for these tables and as you mentioned it used up almost 8000 credits. I have attached the credit spend as two csv files in this message.
Channeled
APP
·
·
Channeled
APP
·
·
Although you are right it did not find a lot of emails, those charged were refunded and no credits were charged as seen when you click into those cells.
(160 kB)
For this table, about 2.33k credits were spent in the Use AI columns. Since your auto update is enabled in both tables, there is a possibility that running these columns triggered the rest of the enrichments in your tables. I talked to the team and have received an approval for the 5260 credits you did not intend to spend. However do note this is the last time we will be able to refund credits due to credit refund history on this account. I am also attaching this guide that I really recommend to conserve credits and prevent unnecessary usage: https://www.clay.com/university/guide/clay-credit-conservation Hope this sorted the issue for now!
Mathew M.
·
·
Hi, I appreciate the credit refund but I am trying to understand how my credits were consumed? I have auto update and the conditions prevent anything from running without emails being found (this is for both tables). I would appreciate a deeper dive into why 8000 credits were used and no emails were found especially since no enrichments were run
Mathew M.
·
·
I am running a random row now and it is queuing and operating the row as expected but I would like to understand why the 2000 rows I run last week failed
LuisArturo
·
·
Hey Matthew sorry for the delay here, taking a look at this, for the Private Schools and Institutions table there was a total of 3235 credits used here, with 2328 credits being used for AI integrations and another 782 credits being used and the remaining 134 credits being used for various integrations for finding emails. Additionally taking a look at the Prospeo column for the water fall there is an error showing that the API key was invalid which led to the entire column never running in the first place
(21 kB)
As for why a majority of these rows did not run, where there any filters in place when initially running?
Mathew M.
·
·
Thanks for sharing, a few questions:
1.
Why did I lose 5.2K credits according to this response? You're saying I spent 3.2K credits - where did the other 2K come from?
2.
I filtered the entire workbook to show the rows with no emails found/empty Work Email cells. Did the "filtering" impact this somehow?
I am quite confused at how the API key failed for Prospeo? We don't even have that as an API key, I've never run into this issue
Channeled
APP
·
·
Hello Mathew! Thanks for reaching out. I can see only 3.2k credits have been spent in that table and not 5.2k. I can see it on my end as well as the credit usage report available to you. LuisArturo mentioned the division of the 3.2k credits. Do let me know if that is where the confusion lies.
(44 kB)
Based on the logs, the error you're seeing (INVALID_API_KEY) indicates that the API key currently being used to call the Prospeo Email Finder endpoint is either incorrect, expired, or not authorized.
To resolve this: 1. Please log in to your Prospeo account and verify the API key you're using. 2. If needed, generate a new API key and update it in your Clay integration (Settings > Connections) or wherever it’s being referenced. 3. Ensure that the key has the necessary permissions for the /email-finder endpoint. Once the correct API key is in place, the request should authenticate successfully, and the action should run without issue.
Channeled
APP
·
·