ads-connector

Routing reference for live ad-platform operations at Creekside Marketing — both READING data and MAKING CHANGES. Meta / Facebook / Instagram is handled via PipeBoard MCP's Meta connector (verified live, full read + write surface). Google Ads is handled via PipeBoard MCP's Google Ads connector under a separate namespace (verified live 2026-04-23 — `list_google_ads_customers` returned 33 Creekside accounts); full read + write surface. Both MCPs are provided by PipeBoard. A read-only Google Ads Python SDK pipeline backs up historical data in Supabase. Use whenever a user or agent asks how to pull, query, read, create, update, pause, duplicate, or otherwise manage ads, ad sets, campaigns, creatives, audiences, pixels, keywords, or lead forms on either platform. Do NOT use for historical trend queries against Supabase tables (e.g. meta_insights_daily, google_ads_insights_daily) — this skill is for live, direct-from-platform operations.