From ce9f85941ff90f95b957e3dced1eb529615d1b63 Mon Sep 17 00:00:00 2001 From: George Dilthey <32441489+george-dilthey@users.noreply.github.com> Date: Thu, 16 Jul 2026 21:09:00 -0400 Subject: [PATCH 1/3] docs(audiences): document signal detection-layer model and Data Hub vs. table scope --- docs/audiences.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/docs/audiences.md b/docs/audiences.md index 98409b80..cb6fd46d 100644 --- a/docs/audiences.md +++ b/docs/audiences.md @@ -241,7 +241,7 @@ To create a new audience: 2. Click **New audience** in the top-right corner of the list, or click the `+` next to `My Audiences` in the sidebar. 3. Select `Criteria` and then add a `Filter` or `Filter group`. - **Filters** evaluate a single condition at a time. All top-level filters are joined with AND — a record must match every one. - - **Filter groups** combine multiple conditions using their own AND/OR logic. Within a single filter group, all conditions share the same operator — all AND or all OR; changing the operator in the group header switches all conditions at once. To mix AND and OR, use a nested filter group. For example, to build `A AND B AND (C OR D)`: add A and B as top-level filters, click **`+ Filter group`**, then add C and D inside the group. Once the group contains two or more conditions, a small **`and`** button appears between them — click it to switch to **`or`**. + - **Filter groups** combine multiple conditions using their own AND/OR logic. Within a single filter group, all conditions share the same operator — all AND or all OR; changing the operator in the group header switches all conditions at once. To mix AND and OR, use a nested filter group. For example, to build `A AND B AND (C OR D)`: add A and B as top-level filters, click **`+ Filter group`**, then add C and D inside the group. Once the group contains two or more conditions, a small **`and`** button appears between them — click it to switch to **`or`**.\ ### Filter operators by field type @@ -344,6 +344,8 @@ After you add a signal: - Multiple signals each get their own column; the `Signal Summary` column aggregates all results. Click any row to see per-signal detail. - Any other segment that filters on this signal type will also surface these results. +**Signals are a detection layer — taking action on results happens in the companion segment.** Signals identify matching records and write results to each record's profile, but do not trigger automated actions on their own. To act on the records a signal detected, navigate to the auto-created companion segment and click `Send` to enroll them in a workflow or CRM export, or click `Enrich` to run a bulk enrichment on the matching records. To enroll new members automatically as the signal continues to fire over time, publish a workflow trigger on the companion segment — see [Connecting a workflow to a segment](#connecting-a-workflow-to-a-segment) below. + **Monitoring signal progress** While the signal is processing its initial run, its status shows **Running**. Once the initial run completes, the status flips to **Monitoring** and displays a **Last run** timestamp. To see how many records were detected, go to **Data Hub** → **Signals** — the **Signals fired (30d)** column shows the count of events the signal emitted over the past 30 days. @@ -675,6 +677,17 @@ Three things to check: - **The default 5-result count was reached.** `Lookup in Audiences` returns 5 signal results per record by default. If a company has more active signals than that, some may not appear — increase the result limit in the column settings (up to 50), or use `Get Audiences Activity` to retrieve a larger set of signal data. - **The signal hasn't fired for that record yet.** Signal results are written asynchronously and may not appear immediately after a signal run completes. If a signal should be recent but is still missing, open the signal's column header → `Edit column` and re-run the signal to refresh the data for that record. +### A signal I created in a table isn't showing up when I try to add it to an audience — why? + +Signals created inside a Clay workbook table write results back to that table and are scoped to it — they cannot be applied to or reassigned to an Audiences segment. When you click `Enrich` → `Signals` on an audience segment, only signals that were originally created through Audiences appear in the list. + +To add a signal to your Audiences, create it from within Audiences in one of two ways: + +- **From a segment:** Navigate to an audience segment → click `Enrich` → `Signals` → select a signal type and configure it. +- **From the Data Hub:** Navigate to **People** or **Companies** → **Data Hub** → **Signals** tab → click `+ Add signal`. + +Signals created either way are stored in the **Data Hub** and can be applied to multiple audience segments. If you have an existing signal configured in a table that you want to use in Audiences, recreate it using either path above — your table-based signal can continue running independently alongside the new Audiences signal. + ### How do I remove records from an audience? To remove a specific set of records from your audience, filter a segment down to just those records and then archive the group. **Admin access is required** — the option is not visible to Members or Viewers. From 189ece44a2eb95506ca017cdb77a94bc057f70d6 Mon Sep 17 00:00:00 2001 From: George Dilthey <32441489+george-dilthey@users.noreply.github.com> Date: Thu, 16 Jul 2026 21:19:57 -0400 Subject: [PATCH 2/3] fix: remove spurious trailing backslash on filter groups line --- docs/audiences.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/audiences.md b/docs/audiences.md index cb6fd46d..73ca588d 100644 --- a/docs/audiences.md +++ b/docs/audiences.md @@ -241,7 +241,7 @@ To create a new audience: 2. Click **New audience** in the top-right corner of the list, or click the `+` next to `My Audiences` in the sidebar. 3. Select `Criteria` and then add a `Filter` or `Filter group`. - **Filters** evaluate a single condition at a time. All top-level filters are joined with AND — a record must match every one. - - **Filter groups** combine multiple conditions using their own AND/OR logic. Within a single filter group, all conditions share the same operator — all AND or all OR; changing the operator in the group header switches all conditions at once. To mix AND and OR, use a nested filter group. For example, to build `A AND B AND (C OR D)`: add A and B as top-level filters, click **`+ Filter group`**, then add C and D inside the group. Once the group contains two or more conditions, a small **`and`** button appears between them — click it to switch to **`or`**.\ + - **Filter groups** combine multiple conditions using their own AND/OR logic. Within a single filter group, all conditions share the same operator — all AND or all OR; changing the operator in the group header switches all conditions at once. To mix AND and OR, use a nested filter group. For example, to build `A AND B AND (C OR D)`: add A and B as top-level filters, click **`+ Filter group`**, then add C and D inside the group. Once the group contains two or more conditions, a small **`and`** button appears between them — click it to switch to **`or`**. ### Filter operators by field type From 96a6028cef44f6b1c1956330194c1a03a6f85272 Mon Sep 17 00:00:00 2001 From: George Dilthey <32441489+george-dilthey@users.noreply.github.com> Date: Thu, 16 Jul 2026 21:35:36 -0400 Subject: [PATCH 3/3] fix: add explicit plan availability framing to signal detection-layer note and FAQ --- docs/audiences.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/audiences.md b/docs/audiences.md index 73ca588d..4f351a4c 100644 --- a/docs/audiences.md +++ b/docs/audiences.md @@ -344,7 +344,7 @@ After you add a signal: - Multiple signals each get their own column; the `Signal Summary` column aggregates all results. Click any row to see per-signal detail. - Any other segment that filters on this signal type will also surface these results. -**Signals are a detection layer — taking action on results happens in the companion segment.** Signals identify matching records and write results to each record's profile, but do not trigger automated actions on their own. To act on the records a signal detected, navigate to the auto-created companion segment and click `Send` to enroll them in a workflow or CRM export, or click `Enrich` to run a bulk enrichment on the matching records. To enroll new members automatically as the signal continues to fire over time, publish a workflow trigger on the companion segment — see [Connecting a workflow to a segment](#connecting-a-workflow-to-a-segment) below. +**Signals are a detection layer — taking action on results happens in the companion segment.** Signals identify matching records and write results to each record's profile, but do not trigger automated actions on their own. To act on the records a signal detected, navigate to the auto-created companion segment and click `Send` to enroll them in a workflow or CRM export, or click `Enrich` to run a bulk enrichment on the matching records. To enroll new members automatically as the signal continues to fire over time, publish a workflow trigger on the companion segment — see [Connecting a workflow to a segment](#connecting-a-workflow-to-a-segment) below. Available on Growth and Enterprise plans — if Audiences is not yet enabled in your workspace, contact your Growth Strategist. **Monitoring signal progress** @@ -679,6 +679,8 @@ Three things to check: ### A signal I created in a table isn't showing up when I try to add it to an audience — why? +Available on Growth and Enterprise plans. If Audiences is not yet enabled in your workspace, contact your Growth Strategist. + Signals created inside a Clay workbook table write results back to that table and are scoped to it — they cannot be applied to or reassigned to an Audiences segment. When you click `Enrich` → `Signals` on an audience segment, only signals that were originally created through Audiences appear in the list. To add a signal to your Audiences, create it from within Audiences in one of two ways: