Analysis of 8k Credit Usage in Clay Workbook Table | Clay

Analysis of 8k Credit Usage in Clay Workbook Table

can u please check this table and let me know why almost 8k credits were being used? https://app.clay.com/workspaces/430254/workbooks/wb_nm7XEEHEybqK

7 comments

Channeled
APP
·
·
To understand why almost 8, 000 credits were used, review the credit usage dashboard in your workspace. This dashboard provides a detailed breakdown of credit consumption by table, integration, and time period. You can filter by when credits were used, the owner, or specific integrations. Credits are typically spent on data enrichment actions, with each provider and data type having its own credit cost. For a more granular view, use the "View Table History" button at the bottom of your table to see which columns used credits, or right-click a column and select “Run Info” for a summary of credits spent on that column. This should help you identify which actions or integrations contributed to the high credit usage in your table.
Sources: Credit usage | Documentation | Clay University Enrichments | Documentation | Clay University
Ankit M.
·
·
https://app.clay.com/workspaces/430254/workbooks/wb_nm7XEEHEybqK
Bo (.
·
·
Hey, to check where the 8k credits were used, click the table name and select “View Credit Usage” from the dropdown. That’ll show a full breakdown by column and source. Often, high usage comes from H-Insights since they charge dynamically based on the number of results and values returned. Let me know if anything looks off.
(95 kB)
Ankit M.
·
·
yup! total should not be over 4k credits. Can you look into this and may be reimburse them?
LuisArturo
·
·
Hey there Ankit thanks for reaching out, taking a look at your workspace, the reason for the credit usage here is due to the HG insight find company feature. If you were to check the credits usage in your workspace you will notice the credit totals do not match up because currently we don't have HG Insights set up to be tracked by table usage.
Ankit M.
·
·
okay, but the issue was created where despite putting the scraping restrictions to a maximum of 20 rows, HG Insights went ahead and added close to 200-250 before i realized that something's wrong. That is when i reported.
LuisArturo
·
·
Hey, thanks for reaching out! I replied in the other thread, so I’ll close this one.