Clay Audiences Reporting: Tie Lists to Real Pipeline

Clay can now tell you which of the accounts you sourced turned into pipeline and closed revenue. Reporting in Audiences shipped in Clay's August 3 product roundup, and it closes the loop between a list you built and the deals that came out of it.

If you have ever been asked "is Clay actually worth it?" and had to answer with credit counts and row totals instead of dollars, this is the update that matters. The other three items in the same release are smaller, but one of them changes how agencies and RevOps teams run Clay in production.

What Clay shipped

Four things landed in the August 3, 2026 roundup.

Reporting in Audiences. You open Reporting from an Audience and see Clay coverage alongside revenue impact. Clay's changelog describes it as showing "the pipeline and revenue your Clay-sourced data actually drove." The stated capability is tracking sourced accounts forward through pipeline stages and into closed-won.

Credit time-series graphs in the Usage dashboard. Usage used to show you a balance. It now shows credit spend over time as a graph, with breakdowns per interval by day, hour, or minute. You can highlight a region of the graph to drill into a spike.

CLI device login. Running clay login --device authenticates Clay's CLI and Agent Plugin using an RFC-standard device authorization flow, so you no longer need a browser OAuth handoff. That makes headless and containerized environments viable.

A Claygent visual refresh. New icons across the product and a dedicated page at clay.com/claygent. No functional change — though if you missed it, Claygent's bigger recent change was adding open-weight models.

Clay's July 27 roundup, one week earlier, also raised Audiences field limits to 600 string fields and added a Connections page for tracing where usage originates. Those two matter more than they sound once you are reporting on Audiences rather than just building them.

Why this matters for outbound teams

Outbound list building has always had an attribution hole in the middle of it. You build a segment, push it to sequences or a dialer, and the moment a contact enters the CRM, the list that produced them stops being a tracked object. Six weeks later a deal closes and nobody can say which sourcing decision created it.

That hole has real consequences. It means ICP refinement runs on gut feel. It means the argument for enrichment budget gets made on cost-per-row, which is the least interesting number in the entire stack. And it means a bad segment can quietly consume credits and rep hours for a full quarter before anyone notices it never converted.

Our read: the value here is not the dashboard. It is that the Audience becomes the unit of measurement. Once you can compare two Audiences on closed-won instead of on reply rate, you can make sourcing decisions the same way you make ad spend decisions.

One caveat worth stating plainly. The changelog does not spell out how Clay determines which accounts became pipeline, and attribution quality always depends on how clean the join between your CRM and your source data is. Before you present these numbers to anyone, spot-check a handful of accounts by hand and confirm the match logic does what you expect.

How we'd use it

Four plays we would run with this, in the order we would run them.

1. Retire segments on revenue, not reply rate. Most teams already split Audiences by firmographic cut: company size band, tech stack signal, hiring signal, region. Reply rate ranks those badly, because the segments that reply fastest are often the ones that buy least. Pull closed-won by Audience over two full sales cycles and cut the bottom third. Reallocate those credits into the top segment's adjacent territory.

2. Build a real cost-per-opportunity number. This is where the reporting and the new usage graph work together. Take credit spend from the time-series view for the window in which an Audience was built and enriched, then divide by opportunities from Reporting. That gives you cost per opportunity by sourcing motion, which is the number that tells you whether to spend the next dollar on a deeper enrichment waterfall or a wider list.

3. Audit your waterfall against outcomes. Enrichment waterfalls accumulate providers. Someone adds a third mobile provider for coverage, it never gets removed, and it bills for two years. With spend visible per interval, you can isolate the exact hours a waterfall ran, tie that spend to the Audience it fed, and check whether the incremental provider showed up in any closed deal at all. Most of the time, the last provider in a waterfall is not paying for itself.

4. Move scheduled Clay runs into proper infrastructure. Device login is the quiet win for anyone running Clay across multiple client workspaces. Browser OAuth is what has kept a lot of Clay automation sitting on someone's laptop instead of in a container or a CI runner. With clay login --device, scheduled enrichment jobs can run on a server, with logs, on a schedule nobody has to remember.

A note on sequencing. Do not start with the dashboard. Start by making sure your Audiences are actually split along decisions you would be willing to change. An Audience of "all US SaaS companies" will report a number, and that number will tell you nothing.

FAQ

Does Clay show revenue attribution now?

Yes, within Audiences. Reporting shows Clay coverage plus pipeline and revenue impact for accounts you sourced, tracked through to closed-won. It is scoped to Clay-sourced data, so it complements CRM attribution rather than replacing it.

How do I see Clay credit spend over time?

The Usage dashboard now includes a credit time-series graph with per-interval breakdowns by day, hour, or minute. Highlight a region of the graph to drill into what caused a spike, which is the fastest way to find a runaway column.

Can Clay's CLI run without a browser login?

Yes. clay login --device uses a device authorization flow, so Clay's CLI and Agent Plugin authenticate in headless and containerized environments without a browser OAuth step.