docs(audiences): add field-filter warning to Snowflake and BigQuery import steps

[george-dilthey]

What changed

Added an inline note to step 6 of both the Importing from Snowflake and Importing from Google BigQuery sections in docs/audiences.md. The note clarifies that only columns mapped during initial setup will appear as filter options in the Audience — matching the note that already exists for Salesforce (step 5) and HubSpot (step 4).

Before:

• Snowflake step 6: Map your Snowflake columns to Audience fields.
• BigQuery step 6: Map your BigQuery columns to Audience fields.

After (both): Map your [source] columns to Audience fields — only columns mapped here will appear as filter options in your Audience. Include all fields you plan to segment by at this stage; fields not mapped during initial setup cannot be used as segment filters unless you reconfigure the sync.

Why

A Handshake enterprise customer (Casey Romeo) asked in Intercom conversation #215475011657921: "Can I add a bulk enrichment from a SQL query that pulls from our own product data tables? Want to create an audience based on product actions."

Human support rep Bo Morin answered correctly (Slack thread linked below), explaining that you can connect BigQuery or Snowflake to import records into Audiences via SQL. The critical caveat Bo highlighted: "Fields that are not brought in during setup cannot be used as segment filters unless the sync is reconfigured."

That caveat is already documented in the Best Practices section ("Import more fields than you think you need") and in the Salesforce and HubSpot import steps — but it was missing from the Snowflake and BigQuery import steps, which are the sources most relevant to customers bringing in product data from a warehouse. This PR closes that parity gap.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/lbdldjky/inbox/conversation/215475011657921
• Slack thread (trigger): https://clay-hq.slack.com/archives/C09LBHW94CT/p1783537248355599

Verifier sub-agent verdicts:

• Claim "fields not mapped during warehouse sync cannot be used as segment filters": PASS — libs/shared/src/filter-builder/filterRuleDefinitions/audiencesRuleFieldDefinitions.ts:188-212 (audienceColumnsToRuleFieldDefinitions filters by canUserCreateFilterWith) and libs/shared/src/audiences/field-management.ts:66-83
• Claim "Upsert Audiences Record action exists": PASS — public-actions/apps/clay-labs/actions/upsert-audiences-record/action-definition.ts:20, isPublic: true, available on all Audiences-enabled plans
• BigQuery SQL import: UNKNOWN (Eppo gate enable-bigquery-audiences outside repo) — the existing doc already correctly notes BigQuery import is "in early access"; this PR does not change that framing

Uncertainties

None for the specific claim this PR adds (only mapped fields are filterable). The verifier returned PASS with concrete file:line evidence.

Related observations

• PR docs(audiences): add Databricks as beta import source #1485 is open on this file and adds a Databricks section. It does not include the filter-field warning on the new Databricks step 7 — the same gap exists there and a reviewer may want to add the same note when reconciling.
• The verifier noted that the "Import from CRM" label in bulk enrichment is a generic V3 action source, not strictly Salesforce-only. This doesn't affect the docs changed in this PR but could be worth clarifying in docs/bulk-enrichment.md separately.

Closes DOC-1088

[linear-code]

DOC-1088