Menstrupedia · TruBuddy — shared audience pool

Audience catalog

Refreshed automatically twice a month. Pick a product to see its ranked, gate-passed audiences — ask Claude for a live recommendation any time, it reads straight from this catalog.

—last refreshed

—audiences catalogued

—currently active (at refresh)

—history window

—

High overlap threshold % audiences overlapping an active audience by more than this are flagged and ranked below the rest

CPO thresholds (₹) an audience whose last 5 completed attempts all cost more than its product's threshold is ranked far below the rest

Ad account Show blacklisted audiences

Catalog not built yet First automatic refresh is scheduled — or ask Claude to run it now to populate this page.

Schema (Cloudflare D1, database meta-ads-audience-catalog): meta_status (refresh metadata) · audiences (targeting, scope, size — refreshed twice a month) · ad_set_facts (raw per-ad-set spend/purchases). Weighted spend, weighted conversions, shrunk CPO, tier, and overlap are computed live on every page load from ad_set_facts, using today's date for recency decay and the actual currently-active ad sets — not precomputed at refresh time. Reach/day is shown normalized to a ₹500/day budget, linearly rescaled from the refresh-time ₹450 basis stored in audiences. "Last used" and "Active now" are scoped to the audience's literal name, not its internal identity — Meta allows the exact same name to be reused across many different targeting definitions, so these reflect what anyone browsing by name in Ads Manager would see. Ranking: audiences passing both the overlap ceiling and 7-day recency gate are ranked first (by confidence tier, then shrunk CPO); anything failing either gate drops below all gate-passing audiences regardless of tier or CPO; audiences benched by track record rank below that; blacklisted audiences rank last of all. Size floor stays a soft badge, not a ranking gate. Bayesian shrinkage uses recency decay (half-life 90 days). Track record (the 5-dot column): an attempt is a run of consecutive days an audience actually spent money, bounded by an observed $0 day — not by ad-set status, since ads inside an ad set can be paused without the ad set itself changing status. Each attempt's CPO is judged against its product's threshold (set above, or that product's own live average CPO if unset); an audience whose last 5 completed attempts all failed is benched. A row with no known attempts shows "—", not empty dots; once it has at least one, grey dots pad any remaining pending slots up to 5. Hover a dot for that attempt's dates, spend, and daily breakdown. This data is only fetched for a bounded set of audiences that matter (top-ranked, currently active, or explicitly requested) via each row's "⋮" menu, never for the whole catalog at once. The "Ad account" toggle above filters which already-loaded rows are shown by which Meta ad account ever ran that audience — it's a view filter only, computed client-side from data already returned by the API; it doesn't change rank numbers, gating, or the overlap/recency math. Each row's "⋮" menu blacklists/unblacklists it (blacklisted audiences are excluded from this table entirely, with no rank gap, unless "Show blacklisted audiences" is checked, in which case they're shown but forced below every other row) and, until fetched, offers "Fetch track record".