Clay Icon
Join the Community
01 Community General

Tips for Monitoring Credit Usage and Forecasting Needs with Clay

Avatar of Kimberley C.Kimberley C.
·
·

I'm running all kinds of experiments with Clay and also applying it to a lot of existing programs and initiatives. One thing I am struggling with is monitoring credit usage and forecasting how many we need ahead of time. Does anyone have any tips on how they've approaching this?

6 comments

  • Avatar of Amit S.
    Amit S.
    ·
    ·

    Create the entire flow for only 10 rows. Count the credits used by each row, and then extrapolate that to your entire data set.

  • Avatar of Kimberley C.
    Kimberley C.
    ·
    ·

    Thank you, I sort of mean this in a broader way, estimating how many for so many different initiatives before I've started tables etc

  • Avatar of Kimberley C.
    Kimberley C.
    ·
    ·

    Clay does not make it super easy to monitor usage

  • Avatar of Amit S.
    Amit S.
    ·
    ·

    Most of this is intuition, and it will be built automatically after you do these things a few times. Like now, I can calculate the # credits it takes to find, enrich, find emails, collect data for personalization, personalize, and push to a tool for a 100 profiles pretty easily. Given that the use cases are different, it would be very hard to estimate the total number of steps required to get an answer, without practice.

  • Avatar of Michael (.
    Michael (.
    ·
    ·

    Kimberley C. I think it's easier to have a set of API to scale Clay tables WITHOUT credits