mcpField
C
campaign-architecture

campaign-architecture

github.com/gtmagentsMarketing & growth42868 installsUpdated 30w ago
Repository

About campaign-architecture

campaign-architecture is a marketing skill for structuring cross-platform campaigns and planning tests. It organizes objectives, audiences, budgets, signals, and funnel stages into a campaign framework.

Key features

  1. 01Align campaign goals with business KPIs
  2. 02Structure campaign, audience, and creative tests
  3. 03Plan CBO and ABO budgets
  4. 04Check conversion signal volume
  5. 05Map funnel lifecycle coverage
  6. 06Use naming and test templates

Use cases

  1. 01Designing campaigns across multiple platforms
  2. 02Reorganizing accounts with overlapping audiences
  3. 03Planning tests across audience, creative, and bidding
  4. 04Reviewing funnel coverage by channel and message

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill campaign-architecture

After installing, type/campaign-architecturein Claude Code to confirm it loaded.

Details

From the project README

Campaign Architecture Patterns Skill

When to Use

  • Designing new campaigns across multiple platforms.
  • Reorganizing accounts bloated with overlapping audiences or learning-phase resets.
  • Planning test cells to isolate variables (audience, creative, bidding).

Framework

  1. Objective Alignment – match campaign objective to business KPIs + conversion events.
  2. Hierarchical Testing – campaign = goal, ad set = audience/bid, ad = creative variant.
  3. Budget Strategy – CBO vs ABO, pacing guardrails, flighting.
  4. Signal Quality – ensure each ad set receives enough conversions/week.
  5. Lifecycle Coverage – separate prospecting, retargeting, and customer expansion streams.

Templates

  • Naming convention guide (Channel_CampaignGoal_Audience_TestID).
  • Funnel coverage matrix (stage vs channel vs messaging).
  • Test design brief (variable, hypothesis, metric, sample size, duration).

Tips

  • Limit active tests to preserve learning phase stability.
  • Centralize exclusions (existing customers, employees, low-LTV segments).
  • Archive underperforming structures monthly to maintain account health.

Comments

Markdown supported