Skip to content

mbfinotti/advertising-skills / skills/lookalike-audience-seeds

lookalike-audience-seeds

Verified

Select and size the seed customer list behind a lookalike, similar, or value-based audience - which customers to upload, how many, and whether the matched count (not the row count) clears the platform floor - with RFM and value-based selection, a negative-selection pass, a privacy and consent gate before any customer list upload, and a fallback ladder when the floor cannot be cleared. Use whenever the user mentions a lookalike or similar audience, a seed list, a customer list upload, match rate, an audience that is too small, or says their lookalike isn't working - even if they never say 'seed'. Covers B2B and B2C. Do NOT use to design the whole targeting tier structure - use mbfinotti/advertising-skills@ad-audience-targeting instead.

FileKindSize
SKILL.mdskill md33.7 KB
evals/evals.jsonconfig40.4 KB
references/examples.mdmarkdown6.4 KB
references/platform-floors.mdmarkdown14.4 KB
references/seed-selection.mdmarkdown14.3 KB

evals/evals.json

View on GitHub
{
  "skill_name": "lookalike-audience-seeds",
  "evals": [
    {
      "id": 1,
      "prompt": "We're Corvid Analytics, a B2B data-quality platform with an ACV around $42K. I exported our closed-won contacts from the CRM - 700 people, work emails only - and I want to build a LinkedIn lookalike from them to find similar buyers. 700 is comfortably above LinkedIn's 300 minimum so we should be fine, right? If we need more volume I can always throw in our MQL list, there are about 6,000 of those. Walk me through how you'd set this up.",
      "expected_output": "A corrected plan that computes the effective matched seed, shows the 700-contact list fails LinkedIn's 300 matched floor, refuses MQL padding, and routes through identity enrichment (fallback rung 1) with its compliance cost, targeting Predictive Audiences rather than the sunset Lookalike product.",
      "files": [],
      "expectations": [
        "States that LinkedIn's 300 minimum applies to matched members, not uploaded rows, and rejects the user's row-count reading",
        "Applies an expected match rate around 30-40% for a work-email contact list on LinkedIn",
        "Computes the effective seed at roughly 210-280 matched (700 x 0.30-0.40) and concludes it fails the 300 matched floor",
        "Corrects the 'LinkedIn lookalike' framing: LinkedIn Lookalike Audiences were sunset in February 2024, replaced by Predictive Audiences",
        "Refuses to add the 6,000 MQLs to the seed, keeping closed-won as the selection and stating that selection quality is never the first thing traded (SQL-only beats all-MQL)",
        "Recommends fallback ladder rung 1, identity enrichment appending personal identifiers, as the route to the floor",
        "Explains why the cheap rungs are structurally empty here: an all-time closed-won list has no recency window left to widen and no adjacent segment that is not lost deals or MQLs",
        "Mentions expanding won accounts into contacts via title, seniority, and function filters before upload",
        "Notes that enrichment brings a vendor DPA, counsel or lawful-basis re-check, and roughly a week or more of procurement coordination",
        "Cites LinkedIn sizing guidance of roughly 10,000+ uploaded emails for a contact list (or 1,000+ companies for a company list) to reliably clear 300 matched",
        "Advises judging early results on match quality and engagement only, deferring the seed verdict to cohort maturity because the B2B sales cycle lags the conversion read",
        "Recommends sizing the post-enrichment upload at 2-3x the target matched count",
        "States that if no procurement route or vendor DPA exists, rung 1 is deleted from the ladder and the honest finding is that no ladder clears the floor - reported as the finding rather than filled with a looser seed"
      ]
    },
    {
      "id": 2,
      "prompt": "I run growth at Lumme Botanica, a DTC skincare brand with about 62,000 lifetime customers. We want a value-based lookalike on Meta. My plan: take the top 15% of customers by total lifetime spend and upload that with lifetime spend as the value column. Our orders are split between our US store (USD) and EU store (EUR), so I'd merge both into one file. Some rows are gift recipients with $0 spend, and one corporate account has spent about 200x our median customer. Sound good?",
      "expected_output": "A rejection of cumulative lifetime spend as the value column with margin or predicted LTV substituted, fixes for the zero values, mixed currencies, and whale outlier, upload-mapping and terms-acceptance checks, and a proper RFM or value-slice selection with recency window and negative-selection pass.",
      "files": [],
      "expectations": [
        "Rejects cumulative lifetime spend/revenue as the value column",
        "Explains the reason: cumulative revenue tracks tenure, and high-revenue low-margin customers poison the model",
        "Recommends margin or predicted LTV as the value column instead",
        "Flags the $0 gift-recipient rows: the value column must contain positive values only",
        "Flags the USD/EUR merge: one currency per list, since platforms do not normalize mixed currencies",
        "Recommends capping or winsorizing the 200x corporate whale so a few large accounts do not skew the model",
        "Requires refunded amounts to be excluded from the value computation",
        "Requires confirming the value column is actually mapped at upload",
        "Warns that an unmapped value column silently builds a standard (not value-based) lookalike, and that the value-based option being absent at audience-build time means the mapping failed",
        "Notes that value-based audiences on Meta require a separate terms acceptance",
        "Recommends selection via RFM Champions + Loyal cohorts, or the top 10-25% by predicted LTV or margin, rather than the top 15% by spend",
        "Applies a recency window (30-90 days default, up to 180 for pixel-tracked buyers) instead of the full lifetime list",
        "Runs the negative-selection pass: strip refunders, chargebacks, serial returners, discount-only buyers, employees, and wholesale accounts",
        "Keeps existing customers in the seed while suppressing them from the acquisition campaign at delivery level"
      ]
    },
    {
      "id": 3,
      "prompt": "Help me figure out our Meta match rate at Fenwright Home. We uploaded a 22,000-row customer CSV through the UI and matched only about 9%. Our security team insisted on SHA-256 hashing every email with a per-customer salt before the file left our network - glad we did that at least. Phones are stored like '+44 07911 123456', emails are mixed case with some trailing spaces, and about a third of the rows date from 2021-2022. Should we just buy a data enrichment service to fix the match rate?",
      "expected_output": "A diagnosis naming the salted pre-hash as the primary cause, a normalization-first fix plan (plaintext UI upload, E.164-style phones, lowercased emails, more identifiers, stale-row cut) ordered ahead of enrichment, with the effective seed recomputed and match rate kept as a hygiene indicator only.",
      "files": [],
      "expectations": [
        "Identifies the salted pre-hash as the primary cause: the platform hashes on ingest, so a salted or double hash never matches",
        "Recommends re-uploading normalized plaintext through the UI, with hashing reserved for API or warehouse syncs that require it",
        "Corrects the phone format to digits with country code, no plus sign, no leading zero (E.164-style, e.g. 447911123456)",
        "Corrects emails to lowercased and trimmed",
        "Recommends adding more identifier types per row, since multiple identifiers per row beat email alone",
        "Flags rows older than 12-18 months as past the decay cliff and recommends dropping or archiving them",
        "Warns that dropping old rows lifts the rate partly by shrinking the denominator, so the effective seed must still clear the floor afterwards",
        "Orders the fixes as: normalize formats first, then join identifiers already held, then drop stale rows, with enrichment last",
        "Answers the enrichment question with no: it is the lowest-ratio lever here and not the first move, reserved for cases like B2B work-email lists on consumer platforms",
        "References Meta's documented band (50-80% on good lists, below 40% signaling a poor or outdated list) as the calibration reference",
        "Mentions Meta's Event Match Quality score with the 6.0+ practitioner target",
        "Recomputes or instructs recomputing the effective seed (rows x match rate) against the platform floor after the fixes",
        "Does not treat the improved match rate as evidence of audience quality - match rate is a data-hygiene leading indicator only"
      ]
    },
    {
      "id": 4,
      "prompt": "We're Hafenlicht, a Berlin-based supplement brand. I want a Customer Match list in Google and a Meta custom audience from our 30,000 EU customers this week, then lookalikes off both. One segment idea: buyers of our sleep-and-anxiety product line converted best, so we'd seed from them. Our agency says consent isn't an issue because everything gets SHA-256 hashed before upload, so it's anonymous data and GDPR doesn't really apply. Legal review is backed up for a month - can we define and upload the seed now and let them review in parallel?",
      "expected_output": "A hard stop at the privacy and consent gate: the hashing-equals-anonymous claim rejected with the German precedent, Consent Mode v2 required for EEA Customer Match, the health-category segment refused, upload-in-parallel refused, and platform-native engagement audiences named as the only currently available seed class.",
      "files": [],
      "expectations": [
        "Stops at the privacy and consent gate before doing any selection work, rather than proceeding with the seed definition",
        "Rejects the agency's claim: SHA-256 output is pseudonymous, not anonymous, so consent obligations survive hashing",
        "References the German precedent - the Bavarian DPA position upheld by the Higher Administrative Court Munich (2018) - that customer-list custom audiences require prior consent",
        "Requires Consent Mode v2 signals with both consent fields GRANTED for EEA use of Google Customer Match, mandatory since March 2024",
        "Rejects the sleep-and-anxiety product segment as a seed built on a sensitive health category",
        "Refuses to upload in parallel with legal review: no upload before the consent basis is confirmed",
        "Names the specific missing gate items (documented lawful basis or consent, Consent Mode v2 status, platform terms acceptance) instead of a generic 'check with legal'",
        "States that suppression, opt-outs, and deletions must be enforced once in the warehouse before any sync, not per-platform afterwards",
        "Disclaims legal advice and routes the lawful-basis question to the user's counsel",
        "Does not emit a Seed Specification, because an unconfirmed consent basis fails the evidence gate",
        "Treats list-based seed sources as unavailable (deleted from the menu), not merely delayed",
        "Offers platform-native engagement audiences as the seed class still available now, since they never leave the ad account and trigger no consent gate",
        "Mentions platform customer-list terms acceptance for the specific ad account as a gate item"
      ]
    },
    {
      "id": 5,
      "prompt": "Bramblewick makes premium dog gear. Meta's docs say a good seed is 1,000-5,000 people, but we only have 850 buyers from the last 90 days. My plan: top up with our 24,000-person newsletter list plus everyone who opened a marketing email in the past 12 months - that gets us way over 5,000. We haven't signed any data vendors and don't plan to. Good approach?",
      "expected_output": "A refusal to pad the seed, showing the 850 buyers already clear Meta's matched floor, with openers rejected in favor of clickers, and any extra volume sought through the fallback ladder - recency widening first given no enrichment vendor - never through undifferentiated subscribers.",
      "files": [],
      "expectations": [
        "Refuses to pad the seed with newsletter subscribers to hit the recommended size",
        "Cites the homogeneity principle: seed homogeneity affects audience effectiveness more than its size, per Meta's own guidance",
        "Notes the practitioner consensus that a few hundred high-value customers outperform thousands of undifferentiated subscribers, labeled directional rather than audited",
        "Distinguishes Meta's 100 matched floor from the 1,000-5,000 recommended band",
        "Computes the effective seed: 850 rows at Meta's 50-80% band is roughly 425-680 matched, which clears the 100 floor",
        "Rejects email openers as a source because Apple Mail Privacy Protection (2021) inflated opens into noise, allowing clickers only",
        "If more volume is wanted, walks the fallback ladder instead of loosening selection quality",
        "Applies the documented ladder flip (rung 2 before rung 1) because no enrichment vendor is contracted and there is recency left to widen: 90 to 180 days first",
        "Mentions stacking an adjacent segment of the same homogeneity (rung 3) as a later step, not the newsletter list",
        "If email clickers are ever exported, requires checking that ESP consent scope covers ad-platform upload rather than assuming it",
        "Runs the negative-selection pass on the 850 buyers before export",
        "Keeps existing customers in the seed and suppresses them from the acquisition campaign at delivery level",
        "Recommends sizing the upload at 2-3x the matched target"
      ]
    },
    {
      "id": 6,
      "prompt": "Nordvik Living sells furniture and lighting online in Germany, France, the Netherlands, the UK, and Sweden - about 18,000 customers total, though Sweden is only around 120 of them. I was going to upload one combined customer list to Meta and build one lookalike targeting all five countries. I'd also love splits by product line (furniture vs lighting), a high-AOV split, and maybe language versions. It's just me managing this, updating lists by hand whenever I remember, and opt-outs get processed inside each ad platform separately when someone complains.",
      "expected_output": "A per-country seed-and-lookalike plan replacing the single global audience, the split order applied with each split floor-checked (Sweden fails), split count capped to the single owner's capacity, a real refresh cadence with warehouse-first opt-out suppression, and an overlap check.",
      "files": [],
      "expectations": [
        "States that Meta lookalikes are country-scoped by construction, so one global seed produces an averaged audience serving no market well",
        "Requires one seed-and-lookalike pair per country",
        "Applies the split order country > product line > high-AOV vs all, with language/region last because it usually correlates with country and adds the least new information",
        "Checks each split's own effective seed against the floor before committing to it",
        "Identifies the Sweden split as failing: roughly 120 customers at 50-80% match is about 60-96 matched, under Meta's 100 floor, so Sweden needs the fallback ladder or gets deferred",
        "Caps the number of splits at what the single named refresh owner can maintain, advising against taking every proposed split at once",
        "Notes each split carries a permanent standing cost: an audience to refresh, monitor for overlap, and keep above its floor forever",
        "Notes that setup effort per split is identical (one WHERE clause) - the standing cost is what limits the count, not the query work",
        "Rejects the 'whenever I remember' refresh: static CSV uploads do not auto-refresh, so a weekly-to-monthly cadence with a named owner is required",
        "Recommends an automated warehouse sync over manual CSV on efficiency and compliance-cost grounds",
        "Flags the per-platform opt-out handling: suppression must be enforced once in the warehouse before any sync, and a manual CSV re-uploads yesterday's opt-outs every cycle",
        "Positions a CSV only as a bridge, with a named owner and a date the sync lands",
        "Recommends an overlap check between the resulting audiences with the roughly 20-30% concern threshold",
        "Frames the high-AOV split as a test (one comparison, keep the winner) run only after the country and product-line splits are settled"
      ]
    },
    {
      "id": 7,
      "prompt": "Perch & Pine, a home-decor DTC brand, launched a Meta lookalike from our customer list 5 days ago. Match rate came back 72%, so the seed is clearly solid, but CPA is running 40% over target already - I think the seed is bad and want to swap it tomorrow. Context: our previous seed version had amazing CPA, but finance later found those customers barely reordered and mostly bought with our 40%-off welcome code. We've never actually measured cohort LTV for acquired customers. Which seed do we keep? I was going to compare the two audiences head-to-head as two ad sets next week.",
      "expected_output": "A measurement correction: match rate rejected as a seed grade, the 5-day read refused pending learning-phase exit, the prior version diagnosed as the low-CPA/weak-LTV pitfall with a re-seed on margin, cohort LTV by seed version installed as the KPI with a baseline-building first checkpoint, and the ad-set head-to-head replaced by a split test or geo holdout.",
      "files": [],
      "expectations": [
        "Rejects '72% match so the seed is solid': match rate is a data-quality leading indicator only, never a grade of seed quality",
        "Refuses to judge the new seed at 5 days because the learning phase has not completed",
        "Cites roughly 50 optimization events per ad set per week, or 2-4 weeks at low volume, as the reading threshold",
        "Diagnoses the previous seed version as the documented low-CPA/weak-LTV pitfall: the seed scaled low-margin converters",
        "Prescribes re-seeding on margin or predicted LTV and retiring that seed version",
        "Flags discount-only buyers (the 40%-off welcome-code cohort) as a negative-selection exclusion for the next seed",
        "Names cohort LTV at 90/180/365 days by seed version as the KPI to grade seeds on",
        "States the pass threshold: the seed version's 90-day acquired-customer cohort LTV meets or beats the account average at equal-or-better CPA",
        "Given no measured baseline, states the seed cannot be graded yet and sets the first cohort checkpoint as the baseline-building run",
        "Rejects the naive two-ad-set head-to-head comparison because audience overlap contaminates it",
        "Recommends a user-level split test or a geo holdout as the valid comparison methods",
        "Defaults to the split test, escalating to the geo holdout when the decision is expensive to reverse or the split test's own read is disputed",
        "Notes the geo holdout's evidence advantage: it survives cross-device identity loss and measures incremental sales rather than platform-attributed ones",
        "Treats the seed as a versioned artifact with a re-check scheduled one cohort window out"
      ]
    },
    {
      "id": 8,
      "prompt": "Our new agency sent Calloway Cycles (bike accessories, B2C plus a wholesale line) a targeting doc that looks recycled: (1) build Google Similar Audiences from our converter list; (2) LinkedIn Lookalike Audiences from our 2,400 wholesale-buyer contacts; (3) a TikTok lookalike from our 400 best customers - the doc says TikTok's minimum is 100, so that's fine; (4) a Google Demand Gen lookalike, the doc says 100 minimum there too; (5) on Meta, hard-restrict delivery to the lookalike so no budget leaks to anyone outside it. Anything we should push back on before signing off?",
      "expected_output": "A point-by-point rebuttal: Similar Audiences and LinkedIn Lookalikes are dead products with named replacements, TikTok and Demand Gen floors corrected to the stricter 1,000 figures (400 rows cannot reach TikTok's floor), the Meta inclusion-lock corrected to suggestion-not-rule, and floors flagged as moving targets to verify live.",
      "files": [],
      "expectations": [
        "Flags Google Similar Audiences as removed in August 2023, so item 1 is a dead product",
        "Notes the replacement mechanism: first-party lists now act as signals (Customer Match) feeding optimized targeting and Demand Gen lookalikes",
        "Flags LinkedIn Lookalike Audiences as sunset in February 2024",
        "Names LinkedIn Predictive Audiences with a 300 matched minimum as the replacement",
        "Mentions the cap of 30 Predictive Audiences per ad account",
        "Takes TikTok's stricter 1,000 floor over the 100 figure, applying the rule that when a platform's own pages disagree you plan against the stricter number",
        "Concludes that 400 customers cannot reach TikTok's 1,000 matched floor at any match rate, since uploaded rows are below the floor itself",
        "Mentions the 10,000 practitioner-recommended TikTok seed as the realistic bar",
        "Takes 1,000 active matched (API docs) as the Google Demand Gen lookalike floor over the Help Center's 100",
        "Corrects the Meta hard-restrict belief: inclusion audiences behave as suggestions under Advantage+, and the delivery algorithm may serve outside them",
        "States that only exclusion/suppression audiences remain hard rules",
        "Notes Meta's detailed-targeting exclusions were removed in March 2025, leaving custom-audience exclusions under Audience Controls as the remaining hard suppression",
        "Computes the LinkedIn wholesale list's effective seed: 2,400 contacts at roughly 30-40% work-email match is about 720-960 matched, clearing the 300 floor",
        "Recommends verifying floors against the platforms' live documentation because floors move, citing Google Customer Match's cut from 1,000 to 100 in 2025 as the example"
      ]
    },
    {
      "id": 9,
      "prompt": "Marlowe Threads is a DTC apparel brand. The founder wants a prospecting lookalike live on Meta by Friday - hard date, board meeting. Problem: our customer data is scattered across three systems, no unified export exists, and our only data engineer is booked out for five weeks. A consultant told us 'purchasers are always the strongest seed, everything else is a downgrade - build the export first, launch later.' The Meta pixel has been on the site for a year with add-to-cart and checkout events firing, and our product videos get decent view counts. What would you actually ship by Friday?",
      "expected_output": "A Friday-shippable plan built on platform-native engagement seeds (high-intent viewers or checkout initiators), the purchaser ranking's export-exists condition stated, the deadline named as what re-ranked the menu, quality floor held above page-engagers/all-visitors, and the starved purchaser-export asset scheduled as the compounding follow-up.",
      "files": [],
      "expectations": [
        "Does not delay the launch to build the purchaser export first",
        "States the condition behind the consultant's rule: purchasers lead the ranking when the customer export already exists, and here it does not",
        "Recommends platform-native engagement seeds for Friday: high-intent page viewers and/or checkout/add-to-cart initiators",
        "Names the hard deadline and data-team unavailability as the interview answers that re-ranked the source menu",
        "Notes platform-native audiences build inside the ad account in minutes and skip the customer-list upload and its consent gate entirely",
        "Refuses to drop below high-intent viewers/lead-form submitters on the ranking - no page-engagers or all-visitors seed, because past that point per-row quality falls faster than effort",
        "If video viewers are used, requires the 75%+ completion tier rather than 3-second views",
        "Flags the one judgment call for high-intent viewers: agreeing which pages count as intent",
        "Notes engagement-sourced audiences auto-refresh (Meta roughly every 3-7 days), removing the manual refresh burden",
        "Names what the efficiency order starves - the customer-identity asset (purchaser export / warehouse sync) - and schedules it as the compounding follow-up rather than dropping it",
        "States a promote-it trigger for the export: a compounding-asset mandate, or the same account losing this round again",
        "Notes platform-native audiences are durable against mobile-OS tracking loss, with retention windows up to 365 days",
        "Respects the learning phase after the Friday launch: no performance verdict before roughly 50 optimization events per ad set per week or 2-4 weeks"
      ]
    },
    {
      "id": 10,
      "prompt": "Vellum Coffee, US-only DTC. We're ready for a Meta lookalike seed and I want the final spec today. Data: 21,000 customers; email plus phone on about 80% of rows; consent for ad matching captured at checkout; opt-outs sync to our warehouse nightly. Our BI tool has a column called 'ltv_score' someone built years ago - nobody remembers whether it's revenue, margin, or a model output, but let's use it as the value column since it's there. After filtering to purchasers from the last 120 days minus the usual junk (refunders, staff, two wholesale accounts), we land at 6,200 rows. For the match rate just use 95% so the numbers look safe. Target: new-customer CPA under $28; our account's 90-day acquired-customer LTV averages $54. Write the spec.",
      "expected_output": "A Seed Specification built on the documented Meta match band instead of the invented 95%, with the unknown-provenance ltv_score refused as a value column (flat seed or provenance requested), effective seed computed against the floor, and consent, refresh, measurement, and re-check lines filled from the given data.",
      "files": [],
      "expectations": [
        "Refuses the 95% match assumption and estimates from Meta's documented 50-80% good-list band, explicitly labeling it an estimate",
        "Applies the evidence gate to 'ltv_score': a value column of unknown provenance means the seed is not value-based until someone can say what the column measures",
        "Does not place 'ltv_score' in the spec as the value column - either specifies a flat seed or requests provenance first",
        "Emits a Seed Specification block carrying the named fields: platform/audience type, definition, value column, row count, expected match, effective seed, fallback used, exclusions, consent basis, refresh, measurement, re-check",
        "Computes the effective-seed line as rows x match vs floor: 6,200 x 0.50-0.80 is roughly 3,100-4,960 matched against Meta's 100 floor, so it clears (within the 1,000-5,000 recommended band)",
        "States the expected-match basis on its line: platform documented range plus a list-quality adjustment",
        "Fills the consent-basis line with the checkout consent and the nightly warehouse-enforced opt-out suppression",
        "Fills the refresh line with a cadence, a named owner, and the mechanism (manual CSV vs automated sync)",
        "Fills the measurement line with the $28 new-customer CPA target and cohort-LTV checkpoints by seed version against the $54 account average",
        "Sets the re-check date one cohort window out (roughly 90 days)",
        "Records the negative-selection pass in the exclusions line and delivers existing-customer suppression as a separate delivery-level audience, keeping purchasers in the seed",
        "Addresses the 120-day recency window against the guidance: acceptable only for pixel/CAPI-tracked buyers (default 30-90 days), otherwise tightened toward 90",
        "States the pass threshold: the seed version's 90-day acquired-customer cohort LTV must meet or beat the $54 account average at equal-or-better CPA"
      ]
    }
  ],
  "trigger_queries": [
    { "query": "Which customers should I upload to build a Meta lookalike?", "should_trigger": true },
    { "query": "My lookalike audience isn't performing - could the source list be the problem?", "should_trigger": true },
    { "query": "How many people do I need in a customer list for a LinkedIn predictive audience?", "should_trigger": true },
    { "query": "Our custom audience match rate is only 12%, what's wrong with our file?", "should_trigger": true },
    { "query": "TikTok says my audience is too small to serve, what now?", "should_trigger": true },
    { "query": "Should I use my newsletter list as the source for a similar audience?", "should_trigger": true },
    { "query": "Help me pick the seed for a value-based lookalike", "should_trigger": true },
    { "query": "What's the minimum audience size for Customer Match lookalikes these days?", "should_trigger": true },
    { "query": "Can I build a lookalike from only 400 customers?", "should_trigger": true },
    { "query": "Best customers to seed a lookalike from - top spenders or most recent buyers?", "should_trigger": true },
    { "query": "I uploaded 8,000 emails to Meta but the audience won't build", "should_trigger": true },
    { "query": "Do I need to hash my customer CSV before uploading it to an ad platform?", "should_trigger": true },
    { "query": "which crm segment should feed our similar audience on google", "should_trigger": true },
    { "query": "We're a B2B SaaS with 350 closed-won customers - can we do lookalikes at all?", "should_trigger": true },
    { "query": "How recent should the customers in my seed list be?", "should_trigger": true },
    { "query": "Should refunders be removed from our customer list before we upload it for ads?", "should_trigger": true },
    { "query": "Is a 30% match rate on our uploaded list normal?", "should_trigger": true },
    { "query": "How do I make a value-based audience actually use our LTV data?", "should_trigger": true },
    { "query": "Our lookalike went stale - do customer lists need refreshing?", "should_trigger": true },
    { "query": "One lookalike for all our European markets, or one per country?", "should_trigger": true },
    { "query": "What list size do I need before Meta's lookalike gets good?", "should_trigger": true },
    { "query": "The audience we uploaded shows fewer people than the rows in the file - why?", "should_trigger": true },
    { "query": "Seed list strategy for a new prospecting audience", "should_trigger": true },
    { "query": "Can I use email subscribers who opened our campaigns as an ad audience source?", "should_trigger": true },
    { "query": "Are work emails okay for a TikTok custom audience upload?", "should_trigger": true },
    { "query": "GDPR and uploading customer lists to Facebook - what do we need before we do it?", "should_trigger": true },
    { "query": "My similar audience on Google disappeared, what replaced it?", "should_trigger": true },
    { "query": "What percentage of uploaded contacts typically match on LinkedIn?", "should_trigger": true },
    { "query": "Should our seed be our best 500 customers or all 20,000?", "should_trigger": true },
    { "query": "how big should a lookalike source audience be", "should_trigger": true },
    { "query": "We only have 900 buyers - pad the audience with site visitors?", "should_trigger": true },
    { "query": "Setting up a predictive audience from our contact list, walk me through sizing", "should_trigger": true },
    { "query": "Is it bad to seed a lookalike from everyone who ever bought, even 5 years ago?", "should_trigger": true },
    { "query": "Customer list upload keeps getting rejected as too small", "should_trigger": true },
    { "query": "What identifiers should each row of an ad-platform customer upload have?", "should_trigger": true },
    { "query": "Do lookalikes work with a phone-number-only list?", "should_trigger": true },
    { "query": "Value column for a Meta value-based audience - revenue or margin?", "should_trigger": true },
    { "query": "How often should we re-upload our customer list to ad platforms?", "should_trigger": true },
    { "query": "Building audiences from our warehouse - what should the export contain for a lookalike?", "should_trigger": true },
    { "query": "Why does our lookalike convert cheap but the customers never come back?", "should_trigger": true },
    { "query": "Our agency wants to build ad audiences from our anxiety-supplement buyers - any issue?", "should_trigger": true },
    { "query": "similar audience seed size for snapchat?", "should_trigger": true },
    { "query": "What counts as a good source audience for Advantage+ lookalikes?", "should_trigger": true },
    { "query": "The ads platform says minimum 1,000 matched - our list is 3,000 rows, are we fine?", "should_trigger": true },
    { "query": "Which is better as an audience source: checkout abandoners or video viewers?", "should_trigger": true },
    { "query": "Should I exclude current customers from the list I upload for prospecting lookalikes?", "should_trigger": true },
    { "query": "First lookalike for our Shopify store - where do I start with the customer list?", "should_trigger": true },
    { "query": "Does list quality really matter more than list size for lookalikes?", "should_trigger": true },
    { "query": "Audience match rate dropped after we salted the hashes - related?", "should_trigger": true },
    { "query": "Pinterest actalike source list requirements?", "should_trigger": true },
    { "query": "We want to find people similar to our top 10% of customers - how do we define that 10%?", "should_trigger": true },
    { "query": "Can a 600-contact ABM list power a LinkedIn audience?", "should_trigger": true },
    { "query": "whats the deal with uploading EU customer emails to google ads now", "should_trigger": true },
    { "query": "How do I know if my uploaded audience is big enough before spending?", "should_trigger": true },
    { "query": "Best practices for the customer file behind a Customer Match campaign", "should_trigger": true },
    { "query": "Our lookalike audience never left 'populating' - is my list the issue?", "should_trigger": true },
    { "query": "Do I split my seed list by product line or keep one big list?", "should_trigger": true },
    { "query": "Fixing a low match rate: enrichment vendor or clean the data first?", "should_trigger": true },
    { "query": "What's a realistic match rate for a 2-year-old email list?", "should_trigger": true },
    { "query": "Reddit ads customer list minimum - is our 5,000 list enough?", "should_trigger": true },
    { "query": "Grade my plan: seed the lookalike with everyone who opened an email in 12 months", "should_trigger": true },
    { "query": "I need an audience of people like our subscribers - what data do I feed the platform?", "should_trigger": true },
    { "query": "The board wants lookalikes live Friday but our customer export doesn't exist yet", "should_trigger": true },
    { "query": "Amazon DSP lookalike from our buyer list - how many user IDs do we need?", "should_trigger": true },
    { "query": "Are lookalike seeds supposed to be refreshed, or is upload once enough?", "should_trigger": true },
    { "query": "help, uploaded customer audience too small to use for a lookalike", "should_trigger": true },
    { "query": "Design our full paid targeting plan - cold, interest, lookalike, and retargeting tiers", "should_trigger": false },
    { "query": "How should we layer prospecting vs retargeting audiences across the funnel?", "should_trigger": false },
    { "query": "Set recency windows and frequency caps for our cart-abandoner retargeting sequence", "should_trigger": false },
    { "query": "Build a message ladder for each stage of our retargeting funnel", "should_trigger": false },
    { "query": "Map the buying committee for our $80K ACV deal and how to reach each role", "should_trigger": false },
    { "query": "Which job functions should we target for enterprise IT purchases?", "should_trigger": false },
    { "query": "Our Meta pixel is double-counting purchases - help me debug deduplication", "should_trigger": false },
    { "query": "Verify our conversion events fire once before the campaign launches", "should_trigger": false },
    { "query": "Meta reports 210 conversions, GA4 shows 92 - reconcile the gap", "should_trigger": false },
    { "query": "Why does our CRM show half the revenue the ad platform claims?", "should_trigger": false },
    { "query": "Our whole account's ROAS dropped 35% this month - diagnose it", "should_trigger": false },
    { "query": "CPA doubled across every campaign, where do I start?", "should_trigger": false },
    { "query": "Is our top video ad fatigued or is it just auction CPM inflation?", "should_trigger": false },
    { "query": "Write 10 ad copy variants from this value proposition", "should_trigger": false },
    { "query": "Draft a creative brief for a UGC video campaign", "should_trigger": false },
    { "query": "Design a creative test plan with per-cell budgets and kill rules", "should_trigger": false },
    { "query": "Mine our search terms report for negative keywords", "should_trigger": false },
    { "query": "Which negative match type should I use at the account level?", "should_trigger": false },
    { "query": "Are we pacing to spend our $60K monthly ad budget?", "should_trigger": false },
    { "query": "Should we switch from manual CPC to target ROAS bidding?", "should_trigger": false },
    { "query": "Split our $200K quarterly budget across Google and Meta", "should_trigger": false },
    { "query": "Set a maximum allowable CAC policy for the whole org", "should_trigger": false },
    { "query": "Compute our blended CAC and judge whether it's healthy", "should_trigger": false },
    { "query": "Which paid channels fit a $5K/month budget for a B2B tool?", "should_trigger": false },
    { "query": "Should we consolidate our 40 ad sets without resetting learning?", "should_trigger": false },
    { "query": "When has our winning campaign earned a budget increase?", "should_trigger": false },
    { "query": "Audit the landing page our ads send traffic to", "should_trigger": false },
    { "query": "Score these five video hooks and tell me which deserve budget", "should_trigger": false },
    { "query": "Build a swipe file of competitor ads organized by hook type", "should_trigger": false },
    { "query": "Is a carousel the wrong format for our lead-gen objective?", "should_trigger": false },
    { "query": "Plan paid promotion of our CEO's LinkedIn posts", "should_trigger": false },
    { "query": "Write UGC scripts with three hook variants for our skincare brand", "should_trigger": false },
    { "query": "Adapt our ad copy for AI assistant answer placements", "should_trigger": false },
    { "query": "How do I move from PPC specialist to paid media lead?", "should_trigger": false },
    { "query": "Design the interview loop for hiring a senior media buyer", "should_trigger": false },
    { "query": "Which paid media newsletters and podcasts should I follow?", "should_trigger": false },
    { "query": "What's my seed round pitch missing? We're raising $2M", "should_trigger": false },
    { "query": "Generate seed data for our staging database", "should_trigger": false },
    { "query": "Best practice for setting a random seed in reproducible ML experiments?", "should_trigger": false },
    { "query": "Run an RFM segmentation for our email retention campaigns", "should_trigger": false },
    { "query": "Which customers should get our loyalty program invite based on LTV?", "should_trigger": false },
    { "query": "Build lookalike models in Python to predict churn", "should_trigger": false },
    { "query": "Find companies similar to our best customers for cold outbound", "should_trigger": false },
    { "query": "Clean our email list to improve deliverability", "should_trigger": false },
    { "query": "Set up a suppression list so we stop emailing unsubscribers", "should_trigger": false },
    { "query": "Do we need a cookie consent banner for our EU site?", "should_trigger": false },
    { "query": "Segment our audience personas for content marketing", "should_trigger": false },
    { "query": "How do I grow my podcast audience?", "should_trigger": false },
    { "query": "Improve our SEO by analyzing search audience intent", "should_trigger": false },
    { "query": "Which influencers have audiences similar to our customer base?", "should_trigger": false },
    { "query": "A/B test our landing page headline", "should_trigger": false },
    { "query": "How should we structure our email welcome sequence?", "should_trigger": false },
    { "query": "Identify our ICP from our customer data", "should_trigger": false },
    { "query": "Export our CRM contacts to a CSV for the sales team", "should_trigger": false },
    { "query": "What's a good survey panel size for statistical significance?", "should_trigger": false },
    { "query": "Estimate the sample size for our conversion A/B test", "should_trigger": false },
    { "query": "Set up reverse ETL from our warehouse to Salesforce", "should_trigger": false },
    { "query": "GDPR data-deletion workflow for our SaaS product", "should_trigger": false },
    { "query": "Hash user passwords - bcrypt or argon2?", "should_trigger": false },
    { "query": "Match and dedupe duplicate contacts inside our CRM", "should_trigger": false },
    { "query": "Which audience should our webinar invite email go to?", "should_trigger": false },
    { "query": "Plan the audience Q&A segment for our conference talk", "should_trigger": false },
    { "query": "Increase our Instagram followers organically", "should_trigger": false },
    { "query": "Winsorize the outliers in our revenue forecast model", "should_trigger": false },
    { "query": "Choose a CDP vendor for our martech stack", "should_trigger": false },
    { "query": "Our display retargeting frequency is annoying users, cap it", "should_trigger": false }
  ]
}
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall