Multi-channel campaign coordination and optimization
Installation
npx claude-plugins install @gtmagents/gtm-agents/campaign-orchestration
Contents
Folders: agents, commands, skills
Included Skills
This plugin includes 3 skill definitions:
campaign-planning
Use when developing campaign strategy, briefs, KPIs, and workback schedules before execution.
View skill definition
Campaign Planning Skill
When to Use
- Before launching multi-channel GTM efforts.
- When stakeholder alignment on goals, personas, and offers is needed.
- During quarterly planning or major product launches.
Framework
- Set Objectives – tie to revenue/pipeline targets, define primary KPIs.
- Audience & Offers – map personas, stages, ICP tiers, and value propositions.
- Messaging Architecture – craft key narrative, proof points, CTA hierarchy.
- Channel Mix – select channels, budget split, cadence, sequencing logic.
- Workback Plan – create timeline with dependencies, approvals, and resource allocation.
- Risk Assessment – identify blockers (legal, creative bandwidth, data access) and mitigations.
Templates
- Campaign Brief: See
templates/campaign_brief.mdfor goal, audience, and KPIs. - RACI matrix for decision-making.
- Timeline Gantt template with creative/ops milestones.
Tips
- Host a kickoff with every execution lead to walk through the brief and capture risks live.
- Keep KPIs to one primary and two secondary to avoid diffused focus.
- Bake review/QA milestones into the workback to prevent last-minute rework.
- Maintain a single source-of-truth dashboard so partner teams see timing, assets, and blockers.
channel-integration
Use when synchronizing messaging, timing, and measurement across multiple campaign channels.
View skill definition
Channel Integration Skill
When to Use
- Running campaigns that span email, social, paid media, events, web, PR.
- Need to prevent message fatigue or conflicting offers.
- Ensuring consistent tracking/UTM taxonomy across channels.
Framework
- Messaging Matrix – align offer, CTA, creative angle per channel/persona.
- Cadence Alignment – stagger sends/posts to avoid overlap; define quiet periods.
- Asset Repository – maintain single source of truth for approved copy/creative.
- Tracking Consistency – standardize UTMs, naming conventions, analytics tags.
- Feedback Loop – daily standup with channel owners to share insights/risks.
- Escalation Path – define who can approve changes when conflicts arise.
Templates
- Channel calendar template (email, paid, social, events, partner).
- UTM builder/validation sheet.
- Real-time channel status dashboard (Ready, QA, Live, Blocked).
- Message/source-of-truth sheet mapping audience × channel × CTA.
Tips
- Use a common taxonomy for statuses (Draft, QA, Scheduled, Live) so every team reads the board the same way.
- Hold 15-minute syncs during peak launch weeks, async updates otherwise.
- Automate delivery of performance snapshots back to planners so adjustments happen fast.
- Designate a single owner for conflict resolution to avoid channel tug-of-war.
performance-tracking
Use when establishing measurement frameworks, dashboards, and optimization rhythms for live campaigns.
View skill definition
Performance Tracking Skill
When to Use
- Before launch to define metrics, data sources, and reporting cadence.
- During active campaigns to monitor pacing vs goals and trigger optimizations.
- Post-campaign retros to capture learnings and benchmarks.
Framework
- Metric Hierarchy – define business (pipeline, revenue), leading (MQL, CTR), and diagnostic metrics (CPC, landing page CVR).
- Data Plumbing – map sources (ad platforms, MA, CRM, BI) and ensure consistent IDs/UTMs.
- Dashboard Build – create executive + operator views with automated refresh.
- Alerting – set thresholds for spend pacing, CPA, conversion drops, SLAs.
- Insight Cadence – daily standups, weekly deep dives, end-of-campaign retros.
- Documentation – record hypotheses, experiments, and outcomes.
Templates
- KPI tree worksheet.
- Dashboard spec (dataset, visualization, owner, refresh schedule).
- Optimization log (date, insight, action, result).
Tips
- Automate alert routing (Slack, email) so anomalies are actioned quickly.
- Pair dashboards with narrative summaries to help execs interpret shifts.
- Capture experiment context in the optimization log to prevent repeating failed tests.
- Align BI/RevOps early so new metrics get logged before launch.