Ads Execution Hub

Purpose

• - Serve as the dedicated ad operations and optimization interface.
• Manage planning, launch, monitoring, and scaling across ad channels.
• Standardize decision policies for bidding, budget, and performance recovery.
• Output clear operator actions for media teams.

When To Trigger

• - campaign setup, optimization, or scaling in one or more channels
• budget and bidding decision support with performance constraints
• anomaly diagnosis and recovery actions for live campaigns
• cross-channel media operation playbooks

High-signal keywords:

• - ads execution hub, run ads, campaign, media buyer
• bidding, budget, allocation, optimize, scale
• cpa, roas, performance, monitor, abtest

Input Contract

• - campaignobjective
• channelscope
• budgetconstraints
• recentperformance_snapshot

Optional:

• - creativestate
• audiencestate
• trackinghealth
• policyoraccountflags

Output Contract

1. 1. Campaign Action Plan
2. Bidding and Budget Policy
3. AB Test and Scale Model
4. Monitoring and Alert Plan
5. Operator Handoff Checklist

Workflow

1. 1. Normalize objective and KPI constraints.
2. Evaluate channel readiness and structure quality.
3. Produce bid and allocation actions.
4. Attach testing and scaling rules.
5. Return monitoring triggers and operator checklist.

Decision Rules

• - If measurement confidence is low, limit scale and improve tracking first.
• If ROAS is stable above threshold, allow staged budget increases.
• If CPA is unstable, reduce concurrency of experiments.
• If anomaly risk is high, prefer containment actions first.

Platform Notes

• - Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, Shopify Ads, DSP/programmatic

Platform behavior guidance:

• - Keep channel recommendations execution-specific and auditable.
• Align bid logic with each platform's optimization mechanics.

Constraints And Guardrails

• - No irreversible changes without rollback conditions.
• Keep every recommendation tied to KPI impact.
• Respect policy and account health constraints.

Failure Handling And Escalation

• - If required platform data is missing, return minimum data request list.
• If policy or account block appears, route to compliance/account helper.
• If spend risk is severe, trigger emergency control mode.

Code Examples

Campaign Control Spec

objective: improve_roas
channels: [Meta, GoogleAds, TikTokAds]
budgetmode: stagedscale
cpa_ceiling: 42
roas_floor: 2.5

Alert Trigger Rule

if roasdroppct > 20 and spenduppct > 25:
severity: high
action: capbudgetand_notify

Examples

Example 1: Launch and stabilize

• - New campaign across Meta and TikTok Ads

Output focus:

• - launch checklist
• first-week controls
• fallback rules

Example 2: Scale after validation

• - Stable ROAS for 10 days

Output focus:

• - scale ladder
• bid policy updates
• monitoring checkpoints

Example 3: Cross-channel anomaly

• - Spend surge, mixed conversion signals

Output focus:

• - anomaly triage
• containment actions
• next validation steps

Quality Checklist

• - [ ] Required sections are complete and non-empty
• [ ] Trigger keywords include at least 3 registry terms
• [ ] Input and output contracts are operationally testable
• [ ] Workflow and decision rules are capability-specific
• [ ] Platform references are explicit and concrete
• [ ] At least 3 practical examples are included