docs(audiences): document ad sync beta availability and per-workspace connections - #2395
Open
george-dilthey wants to merge 2 commits into
Open
docs(audiences): document ad sync beta availability and per-workspace connections#2395george-dilthey wants to merge 2 commits into
george-dilthey wants to merge 2 commits into
Conversation
Contributor
george-dilthey
marked this pull request as ready for review
August 28, 2026 19:07
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
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
Added two notes to the "Syncing audiences to ad platforms" section in
docs/audiences.md:Beta/plan availability framing — Audience ad syncs are available on Growth and Enterprise plans, currently in beta rollout. The "Sync to ad platforms" option is visible to all Audiences-enabled workspaces (as an upgrade prompt for non-eligible plans). If on Growth or Enterprise but still seeing an upgrade prompt, contact your Growth Strategist. (BETA verdict from verifier, attempt 2.)
Per-workspace ad account connections — Ad platform connections are stored per workspace. Connecting them in one workspace does not carry over to other workspaces — users are prompted to re-authenticate during the sync setup flow in each workspace. (PASS verdict from verifier.)
Why
Intercom conversation #215475646437927: Andrea Liu from Xero asked why she couldn't create an ad sync for a "California People" segment in workspace
Xero_Data_Plus_Test, and whether she needed to set up ad accounts in that workspace since they were already configured in the Xero Enterprise workspace.Support rep Bo answered: (1) yes, ad account connections are per workspace, and (2) the feature needed to be enabled for that workspace. Neither fact was documented in the Audiences doc, causing Fin to be unable to answer without human escalation.
Source link(s)
apps/frontend/src/hooks/ad-syncs/useAdsEntitlement.ts:22–36;apps/frontend/src/components/Audiences/AudiencesCommandCenterSidebar/Exports/useAudienceExportDropdownItems.tsx:56–66;#proj-adsAug 20 2026 — billing gate live for Growth/Enterpriseapps/api/v3/auth/models/app-account.model.ts:83,165–168Uncertainties
The billing gate announcement (
#proj-adsAug 20 2026) says Growth/Enterprise workspaces "will have access from a billing perspective" but also notes Clay staff handle flag enablement for plan trials. It's not fully confirmed whether all plan-eligible workspaces auto-unlock today or whether Clay staff still need to enableenableAdsV2per workspace. The doc says "contact your Growth Strategist" which is the safe, actionable guidance regardless. The verifier's Claim 1 FAILed on first attempt (I had incorrectly documented a "join beta from Settings > General" self-serve flow); the corrected claim was verified as BETA on second attempt.Related observations
Materiality confirmation vs. open PRs on this doc: Reviewed all flagged PRs (#2383, #2370, #2356, #2354, #2349, #2348, #2345, #2323, #2321, #2305, #2303, #2295, #2291, #2288, #2280, #2272, #2261, #2251, #2245, #2232, #2231, #2225, #2224, #2215, #2210, #2204, #2203). None add content to the "Syncing audiences to ad platforms" section. The closest is PR #2225 which adds a single mention of ad sync being in beta in the "When should I use Audiences" FAQ bullet — but does not document it in the dedicated "Syncing audiences to ad platforms" section where users landing on that topic would look, and does not add the per-workspace connections note. Both additions here are new and not covered by any open PR.
Closes DOC-2163