Audiences is a feature of 📝Clay that centralizes a company's first- and third-party data — CRM records, warehouse tables, buyer intent signals, and enrichment results — into one model of people, companies, and deals that every Clay table, workflow, and campaign can draw on. It exists because the signals that show when and how to engage a buyer were scattered across CRMs, data warehouses, and point tools, each holding a partial view; Audiences consolidates them and returns enriched results to the CRM. It is built for RevOps and GTM engineering teams at mid-market and enterprise companies managing millions of records.
Clay positions Audiences as its GTM data layer and 📝Clay Workflows as the orchestration layer that acts on it — in its own analogy, Audiences are the rows and Workflows are the columns.
Key Capabilities
- Data imports — Pulls records from 📝Salesforce, including SOQL queries, Opportunities, and Activities, plus HubSpot Deals, Snowflake, and BigQuery.
- TAM sourcing — Bulk-sources a total addressable market from Clay's company, people, and jobs search, then enriches millions of rows without per-table row limits.
- Signal layering — 📝Signals such as job changes, funding, and website visits attach to records, and segments update in near real time as signal runs finish.
- Revenue reporting — Reports the pipeline and closed-won revenue that Clay-sourced accounts actually drove, tying enrichment and outreach back to business outcomes.
- Agent access — Coding agents start with Audiences through the Clay CLI, where reads are free, and Enterprise workspaces can expose it to reps through 📝Clay MCP.
Getting Started
- Connect a CRM or warehouse such as Salesforce, HubSpot, Snowflake, or BigQuery.
- Import the people, companies, and deals to model in Audiences.
- Layer signals and enrichments onto the imported records.
- Build segments and feed them into tables, workflows, ads, or campaigns.