← ClaudeAtlas

marketing-analyticslisted

Analyze marketing performance data using Coupler.io MCP tools (list-dataflows, get-schema, get-data). Use when the user asks to pull or analyze data from Coupler.io dataflows/data sets, generate marketing performance reports, understand campaign ROI, or investigate changes in business metrics. Make sure to use this skill whenever the user mentions Coupler.io data, marketing dashboards, channel comparisons, campaign analysis, or asks questions like "why did conversions drop", "which channel has best ROI", "where should I spend more", "what's working", "show me my marketing numbers", "pull my latest data", even if they don't explicitly say "marketing analytics". For deep paid-ads-only analysis (per-platform ad efficiency, budget pacing, brand vs non-brand, ad fatigue), use the ppc-analytics skill instead — this skill owns the cross-channel view.
coupler-io/skills · ★ 33 · AI & Automation · score 72
Install: claude install-skill coupler-io/skills
# Marketing Analytics Analyze marketing performance across channels using data from Coupler.io dataflows. This skill guides you through retrieving data, computing key metrics, detecting anomalies, and presenting actionable insights — all in language a marketing manager can act on. ## Step 1: Discover and Select Data Sources Every analysis starts by connecting to the user's data through Coupler.io MCP tools. ### 1a. Discover available dataflows Call `list-dataflows` to see what marketing data the user has connected. Each dataflow represents a data pipeline (e.g., "Google Ads → Claude", "Mailchimp Campaigns", "GA4 Traffic"). ### 1b. Select relevant dataflows with the user The number of available dataflows determines how you present the selection: **Fewer than 5 dataflows:** List them all by name and source type. Ask the user to confirm which ones to include in the analysis. **5–20 dataflows:** Group them by apparent channel or source (the dataflow names usually encode this — "google_ads_campaigns", "mailchimp_weekly", etc.). Present the groups with counts. Let the user select entire groups or individual flows. **More than 20 dataflows:** Do not list them all. Instead, infer which are relevant from the user's request (e.g., "budget allocation" → look for flows with spend/cost columns). Present only the candidates — up to 5–7 — with a one-line rationale for each: ```bash I found 3 dataflows likely relevant to your budget question (out of 24 total): 1. google_ads_camp