Analytics & Insights

GA4 "AI Assistant" channel group (added 13 May 2026)

Google Analytics 4 added a new default channel group called "AI Assistant" on 13 May 2026 (GA4 channel groups doc (https://support.google.com/analytics/answer/9164320?hl=en)). When a referrer matches a recognized AI Assistant (ChatGPT, Gemini, Claude, etc.), GA4 automatically:

• Categorizes the session under the AI Assistant channel group
• Sets the Medium dimension to ai-assistant

This is the attribution-side counterpart to the new GSC AI Performance Report (rolled out 3 June 2026 — see /digital-marketing-pro:gsc-ai-performance). Because the GSC AI report intentionally excludes click data, the GA4 AI Assistant channel is currently the cleanest path to attribute actual traffic coming from generative AI surfaces.

Recommended GA4 setup checks when onboarding a brand:

1. Confirm the channel group is live in the property. Newer GA4 properties get it automatically; older ones may need it to appear after Google's backfill completes. If the brand reports their channel reports look unchanged after 13 May, check explore reports filtered by sessionDefaultChannelGroup = "AI Assistant".

2. Add the AI Assistant channel to custom reports + dashboards — for any brand running an AEO program (/digital-marketing-pro:aeo-geo, /digital-marketing-pro:aeo-audit), the AI Assistant channel trend is now a primary KPI alongside organic search clicks.

3. Don't merge AI Assistant into "Organic Search" or "Direct". Some legacy reporting templates roll AI traffic into Direct (because referrers weren't always present) or Organic Search (because answer engines feel "search-like"). Both are misattributions now — the AI Assistant channel is the authoritative bucket.

4. Reconcile with aeo-audit outputs and the GSC AI report. Three data sources, three different views:

   • aeo-audit (synthetic probing) — what AI engines could say about the brand
   • GSC AI Performance Report — actual impressions in Google AI Overviews / AI Mode (no clicks)
   • GA4 AI Assistant channel — actual traffic from AI assistants (clicks materialized)

   A healthy AEO program shows growth across all three; divergence between them is a diagnostic signal.

When to Use This Skill

Activate this module when the user's request involves any of the following:

• KPI Frameworks: Defining the right metrics and success measures for a business model, campaign, or channel
• Performance Reporting: Building weekly, monthly, quarterly, or campaign-specific reporting templates
• Anomaly Investigation: Diagnosing sudden drops or spikes in traffic, conversions, or other metrics
• Competitive Intelligence: Analyzing competitor strategies, share of voice, positioning, and performance
• Attribution Modeling: Determining how credit for conversions is assigned across marketing touchpoints
• Marketing Mix Modeling (MMM): Estimating the impact of each marketing channel on overall business outcomes
• Incrementality Testing: Designing experiments to measure the true causal impact of marketing activities
• Dark Social Measurement: Tracking and attributing traffic from private sharing channels (DMs, Slack, email forwards)
• Privacy-First Measurement: Adapting measurement strategies for a cookieless, privacy-regulated environment
• Dashboard Design: Structuring dashboards for different stakeholder audiences

Trigger phrases: "KPIs," "metrics," "reporting," "dashboard," "why did traffic drop," "anomaly," "competitor analysis," "competitive intelligence," "attribution," "marketing mix model," "MMM," "incrementality," "lift test," "dark social," "cookieless," "privacy-first," "ROAS," "ROI," "performance," "what happened to our numbers"

Brand Context (Auto-Applied)

Before producing any marketing output from this module:

1. Check session context — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels, goals, compliance, and competitors shown there.
2. If you need the full profile, read: ~/.claude-marketing/brands/{slug}/profile.json
3. Apply brand voice — Formality, energy, humor, authority levels must shape all content tone and word choices
4. Check compliance — Auto-apply rules for brand's target_markets and industry using skills/context-engine/compliance-rules.md
5. Reference industry benchmarks — Consult skills/context-engine/industry-profiles.md for the brand's industry
6. Use platform specs — Reference skills/context-engine/platform-specs.md for character limits and format requirements
7. Check campaign history — Run python campaign-tracker.py --brand {slug} --action list-campaigns before planning new work
8. If no brand exists, say: "No brand profile found. Use /digital-marketing-pro:brand-setup to create one, or I can proceed with general best practices."
9. Check brand guidelines — If ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json exists, load and enforce: restrictions.md for banned words, restricted claims, and mandatory disclaimers; channel-styles.md for channel-specific tone overrides (may differ from base voice); messaging.md for approved key messages, taglines, and positioning language; voice-and-tone.md for detailed voice rules beyond the 4 numeric scores. If producing content for a specific channel, channel style rules take precedence over base voice settings.

Do not ask the user for information that already exists in their brand profile.

Required Context

Before executing analytics work, gather:

1. Business Model: SaaS, e-commerce, lead gen, marketplace, etc. (determines the KPI framework)
2. Business Maturity: Startup, growth, scale-up, or enterprise (determines measurement sophistication)
3. Current Metrics: What is already being tracked? What tools are in use?
4. Analytics Stack: Google Analytics (GA4), ad platforms, CRM, BI tools, CDPs, tag managers
5. Data Availability: How much historical data exists? What granularity?
6. Reporting Audience: Who receives reports? (Exec/C-suite, marketing team, board, clients)
7. Known Issues: Any known data quality problems, tracking gaps, or recent changes?
8. Geographic Scope: Single market or multi-market (affects privacy regulations)
9. Privacy Constraints: GDPR, CCPA, ATT — what consent mechanisms are in place?
10. Specific Question: If investigating an anomaly, what exactly changed and when?

For anomaly investigation, prioritize speed. Ask for the specific metric, timeframe, and any known changes. For strategic measurement work, gather the full context.

Capabilities

• KPI Tree Generation per Business Model: Hierarchical metric frameworks that connect top-level business goals to actionable marketing metrics, customized for SaaS, e-commerce, lead gen, marketplace, subscription, media, and other models
• Standardized Reporting: Templates for weekly performance snapshots, monthly strategic reviews, quarterly business reviews, and campaign post-mortems — each designed for different stakeholder audiences
• Anomaly Detection and Root Cause Diagnosis: Structured diagnostic framework for investigating sudden metric changes — systematic elimination of causes (tracking issues, external events, algorithm changes, seasonality, competitive actions, internal changes)
• Competitive Intelligence Framework: Methodology for monitoring competitor activity across channels (SEO, paid, social, content, PR), estimating competitor spend, and benchmarking performance
• Marketing Mix Modeling (MMM) Guidance: Framework for understanding channel-level contribution to business outcomes, including data requirements, model design considerations, and result interpretation
• Incrementality Test Design: Experiment design for geo-based lift tests, holdout tests, conversion lift studies, and matched-market tests to measure true causal marketing impact
• Dark Social Tracking: Methods for measuring private sharing activity (link shorteners, UTM-equipped sharing buttons, dedicated landing pages, survey-based attribution) and estimating dark social contribution
• Cookieless Attribution: Privacy-first attribution approaches including server-side tracking, first-party data strategies, modeled conversions, media mix modeling, and probabilistic methods
• Privacy-First Measurement Stack: Complete measurement architecture designed for GDPR/CCPA compliance, iOS ATT, cookie deprecation, and evolving privacy regulations
• Dashboard Architecture: Stakeholder-appropriate dashboard design with metric hierarchy, visualization best practices, and alert configuration

Process

Primary Workflow: Measurement Framework & Reporting

1. Business Context & Goal Alignment

   • Classify the business model and maturity stage
   • Identify the north star metric (the single metric most tied to business value)
   • Map business goals to marketing objectives to tactical metrics (KPI tree)
   • Determine reporting audience and their decision-making needs

2. KPI Tree Construction

   • Start with the top-level business goal (revenue, growth, profitability)
   • Break into marketing contribution metrics (marketing-sourced revenue, CAC, LTV)
   • Decompose into channel-level metrics (channel CPA, ROAS, conversion rate)
   • Add leading indicators (traffic, engagement, pipeline, MQLs)
   • For each KPI, define:
     • Definition: Exactly how it is calculated (no ambiguity)
     • Source: Where the data comes from
     • Benchmark: Target or industry benchmark
     • Cadence: How often it is reviewed
     • Owner: Who is responsible for this metric
   • Limit the framework to 15-25 KPIs total — more causes metric fatigue and diluted focus

3. Reporting Template Design

   • Weekly Snapshot (for marketing team):
     • Key metrics vs. target (traffic, leads, conversions, spend, CPA)
     • Week-over-week trends with directional indicators
     • Top 3 wins and top 3 concerns
     • Action items for the coming week
   • Monthly Strategic Review (for marketing leadership):
     • Month-over-month and year-over-year performance
     • Channel contribution breakdown
     • Funnel conversion rate analysis
     • Budget utilization and efficiency metrics
     • Strategic insights and recommendations
   • Quarterly Business Review (for executive/board):
     • Marketing contribution to business goals
     • CAC, LTV, and payback period trends
     • Competitive positioning update
     • Next quarter strategic priorities
   • Campaign Report (per campaign):
     • Performance vs. pre-defined KPIs
     • Channel-by-channel analysis
     • Creative and audience performance
     • Learnings and recommendations

4. Anomaly Investigation Protocol When a user reports a sudden metric change, follow this diagnostic sequence:

   • Step 1: Verify the Data

     • Is the tracking code still firing correctly?
     • Did a tag manager change, consent tool update, or analytics filter change occur?
     • Check for platform outages or reporting delays
     • If data is corrupted, fix tracking first — do not analyze bad data

   • Step 2: Define the Anomaly Precisely

     • Which metric changed? By how much? Over what time period?
     • Is it all traffic or a specific segment (channel, device, geography, page)?
     • Did it happen suddenly or gradually?

   • Step 3: Check External Factors

     • Google algorithm update (check SEMrush Sensor, MozCast)
     • Industry news or seasonal patterns
     • Competitor activity changes
     • Platform policy or feature changes

   • Step 4: Check Internal Factors

     • Website changes (deployments, URL changes, redirects)
     • Content changes (published, removed, or modified)
     • Campaign changes (launched, paused, budget shifted)
     • Technical issues (site speed, server errors, mobile rendering)

   • Step 5: Isolate and Diagnose

     • Cross-reference the anomaly with the identified factors
     • Determine the most likely root cause
     • Estimate the impact and expected recovery timeline
     • Recommend corrective actions

5. Privacy-First Measurement Architecture

   • Audit current measurement for privacy compliance gaps
   • Design a measurement stack that works without third-party cookies:
     • Server-side tracking for owned touchpoints
     • First-party data enrichment strategy
     • Privacy-compliant consent management
     • Platform-native conversion APIs (Meta CAPI, Google Enhanced Conversions)
     • Modeled conversions for attribution gaps
     • Marketing mix modeling for channel-level effectiveness
     • Incrementality testing for causal validation
   • Create a transition plan from current state to privacy-first architecture
   • Account for iOS ATT impact on iOS-heavy audience segments

Reference Files

• kpi-frameworks.md — Business-model-specific KPI trees, metric definitions, benchmark databases, and north star metric selection guide
• reporting-templates.md — Weekly, monthly, quarterly, and campaign reporting templates with stakeholder-appropriate formatting and visualization guidance
• anomaly-diagnosis.md — Diagnostic decision tree, common root causes by metric type, verification checklists, and resolution playbooks
• competitive-intelligence.md — Competitor monitoring methodology, tool recommendations, benchmarking frameworks, and competitive response playbooks
• mmm-framework.md — Marketing mix modeling data requirements, model design guidance, result interpretation, and optimization recommendations
• incrementality-testing.md — Experiment design templates (geo lift, holdout, conversion lift), statistical power calculations, and result analysis frameworks
• dark-social-tracking.md — Dark social measurement methods, implementation guides for tracking private shares, and estimation models
• privacy-first-measurement.md — Cookieless attribution approaches, consent management architecture, server-side tracking implementation, and privacy regulation compliance guide

Output Formats

Edge Cases

Insufficient Data for MMM (<2 Years)

• Situation: User wants marketing mix modeling but has less than 2 years of consistent marketing data
• Approach: Be honest about the limitation — MMM requires sufficient time-series data to separate signal from noise. With less than 2 years: (1) Start collecting and structuring data now for future modeling. (2) Use simpler channel-level attribution as a bridge. (3) Run incrementality tests to get causal data on key channels. (4) Consider lighter-weight approaches like regression analysis on available data with clear caveats about confidence levels. (5) Build toward MMM readiness with a data collection roadmap. Do not attempt to build a full MMM on insufficient data — the results will be misleading and potentially harmful to budget decisions.

iOS ATT Destroying Attribution

• Situation: Significant portion of conversions are untrackable due to iOS App Tracking Transparency opt-outs, making attribution data unreliable
• Approach: Acknowledge the gap explicitly rather than pretending attribution data is still complete. Implement: (1) Platform conversion APIs (Meta CAPI, Google Enhanced Conversions) to recover some signal. (2) Server-side tracking for owned touchpoints. (3) Modeled conversions using platform statistical models (with appropriate skepticism about platform self-reporting). (4) First-party data matching where consent exists. (5) Marketing mix modeling as a complement to click-based attribution. (6) Incrementality testing for high-spend channels. (7) Survey-based attribution ("how did you hear about us?") as a qualitative check. The goal is triangulation — no single method is sufficient; combine multiple approaches.

Dark Social Dominating Referral Traffic

• Situation: Large portion of "direct" traffic is actually from private sharing (Slack, WhatsApp, email forwards, Discord) and attribution is blind
• Approach: Estimate dark social impact by analyzing "direct" traffic to non-homepage URLs (people rarely type deep URLs directly). Implement measurement improvements: (1) Add social sharing buttons with UTM parameters to track shared links. (2) Use link shorteners with tracking for shareable content. (3) Create dedicated landing pages for community/sharing use cases. (4) Add "how did you find this?" surveys to key conversion points. (5) Monitor content share velocity using social listening tools. (6) Accept that some dark social will remain unmeasured and build that uncertainty into reporting. (7) Consider investing more in dark-social-friendly channels (community, word-of-mouth, referral) even without perfect measurement.

Multi-Touch B2B Attribution Across 12+ Month Cycles

• Situation: B2B enterprise deals take 12-24 months with dozens of touchpoints across multiple stakeholders, making traditional attribution models meaningless
• Approach: Abandon pure last-touch or first-touch models — neither represents reality. Implement: (1) Account-based attribution that measures touchpoints at the account level, not individual level. (2) Influence-based reporting that shows which channels contributed to pipeline, even if they didn't "source" the deal. (3) Weight models toward time-decay with higher weights on recent high-intent touchpoints. (4) Use self-reported attribution from sales team and buyer surveys as a complement to digital tracking. (5) Measure channel effectiveness by pipeline velocity (does this channel accelerate deals?) not just by sourcing. (6) Accept that perfect attribution is impossible for complex B2B and focus on directional insights rather than false precision.

Regulated Data Handling

• Situation: User is in healthcare (HIPAA), financial services, education (FERPA), or other industries with strict data handling regulations
• Approach: Before any analytics implementation, flag the regulatory context. Ensure: (1) PII is never passed through analytics platforms without proper consent and processing agreements. (2) Data storage complies with regional requirements (data residency). (3) Consent management is explicit and granular. (4) Analytics vendors have appropriate compliance certifications (SOC 2, BAA for HIPAA, etc.). (5) User-level tracking is replaced with cohort or aggregate analysis where required. (6) Data retention policies are documented and enforced. Recommend involving a compliance officer or legal counsel for any measurement architecture in regulated industries. Never assume general analytics best practices are compliant in regulated contexts.

Related Skills

• Campaign Orchestrator — For translating analytics insights into campaign optimizations, budget reallocation, and strategic decisions
• Funnel Architect — For connecting funnel-stage metrics to the KPI framework and diagnosing conversion rate anomalies
• Content Engine — For measuring content performance, identifying content decay, and informing content strategy with data
• AEO/GEO Intelligence — For tracking AI visibility metrics and incorporating AI citation data into the measurement framework
• Audience Intelligence — For validating persona hypotheses with behavioral data and building data-driven segments
• Digital PR & Authority — For measuring earned media impact, backlink acquisition, and share of voice

Context efficiency

This skill's reference docs (skills/<this-skill>/*.md) sum to ~30-50KB. Don't load them eagerly — pick targeted sections:

• Grep before Read. Find the keyword or section heading first, then Read with offset + limit to pull just that range.
• Walk ${CLAUDE_SKILL_DIR} once. Use a single directory listing to see what's there, then Read only the files that match your current step.
• One source at a time. If the workflow says "consult three reference files," read them sequentially after deciding what you need from each. Bulk-loading all three blows the per-skill 5K-token budget that auto-compaction reserves.
• Strip noise from CSV inputs. If the input is a large CSV, grep the header line first to pick columns, then process row-by-row — do not Read the whole file into context.

---

Supporting file: anomaly-diagnosis.md

Anomaly Diagnosis — Metric Investigation Framework

Core Principle

When a metric moves unexpectedly, the first question is never "What happened?" — it is "Is the data correct?" Most apparent anomalies are measurement errors. After confirming data integrity, follow a structured diagnostic tree to isolate root cause before taking action.

---

Verification Checklist — Run This First

Before investigating any anomaly, complete this checklist to rule out data and tracking issues.

Data Integrity Checks

• Tracking code present — Verify the tracking pixel/tag is still firing on all relevant pages
• Tag manager audit — Check for recent container changes, paused tags, or version rollbacks
• Consent management — Confirm consent banners are functioning and not blocking tracking
• Bot filtering — Verify bot/spider filtering is active; check for traffic spikes from known bot IPs
• Cross-platform reconciliation — Compare the metric across two independent sources (e.g., GA4 vs platform data vs backend)
• Date range alignment — Ensure comparison periods have equal days and account for holidays or seasonal shifts
• Currency / timezone consistency — Confirm reports use consistent timezone and currency settings
• Attribution window — Check if the attribution window changed (Meta's default shifts, Google Ads attribution model change)
• Sampling — In GA4, check if data is sampled (yellow shield icon); switch to unsampled export if needed
• Conversion counting — Verify conversion counting method (one-per-click vs every conversion) hasn't changed
• Server / site uptime — Check for outages, slow load times, or 500 errors during the anomaly period

Quick Validation Questions

---

Diagnostic Decision Trees

Traffic Drop Decision Tree

Traffic dropped significantly
├── Is tracking working correctly?
│   ├── NO → Fix tracking. Revalidate after fix.
│   └── YES → Continue
├── Is the drop across all channels or one channel?
│   ├── ONE CHANNEL → Go to channel-specific diagnosis
│   │   ├── Organic Search dropped
│   │   │   ├── Check Google Search Console for indexing errors
│   │   │   ├── Check for manual actions or algorithmic update
│   │   │   ├── Check robots.txt and sitemap for changes
│   │   │   ├── Check for ranking losses on high-traffic keywords
│   │   │   └── Check for technical SEO regressions (page speed, crawl errors)
│   │   ├── Paid Search dropped
│   │   │   ├── Check budget pacing (did budget run out?)
│   │   │   ├── Check for paused campaigns/ad groups
│   │   │   ├── Check auction insights for new competitors
│   │   │   ├── Check quality score changes
│   │   │   └── Check for disapproved ads
│   │   ├── Paid Social dropped
│   │   │   ├── Check for ad account issues (policy violations, spending limits)
│   │   │   ├── Check for audience saturation (frequency > 3)
│   │   │   ├── Check for creative fatigue (CTR declining over time)
│   │   │   └── Check for CPM increases (auction competition)
│   │   ├── Email / SMS dropped
│   │   │   ├── Check deliverability (bounce rate, spam complaints)
│   │   │   ├── Check send volume (were fewer campaigns sent?)
│   │   │   └── Check open rate decline (subject line, send time)
│   │   └── Direct / Referral dropped
│   │       ├── Check for lost referral partnerships or broken links
│   │       └── Check for brand search volume decline (Google Trends)
│   └── ALL CHANNELS → Sitewide issue
│       ├── Check for site outage or performance degradation
│       ├── Check for domain / DNS issues
│       ├── Check for major market event or seasonal shift
│       └── Check for Google Analytics configuration change

Conversion Rate Drop Decision Tree

Conversion rate dropped
├── Is the tracking pixel firing on the confirmation page?
│   ├── NO → Fix conversion tracking
│   └── YES → Continue
├── Did traffic source mix shift?
│   ├── YES → Lower-intent traffic is diluting CVR; segment analysis needed
│   └── NO → Continue
├── Was there a site change?
│   ├── YES → Check deployment logs
│   │   ├── Checkout flow changed → A/B test or rollback
│   │   ├── Page speed degraded → Performance fix
│   │   ├── Pricing changed → Expected CVR impact; monitor AOV
│   │   └── Design / layout changed → UX investigation
│   └── NO → Continue
├── Is the drop device-specific?
│   ├── Mobile only → Check mobile rendering, forms, payment flow
│   ├── Desktop only → Check for browser-specific issues
│   └── All devices → Continue
├── Is the drop geo-specific?
│   ├── YES → Check regional payment processing, shipping, or compliance issues
│   └── NO → Continue
└── External factors
    ├── Competitor launched promotion or undercut pricing
    ├── Seasonality or macro-economic shift
    └── Platform algorithm change affecting traffic quality

Cost Spike Decision Tree

CPA / CPM / CPC spiked
├── Is the cost increase across all campaigns or isolated?
│   ├── ISOLATED → Investigate specific campaign
│   │   ├── Check for audience overlap / self-competition
│   │   ├── Check for bid strategy malfunction
│   │   ├── Check for quality score / relevance score drop
│   │   └── Check for creative fatigue (CTR drop → CPC increase)
│   └── ALL CAMPAIGNS → Platform-level or market-level shift
│       ├── Check for auction competition (new advertiser, Q4 seasonality)
│       ├── Check for platform policy change affecting targeting
│       ├── Check for iOS / privacy update affecting optimization
│       └── Check CPM trends in industry benchmarking tools
├── Did conversion volume also drop?
│   ├── YES → Likely a targeting or quality issue (bad traffic at higher cost)
│   └── NO → May be acceptable if ROAS still within target
└── Action framework
    ├── If ROAS still acceptable → Monitor but don't react
    ├── If ROAS degraded → Reduce spend on worst performers, reallocate
    └── If systemic → Diversify channels, improve organic/owned

Revenue Decline Decision Tree

Revenue declined
├── Is the decline in transaction count or average order value?
│   ├── TRANSACTION COUNT → Follow Conversion Rate Drop tree
│   ├── AOV DECLINED
│   │   ├── Check for pricing changes or promotions
│   │   ├── Check product mix shift (more low-price items)
│   │   ├── Check for discount code abuse
│   │   └── Check for bundle / upsell feature breakage
│   └── BOTH → Systemic issue; investigate traffic quality + site experience
├── Is the decline in new customer revenue or returning customer revenue?
│   ├── NEW CUSTOMER → Acquisition issue; check paid channels and landing pages
│   ├── RETURNING CUSTOMER → Retention issue; check email, loyalty, product experience
│   └── BOTH → Market-level concern or major site issue
└── Revenue attribution check
    ├── Is the decline real in backend data (Shopify, Stripe, etc.)?
    ├── Or is it only in the analytics platform (attribution loss)?
    └── If discrepancy → Attribution model or tracking issue, not revenue issue

---

Common Root Causes Table

---

Resolution Playbooks

Playbook: Traffic Recovery

1. Confirm the drop is real (verification checklist complete)
2. Identify the affected channel and segment
3. For paid: check budget, ad status, bid strategy, approval status
4. For organic: check GSC for crawl errors, index coverage, ranking changes
5. For email: check deliverability, send volume, list health
6. Implement fix and monitor recovery for 48-72 hours
7. If no recovery, escalate to channel specialist or platform support
8. Document root cause and update monitoring alerts

Playbook: Conversion Rate Recovery

1. Confirm tracking integrity on conversion pages
2. Segment CVR by device, geo, source, and landing page
3. Check for site changes in the deployment log
4. Run QA on the full conversion funnel (search → PDP → cart → checkout → confirmation)
5. Test on multiple devices and browsers
6. If site change identified, revert or A/B test the change
7. If traffic quality issue, adjust targeting or bid strategy
8. Monitor CVR for 7 days post-fix to confirm recovery

Playbook: Cost Optimization

1. Confirm cost spike is not a data lag or reporting error
2. Isolate to specific campaigns, ad sets, or keywords
3. Check for self-competition (audience overlap, keyword cannibalization)
4. Review bid strategy (is automated bidding over-indexing on expensive clicks?)
5. Reduce spend on worst-performing segments by 20-30%
6. Refresh creative if CTR has declined (creative fatigue)
7. Expand audience or keyword set to find cheaper inventory
8. Monitor for 5-7 days and reassess

---

Alert Configuration Framework

Recommended Alert Thresholds

Alert Design Principles

• Use percentage deviation from rolling average, not absolute thresholds (accounts for seasonality)
• Apply day-of-week adjustments for metrics with strong weekly patterns (e.g., B2B traffic dips on weekends)
• Set a "cool-down" period (4-6 hours) to avoid duplicate alerts for the same issue
• Require two consecutive data points before triggering (avoids one-off blips)
• Include direct links to relevant dashboards in every alert message
• Route alerts to the metric owner, not a shared channel that everyone ignores
• Review and tune thresholds monthly — if an alert fires more than 3 times/week with no action taken, the threshold is wrong

---

Investigation Documentation Template

When completing any anomaly investigation, record findings using this format:

---

Supporting file: clv-analysis.md

Customer Lifetime Value (CLV) — Analysis & Application Reference

CLV Models Overview

---

Calculation Methods

Method 1: Simple CLV

The quickest estimate. Useful for early-stage businesses or initial benchmarking.

CLV = Average Order Value (AOV) x Purchase Frequency x Customer Lifespan

Where:
- AOV = Total Revenue / Total Orders (in period)
- Purchase Frequency = Total Orders / Unique Customers (in period)
- Customer Lifespan = 1 / Churn Rate (annualized)

Example:

• AOV = $85
• Purchase frequency = 3.2 orders/year
• Customer lifespan = 1 / 0.25 churn = 4 years
• CLV = $85 x 3.2 x 4 = $1,088

Limitations: Assumes constant behavior, ignores margin, does not account for time value of money.

Method 2: Margin-Adjusted CLV

Adds gross margin and discount rate for more realistic valuation.

CLV = (AOV x Purchase Frequency x Gross Margin %) x (1 / Churn Rate) x (1 / (1 + Discount Rate))

Or simplified:
CLV = (ARPU x Gross Margin %) / Churn Rate

Example (SaaS):

• Monthly ARPU = $99
• Gross margin = 80%
• Monthly churn = 3%
• CLV = ($99 x 0.80) / 0.03 = $2,640

Method 3: Cohort-Based CLV

Tracks actual revenue generated by acquisition cohorts over time. Most accurate for businesses with 12+ months of data.

Month 0 cohort (Jan 2024): 500 customers acquired
├── Month 0: $42,500 revenue (500 customers, $85 AOV)
├── Month 1: $12,750 (150 returning, $85)
├── Month 2: $8,500 (100 returning, $85)
├── Month 3: $7,225 (85 returning, $85)
├── ...
├── Month 12: $3,400 (40 returning, $85)
└── 12-month cohort revenue: $125,000

12-month CLV = $125,000 / 500 = $250 per customer

Cohort Revenue Table Template

Method 4: Contractual CLV (SaaS / Subscription)

CLV = (Monthly Revenue per Account x Gross Margin %) / Monthly Churn Rate

With expansion:
CLV = (Monthly Revenue x Gross Margin %) x (1 + Net Expansion Rate) / Monthly Churn Rate

---

CLV Segmentation

CLV by Acquisition Channel

CLV by First Purchase Behavior

CLV by Customer Persona

---

CLV:CAC Ratio

Ratio Interpretation

CAC Calculation (Fully Loaded)

Fully Loaded CAC = (Ad Spend + Marketing Salaries + Tools & Software + Agency Fees + Content Production) / New Customers Acquired

Paid CAC = Paid Channel Spend / Customers Acquired via Paid Channels

Blended CAC = Total Marketing + Sales Cost / Total New Customers (including organic)

Important: Use the fully loaded CAC for business planning. Use paid CAC for channel optimization. The gap between blended and paid CAC represents the value of your organic and brand channels.

---

Payback Period

Definition and Calculation

CAC Payback Period = CAC / (Monthly Revenue per Customer x Gross Margin %)

Example:
- CAC = $300
- Monthly revenue = $50
- Gross margin = 80%
- Payback = $300 / ($50 x 0.80) = 7.5 months

Payback Period Benchmarks

Cash Flow Implications

• Short payback (<6 months): Self-funding growth is possible; reinvest revenue into acquisition
• Medium payback (6-12 months): Growth requires working capital; plan for cash flow gaps
• Long payback (12-24 months): Requires external capital or careful cash management; every churn event is expensive
• Payback > CLV: Unit economics are broken; fix retention or reduce CAC before scaling

---

Improving CLV

Lever 1: Increase Average Order Value

Lever 2: Increase Purchase Frequency

Lever 3: Increase Customer Lifespan (Reduce Churn)

Lever 4: Reduce Cost of Goods Sold

---

CLV in Budget Decisions

Setting Allowable CAC by Channel

Allowable CAC = CLV x Target CLV:CAC Ratio Inverse

Example:
- CLV = $900
- Target CLV:CAC ratio = 3:1
- Allowable CAC = $900 / 3 = $300

Channel allocation:
- Organic (CAC $50) → Scale aggressively
- Paid search brand (CAC $120) → Scale aggressively
- Paid search non-brand (CAC $250) → Scale with monitoring
- Paid social (CAC $350) → Optimize before scaling (exceeds allowable)
- Display (CAC $500) → Pause or restructure targeting

LTV-Based Bidding Strategy

High-Value Customer Identification Signals

Use these signals to identify potentially high-CLV customers early (before full CLV data exists):

---

Industry Benchmarks

eCommerce CLV Benchmarks

SaaS CLV Benchmarks

Subscription Business CLV Benchmarks

---

Data Requirements Checklist

Minimum Data for CLV Analysis

• Customer ID (unique identifier across all transactions)
• Transaction date (order date for each purchase)
• Transaction value (revenue per order, ideally after returns/refunds)
• Customer acquisition date (first purchase or signup date)
• Acquisition channel/source (how each customer was acquired)

Recommended Additional Data

• Product categories purchased (enables category-level CLV segmentation)
• Gross margin by product/order (enables margin-adjusted CLV)
• Customer support interactions (enables cost-adjusted CLV)
• Discount/promotion usage per order (identifies discount-dependent customers)
• Customer demographic data (enables persona-level CLV)
• Engagement metrics (email opens, site visits, app usage between purchases)
• NPS or satisfaction scores (leading indicator of churn/retention)
• Subscription status changes (upgrades, downgrades, cancellations, pauses)

Data Quality Checks

• Customer IDs are consistent across channels (no duplicates for same person)
• Refunds and returns are reflected in transaction values
• Acquisition dates are accurate (not overwritten by subsequent activity)
• Channel attribution is reliable for first-touch acquisition source
• At least 12 months of historical data exists for cohort analysis
• Sample sizes are sufficient per segment (minimum 100 customers per segment for statistical validity)

---

CLV is the single most important metric in marketing because it answers the fundamental question: how much can you afford to spend to acquire a customer and still build a profitable business? Every budget decision, channel investment, and retention initiative should be evaluated through the CLV lens.

---

Supporting file: competitive-intelligence.md

Competitive Intelligence — Monitoring & Analysis

Purpose

Competitive intelligence is not about copying competitors. It is about understanding the market landscape to make better-informed strategic decisions — identifying gaps, anticipating threats, and finding positioning advantages that competitors have missed.

---

Competitor Monitoring Framework

What to Track

Competitor Tier Classification

---

Tool Recommendations

Free Tools

Paid Tools

---

Competitive Benchmarking Framework

Traffic & Engagement Benchmark Template

Source: SimilarWeb or SEMrush. Note: These are estimates with +/- 20% accuracy.

SEO Benchmark Template

Paid Media Benchmark Template

Positioning & Messaging Benchmark

---

Competitive Response Playbooks

Playbook: Competitor Launches Price Cut

1. Assess scope — Is it a temporary promotion or permanent price change?
2. Measure impact — Monitor your CVR, traffic, and branded search volume for 2 weeks
3. Analyze margins — Can the competitor sustain this price? Check their funding/financial position
4. Response options:
   • Do nothing (if your differentiation is strong and CVR is stable)
   • Match selectively (discount for competitive switchers only, not existing customers)
   • Add value (bundle, extended warranty, better support) instead of cutting price
   • Emphasize differentiation in ad copy and landing pages
5. Avoid: Reflexive price matching that erodes margins without evidence of customer loss

Playbook: Competitor Launches New Feature / Product

1. Assess overlap — Does this feature compete with your core offering or a peripheral area?
2. Gauge demand — Check search trends, social mentions, and customer feedback for the feature
3. Timeline assessment — How long to build a comparable feature? Is it even strategic for you?
4. Response options:
   • Fast follow (if the feature aligns with your roadmap and is high-demand)
   • Differentiate (double down on your strengths and highlight in messaging)
   • Partner (integrate a third-party solution rather than building)
   • Ignore (if the feature is niche and your data shows low customer demand)
5. Update sales enablement — Provide talking points for sales/CS on how to position against the new feature

Playbook: Competitor Increases Ad Spend Significantly

1. Verify — Use SpyFu, Pathmatics, or Meta Ad Library to confirm the increase
2. Measure impact — Track your impression share, CPCs, and auction competition metrics
3. Assess duration — Is this a campaign burst or a sustained increase?
4. Response options:
   • Hold position on high-ROI campaigns; reduce spend on marginal campaigns
   • Shift budget to channels where the competitor is not present
   • Improve ad quality (creative, landing page) to maintain position at lower cost
   • Increase spend only in segments where you have a clear efficiency advantage
5. Do not engage in a bidding war on broad terms with poor ROAS

Playbook: New Competitor Enters Market

1. Profile immediately — Funding, team, positioning, pricing, initial channels
2. Classify tier — Usually Tier 4 initially; upgrade if traction is evident
3. Monitor traction signals — Traffic growth, social following, review volume, hiring
4. Response options:
   • Strengthen your incumbent advantages (reviews, content, SEO moat, customer relationships)
   • Consider defensive content targeting their brand name comparisons
   • Accelerate feature/product development that widens your differentiation
5. Brief the team — Update sales and CS so they can address the new competitor in conversations

---

Win/Loss Analysis Methodology

Data Collection

Win/Loss Interview Guide

1. What were you trying to solve? (Job to be done)
2. Who else did you evaluate? (Competitive set)
3. What were your decision criteria? (Prioritized)
4. What did you like about our solution? (Strengths)
5. What concerned you? (Weaknesses)
6. Why did you ultimately choose [winner]? (Decision driver)
7. What could we have done differently? (Actionable feedback)

Analysis Framework

---

Monthly Competitive Review Template

Cadence: First week of each month. Duration: 60-minute meeting.

Agenda

1. Tier 1 Competitor Updates (20 min)

   • Major moves from each direct competitor (product, pricing, campaigns, hiring)
   • Impact assessment (actual or anticipated)

2. Market Signals (10 min)

   • New entrants, funding rounds, M&A activity
   • Regulatory or platform changes affecting the competitive landscape

3. Benchmarking Update (10 min)

   • Traffic, SEO, paid media, and share-of-voice trends
   • Any significant ranking or positioning shifts

4. Win/Loss Summary (10 min)

   • Monthly win rate vs. each competitor
   • Notable themes from losses

5. Action Items (10 min)

   • Competitive responses needed
   • Intelligence gaps to fill
   • Updates to sales battlecards or marketing positioning

Competitive Intelligence Maintenance Checklist

• Tier 1 competitor ad libraries reviewed weekly
• Competitor email flows reviewed (sign up refreshed if needed)
• Keyword ranking overlap tracked bi-weekly
• Website change monitoring active for all Tier 1 competitors
• Win/loss interviews conducted (minimum 3-5 per month)
• Competitive benchmarking spreadsheet updated monthly
• Sales battlecards refreshed after any major competitor move
• Quarterly competitive landscape presentation prepared for leadership
• New competitor watch list reviewed and updated quarterly
• Team trained on competitive positioning (quarterly enablement session)

---

Supporting file: dark-social-tracking.md

Dark Social Tracking — Measurement Methods

What is Dark Social?

Dark social refers to content sharing and referral traffic that occurs through private, untraceable channels — direct messages, private group chats, SMS, email forwards, Slack, WhatsApp, Discord, and native mobile app sharing. When a user copies a link and pastes it into a group chat, the referrer header is stripped. The resulting visit appears as "direct traffic" in analytics, making it invisible to standard attribution.

Why It Matters

What Channels Generate Dark Social Traffic?

---

Measurement Methods

Method 1: UTM Tracking for Shareable Content

The most direct approach is to embed tracking parameters into every shareable link so that even when the referrer is stripped, the UTM parameters persist.

UTM Structure for Dark Social:

Example:

https://example.com/blog/post-title?utm_source=whatsapp&utm_medium=share&utm_campaign=blog-post-title

Method 2: Platform-Specific Share Buttons

Replace generic "copy link" buttons with platform-specific share buttons that pre-populate UTMs.

Implementation checklist:

• WhatsApp share button with utm_source=whatsapp
• Telegram share button with utm_source=telegram
• SMS share button (using sms: protocol) with utm_source=sms
• Email share button with utm_source=email_share
• LinkedIn share button with utm_source=linkedin_share
• Twitter/X share button with utm_source=twitter_share
• "Copy Link" button that automatically appends utm_source=copy_link&utm_medium=share
• Each button fires a GA4 custom event (e.g., share_click) with the platform as a parameter

Technical implementation notes:

• Use JavaScript to dynamically append UTMs when the share button is clicked
• For "Copy Link," intercept the clipboard write to append parameters to the URL
• Store the page URL + UTMs in the clipboard, not just the clean URL
• On mobile, use the Web Share API (navigator.share()) with UTM-tagged URL

Method 3: Shortened URLs with Tracking

Use branded short URLs that redirect through a tracking layer.

Best practice: Use shortened URLs for content distributed through dark social-heavy channels (newsletters, podcasts, communities). Embed full UTMs in the redirect destination.

Method 4: Direct Traffic Segmentation

Since dark social inflates Direct traffic, analyze Direct traffic patterns to estimate the dark social component.

Segmentation logic:

GA4 implementation:

1. Create a segment: Source = (direct), Landing Page does NOT match homepage, Device = Mobile
2. This segment approximates mobile dark social traffic
3. Track this segment's volume and trends over time
4. Compare to content pages receiving high known social traffic for calibration

Method 5: Self-Reported Attribution ("How Did You Hear About Us?")

Add a "How did you hear about us?" question to key conversion points.

Implementation options:

Recommended answer options:

• Search engine (Google, Bing)
• Social media (Instagram, TikTok, LinkedIn, etc.)
• Friend or colleague recommended
• Podcast
• Newsletter or email
• Online community (Reddit, Discord, Slack)
• Blog post or article
• YouTube video
• Saw an ad
• Other (please specify): ___

Analysis guidance:

• "Friend or colleague recommended" and "Online community" are strong dark social indicators
• Cross-reference self-reported source with analytics-attributed source to quantify attribution gaps
• Track self-reported attribution trends monthly; shifts indicate changing discovery patterns

---

Estimation Models

Dark Social Traffic Estimation Formula

Estimated Dark Social = Direct Traffic to Non-Homepage Pages (New Users, Mobile)

More refined estimation:

Calibration: Compare estimated dark social volume against known sharing activity (share button clicks, shortened URL clicks) to validate the estimate. Typical finding: estimated dark social is 3-5x the tracked sharing activity.

Dark Social Impact Assessment

---

Platform-Specific Patterns

Where Dark Social Traffic Originates by Platform

---

Reporting Framework

Dark Social Dashboard Components

Monthly Dark Social Report Template

Section 1: Volume & Trends

• Estimated dark social sessions this month vs last month
• Dark social as % of total traffic (trend over 6 months)
• Share button click volume by platform

Section 2: Content Performance

• Top 10 most-shared content pieces (by share button clicks + estimated dark social traffic)
• Content themes that drive the most sharing
• New vs evergreen content sharing patterns

Section 3: Conversion Impact

• Estimated revenue from dark social traffic
• Dark social conversion rate vs overall site conversion rate
• Self-reported attribution data (% saying "friend," "community," "podcast")

Section 4: Attribution Gap Analysis

• Comparison of GA4 channel attribution vs self-reported attribution
• Channels most undercounted by analytics (typically organic social, podcasts, word-of-mouth)
• Implications for budget allocation

Section 5: Recommendations

• Content to invest in based on sharing patterns
• Share UX improvements to implement
• Channels where dark social indicates underinvestment

---

Implementation Roadmap

Phase 1: Foundation (Week 1-2)

• Implement platform-specific share buttons on all key content pages
• Configure "Copy Link" button to append UTMs automatically
• Set up GA4 custom events for share button clicks
• Create Direct traffic segmentation for dark social estimation
• Add "How did you hear about us?" to primary conversion form

Phase 2: Measurement (Week 3-4)

• Build dark social estimation model using the segmentation logic
• Create initial dark social dashboard
• Set up branded short links for podcast and community distribution
• Configure vanity URLs for offline channels
• Establish baseline metrics for dark social volume and conversion

Phase 3: Optimization (Month 2+)

• Analyze share button usage to optimize placement and design
• Identify top-shared content and invest in similar formats
• Cross-reference self-reported attribution with analytics attribution monthly
• Adjust budget allocation based on attribution gap analysis
• Test new share prompts (e.g., "Share this with a colleague who..." copy)
• Report dark social trends quarterly to leadership as part of attribution review

Phase 4: Advanced (Quarter 2+)

• Integrate self-reported attribution data into MMM as an additional signal
• Build a "shareability score" for content planning (predicting which content will be shared)
• Implement Web Share API for mobile-first sharing experience
• Test incentivized sharing (referral rewards) and measure incremental impact
• Incorporate dark social insights into content strategy planning process

---

Supporting file: dashboard-design.md

Marketing Dashboard Design — Architecture & Best Practices

Dashboard Hierarchy

Marketing dashboards should exist in three tiers, each serving a different audience, cadence, and depth of detail.

Executive Dashboard (C-Suite, VP)
├── 5-7 KPIs | Monthly review | Strategic decisions
│
Operational Dashboard (Directors, Managers)
├── 15-20 metrics | Weekly review | Tactical adjustments
│
Campaign Dashboard (Specialists, Analysts)
└── 30+ metrics | Daily/real-time | Execution optimization

---

Executive Dashboard Template

Purpose

Give leadership a single-screen view of marketing's impact on business outcomes. No scrolling. No tabs. Every metric has context (vs. target, vs. prior period).

Required Metrics (5-7 maximum)

Executive Dashboard Layout

┌────────────────────────────────────────────────────────────────┐
│  MARKETING PERFORMANCE — [Month] [Year]          [Date range] │
├──────────┬──────────┬──────────┬──────────┬──────────┐        │
│ Revenue  │ CAC      │ Pipeline │ ROAS     │ Leads    │        │
│ $1.2M    │ $142     │ $4.8M    │ 5.2x     │ 3,841    │        │
│ ▲ +12%   │ ▼ -8%    │ ▲ +18%   │ ▲ +0.3x  │ ▲ +15%   │        │
│ vs target│ vs target│ vs target│ vs target│ vs target│        │
├──────────┴──────────┴──────────┴──────────┴──────────┘        │
│                                                                │
│  ┌─── Revenue by Channel (6-mo) ──┐  ┌── Funnel (MoM) ──────┐│
│  │ [Stacked bar chart]             │  │ Visitors → Leads      ││
│  │                                 │  │ Leads → MQLs          ││
│  │                                 │  │ MQLs → SQLs           ││
│  │                                 │  │ SQLs → Closed Won     ││
│  └─────────────────────────────────┘  └───────────────────────┘│
└────────────────────────────────────────────────────────────────┘

Executive Dashboard Rules

• Every metric shows comparison context (vs. target, vs. prior period, vs. same period last year)
• Color coding: green = on track, yellow = within 10% of target, red = more than 10% off target
• No more than 7 metrics on the primary view
• Trend direction arrows on every scorecard
• Date range selector defaults to current month with prior month comparison
• No jargon — use business language, not platform-specific terms

---

Operational Dashboard Template

Purpose

Enable marketing managers to identify issues, spot opportunities, and make weekly tactical adjustments across all channels.

Metric Groups

Traffic & Acquisition

Conversion & Revenue

Email Performance

Social Media

Paid Advertising

---

Campaign Dashboard Template

Purpose

Provide real-time performance data for active campaigns so specialists can optimize execution daily.

Campaign-Level Metrics

Budget Pacing Visualization

Budget: $10,000 | Period: Nov 1-30 | Today: Nov 15 (50% elapsed)

Ideal pace:   ████████████████░░░░░░░░░░░░░░░░  50% ($5,000)
Actual spend:  ███████████████████░░░░░░░░░░░░░  58% ($5,800)  ⚠️ Over-pacing

Status: Over-pacing by 8% — reduce bids by 5-10% or pause low-performers

---

Visualization Best Practices

Chart Type Selection Guide

Design Principles

• Use consistent color palettes across all dashboards (assign one color per channel permanently)
• Left-to-right reading order: most important metrics on the top-left
• White space between sections — do not cram metrics together
• Every chart has a title that states the insight, not just the metric name ("Revenue is trending 12% above target" not "Revenue")
• Include the date range and last refresh time on every dashboard page
• Use consistent number formatting (currency, percentages, abbreviations)
• Add annotations for known events (campaign launch, site outage, holiday, algorithm update)
• Sparklines for compact trend visualization on scorecards
• Conditional formatting: red/yellow/green tied to specific thresholds, not arbitrary ranges

---

Alert Threshold Configuration

Critical Alerts (Immediate Notification)

Warning Alerts (Next Business Day)

Informational Alerts (Weekly Review)

---

Tool Recommendations

Tool Selection Decision Tree

Do you primarily use Google ecosystem (GA4, Google Ads)?
├── Yes → Looker Studio (free, native integration)
│   └── Need advanced modeling? → Add Supermetrics for data pipeline
│
├── No → Multi-platform data sources?
│   ├── Yes, many sources → Databox or Klipfolio (pre-built connectors)
│   └── Few sources → Power BI (affordable) or Tableau (powerful)
│
└── Agency with multiple clients?
    └── Klipfolio (white-label) or Databox (automated reports)

---

Data Freshness Trade-offs

Recommended Freshness by Dashboard

• Executive: Daily refresh is sufficient (decisions are monthly/quarterly)
• Operational: Daily refresh minimum, hourly for paid advertising metrics
• Campaign: Real-time for spend and impressions, hourly for conversions and CPA

---

Dashboard Anti-Patterns

---

Business Model Templates

SaaS Dashboard Focus Areas

eCommerce Dashboard Focus Areas

B2B Lead Gen Dashboard Focus Areas

Agency Dashboard Focus Areas

---

Implementation Checklist

• Dashboard hierarchy defined (executive, operational, campaign)
• Metric owners assigned for every metric on every dashboard
• Data sources connected and validated (cross-check with platform native reports)
• Refresh frequency configured per dashboard tier
• Color palette standardized across all dashboards (one color per channel/source)
• Alert thresholds configured for critical and warning conditions
• Comparison context added to every metric (vs. target, vs. prior period)
• Drill-down paths linked between dashboard tiers
• Glossary tab with metric definitions added to each dashboard
• Event annotations configured for campaigns, launches, outages
• Access permissions set (executives see executive tier, not campaign noise)
• Automated distribution scheduled (email PDFs weekly, link sharing)
• Quarterly dashboard audit scheduled (remove unused metrics, add new ones)
• User training completed for all dashboard consumers

---

A dashboard that nobody checks is worse than no dashboard at all. Design for your audience's decisions, not your analyst's curiosity. Every metric on screen should answer a question someone actually asks, and every answer should suggest an action they can actually take.

---

Supporting file: incrementality-testing.md

Incrementality Testing — Experiment Design

Why Incrementality Testing Matters

Attribution models tell you which channels touched a conversion. Incrementality tests tell you which channels caused a conversion. The difference is critical: a channel can receive attribution credit for conversions that would have happened anyway (organic demand captured by paid). Incrementality testing isolates the true causal lift by comparing a treatment group (exposed to marketing) against a control group (not exposed).

---

When to Use Each Measurement Approach

---

Experiment Design Templates

1. Geo-Lift Test

Purpose: Measure the incremental impact of a channel or campaign by comparing treated geographies to control geographies.

Best for: Channels where user-level holdout is difficult (TV, radio, OOH, YouTube) or when platform-level conversion lift is unavailable.

Step-by-step guide:

1. Define the hypothesis — "Increasing Facebook spend by 50% in treatment geos will generate incremental revenue with an iROAS > 2.0"
2. Select geos — Pull 12-24 months of historical weekly revenue by geo. Identify 4-10 treatment geos and 10-20 potential control geos.
3. Match geos — Use synthetic control methods (CausalImpact in R, GeoLift by Meta) to find the control group that best replicates treatment group's pre-test behavior.
4. Validate the match — Run a pre-test "placebo" period. The synthetic control should track the treatment group within 2-3% during the pre-test period.
5. Run the test — Implement the treatment (increase/decrease spend) only in treatment geos. Change nothing in control geos.
6. Monitor weekly — Track for data quality issues but avoid making mid-test changes.
7. Analyze results — Compare actual treatment performance vs synthetic control prediction. Calculate lift, confidence interval, and iROAS.
8. Validate — Check that the lift is statistically significant (p < 0.10 for marketing tests) and economically meaningful.

2. User-Level Holdout Test

Purpose: Randomly withhold marketing from a subset of users to measure incremental lift.

Best for: Email, push notifications, retargeting, CRM campaigns.

Key considerations:

• Control group must be truly held out — no ad exposure, no email, no retargeting
• Ensure randomization is at the user level, not the session level (prevents contamination)
• Track both groups for the same duration, including post-exposure conversion window

3. Platform Conversion Lift Tests

These are built-in incrementality tools provided by ad platforms.

Meta Conversion Lift:

Google Conversion Lift:

---

Statistical Power Calculations

Why Power Matters

A test without sufficient statistical power will produce inconclusive results. Running an underpowered test wastes time and budget. Calculate power before starting.

Key Parameters

Power Calculation Rules of Thumb

Based on two-sided test, alpha=0.05, power=0.80. For alpha=0.10 (common in marketing), sample sizes are ~20% lower.

Duration Calculation

Test Duration (weeks) = Required Sample Size / Weekly Eligible Users

If the required duration exceeds 8 weeks, you have three options:

1. Increase the MDE (accept you can only detect larger effects)
2. Relax alpha to 0.10
3. Increase test group size (reduce control holdout percentage)

---

Result Analysis Framework

Calculating Incremental ROAS (iROAS)

iROAS = (Revenue_treatment - Revenue_control_projected) / Incremental_Spend

Where:

• Revenue_treatment = Actual revenue in treatment group/geos
• Revenue_control_projected = Control group revenue scaled to treatment group size (or synthetic control prediction)
• Incremental_Spend = Additional spend in treatment vs what control would have received

Interpreting Results

Confidence Interval Interpretation

Always report confidence intervals, not just point estimates.

---

Common Pitfalls

Design Pitfalls

Analysis Pitfalls

---

Incrementality Testing Roadmap

Prioritization Framework

Annual Testing Calendar Template

---

Implementation Checklist

• Identified top 3 channels to test based on spend and attribution confidence gap
• Defined hypothesis, primary metric, and success criteria for each test
• Completed power calculations and confirmed sufficient sample size
• Selected test design (geo-lift, user holdout, platform conversion lift)
• Matched treatment and control groups with validated pre-test alignment
• Documented the test plan including start date, end date, and analysis method
• Configured monitoring to detect data quality issues during the test
• Committed to no changes in treatment or control during the test period
• Analyzed results with confidence intervals, not just point estimates
• Shared findings with stakeholders and documented in a test log
• Used results to calibrate MMM or update budget allocation
• Scheduled the next round of tests based on the annual roadmap

---

Supporting file: kpi-frameworks.md

KPI Frameworks — Business-Model-Specific Metric Trees

KPI Tree Methodology

A KPI tree is a hierarchical decomposition of business outcomes into measurable, actionable metrics. Every metric in the tree should trace back to a single North Star and forward to a specific team or lever.

Hierarchy Levels

Building a KPI Tree — Step by Step

1. Define the North Star — What single metric, if maximized, would guarantee long-term business health?
2. Decompose mathematically — Break the North Star into a formula (e.g., Revenue = Customers x AOV x Frequency)
3. Assign primary metrics — Each variable in the formula becomes a primary metric
4. Layer supporting metrics — For each primary metric, identify the 2-4 inputs that drive it
5. Add diagnostics — For each supporting metric, list the granular signals you would check if it moved unexpectedly
6. Assign owners — Every metric gets one owner, never shared
7. Set targets — Use historical baselines + industry benchmarks + growth goals

---

North Star Metric Selection Guide

Your North Star must satisfy all five criteria:

• Value-aligned — It reflects genuine value delivered to customers
• Leading — It predicts long-term revenue, not just measures past revenue
• Actionable — Teams can influence it through their daily work
• Measurable — It can be tracked accurately with existing infrastructure
• Simple — Anyone in the company can understand and recite it

---

Full KPI Trees by Business Model

B2B SaaS KPI Tree

North Star: Net Revenue Retention (NRR)

SaaS Quick Ratios:

• Growth Efficiency: Magic Number = Net New ARR / Sales & Marketing Spend (target > 0.75)
• Burn Efficiency: Burn Multiple = Net Burn / Net New ARR (target < 2x)
• Rule of 40: Revenue Growth % + Profit Margin % > 40

eCommerce KPI Tree

North Star: Revenue per Visitor (RPV)

Marketplace KPI Tree

North Star: Gross Merchandise Volume (GMV) per Active User

Local Business KPI Tree

North Star: Monthly Repeat Visit Rate

DTC Brand KPI Tree

North Star: 90-Day Repeat Purchase Rate

---

Industry Benchmark Reference Table

---

Metric Definitions Glossary

---

Implementation Checklist

• North Star metric selected and validated against five criteria
• KPI tree built with all four levels populated
• Every metric has a single owner assigned
• Benchmarks established (internal baseline + industry)
• Targets set for current quarter
• Tracking infrastructure verified for every metric
• Dashboard built reflecting the tree hierarchy
• Review cadence established (weekly for Primary/Supporting, monthly for full tree)
• Alert thresholds configured for Primary and Supporting metrics
• Documentation shared with all metric owners

---

Supporting file: mmm-framework.md

Marketing Mix Modeling — Framework & Implementation

What is Marketing Mix Modeling?

Marketing Mix Modeling (MMM) is a statistical technique that quantifies the impact of each marketing channel (and external factors) on business outcomes — typically revenue or conversions. Unlike multi-touch attribution, MMM uses aggregate data (not user-level tracking), making it privacy-compliant by design and capable of measuring offline and non-clickable channels.

When MMM is the Right Approach

---

MMM vs Attribution vs Incrementality

Use together: MMM sets the strategic budget allocation. Attribution optimizes within channels. Incrementality tests validate both.

---

Data Requirements Checklist

Minimum Data Requirements

• Time period: 2+ years of weekly data (104+ data points minimum)
• Dependent variable: Weekly revenue, conversions, or other KPI
• Marketing spend: Weekly spend by channel (at minimum: Paid Search, Paid Social, Display, Email, TV, Radio, OOH, Affiliate — as applicable)
• Impression / GRP data: For channels where spend alone does not capture delivery (especially TV)
• Pricing data: Average selling price or discount depth per week
• Promotion calendar: Dates and types of all promotions (sale events, coupons, bundles)
• Distribution changes: Store openings/closings, new retail partners, website availability changes

Recommended Additional Variables

• Seasonality indicators: Week of year, holiday flags, back-to-school, etc.
• Macroeconomic data: Consumer confidence index, unemployment rate, category trends
• Competitive activity: Competitor spend estimates (SimilarWeb/Pathmatics), competitor promotion flags
• Weather data: Temperature, precipitation (for relevant categories like beverages, apparel, travel)
• PR / earned media: Media mentions, share of voice, viral event flags
• Product launches: Dates of new product introductions
• Platform changes: iOS updates, algorithm changes, cookie deprecation milestones

Data Quality Standards

---

Model Design Guidance

Adstock Transformation

Advertising has a carryover effect — an ad seen this week still influences behavior next week. Adstock models this decay.

Geometric adstock formula:

Adstock_t = Spend_t + decay_rate * Adstock_(t-1)

Diminishing Returns (Saturation)

Each additional dollar spent yields less incremental return. Model this with a Hill function or log transformation.

Hill function:

Response = Spend^alpha / (Spend^alpha + K^alpha)

Where:

• alpha controls the shape of the curve (steepness)
• K is the half-saturation point (spend level at which response reaches 50% of maximum)

Interpretation guide:

---

Result Interpretation Guide

Key Outputs from an MMM

Interpreting the Budget Optimizer

The optimization should equalize marginal ROI across channels. The optimal allocation is where:

• Marginal ROI of Channel A = Marginal ROI of Channel B = ... = Marginal ROI of Channel N

Reallocation decision framework:

Red Flags in MMM Results

• A channel with known poor performance shows high ROI (possible confounding)
• Baseline is > 80% of total (marketing appears to have almost no impact — likely a model issue)
• Recommended reallocation suggests cutting a channel by > 50% (validate with incrementality test first)
• Adstock decay rates seem unreasonable (e.g., paid search decay > 0.8)
• Model R-squared is < 0.8 (significant unexplained variance)
• Out-of-sample MAPE (Mean Absolute Percentage Error) is > 15%

---

Budget Optimization Using MMM

Step-by-Step Process

1. Run the model with current data to establish baseline contribution and ROI by channel
2. Generate saturation curves for every channel to visualize diminishing returns
3. Calculate marginal ROI at current spend levels for every channel
4. Run the optimizer with total budget held constant to find the allocation that maximizes total revenue
5. Apply business constraints (minimum brand spend, contractual obligations, channel minimums)
6. Generate scenarios — Optimize at current budget, +10%, +20%, -10%, -20%
7. Validate key recommendations with incrementality tests before making large shifts
8. Implement gradually — Shift budgets 10-20% per quarter, not all at once
9. Re-run the model after 1-2 quarters with new data to assess impact

Scenario Planning Template

---

Implementation Options

Open-Source Frameworks

Build vs Buy Decision

---

Validation Methodology

In-Sample Validation

• R-squared (adjusted): Should be > 0.85 for a well-fitted model
• Residual analysis: Residuals should be normally distributed with no systematic pattern
• Coefficient signs: All channel coefficients should be positive (marketing should increase revenue)
• VIF (Variance Inflation Factor): Check for multicollinearity; VIF > 5 warrants investigation

Out-of-Sample Validation

• Holdout period: Reserve the most recent 10-15% of data for validation
• MAPE (Mean Absolute Percentage Error): Target < 10%, acceptable < 15%
• Prediction interval coverage: Actual values should fall within the 90% prediction interval ~90% of the time

External Validation

• Incrementality test calibration: Run a geo-lift or holdout test on a key channel and compare the measured lift to the MMM's predicted contribution. If they diverge by > 30%, recalibrate the model.
• Business sense check: Share results with channel managers. If anyone says "this doesn't match what I see operationally," investigate before publishing.
• Cross-model comparison: If possible, run a second modeling approach (e.g., Bayesian + Frequentist) and compare. Convergence increases confidence.

Validation Checklist

• R-squared > 0.85
• MAPE < 15% on holdout data
• All channel coefficients have correct sign (positive)
• No multicollinearity issues (VIF < 5)
• Residuals show no systematic pattern
• Adstock parameters fall within reasonable ranges
• At least one incrementality test corroborates a key MMM finding
• Channel managers have reviewed and stress-tested results
• Saturation curves align with operational intuition
• Budget optimizer recommendations are directionally sensible

---

MMM Program Maintenance

---

Supporting file: privacy-first-measurement.md

Privacy-First Measurement — Cookieless Attribution

The Privacy Landscape

The era of unrestricted cross-site tracking is over. Safari and Firefox have blocked third-party cookies since 2020. Chrome has introduced significant restrictions through the Privacy Sandbox. Regulations like GDPR, CCPA/CPRA, and emerging state and international laws require explicit consent for tracking. Marketers who do not adapt their measurement infrastructure will lose visibility into 40-60% of their customer journey.

What Has Changed

---

Cookieless Attribution Approaches

The New Measurement Stack

The replacement for cookie-based attribution is not a single solution but a combination of approaches.

---

Consent Management Architecture

Consent Management Platform (CMP) Requirements

A CMP is the foundation of privacy-compliant measurement. It must handle:

CMP Tool Options

Consent Mode Implementation

Google Consent Mode v2 allows your tags to adjust behavior based on user consent:

Implementation checklist:

• CMP installed and configured for all applicable jurisdictions
• Google Consent Mode v2 integrated with CMP
• Default consent state set correctly by region (denied for EEA, granted for US unless opted out)
• All Google tags (GA4, Ads, Floodlight) updated to respect consent signals
• Meta Pixel configured to respect consent (via CMP integration or Meta Consent Mode)
• Consent rates monitored and optimized (target > 70% opt-in with compliant UX)
• Server-side backup measurement active for non-consented users

---

Server-Side Tracking Implementation

Meta Conversions API (CAPI)

CAPI sends conversion events from your server directly to Meta, bypassing browser-based pixel limitations.

Architecture:

User converts on your site
    → Your server captures event data
    → Your server sends event to Meta CAPI endpoint
    → Meta matches the event to the user via hashed identifiers
    → Meta uses the event for optimization and reporting

Implementation options:

Data to send via CAPI:

Deduplication: If you run both the browser pixel and CAPI, you must include an event_id in both to prevent double-counting. Use the same unique ID (e.g., order ID) in both the pixel event and the CAPI event.

Google Enhanced Conversions

Enhanced Conversions sends hashed first-party data (email, phone, address) with your Google Ads conversion tags, improving match rates.

Types:

Implementation checklist:

• Accept Google Ads Enhanced Conversions terms
• Identify where user data is captured (checkout, lead form, account creation)
• Configure gtag.js or GTM to capture and hash user data fields (email, phone, name, address)
• Verify Enhanced Conversions in Google Ads diagnostics (check match rate — target > 60%)
• For leads: Set up offline conversion import with GCLID or hashed email matching
• Test with Google Tag Assistant to confirm hashed data is sending correctly

TikTok Events API

---

First-Party Data Strategy

Building a First-Party Data Foundation

First-Party Audience Activation

Match rate optimization:

• Include as many identifiers as possible (email + phone + name + address)
• Clean and standardize data before upload (lowercase, trim whitespace, consistent formatting)
• Update lists regularly (weekly or automated sync via CDP)
• Use double opt-in email to ensure valid addresses
• Enrich data with phone number capture at checkout

---

Data Clean Rooms

What Are Data Clean Rooms?

A data clean room is a secure, privacy-preserving environment where two or more parties can match and analyze their data without either party seeing the other's raw data.

Use Cases

---

Privacy-Preserving Reporting

Aggregated Reporting Standards

GA4 Privacy Configuration

• Data retention set to appropriate period (14 months max, or shorter per policy)
• IP anonymization confirmed (default in GA4)
• Google Signals enabled only if consent is collected
• User-ID tracking implemented only with consent
• Data deletion requests automated via API
• Consent Mode v2 active and verified
• Thresholding understood (GA4 hides rows when sample size is too small)
• BigQuery export configured for raw data analysis (where consent supports it)

---

Privacy Regulation Compliance for Measurement

Compliance Checklist by Regulation

Measurement-Specific Compliance Actions

• Privacy policy updated to disclose all tracking technologies and data sharing with ad platforms
• Data Processing Agreements (DPAs) signed with all analytics and ad platform vendors
• Consent records stored and auditable (which users consented, when, to what)
• Data subject requests (deletion, access) can be fulfilled within 30 days
• Server-side tracking processes only consented data (or aggregated, non-personal data)
• Hashing of PII occurs client-side before transmission to third parties
• Regular privacy audit of all tags, pixels, and server-side connections (quarterly minimum)
• Marketing team trained on privacy requirements relevant to their tools and workflows
• Legal review of any new tracking implementation before deployment

---

Implementation Roadmap

Phase 1: Foundation (Month 1)

• Deploy CMP with geo-based consent rules
• Implement Google Consent Mode v2
• Audit all existing tracking tags for consent compliance
• Enable Meta CAPI (use Shopify native or GTM server-side)
• Enable Google Enhanced Conversions
• Monitor consent rates and optimize banner UX

Phase 2: First-Party Data (Month 2-3)

• Audit first-party data collection points (email, phone, account creation)
• Implement server-side event streaming for key conversions
• Set up first-party audience syncs to major ad platforms (Custom Audiences, Customer Match)
• Deploy deduplication between browser and server-side events
• Verify match rates across all platforms (target > 60%)

Phase 3: Advanced Measurement (Month 3-6)

• Implement or commission Marketing Mix Modeling
• Design and run first incrementality test
• Evaluate data clean room options for cross-platform measurement
• Build privacy-compliant reporting dashboard with modeled conversions
• Establish quarterly measurement accuracy review

Phase 4: Optimization (Ongoing)

• Continuously improve consent rates through UX optimization
• Expand first-party data collection (loyalty program, quizzes, progressive profiling)
• Calibrate MMM with incrementality test results
• Update privacy compliance as new regulations take effect
• Train team quarterly on evolving privacy landscape and measurement approaches
• Document measurement methodology and known limitations for stakeholder transparency

---

Supporting file: reporting-templates.md

Reporting Templates — Weekly, Monthly, Quarterly

Reporting Philosophy

Reports exist to drive decisions, not to display data. Every section of every report should answer one of three questions: What happened? Why did it happen? What should we do about it?

Report Design Principles

---

Weekly Performance Report Template

Purpose: Surface what changed this week, why it matters, and what to do next week. Audience: Marketing team, department leads. Delivery: Every Monday by 10am.

Section 1: Executive Summary (3-5 sentences)

Write a brief narrative covering:

• Overall performance vs. target (on track / off track / ahead)
• The single most important thing that happened this week
• The single most important action for next week

Section 2: Scorecard

Color coding convention:

• Green: > 5% above target
• Yellow: Within 5% of target
• Red: > 5% below target

Section 3: Channel Performance Snapshot

Section 4: Alerts & Anomalies

For each anomaly detected:

1. What: Which metric moved and by how much
2. Why: Root cause (confirmed or hypothesized)
3. So what: Impact if left unaddressed
4. Now what: Recommended action

Section 5: This Week's Tests & Experiments

Section 6: Next Week Priorities

• Priority 1: [Action] — Owner — Due date
• Priority 2: [Action] — Owner — Due date
• Priority 3: [Action] — Owner — Due date

---

Monthly Performance Report Template

Purpose: Full performance review with trend analysis and strategic implications. Audience: Marketing leadership, cross-functional stakeholders, finance. Delivery: By the 5th business day of the following month.

Section 1: Executive Summary

Section 2: Revenue & Conversion Funnel

Stage-by-stage conversion rates:

Section 3: Channel Deep-Dive

For each active channel, report:

Paid Search

• Spend: $X (vs $X budget)
• Revenue attributed: $X
• ROAS: X.Xx
• Top performing campaigns (top 3 by revenue)
• Underperforming campaigns flagged
• Keyword-level insights (new winners, rising CPCs)

Paid Social

• Spend: $X (vs $X budget)
• Revenue attributed: $X
• ROAS: X.Xx
• Creative performance summary (top 3 ads by ROAS, creative fatigue alerts)
• Audience insights (best segments, saturation signals)

SEO / Organic

• Sessions: X (MoM trend)
• Keyword rankings: Movement summary
• Content performance: Top pages by traffic and conversion
• Technical health: Core Web Vitals, crawl errors

Email / SMS

• Revenue: $X
• Revenue as % of total: X%
• List growth: +X net new subscribers
• Campaign performance: Open rate, CTR, revenue per send
• Flow performance: Revenue from automated flows

Referral / Affiliate / Partnerships

• Revenue: $X
• Top referral sources
• Partner performance

Section 4: Cohort & Retention Analysis (if applicable)

Section 5: Budget Reconciliation

Section 6: Experiment Results

Section 7: Next Month Plan

• Top 3 priorities with owners and success criteria
• Budget allocation changes (if any)
• Planned experiments
• Known risks or dependencies

---

Quarterly Business Review (QBR) Template

Purpose: Strategic review connecting marketing performance to business outcomes. Audience: Executive team, board (if applicable). Delivery: Within 10 business days of quarter end.

QBR Structure

1. Quarter Summary (1 slide / section)

   • Revenue vs target, spend vs budget, key efficiency metrics
   • 3 headline wins, 1 headline miss

2. Goal Scorecard (1 slide / section)

   Q[X] Goal	Target	Actual	Status	Commentary
   Revenue	$X	$X	On/Off Track
   New Customers	X	X
   CAC	$X	$X
   LTV:CAC	X:1	X:1
   Brand Metric	X	X

3. Channel Portfolio Review (1 slide per channel)

   • Quarterly performance, trend vs prior quarters, efficiency, saturation signals

4. Customer Insights (1 slide / section)

   • Acquisition channel mix shift, retention trends, segment-level performance

5. Competitive Landscape (1 slide / section)

   • Market share movement, competitor activity, share of voice

6. Experiment Learnings (1 slide / section)

   • All tests run in quarter, results, cumulative impact

7. Next Quarter Strategy (2-3 slides / sections)

   • Goals, budget request, channel strategy, key bets, risk mitigation

8. Appendix

   • Detailed data tables, methodology notes, glossary

---

Campaign Report Template

Purpose: Evaluate a specific campaign's performance against its objectives. Use: Post-campaign (within 5 business days of campaign end).

Campaign Overview

Performance vs Objectives

Creative Performance

Audience Performance

Key Learnings

1. What worked and should be repeated
2. What underperformed and why
3. What should be tested next time

---

Data Visualization Best Practices

Formatting Rules for Executive Dashboards

• No more than 6-8 metrics visible without scrolling
• Every metric has comparison context (vs target, vs prior period)
• Color is used for status, not decoration (red/yellow/green only)
• Titles are insights, not labels ("Revenue up 12% MoM" not "Revenue Chart")
• Filters default to the most common view (last 30 days, all channels)
• Mobile-readable if stakeholders access on phone
• Data refreshes automatically — no manual updates required

---

Stakeholder Formatting Guide

---

Checklist: Before Sending Any Report

• Every metric has comparison context (prior period, target, or benchmark)
• Anomalies are explained, not just flagged
• The executive summary can stand alone without reading the full report
• Action items have owners and deadlines
• Data has been validated against source of truth
• Visualization choices match the message (trend = line, comparison = bar)
• Report was reviewed by at least one other team member
• Sent on schedule (never late — set expectations if data is delayed)