From 5e6550fbab12ea37bc8e96a8b37881240bfabcec Mon Sep 17 00:00:00 2001
From: George Dilthey <32441489+george-dilthey@users.noreply.github.com>
Date: Mon, 13 Jul 2026 21:03:44 -0400
Subject: [PATCH 1/2] =?UTF-8?q?docs(audiences):=20add=20FAQ=20clarifying?=
 =?UTF-8?q?=20dedup=20scope=20=E2=80=94=20Audiences=20only,=20not=20Clay?=
 =?UTF-8?q?=20tables?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/audiences.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/audiences.md b/docs/audiences.md
index 479531e5..cb58cace 100644
--- a/docs/audiences.md
+++ b/docs/audiences.md
@@ -430,6 +430,12 @@ The simplest framing: Tables are how you _work on_ data. Audiences is where your
 | Connections | Built per workflow | Continuously synced to your CRM, warehouse, and other sources |
 | Scale | Up to 50,000 rows | Millions of records |
 
+### Does Audiences Companies deduplication apply to my regular Clay tables?
+
+No. Deduplication in Audiences is scoped to the Audiences data layer only — it does not affect records in your regular Clay tables. When you upload a company list to Audiences Companies, duplicate records are merged into a single company profile within Audiences based on domain matching. Your Clay tables keep their own rows and are not touched by Audiences deduplication.
+
+To work from the deduplicated company list in a table, pull records from your Audience instead of uploading the same list into the table separately. Use `Lookup in Audiences` or `Get Audiences Activity` in a table column to query Audiences data — see [Using Audiences from a Clay table](#adding-enrichments) for the full list of table ↔ Audience actions.
+
 ### What if my integration isn't supported yet?
 
 Use the `Upsert Audiences Record` table enrichment as a bridge. Bring your data into a Clay table from any source, then use Upsert to push those records permanently into your Audience. This works for any source Audiences doesn't yet natively support.

From 0ec84716672b15fe599fe21e4946bf1a3726e51a Mon Sep 17 00:00:00 2001
From: George Dilthey <32441489+george-dilthey@users.noreply.github.com>
Date: Mon, 13 Jul 2026 21:15:11 -0400
Subject: [PATCH 2/2] =?UTF-8?q?docs(audiences):=20correct=20FAQ=20?=
 =?UTF-8?q?=E2=80=94=20dedup=20not=20automatic,=20requires=20deterministic?=
 =?UTF-8?q?=20matching=20config?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/audiences.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/audiences.md b/docs/audiences.md
index cb58cace..089ff87f 100644
--- a/docs/audiences.md
+++ b/docs/audiences.md
@@ -432,9 +432,11 @@ The simplest framing: Tables are how you _work on_ data. Audiences is where your
 
 ### Does Audiences Companies deduplication apply to my regular Clay tables?
 
-No. Deduplication in Audiences is scoped to the Audiences data layer only — it does not affect records in your regular Clay tables. When you upload a company list to Audiences Companies, duplicate records are merged into a single company profile within Audiences based on domain matching. Your Clay tables keep their own rows and are not touched by Audiences deduplication.
+No. Deduplication in Audiences is scoped to the Audiences data layer only — it does not affect records in your regular Clay tables. Your Clay tables keep their own rows and are not touched by anything in Audiences.
 
-To work from the deduplicated company list in a table, pull records from your Audience instead of uploading the same list into the table separately. Use `Lookup in Audiences` or `Get Audiences Activity` in a table column to query Audiences data — see [Using Audiences from a Clay table](#adding-enrichments) for the full list of table ↔ Audience actions.
+Domain-based deduplication within Audiences itself is also not automatic. Uploading a company list to Audiences Companies does not deduplicate records by domain on its own. To enable domain-based deduplication across sources, an admin must explicitly configure **deterministic matching** at import setup time and select domain as the match key — see [Entity resolution and deduplication](#entity-resolution-and-deduplication) above. Without that configuration, no domain-based deduplication occurs at upload time.
+
+To query Audiences data from a Clay table, use `Lookup in Audiences` or `Get Audiences Activity` in a table column — see [Using Audiences from a Clay table](#adding-enrichments) for the full list of table ↔ Audience actions.
 
 ### What if my integration isn't supported yet?