Skip to content
FlowForge Logo FlowForge

FFT-Media-Buyer - Ad Console Operations

Overview

Section titled “Overview”

FFT-Media-Buyer is the execution leaf of FlowForge’s paid-media pair — the industry’s media buyer, the Brazilian gestor de tráfego. It takes the campaign brief authored by fft-paid-media-architect and puts it in motion inside the actual consoles: Meta Ads Manager / Business Manager and Google Ads / YouTube. Account and tracking setup, audience build, campaign→ad-set→ad construction, budget and bid entry, a hard pre-launch QA gate, then the post-launch optimisation loop against the architect’s measurement plan. It never re-authors strategy; evidence that contradicts the brief goes back up as an escalation.

Capabilities

Section titled “Capabilities”
  • Account + asset setup: Business Manager structure, ad accounts, domain verification, Pixel + Conversions API dual setup with event dedup; Google Ads conversion actions, Google Tag/GTM, enhanced conversions, GA4 linking
  • Audience build: Meta custom audiences, lookalikes, retargeting windows, and exclusion hygiene; Google in-market/custom-intent/customer-match and YouTube view-based lists
  • Campaign construction: Meta campaign→ad-set→ad build with the brief’s objective, optimization event, placements, and naming conventions; Google Search ad groups, RSAs, match types, negatives; YouTube for Action builds
  • Budget/bid entry: enters the architect’s budgets and bid strategies exactly — the decimal-place error class is a named enemy
  • Pre-launch QA gate: pixel/CAPI test events verified, every link resolves, UTMs correct, copy proofed, geo/placement/exclusions match the brief, budget double-checked — nothing launches with a failed line
  • Optimisation loop: first-72h learning discipline, daily pacing and CPA checks, kill/scale rules as written in the brief, creative rotation on fatigue evidence, structured escalation when data contradicts the brief
  • Console-truth reporting: spend, delivery, and funnel metrics per stage back to the architect on the brief’s cadence

When to Use

Section titled “When to Use”
  • Routing rule: console build, launch QA, and optimisation work → dispatch fft-media-buyer, always against an existing fft-paid-media-architect campaign brief
  • Setting up tracking (pixel/CAPI, conversion actions) before a campaign launches
  • Building and launching the campaign structure the brief specifies
  • Running the daily optimisation loop and reporting console truth

Do NOT dispatch to decide strategy, offers, budgets, or channel mix — that is fft-paid-media-architect. The buyer escalates deviations; it does not improvise them.

Example Prompts

Section titled “Example Prompts”
"Build the campaign in this brief: Meta ad account + pixel/CAPI verification, audiences with exclusions, campaign→ad-set→ad structure, budgets as specified — then run the full pre-launch QA checklist and report each line."
"Day 6 report: pacing, CPA vs the brief's threshold, CTR and frequency trends, and any kill/scale rules that fired. Flag anything that contradicts the brief as an escalation, not a change."