<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/4b0bae0d618a43a5905726c340b5021f&quot; frameborder=&quot;0&quot; width=&quot;1724&quot; height=&quot;1293&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1293</height><width>1724</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1293</thumbnail_height><thumbnail_width>1724</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/4b0bae0d618a43a5905726c340b5021f-84912f2480fc1bf0.gif</thumbnail_url><duration>702.274</duration><title>Audiences, Workbooks, and Tables Explained</title><description>This Loom explains when to use audiences versus workbooks versus tables in Clay, especially at scale. It highlights that audiences are best for segmenting millions of CRM records and running enrichment that fills stable fields like firmographics and demographics, while tables are the primary testing ground for experiments and complex multi step logic with conditional orchestration. The video also demonstrates how to move between a table and an audience using upsert and send to table, including updating only selected fields and running on limited row counts (such as 10 or 500) before deploying to a larger audience (like 7,000 companies). It concludes with a principle: only send secure and reliable data back to audiences, and test uncertain logic in tables first.</description></oembed>