docs(clay-ads): broaden beta note from Sync panel to Clay Ads feature

[george-dilthey]

What changed

Updated a single note in docs/clay-ads.md: replaced "The Sync panel is currently in beta" with "Clay Ads is currently in beta". The previous phrasing scoped the beta status to one specific UI panel; the deployed commit adds a BetaBadge to the entire Ad Sync top navigation bar (visible on every Ad Sync view), making the broader scope accurate.

Why

Deploy clay-run/clay-base 6e59a78...8e4eb05 (https://github.com/clay-run/clay-base/actions/runs/29109126961) introduced commit 8e4eb050: fix(ads): bad css,remove press that leads to billing page,beta badge (#43418). Among other CSS/UX fixes, this commit adds <BetaBadge /> to WorkspaceTopbarNavigatorAdSync.tsx — the breadcrumb/top navigation shown when a user is viewing any Ad Sync. The badge renders unconditionally for all users who have access to the Ad Sync route.

The existing doc note said only "The Sync panel" (the right-hand status panel in Step 4) is in beta, which undersells the beta scope: the verifier confirmed the entire Ad Sync route is gated by the EnableAdsV2 Eppo flag (default false) at apps/frontend/src/routes/WorkspaceRoutes.tsx:214-223, and the BetaBadge appears on the overall feature view, not just one panel within it.

Source link(s)

• Deploy compare: https://github.com/clay-run/clay-base/compare/6e59a78574d87574ee2b6ccb7f02433209612c25...8e4eb050e3d8d5d340887f508fb187d8f405b44d
• Deployed commit 8e4eb050: WorkspaceTopbarNavigatorAdSync.tsx:40 adds <BetaBadge /> unconditionally (verifier file:line evidence)
• Eppo gate: EppoFeatureFlags.EnableAdsV2 = 'enable-ads-v2', default false, at libs/shared/src/EppoFeatureFlags.ts:206 — gates the entire Ad Sync route
• BetaBadge tooltip: 'This feature is only available to Beta users' at apps/frontend/src/components/Badges/BetaBadge.tsx:9
• Verifier verdict: BETA — BetaBadge renders unconditionally within the component; Ad Sync route is gated to users with EnableAdsV2 enabled

Uncertainties

The EnableAdsV2 flag's exact targeting config lives in the Eppo dashboard (outside the repo). The verifier's Slack context confirms "open beta for Growth plan" as of a July 9 message, consistent with rolling out to Growth and Enterprise as the docs state. No hard uncertainty on the claim itself.

Related observations

• A July 7 Slack announcement in #proj-ads by Larry Li describes relaxing the GDPR filter so non-US contacts from 1P-origin data (CSV/CRM/DWH) are no longer auto-filtered from LinkedIn/Meta syncs. This is a separate behavioral change from a prior deploy and may warrant a separate doc update to clay-ads-compliance-best-practices.md (which currently says "Today, you're not able to source contacts outside the US for ad targeting" — potentially stale after the July 7 change).
• A March 2026 Slack note flagged that the Clay Ads doc title still said "Clay Ads (beta)" after the feature GA'd; a Notion task was created to remove the beta label. The July 10 deploy re-adds a BetaBadge (for the feature as a whole, gated by EnableAdsV2), which is consistent with the feature still being in controlled beta rollout despite the earlier GA announcement for Enterprise customers.

Confidence: medium

Closes DOC-1085

[linear-code]

DOC-1085