getaero-io/gtm-eng-skills / skills/deepline-gtm
deepline-gtm
UnverifiedGTM leads, enrichment, outreach, Plays, developer signals/Reo.dev. Providers: adyntel,affinity,ai_ark,akta,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bluesky,bounceban,brave,browserbase,builtwith,buyercaddy,cbinsights,clay,clickhouse,close,cloudflare,contactout,contextdev,crunchbase,crustdata-v3,customer_db,databricks,dataforseo,datagma,dealroom,deepline_ip_to_company,deepline_native,deeplineagent,deepseek,discolike,dnb,edges,emailbison,emailguard,enformion,enigma,exa,findymail,firecrawl,fireflies,firmable,forager,fullenrich,fundable,generic_http,getleads,gong,google_ads_audiences,google_workspace,govfiles,grain,hackernews,harvestapi,heyreach,hubspot,hunter,icypeas,instantly,intercom,ipqs,kaspr,kernel,kickbox,leadmagic,lemlist,limadata,linkedin_ads_audiences,luma,lusha,meerapi,meta_audiences,millionverifier,nooks,notion,openmart,opensosdata,openwebninja,outreach,parallel,particle,peopledatalabs,pitchbook,podscan,polymarket,postgres,predictleads,prospeo,quickenrich,rapidapi,….
provider-playbooks/meta-audiences.md
View on GitHub# Meta Audiences
Use these tools for Meta customer-list custom audiences and Conversions API events.
- `meta_audiences_send_conversion_events` sends standard or custom events to an explicit pixel/dataset ID, with hashed matching identifiers and optional estimated lifetime value. See its tool documentation for event fields, permissions, deduplication, and test-event verification.
- Collect `_fbc` and `_fbp` from the actual visitor's first-party browser cookies at signup/action time, before invoking a Play. Forward only those values as `request_context.cookies._fbc` / `_fbp`, or map them to `user_data.fbc` / `fbp`. Preserve them unchanged and unhashed through enrichment, batching and retries. A server-side Play cannot recover a visitor's browser cookies later; never substitute a worker/Deepline session or enrichment data. Omit unavailable cookies. Only `fbc` may be derived from a real `fbclid` plus its original observation time; never synthesize `fbp`.
- `meta_audiences_get_conversion_quality` reads web-event match quality, identifier coverage, event coverage, deduplication feedback, freshness, and additional conversions reported. It requires Dataset Quality access, which is separate from audience access. See its tool documentation for permissions and metric selection.
- Pick the ad account first: call `meta_audiences_list_ad_accounts` and confirm the target by `name`. Only accounts with `enabled: true` can be targeted; `is_default` marks the one an omitted `ad_account_id` resolves to. Either pass that account's `id`, or omit `ad_account_id` and read the account the call used back from `data.ad_account_id` (`data.ad_account_source` says `explicit`, `default`, or `sole`). Never copy an ad account id from old runs, files, or another workspace: it can belong to a customer.
- Create one custom audience per segment and then keep syncing member files into the same audience ID.
- Use `mode: "replace"` for full snapshots and `mode: "append"` for incremental adds.
- Deepline hashes supported identifiers locally before upload.
- Watch `operation_status`, `delivery_status`, the `approximate_count_*_bound` pair, and invalid-entry counts when evaluating match health.
- Meta reports audience size as a range. Read `approximate_count_lower_bound` and `approximate_count_upper_bound`; `approximate_count` is a midpoint Deepline derives for backward compatibility, not a figure Meta returns.
- Sizes stay null until Meta finishes processing an upload, and Meta withholds them entirely for audiences below its minimum size threshold. A null count shortly after a sync is normal, not a failed upload.
- Meta never reports a customer-list audience below 1,000 people: a new or empty audience reads back with both bounds at 1000. When `approximate_count_is_minimum_bucket` is true, report the size as "under about 1,000, not yet measurable", never as 1,000 matched people.
- `delivery_status` code 411 means a low rate of matched people, which is the signal that a list matched poorly.
- Meta locks an audience while a users upload ingests: `operation_status` code 414 means a replace is still processing, and further writes fail with `META_AUDIENCE_UPDATE_IN_PROGRESS` until it settles. Poll `meta_audiences_get_audience_status` until `operation_status` code returns 200, then retry the full sync in one call. Do not resume a partial upload with `mode: "append"`; re-send the complete list.
- Send the whole member list in one `sync_audience_members` call. Chunking into separate calls collides with the ingest lock and strands a partial audience.
- `audience_id` must be the numeric id Meta returns. Read it from `meta_audiences_create_audience` at `data.audience_id` (the same field delete and sync return; `data.audience.id` holds the same value); a literal "undefined" id means the caller read the wrong response field, and the tool now rejects it before compiling the payload.
- Connect with a system user token: Dashboard → Integrations → Meta Audiences → Connect opens the setup page, which saves the token through `POST /api/v2/integrations/meta_audiences/token`. The dashboard no longer offers Meta Login for Business, because until Meta approves Deepline's App Review it only works for accounts that hold a role on the Deepline app. Existing Login for Business connections keep working. The token comes from the customer's own Business Manager: create a Meta app with the Marketing API product, add a system user (Employee role is enough), assign the ad account with Manage campaigns (ads) and the app with Develop app, and generate a token with `ads_management` and `ads_read` and no expiry (`business_management` is not needed). A human in that business must accept the Custom Audience terms once per ad account, or audience creation fails with "Custom audience terms not accepted" and a terms link; send that link to the customer. The accounts API reports `customAudienceTermsAccepted` per account after setup.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |