Marketing analytics skill

Marketing analytics and data-driven optimization for B2B SaaS campaigns.

by shalintripathi·MIT license·★ 20 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Marketing Analytics

## Step 0 (always first): Load brand context

**Before producing any deliverable, look for a `brand-context.md` file** in the user's project root (also check `./.claude/brand-context.md…

- **If it exists:** read it in full and treat it as binding for this run. Hand its contents to every specialist agent you route work to, al…
- **If it does not exist:** say so, point the user at the template ([`templates/brand-context.md`](../../templates/brand-context.md)), and…

**Non-negotiable regardless of which path applies:** do not invent customer names, metrics, funding, integrations, certifications, or outco…

---

## What This Is

Marketing Analytics brings together performance analysts, conversion rate optimization specialists, customer insights researchers, data sto…

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Marketing analytics

shalintripathi/main1 file shown
SKILL.md
Show the full text410 lines

Marketing Analytics

Step 0 (always first): Load brand context

Before producing any deliverable, look for a brand-context.md file in the user's project root (also check ./.claude/brand-context.md and ./docs/brand-context.md). It holds the company's ICP, positioning, messaging pillars, citable proof, voice, banned words, and compliance constraints.

  • If it exists: read it in full and treat it as binding for this run. Hand its contents to every specialist agent you route work to, alongside the task brief. Its "Rules for agents reading this file" section overrides an agent's own defaults.
  • If it does not exist: say so, point the user at the template (templates/brand-context.md), and offer to generate a filled draft by interviewing them or by reading their website and existing content. Then proceed with explicitly-labelled assumptions — never silently invented ones.

Non-negotiable regardless of which path applies: do not invent customer names, metrics, funding, integrations, certifications, or outcomes. Only proof recorded in brand-context.md (or supplied directly in the request) may be used as fact. Where a claim would help but no evidence exists, emit a [NEEDS INPUT: …] marker in the deliverable rather than a plausible-sounding guess.


What This Is

Marketing Analytics brings together performance analysts, conversion rate optimization specialists, customer insights researchers, data storytellers, and marketing operations architects to transform data into decisions. This skill orchestrates your analytics practice to measure what matters (pipeline impact, customer quality, efficient CAC), identify optimization opportunities (conversion rate improvements, targeting precision, channel efficiency), and communicate findings to stakeholders. Whether you're building a marketing dashboard, running an A/B test program, conducting customer research to understand buyer behavior, or presenting performance analysis to leadership, Marketing Analytics routes your request to the right specialist and ensures your data drives better marketing decisions.

The Team: 9 Specialist Agents

# Agent File What They Do
1 Performance Analyst agents/analytics-performance-analyst.md Measures and optimizes marketing performance across channels and campaigns, tracks KPIs, and identifies performance drivers through data analysis and reporting
2 Conversion Rate Optimizer agents/analytics-conversion-rate-optimizer.md Designs and executes CRO testing programs, analyzes conversion funnels, identifies friction points, optimizes user experience for higher conversion rates, and gates every experiment on whether the funnel can actually power it (sample size, duration, comparability horizon)
3 Customer Insights Researcher agents/analytics-customer-insights-researcher.md Designs and runs customer research (interviews, surveys, VoC mining) and grades what it can claim — sampling frame and non-response, evidence levels, cross-channel corroboration, saturation, jobs-to-be-done and research-based personas
4 Data Storyteller agents/analytics-data-storyteller.md Translates data analysis into clear narratives and compelling visualizations that communicate findings and drive decision-making
5 Marketing Ops Architect agents/analytics-marketing-ops-architect.md Designs the data architecture inside the stack — MAP/CRM integration, lead lifecycle and scoring, field governance, duplicate prevention (resolve before create) and merge survivorship rules — authors the marketing instrumentation contract (tracking plan, event taxonomy, UTM taxonomy) that every measurement audit grades against, implements tracking and attribution, and builds dashboards and reporting systems that enable data-driven marketing
6 GTM Data Strategist agents/analytics-gtm-data-strategist.md Owns the go-to-market data that arrives from outside — the data requirement written before shopping, provider bake-offs on a held-out sample of your own accounts, coverage scored separately from accuracy and wrong answers, identity-match corroboration, enrichment waterfalls ordered by measured cost per usable record, a decay rate measured rather than quoted, verification states including accept-all, suppression screening, and the provenance and lawful-basis record (GDPR Article 14) behind every acquired list
7 MarTech Stack Strategist agents/analytics-martech-stack-strategist.md Owns the martech stack as a portfolio: capability-first tool selection and build-vs-buy, shadow-tool and overlap rationalization, and the true switching cost of replacing a system — including the suppression record, engagement history, personalization layer and measurement continuity a platform migration puts at risk
8 Demand Planner agents/analytics-demand-planner.md Builds the number before the period starts — the revenue target decomposed backwards through the funnel into stage volumes, an assumption register where every conversion rate and cycle time is a dated own-funnel measurement or is stamped inferred, the sales-cycle lag that decides which period a lead can land in (carry-in, carry-out, latest useful creation date), the sales / production / addressable-audience ceilings that cap what a plan may promise, marginal rather than blended cost per source, a scenario band derived from your own plan-versus-actual dispersion instead of a borrowed ±20%, declared re-forecast triggers, and a versioned plan of record that makes a miss diagnosable
9 Marketing AI Operations Lead agents/analytics-marketing-ai-ops-lead.md Governs how the team uses AI — an AI use register per use case, legalize-don't-ban intake for shadow AI, data-class rules for which tool may receive what, an autonomy ladder with a never-generate list, a prompt-injection check (private data + untrusted content + outbound path caps a workflow at human review), eval sets re-run on every model/prompt/vendor change, default-on platform AI settings, kill switches, an AI incident log, and an EU AI Act Art. 4 literacy record by role

How to Use

Routing User Requests

Marketing Performance Analysis → Performance Analyst

  • "Analyze the performance of our latest demand generation campaign"
  • "Create a monthly marketing dashboard showing KPIs by channel"
  • "Identify which channels are driving the most qualified pipeline"
  • "Compare performance across campaigns to identify what's working"

Demand & Pipeline Planning → Demand Planner

  • "How many leads do we need next year to hit the revenue target?"
  • "Build the bottom-up marketing plan and reconcile it against the number finance gave us"
  • "Our Q1 plan assumes leads created in January close in March — is that possible?"
  • "Give me a conservative / planned / upside band with the triggers that tell us which one we are in"
  • "We missed plan — which assumption was wrong?"

Conversion Rate Optimization → Conversion Rate Optimizer

  • "Design a CRO testing program for our landing pages"
  • "Analyze our conversion funnel and identify where prospects drop off"
  • "Run A/B test comparing headline variations on our homepage"
  • "Optimize form fields to increase lead capture completion rate"
  • "How much traffic do we need to A/B test this page, and how long will it take?"
  • "We don't have enough traffic to reach significance — what should we do instead?"
  • "Should we use a Bayesian test because our sample is small?"

Customer Research & Insights → Customer Insights Researcher

  • "Conduct survey research to understand what messages resonate with our target buyer"
  • "Interview customers to understand decision process and evaluation criteria"
  • "Analyze user behavior data to identify content preferences"
  • "Research competitive buyer perception to understand market positioning opportunity"

Data Communication & Visualization → Data Storyteller

  • "Create a visual dashboard showing marketing funnel metrics"
  • "Present Q3 performance analysis to executive leadership"
  • "Design infographic summarizing campaign results for stakeholders"
  • "Build a customer journey visualization based on analytics data"

Marketing Systems & Infrastructure → Marketing Ops Architect

  • "Design our marketing attribution model (multi-touch vs. first-touch vs. last-touch)"
  • "Build a marketing dashboard infrastructure with real-time data updates"
  • "Implement tracking and data collection for marketing funnel"
  • "Create a data dictionary and standardized metrics definitions for marketing"

MarTech Stack, Tool Selection & Platform Migration → MarTech Stack Strategist

  • "Audit our martech stack — what are we paying for that we don't use?"
  • "We have too many tools and they don't talk to each other"
  • "Should we buy this tool, build it, or does something we already own do it?"
  • "What does it actually cost us to move off our current ESP / MAP / CRM?"
  • "Plan the cutover: what has to carry across, and what breaks if it doesn't?"
  • "How do we make sure our unsubscribes survive the migration?"

Marketing AI Governance & AI Operations → Marketing AI Operations Lead

  • "We need an AI policy for the marketing team — what's allowed?"
  • "Can I paste our customer list / call transcripts into ChatGPT?"
  • "Half the team uses AI tools we never approved — what do we do?"
  • "Our AI email personalization is about to send on its own — is it ready?"
  • "The vendor changed the model and the outputs changed — how would we even know?"
  • "Which AI features are switched on by default in our ad accounts and ESP?"
  • "What AI-literacy training do we need to show under the EU AI Act?"
Execution Model

Phase 1: Baseline & Measurement (1-2 weeks)

  • Marketing Ops Architect establishes current measurement infrastructure: what's being tracked, what's missing, data quality issues
  • Performance Analyst establishes baseline metrics: current funnel conversion rate, cost per lead, cost per acquisition, channel performance
  • Identify measurement gaps: what's not being tracked that should be (first-touch vs. last-touch, buyer quality signals, sales pipeline influence)
  • Define KPIs and success metrics for next phase of work

Phase 2: Analysis & Diagnosis (2-3 weeks)

  • Performance Analyst analyzes historical performance data to identify trends, patterns, anomalies
  • Customer Insights Researcher conducts qualitative research (surveys, interviews) to understand why metrics look the way they do
  • Conversion Rate Optimizer identifies conversion funnel bottlenecks: where do prospects drop off most
  • Develop hypothesis for optimization opportunities
  • Data Storyteller synthesizes findings into narrative and visualizations

Phase 3: Experimentation & Testing (4-12 weeks depending on scope)

  • Conversion Rate Optimizer designs and launches A/B testing program with prioritized hypotheses
  • Marketing Ops Architect ensures testing infrastructure (statistical significance tracking, proper audience segmentation, variant tracking)
  • Customer Insights Researcher collects feedback on tested variations (surveys, interviews to understand why winners won)
  • Performance Analyst monitors test results weekly, identifies winners, and tracks cumulative impact
  • Data Storyteller communicates test results and learnings to stakeholders

Phase 4: Optimization & Scaling (ongoing)

  • Scale winning variations (increase traffic to better-performing page, increase spend on better-performing channel)
  • Iterate next set of tests based on learning from prior tests
  • Customer Insights Researcher continuously monitors sentiment and satisfaction (NPS, CSAT, customer interviews)
  • Performance Analyst tracks improvement impact on downstream metrics (pipeline quality, customer lifetime value)
  • Marketing Ops Architect maintains data freshness and dashboard accuracy
Testing Methodology

CRO Testing Framework

  1. Hypothesis formation (based on data analysis or customer research insight)

    • Expected: Landing page headline focusing on outcome (vs. feature) will increase conversion rate
    • Why: Customer research showed buyers care about time savings more than features
    • Metric: Track conversion rate, form completion rate, downstream pipeline quality
  2. Test design (control, test variant, sample size, duration)

    • Control: current page (baseline performance)
    • Variant: new headline focusing on outcome
    • Sample size: 100 conversions per variant to reach 95% statistical significance
    • Duration: 2 weeks or until sample size achieved
  3. Execution (launch test, monitor for data quality)

    • Route 50% traffic to control, 50% to variant
    • Ensure proper tracking implementation (no missing conversions, no duplicate counts)
    • Monitor daily for anomalies (traffic drop, conversion spike indicating technical error)
  4. Analysis (determine winner, measure impact, document learning)

    • Did test win or lose (statistical significance threshold: 95% confidence, 5% significance level)
    • If winner: magnitude of improvement (e.g., 12% lift in conversion rate = 0.5% absolute improvement)
    • If loser: why did it lose? Did it hurt downstream metrics (lead quality, sales conversion)?
    • Document learning: which element drove result (headline, color, form field, CTA placement)
  5. Iteration (scale winner, test next hypothesis)

    • Scale winning variant to 100% traffic (or keep testing if hold-back analysis desired)
    • Identify next testing hypothesis based on remaining friction points
    • Queue up next test for launch

Testing Prioritization

  • Prioritize tests by estimated impact × confidence level
  • High-traffic pages (more statistical power) → test bigger changes
  • Low-traffic pages → test smaller changes (less power) or focus on traffic growth
  • Test single variable per test (isolates learnings)
  • Test highest-impact elements first: traffic source → landing page → form completion → downstream quality

Statistical Rigor

  • Sample size calculation: depends on baseline conversion rate, desired lift, desired significance level
  • Significance threshold: 95% confidence (5% alpha, meaning 5% chance of false positive)
  • Running time: continue test until sample size achieved or 2-4 weeks, whichever comes first
  • Avoid peeking: don't declare winner until test complete (peeking inflates error rate)
Metrics Hierarchy

Top-Level KPIs (North Star Metrics)

  • Marketing-Influenced Pipeline: revenue impact of marketing activities (pipeline value marketing generated)
  • Marketing Qualified Leads (MQLs): leads that meet quality threshold for sales handoff
  • Customer Acquisition Cost (CAC): fully-loaded cost to acquire new customer (including marketing + sales)
  • Customer Lifetime Value (CLV): expected revenue from customer over lifetime

Mid-Level Metrics (Channel Performance)

  • Cost Per Lead (CPL): average marketing spend to acquire one lead
  • Lead-to-Opportunity Conversion: percentage of leads that convert to sales-accepted opportunity
  • Opportunity-to-Customer Conversion: percentage of opportunities that close to customer
  • Cost Per Opportunity: marketing spend to generate one sales-accepted opportunity
  • Cost Per Acquisition: marketing spend to close one customer deal

Funnel Metrics (Conversion Analysis)

  • Website Traffic: monthly unique visitors by source (organic, paid, direct, referral)
  • Page Conversion Rate: percentage of page visitors who take desired action (form submission, email signup)
  • Form Completion Rate: percentage of form starters who complete form submission
  • Demo/Trial Signup Rate: percentage of engaged prospects who request demo or free trial
  • Sales Accepted Lead Rate: percentage of inbound leads meeting sales qualification criteria

Campaign Metrics (Campaign Performance)

  • Click-Through Rate (CTR): percentage of ad impressions that receive clicks (LinkedIn: 0.5-2%, Google: varies by audience)
  • Cost Per Click (CPC): average cost per paid click (compare to historical benchmark and competitor spend)
  • Video Completion Rate: percentage of video viewers who watch 75%+ of video (YouTube 25-40%, in-feed 15-25%)
  • Lead Quality Score: MQL to SAL conversion rate (higher = better quality leads from source)
  • Return on Ad Spend (ROAS): revenue generated per dollar of paid ad spend

Customer Quality Metrics

  • Sales Cycle Length: average time from opportunity creation to closed customer
  • Win Rate: percentage of opportunities that close to customer (competitive benchmark varies)
  • Average Contract Value: average customer deal size
  • Customer Retention Rate: percentage of customers retained year-over-year
  • Net Revenue Retention: revenue retention + expansion revenue from existing customers
Routing by Analytics Use Case

Landing Page Optimization

  • Conversion Rate Optimizer leads CRO program with testing roadmap
  • Marketing Ops Architect ensures tracking and statistical testing infrastructure
  • Data Storyteller visualizes funnel and testing results
  • Performance Analyst measures impact on downstream metrics (pipeline, customer quality)
  • Success metrics: 20-30% conversion rate improvement over 6 months, improved lead quality

Demand Generation Campaign Analysis

  • Performance Analyst analyzes campaign performance by channel and content
  • Customer Insights Researcher surveys engaged prospects to understand preferences
  • Conversion Rate Optimizer identifies highest-converting assets and channels
  • Data Storyteller visualizes campaign funnel and highlights top performers
  • Marketing Ops Architect ensures proper attribution and tracking
  • Success metrics: hit campaign pipeline goal, exceed average cost-per-lead benchmark, high lead quality

Attribution & Analytics Infrastructure

  • Marketing Ops Architect designs multi-touch attribution model
  • Performance Analyst implements tracking and validates data quality
  • Data Storyteller creates dashboards showing attribution by channel, campaign, source
  • Marketing Ops Architect establishes data governance and standardized metrics
  • Success metrics: 95%+ tracking accuracy, real-time dashboard updates, executive confidence in data

Customer Research Program

  • Customer Insights Researcher conducts qualitative and quantitative research
  • Surveys: 100-200 target buyers on messaging, positioning, feature priorities
  • Interviews: 10-20 deep-dive conversations with buyers and existing customers
  • Behavioral analysis: analyze user behavior on website, demo usage, content preferences
  • Data Storyteller synthesizes findings into narrative and visualizations
  • Success metrics: identify 5-10 actionable customer insights, 3+ changes implemented based on research

Output Standards

Analytics Quality Checklist

Data Accuracy

  • Validation: Data validated against source systems (CRM, ad platform, GA) for accuracy
  • Completeness: 95%+ of expected events tracked and recorded
  • Freshness: Dashboards updated daily or hourly for real-time decision-making
  • Reconciliation: Monthly reconciliation between systems to ensure consistency
  • Documentation: Data dictionary documenting every metric, calculation method, data source

Funnel Analysis

  • All stages defined: awareness → engagement → MQL → SAL → opportunity → customer
  • Conversion rates calculated: percentage of visitors reaching each stage
  • Benchmarks established: compare conversion rates to historical baseline and industry benchmark
  • Segment analysis: conversion rates by traffic source, campaign, buyer persona, vertical
  • Bottleneck identification: which stage has lowest conversion or highest drop-off

Testing Rigor

  • Sample size: adequate sample size (100+ conversions per variant) to reach 95% statistical significance
  • Duration: test runs until sample size achieved or 2-4 weeks minimum
  • Single variable: each test isolates one change (control constant, one variable changed)
  • Statistical significance: 95% confidence level, 5% significance threshold
  • Learning documentation: document what we learned and how it applies to future tests

Dashboard Quality

  • Clarity: metrics labeled clearly, units defined (rates as %, numbers as count or $)
  • Timeliness: updated daily or hourly depending on decision-making frequency
  • Actionability: dashboard shows what's working/not working, not just data points
  • Drilling down: ability to click through to see underlying data (top traffic sources, best-performing content, etc.)
  • Comparisons: shows trends over time and comparisons to benchmarks/targets
Deliverable Specifications

Marketing Dashboard

  • Executive dashboard (1-2 pages): top KPIs, traffic, pipeline, campaign ROI, quarter performance vs. goal
  • Funnel dashboard: conversion rates by stage, segment analysis (by source, campaign, persona), bottleneck identification
  • Channel dashboard: performance by channel (organic, paid, direct, referral, email), cost per lead, conversion rate, trend
  • Campaign dashboard: active campaigns, performance vs. goal, cost per lead, lead volume, quality metrics
  • Testing dashboard: active tests, results, statistical significance, learning captured
  • Daily dashboard: refresh rate hourly, daily KPI performance, alert if metrics miss thresholds

CRO Testing Roadmap

  • Testing hypothesis bank: 20-30 prioritized hypotheses with expected impact and effort estimate
  • Hypothesis: description of test variant, expected outcome, business rationale, success metric
  • Estimated lift: expected conversion rate improvement based on similar tests or industry benchmarks
  • Sample size & duration: how long test will run to reach statistical significance
  • Timeline: Quarters 1-4 roadmap with hypothesis sequence
  • Resource requirements: design effort, analytics effort, traffic required

Performance Analysis Report

  • Executive summary: key findings, performance vs. goal, recommended actions
  • Performance overview: KPIs, trends, comparison to prior period and target
  • Channel analysis: performance by traffic source (organic, paid, direct), cost per lead, conversion rate
  • Campaign analysis: performance by campaign, content, topic, top performers
  • Customer quality analysis: lead quality by source, sales cycle length, customer retention
  • Competitive benchmarking: performance vs. industry benchmarks
  • Recommendations: 3-5 prioritized actions to improve performance

Customer Insights Report

  • Research methodology: survey sample size, interview count, data collection approach
  • Key findings: 5-10 major insights about buyer behavior, preferences, decision criteria
  • Messaging preferences: what messages resonate, which value props matter most by persona
  • Competitive positioning: how buyers perceive competitive alternatives, key decision factors
  • Buying process: stages in buyer journey, key decision drivers by stage
  • Persona profiles: updated or confirmed persona attributes, priorities, concerns
  • Recommendations: how findings should inform marketing strategy, messaging, product

CRO Test Results Document

  • Test overview: hypothesis, expected outcome, why this test matters
  • Test design: control variant, test variant, sample size, duration, audience selection
  • Results: conversion rate by variant, percentage lift, statistical significance
  • Statistical analysis: confidence level, p-value, sample size achieved
  • Impact: downstream metrics (lead quality, sales conversion, customer retention)
  • Learning: what we learned, why winner won, how to apply to future tests
  • Follow-up: next test to run based on this learning

Attribution Model Specification

  • Model type: first-touch vs. last-touch vs. multi-touch (time decay, linear, custom)
  • Touch definitions: what actions count as "touch" (landing page view, form submission, email click)
  • Credit allocation: how credit is allocated among touches (first touch gets 100%, or distributed across journey)
  • Window: how long to track touches (7-day, 30-day, 90-day cookie window)
  • Implementation: technical specification for tracking and attribution calculation
  • Reporting: how results will be reported and updated
  • Validation: methodology to validate attribution accuracy
Quality Review Process

Before publishing any analytics finding or dashboard:

  1. Data Validation: Is the data accurate and complete? Have we reconciled against source systems?
  2. Statistical Rigor: Do findings meet statistical significance requirements? Is sample size adequate?
  3. Bias Check: Could sample bias, selection bias, or confounding variables affect findings?
  4. Clarity: Can stakeholders understand findings without extended explanation?
  5. Actionability: Do findings lead to clear recommendations or decisions?
  6. Sensitivity Check: How sensitive are findings to assumptions? What changes would reverse finding?
Success Metrics by Analytics Program

Conversion Rate Optimization

  • Test execution: launch 1-2 tests per week, completion of testing roadmap
  • Test quality: 80%+ of tests have adequate sample size and statistical rigor
  • Win rate: 40-50% of tests show positive lift (indicates healthy hypothesis generation)
  • Conversion improvement: 20-30% cumulative conversion rate improvement over 6 months
  • Downstream impact: 10-15% improvement in lead quality or sales cycle length

Marketing Dashboard & Reporting

  • Dashboard adoption: 90%+ of stakeholders use dashboard for decision-making
  • Update frequency: dashboards updated daily or hourly with zero latency delays
  • Accuracy: 98%+ data accuracy compared to source systems
  • Action tracking: 80%+ of dashboard insights lead to actionable decisions
  • Executive confidence: stakeholder survey showing 90%+ confidence in data accuracy

Customer Research Program

  • Research completion: conduct 20-30 interviews and 100-200 survey responses per quarter
  • Insight generation: 5-10 actionable insights per research cycle
  • Implementation rate: 80%+ of recommended changes implemented within 90 days
  • Impact measurement: track how recommendations influence performance (messaging changes, product decisions)
  • Stakeholder value: research findings cited in 80%+ of marketing strategy decisions

Performance Analysis & Reporting

  • Analysis freshness: monthly analysis completed within 3 days of month close
  • Finding specificity: analysis identifies specific recommendations, not just observations
  • Action tracking: recommendations tracked and measured for impact
  • Stakeholder value: analysis drives 3-5 major decisions or strategy changes per quarter

Tools & Systems

Analytics Platform Stack

  • Website analytics (Google Analytics 4, Mixpanel, Amplitude for event tracking)
  • CRM analytics (Salesforce reporting, custom dashboards showing pipeline/forecast)
  • Attribution platform (multi-touch attribution, marketing mix modeling)
  • Marketing automation (HubSpot, Marketo for email performance, nurture metrics)
  • Ad platform analytics (LinkedIn Campaign Manager, Google Ads reporting)

Testing Infrastructure

  • A/B testing platform (Optimizely, VWO, LaunchDarkly for running and tracking tests)
  • Statistical calculator (proper sample size calculation, significance testing)
  • Audience segmentation (proper test audience targeting and randomization)
  • Test tracking (UTM parameters, conversion pixels, event tracking for test attribution)

Dashboard & Reporting

  • Dashboard platform (Tableau, Looker, Google Data Studio for visualization)
  • Data warehouse (Snowflake, BigQuery for centralized data)
  • ETL/data integration (Stitch, Fivetran for syncing data from multiple sources)
  • Reporting automation (scheduled reports, alert triggers)

Customer Research

  • Survey platform (SurveyMonkey, Typeform, Qualtrics for survey distribution)
  • Interview transcription (Otter.ai, Rev for interview recording and transcription)
  • Analysis tools (MAXQDA, Dovetail for qualitative data analysis)
  • Data repository (shared database of customer research findings and insights)

Data Governance & Standards

Metrics Definition

  • Every metric must have documented definition: calculation method, data source, refresh frequency
  • Standardized naming conventions: consistent names across dashboards and reports
  • Metric ownership: each metric has owner responsible for accuracy and interpretation
  • Update process: documented process for metric changes, with stakeholder review

Data Quality Standards

  • Data reconciliation: monthly reconciliation between source systems and reporting systems
  • Validation rules: automated checks for data quality (missing values, outliers, impossible values)
  • Tracking validation: quarterly audit of tracking implementation accuracy
  • Documentation: maintain audit trail of data changes, corrections, and transformations

Attribution Standards

  • Touch definition: documented definition of what constitutes a marketing touch
  • Window definition: documented customer journey tracking window (7-day, 30-day, 90-day)
  • Model validation: monthly validation of attribution model accuracy vs. actual results
  • Stakeholder alignment: regular reviews of attribution methodology with sales and finance
1---
2name: marketing-analytics
3description: "Marketing analytics and data-driven optimization for B2B SaaS campaigns. Use this skill when analyzing marketing performance, optimizing conversion rates, running A/B tests, conducting customer research, creating marketing dashboards, building attribution models, analyzing funnel metrics, or storytelling with data. Also triggers on: marketing ops, performance analytics, CRO, A/B testing, data storytelling, customer insights, tracking plan, event taxonomy, UTM taxonomy, GA4 audit, consent mode, instrumentation contract, sample size calculation, minimum detectable effect, test duration, not enough traffic to A/B test, statistical significance, Bayesian vs frequentist, sample ratio mismatch, experiment feasibility, martech stack, marketing tech stack audit, tool consolidation, build vs buy, vendor evaluation, shadow IT tools, ESP/CRM/platform migration, switching cost, cutover plan, suppression list migration, data portability, customer interviews, survey design, sampling frame, non-response bias, how many people should I interview, thematic saturation, voice of customer, jobs-to-be-done, buyer persona research, is this finding real, data enrichment, which enrichment provider should we buy, waterfall enrichment, contact data quality, match rate, our list data is bad, email verification, catch-all domain, accept-all, bounce rate from bad data, B2B data decay, how often should we re-verify contacts, ZoomInfo vs Apollo vs Clearbit evaluation, cost per usable record, where did this list come from, GDPR Article 14 notice, purchased list compliance, suppression screening, TAM list building, demand planning, marketing plan, how many leads do we need, what pipeline target should marketing carry, funnel model, top-down vs bottom-up plan, plan of record, annual marketing planning, quarterly planning, pipeline coverage we have to create, sales cycle lag, our leads cannot close this quarter, carry-in pipeline, scenario planning, conservative moderate aggressive forecast, stretch target, reforecast, re-forecast triggers, assumption register, capacity ceiling, addressable audience ceiling, marginal cost per lead, blended CPL is wrong, we missed plan and nobody knows why, AI policy for the marketing team, AI governance, AI acceptable use policy, which AI tools are we allowed to use, can I paste customer data into ChatGPT, shadow AI, AI use register, human review of AI output, AI evals, our AI vendor changed the model, AI output went out wrong, prompt injection, can our AI read prospect replies safely, lethal trifecta, the AI leaked internal notes, turn off auto-generated ad assets, auto-applied recommendations, AI literacy training, EU AI Act Article 4, duplicate records in the CRM, dedupe before import, which value wins in a merge, CRM cleanup."
4---
5 
6# Marketing Analytics
7 
8## Step 0 (always first): Load brand context
9 
10**Before producing any deliverable, look for a `brand-context.md` file** in the user's project root (also check `./.claude/brand-context.md` and `./docs/brand-context.md`). It holds the company's ICP, positioning, messaging pillars, citable proof, voice, banned words, and compliance constraints.
11 
12- **If it exists:** read it in full and treat it as binding for this run. Hand its contents to every specialist agent you route work to, alongside the task brief. Its "Rules for agents reading this file" section overrides an agent's own defaults.
13- **If it does not exist:** say so, point the user at the template ([`templates/brand-context.md`](../../templates/brand-context.md)), and offer to generate a filled draft by interviewing them or by reading their website and existing content. Then proceed with explicitly-labelled assumptions — never silently invented ones.
14 
15**Non-negotiable regardless of which path applies:** do not invent customer names, metrics, funding, integrations, certifications, or outcomes. Only proof recorded in `brand-context.md` (or supplied directly in the request) may be used as fact. Where a claim would help but no evidence exists, emit a `[NEEDS INPUT: …]` marker in the deliverable rather than a plausible-sounding guess.
16 
17---
18 
19## What This Is
20 
21Marketing Analytics brings together performance analysts, conversion rate optimization specialists, customer insights researchers, data storytellers, and marketing operations architects to transform data into decisions. This skill orchestrates your analytics practice to measure what matters (pipeline impact, customer quality, efficient CAC), identify optimization opportunities (conversion rate improvements, targeting precision, channel efficiency), and communicate findings to stakeholders. Whether you're building a marketing dashboard, running an A/B test program, conducting customer research to understand buyer behavior, or presenting performance analysis to leadership, Marketing Analytics routes your request to the right specialist and ensures your data drives better marketing decisions.
22 
23## The Team: 9 Specialist Agents
24 
25| # | Agent | File | What They Do |
26|---|-------|------|-------------|
27| 1 | Performance Analyst | `agents/analytics-performance-analyst.md` | Measures and optimizes marketing performance across channels and campaigns, tracks KPIs, and identifies performance drivers through data analysis and reporting |
28| 2 | Conversion Rate Optimizer | `agents/analytics-conversion-rate-optimizer.md` | Designs and executes CRO testing programs, analyzes conversion funnels, identifies friction points, optimizes user experience for higher conversion rates, and gates every experiment on whether the funnel can actually power it (sample size, duration, comparability horizon) |
29| 3 | Customer Insights Researcher | `agents/analytics-customer-insights-researcher.md` | Designs and runs customer research (interviews, surveys, VoC mining) and grades what it can claim — sampling frame and non-response, evidence levels, cross-channel corroboration, saturation, jobs-to-be-done and research-based personas |
30| 4 | Data Storyteller | `agents/analytics-data-storyteller.md` | Translates data analysis into clear narratives and compelling visualizations that communicate findings and drive decision-making |
31| 5 | Marketing Ops Architect | `agents/analytics-marketing-ops-architect.md` | Designs the data architecture inside the stack — MAP/CRM integration, lead lifecycle and scoring, field governance, duplicate prevention (resolve before create) and merge survivorship rules — authors the marketing instrumentation contract (tracking plan, event taxonomy, UTM taxonomy) that every measurement audit grades against, implements tracking and attribution, and builds dashboards and reporting systems that enable data-driven marketing |
32| 6 | GTM Data Strategist | `agents/analytics-gtm-data-strategist.md` | Owns the go-to-market data that arrives from outside — the data requirement written before shopping, provider bake-offs on a held-out sample of your own accounts, coverage scored separately from accuracy and wrong answers, identity-match corroboration, enrichment waterfalls ordered by measured cost per usable record, a decay rate measured rather than quoted, verification states including accept-all, suppression screening, and the provenance and lawful-basis record (GDPR Article 14) behind every acquired list |
33| 7 | MarTech Stack Strategist | `agents/analytics-martech-stack-strategist.md` | Owns the martech stack as a portfolio: capability-first tool selection and build-vs-buy, shadow-tool and overlap rationalization, and the true switching cost of replacing a system — including the suppression record, engagement history, personalization layer and measurement continuity a platform migration puts at risk |
34| 8 | Demand Planner | `agents/analytics-demand-planner.md` | Builds the number before the period starts — the revenue target decomposed backwards through the funnel into stage volumes, an assumption register where every conversion rate and cycle time is a dated own-funnel measurement or is stamped inferred, the sales-cycle lag that decides which period a lead can land in (carry-in, carry-out, latest useful creation date), the sales / production / addressable-audience ceilings that cap what a plan may promise, marginal rather than blended cost per source, a scenario band derived from your own plan-versus-actual dispersion instead of a borrowed ±20%, declared re-forecast triggers, and a versioned plan of record that makes a miss diagnosable |
35| 9 | Marketing AI Operations Lead | `agents/analytics-marketing-ai-ops-lead.md` | Governs how the team uses AI — an AI use register per use case, legalize-don't-ban intake for shadow AI, data-class rules for which tool may receive what, an autonomy ladder with a never-generate list, a prompt-injection check (private data + untrusted content + outbound path caps a workflow at human review), eval sets re-run on every model/prompt/vendor change, default-on platform AI settings, kill switches, an AI incident log, and an EU AI Act Art. 4 literacy record by role |
36 
37## How to Use
38 
39### Routing User Requests
40 
41**Marketing Performance Analysis** → Performance Analyst
42- "Analyze the performance of our latest demand generation campaign"
43- "Create a monthly marketing dashboard showing KPIs by channel"
44- "Identify which channels are driving the most qualified pipeline"
45- "Compare performance across campaigns to identify what's working"
46 
47**Demand & Pipeline Planning** → Demand Planner
48- "How many leads do we need next year to hit the revenue target?"
49- "Build the bottom-up marketing plan and reconcile it against the number finance gave us"
50- "Our Q1 plan assumes leads created in January close in March — is that possible?"
51- "Give me a conservative / planned / upside band with the triggers that tell us which one we are in"
52- "We missed plan — which assumption was wrong?"
53 
54**Conversion Rate Optimization** → Conversion Rate Optimizer
55- "Design a CRO testing program for our landing pages"
56- "Analyze our conversion funnel and identify where prospects drop off"
57- "Run A/B test comparing headline variations on our homepage"
58- "Optimize form fields to increase lead capture completion rate"
59- "How much traffic do we need to A/B test this page, and how long will it take?"
60- "We don't have enough traffic to reach significance — what should we do instead?"
61- "Should we use a Bayesian test because our sample is small?"
62 
63**Customer Research & Insights** → Customer Insights Researcher
64- "Conduct survey research to understand what messages resonate with our target buyer"
65- "Interview customers to understand decision process and evaluation criteria"
66- "Analyze user behavior data to identify content preferences"
67- "Research competitive buyer perception to understand market positioning opportunity"
68 
69**Data Communication & Visualization** → Data Storyteller
70- "Create a visual dashboard showing marketing funnel metrics"
71- "Present Q3 performance analysis to executive leadership"
72- "Design infographic summarizing campaign results for stakeholders"
73- "Build a customer journey visualization based on analytics data"
74 
75**Marketing Systems & Infrastructure** → Marketing Ops Architect
76- "Design our marketing attribution model (multi-touch vs. first-touch vs. last-touch)"
77- "Build a marketing dashboard infrastructure with real-time data updates"
78- "Implement tracking and data collection for marketing funnel"
79- "Create a data dictionary and standardized metrics definitions for marketing"
80 
81**MarTech Stack, Tool Selection & Platform Migration** → MarTech Stack Strategist
82- "Audit our martech stack — what are we paying for that we don't use?"
83- "We have too many tools and they don't talk to each other"
84- "Should we buy this tool, build it, or does something we already own do it?"
85- "What does it actually cost us to move off our current ESP / MAP / CRM?"
86- "Plan the cutover: what has to carry across, and what breaks if it doesn't?"
87- "How do we make sure our unsubscribes survive the migration?"
88 
89**Marketing AI Governance & AI Operations** → Marketing AI Operations Lead
90- "We need an AI policy for the marketing team — what's allowed?"
91- "Can I paste our customer list / call transcripts into ChatGPT?"
92- "Half the team uses AI tools we never approved — what do we do?"
93- "Our AI email personalization is about to send on its own — is it ready?"
94- "The vendor changed the model and the outputs changed — how would we even know?"
95- "Which AI features are switched on by default in our ad accounts and ESP?"
96- "What AI-literacy training do we need to show under the EU AI Act?"
97 
98### Execution Model
99 
100**Phase 1: Baseline & Measurement (1-2 weeks)**
101- Marketing Ops Architect establishes current measurement infrastructure: what's being tracked, what's missing, data quality issues
102- Performance Analyst establishes baseline metrics: current funnel conversion rate, cost per lead, cost per acquisition, channel performance
103- Identify measurement gaps: what's not being tracked that should be (first-touch vs. last-touch, buyer quality signals, sales pipeline influence)
104- Define KPIs and success metrics for next phase of work
105 
106**Phase 2: Analysis & Diagnosis (2-3 weeks)**
107- Performance Analyst analyzes historical performance data to identify trends, patterns, anomalies
108- Customer Insights Researcher conducts qualitative research (surveys, interviews) to understand why metrics look the way they do
109- Conversion Rate Optimizer identifies conversion funnel bottlenecks: where do prospects drop off most
110- Develop hypothesis for optimization opportunities
111- Data Storyteller synthesizes findings into narrative and visualizations
112 
113**Phase 3: Experimentation & Testing (4-12 weeks depending on scope)**
114- Conversion Rate Optimizer designs and launches A/B testing program with prioritized hypotheses
115- Marketing Ops Architect ensures testing infrastructure (statistical significance tracking, proper audience segmentation, variant tracking)
116- Customer Insights Researcher collects feedback on tested variations (surveys, interviews to understand why winners won)
117- Performance Analyst monitors test results weekly, identifies winners, and tracks cumulative impact
118- Data Storyteller communicates test results and learnings to stakeholders
119 
120**Phase 4: Optimization & Scaling (ongoing)**
121- Scale winning variations (increase traffic to better-performing page, increase spend on better-performing channel)
122- Iterate next set of tests based on learning from prior tests
123- Customer Insights Researcher continuously monitors sentiment and satisfaction (NPS, CSAT, customer interviews)
124- Performance Analyst tracks improvement impact on downstream metrics (pipeline quality, customer lifetime value)
125- Marketing Ops Architect maintains data freshness and dashboard accuracy
126 
127### Testing Methodology
128 
129**CRO Testing Framework**
1301. Hypothesis formation (based on data analysis or customer research insight)
131 - Expected: Landing page headline focusing on outcome (vs. feature) will increase conversion rate
132 - Why: Customer research showed buyers care about time savings more than features
133 - Metric: Track conversion rate, form completion rate, downstream pipeline quality
134 
1352. Test design (control, test variant, sample size, duration)
136 - Control: current page (baseline performance)
137 - Variant: new headline focusing on outcome
138 - Sample size: 100 conversions per variant to reach 95% statistical significance
139 - Duration: 2 weeks or until sample size achieved
140 
1413. Execution (launch test, monitor for data quality)
142 - Route 50% traffic to control, 50% to variant
143 - Ensure proper tracking implementation (no missing conversions, no duplicate counts)
144 - Monitor daily for anomalies (traffic drop, conversion spike indicating technical error)
145 
1464. Analysis (determine winner, measure impact, document learning)
147 - Did test win or lose (statistical significance threshold: 95% confidence, 5% significance level)
148 - If winner: magnitude of improvement (e.g., 12% lift in conversion rate = 0.5% absolute improvement)
149 - If loser: why did it lose? Did it hurt downstream metrics (lead quality, sales conversion)?
150 - Document learning: which element drove result (headline, color, form field, CTA placement)
151 
1525. Iteration (scale winner, test next hypothesis)
153 - Scale winning variant to 100% traffic (or keep testing if hold-back analysis desired)
154 - Identify next testing hypothesis based on remaining friction points
155 - Queue up next test for launch
156 
157**Testing Prioritization**
158- Prioritize tests by estimated impact × confidence level
159- High-traffic pages (more statistical power) → test bigger changes
160- Low-traffic pages → test smaller changes (less power) or focus on traffic growth
161- Test single variable per test (isolates learnings)
162- Test highest-impact elements first: traffic source → landing page → form completion → downstream quality
163 
164**Statistical Rigor**
165- Sample size calculation: depends on baseline conversion rate, desired lift, desired significance level
166- Significance threshold: 95% confidence (5% alpha, meaning 5% chance of false positive)
167- Running time: continue test until sample size achieved or 2-4 weeks, whichever comes first
168- Avoid peeking: don't declare winner until test complete (peeking inflates error rate)
169 
170### Metrics Hierarchy
171 
172**Top-Level KPIs (North Star Metrics)**
173- Marketing-Influenced Pipeline: revenue impact of marketing activities (pipeline value marketing generated)
174- Marketing Qualified Leads (MQLs): leads that meet quality threshold for sales handoff
175- Customer Acquisition Cost (CAC): fully-loaded cost to acquire new customer (including marketing + sales)
176- Customer Lifetime Value (CLV): expected revenue from customer over lifetime
177 
178**Mid-Level Metrics (Channel Performance)**
179- Cost Per Lead (CPL): average marketing spend to acquire one lead
180- Lead-to-Opportunity Conversion: percentage of leads that convert to sales-accepted opportunity
181- Opportunity-to-Customer Conversion: percentage of opportunities that close to customer
182- Cost Per Opportunity: marketing spend to generate one sales-accepted opportunity
183- Cost Per Acquisition: marketing spend to close one customer deal
184 
185**Funnel Metrics (Conversion Analysis)**
186- Website Traffic: monthly unique visitors by source (organic, paid, direct, referral)
187- Page Conversion Rate: percentage of page visitors who take desired action (form submission, email signup)
188- Form Completion Rate: percentage of form starters who complete form submission
189- Demo/Trial Signup Rate: percentage of engaged prospects who request demo or free trial
190- Sales Accepted Lead Rate: percentage of inbound leads meeting sales qualification criteria
191 
192**Campaign Metrics (Campaign Performance)**
193- Click-Through Rate (CTR): percentage of ad impressions that receive clicks (LinkedIn: 0.5-2%, Google: varies by audience)
194- Cost Per Click (CPC): average cost per paid click (compare to historical benchmark and competitor spend)
195- Video Completion Rate: percentage of video viewers who watch 75%+ of video (YouTube 25-40%, in-feed 15-25%)
196- Lead Quality Score: MQL to SAL conversion rate (higher = better quality leads from source)
197- Return on Ad Spend (ROAS): revenue generated per dollar of paid ad spend
198 
199**Customer Quality Metrics**
200- Sales Cycle Length: average time from opportunity creation to closed customer
201- Win Rate: percentage of opportunities that close to customer (competitive benchmark varies)
202- Average Contract Value: average customer deal size
203- Customer Retention Rate: percentage of customers retained year-over-year
204- Net Revenue Retention: revenue retention + expansion revenue from existing customers
205 
206### Routing by Analytics Use Case
207 
208**Landing Page Optimization**
209- Conversion Rate Optimizer leads CRO program with testing roadmap
210- Marketing Ops Architect ensures tracking and statistical testing infrastructure
211- Data Storyteller visualizes funnel and testing results
212- Performance Analyst measures impact on downstream metrics (pipeline, customer quality)
213- Success metrics: 20-30% conversion rate improvement over 6 months, improved lead quality
214 
215**Demand Generation Campaign Analysis**
216- Performance Analyst analyzes campaign performance by channel and content
217- Customer Insights Researcher surveys engaged prospects to understand preferences
218- Conversion Rate Optimizer identifies highest-converting assets and channels
219- Data Storyteller visualizes campaign funnel and highlights top performers
220- Marketing Ops Architect ensures proper attribution and tracking
221- Success metrics: hit campaign pipeline goal, exceed average cost-per-lead benchmark, high lead quality
222 
223**Attribution & Analytics Infrastructure**
224- Marketing Ops Architect designs multi-touch attribution model
225- Performance Analyst implements tracking and validates data quality
226- Data Storyteller creates dashboards showing attribution by channel, campaign, source
227- Marketing Ops Architect establishes data governance and standardized metrics
228- Success metrics: 95%+ tracking accuracy, real-time dashboard updates, executive confidence in data
229 
230**Customer Research Program**
231- Customer Insights Researcher conducts qualitative and quantitative research
232- Surveys: 100-200 target buyers on messaging, positioning, feature priorities
233- Interviews: 10-20 deep-dive conversations with buyers and existing customers
234- Behavioral analysis: analyze user behavior on website, demo usage, content preferences
235- Data Storyteller synthesizes findings into narrative and visualizations
236- Success metrics: identify 5-10 actionable customer insights, 3+ changes implemented based on research
237 
238## Output Standards
239 
240### Analytics Quality Checklist
241 
242**Data Accuracy**
243- Validation: Data validated against source systems (CRM, ad platform, GA) for accuracy
244- Completeness: 95%+ of expected events tracked and recorded
245- Freshness: Dashboards updated daily or hourly for real-time decision-making
246- Reconciliation: Monthly reconciliation between systems to ensure consistency
247- Documentation: Data dictionary documenting every metric, calculation method, data source
248 
249**Funnel Analysis**
250- All stages defined: awareness → engagement → MQL → SAL → opportunity → customer
251- Conversion rates calculated: percentage of visitors reaching each stage
252- Benchmarks established: compare conversion rates to historical baseline and industry benchmark
253- Segment analysis: conversion rates by traffic source, campaign, buyer persona, vertical
254- Bottleneck identification: which stage has lowest conversion or highest drop-off
255 
256**Testing Rigor**
257- Sample size: adequate sample size (100+ conversions per variant) to reach 95% statistical significance
258- Duration: test runs until sample size achieved or 2-4 weeks minimum
259- Single variable: each test isolates one change (control constant, one variable changed)
260- Statistical significance: 95% confidence level, 5% significance threshold
261- Learning documentation: document what we learned and how it applies to future tests
262 
263**Dashboard Quality**
264- Clarity: metrics labeled clearly, units defined (rates as %, numbers as count or $)
265- Timeliness: updated daily or hourly depending on decision-making frequency
266- Actionability: dashboard shows what's working/not working, not just data points
267- Drilling down: ability to click through to see underlying data (top traffic sources, best-performing content, etc.)
268- Comparisons: shows trends over time and comparisons to benchmarks/targets
269 
270### Deliverable Specifications
271 
272**Marketing Dashboard**
273- Executive dashboard (1-2 pages): top KPIs, traffic, pipeline, campaign ROI, quarter performance vs. goal
274- Funnel dashboard: conversion rates by stage, segment analysis (by source, campaign, persona), bottleneck identification
275- Channel dashboard: performance by channel (organic, paid, direct, referral, email), cost per lead, conversion rate, trend
276- Campaign dashboard: active campaigns, performance vs. goal, cost per lead, lead volume, quality metrics
277- Testing dashboard: active tests, results, statistical significance, learning captured
278- Daily dashboard: refresh rate hourly, daily KPI performance, alert if metrics miss thresholds
279 
280**CRO Testing Roadmap**
281- Testing hypothesis bank: 20-30 prioritized hypotheses with expected impact and effort estimate
282- Hypothesis: description of test variant, expected outcome, business rationale, success metric
283- Estimated lift: expected conversion rate improvement based on similar tests or industry benchmarks
284- Sample size & duration: how long test will run to reach statistical significance
285- Timeline: Quarters 1-4 roadmap with hypothesis sequence
286- Resource requirements: design effort, analytics effort, traffic required
287 
288**Performance Analysis Report**
289- Executive summary: key findings, performance vs. goal, recommended actions
290- Performance overview: KPIs, trends, comparison to prior period and target
291- Channel analysis: performance by traffic source (organic, paid, direct), cost per lead, conversion rate
292- Campaign analysis: performance by campaign, content, topic, top performers
293- Customer quality analysis: lead quality by source, sales cycle length, customer retention
294- Competitive benchmarking: performance vs. industry benchmarks
295- Recommendations: 3-5 prioritized actions to improve performance
296 
297**Customer Insights Report**
298- Research methodology: survey sample size, interview count, data collection approach
299- Key findings: 5-10 major insights about buyer behavior, preferences, decision criteria
300- Messaging preferences: what messages resonate, which value props matter most by persona
301- Competitive positioning: how buyers perceive competitive alternatives, key decision factors
302- Buying process: stages in buyer journey, key decision drivers by stage
303- Persona profiles: updated or confirmed persona attributes, priorities, concerns
304- Recommendations: how findings should inform marketing strategy, messaging, product
305 
306**CRO Test Results Document**
307- Test overview: hypothesis, expected outcome, why this test matters
308- Test design: control variant, test variant, sample size, duration, audience selection
309- Results: conversion rate by variant, percentage lift, statistical significance
310- Statistical analysis: confidence level, p-value, sample size achieved
311- Impact: downstream metrics (lead quality, sales conversion, customer retention)
312- Learning: what we learned, why winner won, how to apply to future tests
313- Follow-up: next test to run based on this learning
314 
315**Attribution Model Specification**
316- Model type: first-touch vs. last-touch vs. multi-touch (time decay, linear, custom)
317- Touch definitions: what actions count as "touch" (landing page view, form submission, email click)
318- Credit allocation: how credit is allocated among touches (first touch gets 100%, or distributed across journey)
319- Window: how long to track touches (7-day, 30-day, 90-day cookie window)
320- Implementation: technical specification for tracking and attribution calculation
321- Reporting: how results will be reported and updated
322- Validation: methodology to validate attribution accuracy
323 
324### Quality Review Process
325 
326Before publishing any analytics finding or dashboard:
327 
3281. **Data Validation**: Is the data accurate and complete? Have we reconciled against source systems?
3292. **Statistical Rigor**: Do findings meet statistical significance requirements? Is sample size adequate?
3303. **Bias Check**: Could sample bias, selection bias, or confounding variables affect findings?
3314. **Clarity**: Can stakeholders understand findings without extended explanation?
3325. **Actionability**: Do findings lead to clear recommendations or decisions?
3336. **Sensitivity Check**: How sensitive are findings to assumptions? What changes would reverse finding?
334 
335### Success Metrics by Analytics Program
336 
337**Conversion Rate Optimization**
338- Test execution: launch 1-2 tests per week, completion of testing roadmap
339- Test quality: 80%+ of tests have adequate sample size and statistical rigor
340- Win rate: 40-50% of tests show positive lift (indicates healthy hypothesis generation)
341- Conversion improvement: 20-30% cumulative conversion rate improvement over 6 months
342- Downstream impact: 10-15% improvement in lead quality or sales cycle length
343 
344**Marketing Dashboard & Reporting**
345- Dashboard adoption: 90%+ of stakeholders use dashboard for decision-making
346- Update frequency: dashboards updated daily or hourly with zero latency delays
347- Accuracy: 98%+ data accuracy compared to source systems
348- Action tracking: 80%+ of dashboard insights lead to actionable decisions
349- Executive confidence: stakeholder survey showing 90%+ confidence in data accuracy
350 
351**Customer Research Program**
352- Research completion: conduct 20-30 interviews and 100-200 survey responses per quarter
353- Insight generation: 5-10 actionable insights per research cycle
354- Implementation rate: 80%+ of recommended changes implemented within 90 days
355- Impact measurement: track how recommendations influence performance (messaging changes, product decisions)
356- Stakeholder value: research findings cited in 80%+ of marketing strategy decisions
357 
358**Performance Analysis & Reporting**
359- Analysis freshness: monthly analysis completed within 3 days of month close
360- Finding specificity: analysis identifies specific recommendations, not just observations
361- Action tracking: recommendations tracked and measured for impact
362- Stakeholder value: analysis drives 3-5 major decisions or strategy changes per quarter
363 
364## Tools & Systems
365 
366**Analytics Platform Stack**
367- Website analytics (Google Analytics 4, Mixpanel, Amplitude for event tracking)
368- CRM analytics (Salesforce reporting, custom dashboards showing pipeline/forecast)
369- Attribution platform (multi-touch attribution, marketing mix modeling)
370- Marketing automation (HubSpot, Marketo for email performance, nurture metrics)
371- Ad platform analytics (LinkedIn Campaign Manager, Google Ads reporting)
372 
373**Testing Infrastructure**
374- A/B testing platform (Optimizely, VWO, LaunchDarkly for running and tracking tests)
375- Statistical calculator (proper sample size calculation, significance testing)
376- Audience segmentation (proper test audience targeting and randomization)
377- Test tracking (UTM parameters, conversion pixels, event tracking for test attribution)
378 
379**Dashboard & Reporting**
380- Dashboard platform (Tableau, Looker, Google Data Studio for visualization)
381- Data warehouse (Snowflake, BigQuery for centralized data)
382- ETL/data integration (Stitch, Fivetran for syncing data from multiple sources)
383- Reporting automation (scheduled reports, alert triggers)
384 
385**Customer Research**
386- Survey platform (SurveyMonkey, Typeform, Qualtrics for survey distribution)
387- Interview transcription (Otter.ai, Rev for interview recording and transcription)
388- Analysis tools (MAXQDA, Dovetail for qualitative data analysis)
389- Data repository (shared database of customer research findings and insights)
390 
391## Data Governance & Standards
392 
393**Metrics Definition**
394- Every metric must have documented definition: calculation method, data source, refresh frequency
395- Standardized naming conventions: consistent names across dashboards and reports
396- Metric ownership: each metric has owner responsible for accuracy and interpretation
397- Update process: documented process for metric changes, with stakeholder review
398 
399**Data Quality Standards**
400- Data reconciliation: monthly reconciliation between source systems and reporting systems
401- Validation rules: automated checks for data quality (missing values, outliers, impossible values)
402- Tracking validation: quarterly audit of tracking implementation accuracy
403- Documentation: maintain audit trail of data changes, corrections, and transformations
404 
405**Attribution Standards**
406- Touch definition: documented definition of what constitutes a marketing touch
407- Window definition: documented customer journey tracking window (7-day, 30-day, 90-day)
408- Model validation: monthly validation of attribution model accuracy vs. actual results
409- Stakeholder alignment: regular reviews of attribution methodology with sales and finance
410 

Discussion

Alternatives

⚡ NEXUS Quick-Start Guide> Get from zero to orchestrated multi-agent pipeline in 5 minutes.Business & ops · MITclean-cut — the step-1 cut pipelineStep 1 of the AI Video Editor pipeline — turn raw talking-head footage into a clean master cut. Use when the user wants to "clean cut", "cut the raw footage", "remove filler / dead air / bad takes", "tighten the pacing", produce cuts.json, run the cut editor, or render a cleaned preview/master for a video-N project in this repo. Covers audio extraction, AssemblyAI transcription, authoring cuts.json (keeps/cuts/fluff categorized), the cut policy (content-aggressive, pause-natural ~0.5s), QA + review docs, the local cut-editor UI, tight/natural previews, the final 4K60 render, and producing edited-transcript.json as the handoff to /make-tsx. Not for building TSX overlays (that is /make-tsx) or the raw TSX authoring rules (that is vidtsx-2d-generator).Sales & ecommerce · MITVocaloid-style MV pipeline (手書き / 文字PV)Make an original animated music video (MV / PV) for a song from its audio file plus lyrics, in the Vocaloid / J-pop lyric-video tradition: 手書き/tegaki (V家手书, 手描きMV, ボカロPV), 文字PV and kinetic typography (リリックモーション, リリックビデオ, 歌詞動画, 歌词视频, 动态歌词), anime-illustration MVs with an original character — for any mood, from dark ballads to bright upbeat summer pop. Renders to MP4 with a deterministic Canvas2D/WebGL2 engine in a headless browser: JIZURA lyric motion, AI-generated art, optional Blender toon 3D, beat-locked editing, 9:16 vertical/Shorts version. Use it whenever the user wants a music video, MV, PV, lyric video or beat-synced animation for a song, e.g. make an MV for my song", "turn this track into a lyric video", "给这首歌做个MV/PV", "做个V家手书", "この曲のMVを作って", ボカロPV作って", "縦型ショートも" — even if they only give a .wav/.mp3 and say "make a cool video for it". Not for editing existing footage or clip compilations.Sales & ecommerce · MITConstruction Agent — Email → Project Management PipelineConstruction company AI agent — orchestrates email (Google Workspace), project management (JobTread Pave API), and file routing for a construction business. Handles email triage, attachment routing to JobTread, project status, task management, and daily briefings via Telegram. Reference implementation for a construction/trades business with an existing email→Drive→PM pipeline.Sales & ecommerce · MIT