---
title: Marketing Router
category: product
entity_type: skill
price: $15
canonical: https://forgehouse.ai/skills/marketing-router/
lang: en
hreflang_alt: https://forgehouse.ai/tr/skiller/marketing-router/
last_updated: 2026-06-20
---

# Marketing Router

> Marketing pod orkestrasyon skill'i.

A central orchestration layer that reads your marketing request, matches keywords to the right specialist pod, and dispatches work to the correct skill and agent. It coordinates multi-step campaigns across seven domains so the right capability runs at the right time, in the right order, with no duplicated effort.

## Use cases
- Deciding which marketing skill handles an incoming request
- Coordinating a landing page plus ad campaign across copy, conversion, and channels
- Routing blog work through content then SEO review
- Sequencing tracking setup before launching paid campaigns
- Resolving ambiguous requests that touch more than one marketing area
- Orchestrating a full new-product go-to-market across multiple teams

## Benefits
- Stop guessing which tool to use: requests land on the right specialist instantly
- Eliminate rework from wrong handoffs and out-of-order steps
- Run multi-domain campaigns first-time-right with built-in cross-domain coordination
- Free your team from manual triage so they execute instead of routing

## What’s included
- Seven-pod model covering content, SEO, conversion, channels, growth, intelligence, and sales
- Keyword-to-pod matching table with priority rules for ambiguous requests
- Four operating modes: single sprint, deep-dive, multi-pod handoff, and dependency chain
- Mandatory cross-pod coordination rules (content×SEO, conversion×channels, tracking-before-ads)
- Deterministic output format naming pod, skill, agent, and required coordination
- Action-verb disambiguation logic for requests matching multiple domains

## Who it’s for
Marketing teams, agencies, and operators who run multi-channel campaigns and need a reliable way to route work to the right specialist every time.

## How it runs
Routing is settled before any work starts: keywords map to seven pods, action verbs break the ties, and mandatory pairs like content-plus-SEO-review cannot be skipped. The router dispatches; named agents execute.
1. Matches the request keywords against the 7-pod table covering 32 skills: CONTENT, SEO, CRO, CHANNELS, GROWTH, INTELLIGENCE and SALES, each pod owned by a named specialist agent.
2. When a keyword fits more than one pod, reads the action verb to break the tie: write or create routes to CONTENT, optimize or improve to CRO, analyze or compare to INTELLIGENCE, set up or integrate to GROWTH or CHANNELS. Still ambiguous means the user is offered the pod choice explicitly.
3. Picks the working mode: Solo Sprint for single-pod tasks (about 80 percent of requests), Domain Deep-Dive for multiple skills inside one pod, Multi-Pod Handoff for coordinated cross-pod work, Skill Chain when one skill's output is the next skill's input and the order cannot flip.
4. Enforces the mandatory coordination pairs: content production always gets an SEO review, landing page CRO is done in the context of its ad traffic for message match, and tracking setup must complete before any ad campaign launches. Trigger combos like "landing page plus ads" auto-activate the handoff.
5. Emits the dispatch ticket in a fixed format: POD, SKILL, AGENT, MODE, CROSS-POD coordination, written as an ordered chain when multiple pods are involved.
6. Never executes the work itself. The named agent does, and pod outputs are measured downstream (traffic for content, conversion rate for CRO) so monthly routing retrospectives recalibrate which pod handles which task type best.

## FAQ
### I am a solo marketer, not an agency. Is an orchestration layer overkill?
It earns its keep when requests cross domains, which happens solo too: a landing page touches copy, conversion, and channels at once. If your work genuinely lives in one pod, say content only, you would use the router rarely; its value scales with how often tasks span two or more areas.

### What happens with an ambiguous request, like 'improve our blog conversion'?
That is what the priority rules and action-verb disambiguation handle: the request is matched against the keyword-to-pod table, and when it touches multiple pods the router picks one of four operating modes, from single sprint to dependency chain. Cross-pod rules like tracking-before-ads enforce the order.

### Does the router do the marketing work itself?
No. It decides who works, in what order, and with what coordination, then names the pod, skill, and agent in a deterministic output. The actual copywriting, SEO review, or campaign setup happens in the specialist skills it dispatches to.

## Price
$15, one-time, no subscription. VAT included.

Related guide: [AI Google Ads and Meta Ads management](https://forgehouse.ai/guides/ai-google-ads-management/)