docs(audiences): add CSV export workaround via Add to workbook#1550
Open
george-dilthey wants to merge 3 commits into
Open
docs(audiences): add CSV export workaround via Add to workbook#1550george-dilthey wants to merge 3 commits into
george-dilthey wants to merge 3 commits into
Conversation
Expands the "How do I export my audience data to CSV?" FAQ section from a one-sentence dead end to a complete answer with workaround steps. Adds the Add to workbook path (Send → Add to workbook → export from the resulting Clay table), the 50,000 row limit, the paid plan requirement for table CSV export, and beta framing for the Add to workbook feature which is rolling out to Growth/Enterprise. Triggered by Intercom conversation 215475023741402 where a customer could not find the export button because they were in the Audiences view, and Fin had no workaround to offer.
Contributor
The prior note incorrectly stated that CSV export is unavailable on trial workspaces. Per code (useViewRecordCount.ts:14, useStartViewExport.ts:28-29), trial workspaces can export but are capped to 50 rows per download. Updated both docs to use accurate "may be capped to 50 rows" language (BETA — behind enable-view-record-limit-on-trial Eppo flag, ~34% rollout as of late Jun). Also corrects the same wrong claim in docs/sources.md line 66 for consistency.
The note added in the prior commit incorrectly stated CSV export is unavailable on trial workspaces. Updated to reflect that trial workspaces may be capped to 50 rows per download (behind Eppo flag enable-view-record-limit-on-trial). Verified: useViewRecordCount.ts:14 VIEW_RECORD_LIMIT_ON_TRIAL=50, useStartViewExport.ts:28-29 passes recordLimit=50 when trial limit exceeded. Flag was at ~34% rollout as of late Jun 2026 per #team-growth-eng Slack.
This was referenced Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Expanded the "How do I export my audience data to CSV?" FAQ entry in
docs/audiences.mdfrom a one-sentence dead end into a complete answer with the workaround steps. Also corrected a wrong claim about trial workspace CSV export limits in bothdocs/audiences.mdanddocs/sources.md.audiences.md changes:
sources.md change:
Why
Intercom conversation #215475023741402 shows a customer ("how can I export my people list") who was looped in circles by Fin for nearly an hour. Fin correctly identified that the Audiences screen has no CSV export button, but had nothing actionable to offer next. The existing doc FAQ confirmed the limitation in one sentence and stopped there — no workaround.
Human support agents Ryan Phung and Bo (bo.morin@clay.com) gave the correct answer: use Add to workbook (Send → Add to workbook) to push the audience to a regular Clay table, then export from there. Bo also mentioned a 50,000-row cap and said "exporting is a paid feature." Screenshots in the conversation (Intercom parts #11, #16, #36, #41) show the customer's Audiences view, the theme menu they were clicking instead of the export path, and the enrichment panel.
Verifier results (two rounds)
Round 1 verifier — Claim 1:
PASS — Audiences header and Send dropdown contain no CSV export action. Code:
ExportsDropdown.tsx,useAvailableExportActionsForSegment.ts.Round 1 verifier — Claim 2 (Add to workbook feature):
UNKNOWN — Feature exists (
ExportAudienceToWorkbookModal.tsx) but gated behindEppoFeatureFlags.EnableAudiencesSendToWorkbook(defaultfalse). Liveness unconfirmable from code alone. First verifier found Slack signal in #product-releases ("rolling out to Growth/Enterprise by end of sprint") — conservatively framed as BETA in the doc.Round 1 verifier — Claim 3 (trial plan export):
FAIL — The initial note said "not available on trial workspaces." Code shows trial CAN export, capped to 50 rows via
VIEW_RECORD_LIMIT_ON_TRIAL = 50(useViewRecordCount.ts:14) andrecordLimitquery param (useStartViewExport.ts:28-29). Corrected in attempt 1.Round 2 verifier — Corrected Claim 3:
BETA — 50-row cap confirmed correct. Gated behind
enable-view-record-limit-on-trialEppo flag (~34% rollout as of late Jun per #team-growth-eng Slack). Updated both docs to say "may be capped to 50 rows" to account for partial rollout. Verifier confirmed: do NOT document free plan export blocking (no code evidence, no Slack signal).Source link(s)
clay-base/apps/frontend/src/components/Audiences/AudiencesCommandCenterSidebar/Exports/ExportsDropdown.tsx(no CSV export in Audiences dropdown)clay-base/apps/frontend/src/components/Audiences/AudiencesCommandCenterSidebar/Exports/useAvailableExportActionsForSegment.ts:22(EnableAudiencesSendToWorkbookflag, default false)clay-base/apps/frontend/src/components/Audiences/AudiencesCommandCenterSidebar/Exports/ExportAudienceToWorkbookModal.tsx(modal title "Send to workbook", max 50,000 rows)clay-base/apps/frontend/src/state/View/useViewRecordCount.ts:14(VIEW_RECORD_LIMIT_ON_TRIAL = 50)clay-base/apps/frontend/src/components/TableToolbar/useStartViewExport.ts:28-29(trial export passesrecordLimit=50)Uncertainties
Add to workbook: Gated behind
EnableAudiencesSendToWorkbookEppo flag (defaultfalse). Liveness can't be confirmed from code — targeting config lives in Eppo dashboard. A Slack thread in #product-releases indicates it's rolling out to Growth/Enterprise but no GA date was found. Doc uses conservative beta framing: "currently rolling out to Growth and Enterprise workspaces — if you don't see it, contact support to enable it."Trial export 50-row cap: Correct value per code (
VIEW_RECORD_LIMIT_ON_TRIAL = 50) but itself gated behindenable-view-record-limit-on-trialEppo flag at ~34% rollout as of late Jun 2026. Doc uses "may be capped" language. A Jul 6 Slack thread confirms the feature is live and affecting customers but also notes known bugs.Free plan export blocking: No code evidence that free plans are blocked from CSV export (backend default is
export: true; any blocking would be in Stripe product metadata outside the repo). No Slack signal either. Did NOT document any free-plan restriction.Related observations
docs/audiences.mddo NOT cover this gap: PR docs(audiences): add FAQ clarifying dedup scope — Audiences only, not Clay tables #1547 (deduplication FAQ), PR docs(audiences): document Salesforce custom object export limitation and workaround #1528 (Salesforce custom object export FAQ), PR docs(audiences): add field-filter warning to Snowflake and BigQuery import steps #1507 (Snowflake/BigQuery field mapping note), PR docs(audiences): add Databricks as beta import source #1485 (Databricks import section). All are materially different from the CSV export workaround added here.docs/audiences.mdhas no step-by-step section for importing records via CSV directly into Audiences (the customer's original import method). The frontmatter and plan availability paragraph mention "importing via CSV" but there are no instructions. This is a separate gap not triggered by this ticket.sources.md:66wrong claim ("Export is unavailable on trial workspaces") was also present in the existing docs. Corrected in this PR as a consistency fix exposed by this change.Closes DOC-1143