Facebook Media Buyer
Facebook Media Buyer VA: Meta ads operations support delivers campaign execution for Facebook Ads and Instagram Ads inside Meta Ads Manager. This role runs the operational layer: build, QA, pacing checks, signal monitoring, test logging, and weekly reporting. You own strategy, budgets, and approvals.
Core outputs
- Campaign build + QA inside Business Manager and Ads Manager
- Measurement readiness checks: Pixel, CAPI, domain verification, AEM event priority
- Attribution clarity: 7-day click / 1-day view reporting views and consistent comparisons
- Delivery signal monitoring: Learning Phase resets, auction overlap, frequency pressure
- Creative test ops: naming metadata, sandbox tests, iteration queue
- Policy and brand safety: disapproval triage, claim-safe copy routing, escalation notes
What this role is
A paid social operations assistant runs Meta execution under your direction.
The assistant builds assets, verifies signals, monitors delivery health, logs changes, and prepares decision-ready reports.
The owner approves claims, budgets, offers, and major pivots.
Ready to talk?
Technical scope inside the Meta ecosystem
1) Build system and metadata
Campaign taxonomy creates clean reporting and reduces data ambiguity.
Naming metadata encodes offer, audience, creative concept, format, and test ID.
UTM structure enables cross-tool matching in GA4, Looker Studio, and CRM views.
2) Measurement and signal integrity
Pixel events define on-site conversion actions.
Conversions API (CAPI) improves event matching and stabilizes measurement under iOS constraints.
Aggregated Event Measurement (AEM) defines event priority for iOS traffic.
Domain verification enforces event configuration control.
3) Delivery and learning mechanics
Learning Phase defines early delivery volatility.
Learning resets signal instability from edits, budget jumps, or audience shifts.
Auction overlap increases cost by competing against your own ad sets.
Frequency and creative decay reduce incremental performance over time.
4) Formats and sub-entities that affect outcomes
Advantage+ Shopping Campaigns support automated shopping delivery for eligible catalogs.
Catalog Sales (DPA) uses product sets and feed rules for dynamic retargeting.
Instant Experience improves mobile engagement flows for certain offers.
Reel placements change creative constraints and attention patterns.
Lead Ads change funnel ownership and require CRM routing discipline.
Responsibilities
Ad operations and build execution
Ads Manager execution includes campaign creation, ad set configuration, and ad assembly.
Placement configuration aligns to creative formats across Feed, Stories, and Reels.
Advantage+ usage follows your rules for automation boundaries and exclusions.
Catalog configuration support covers product set mapping and DPA structure (feed ownership stays with your team if required).
Signal and tracking verification
Event verification confirms Pixel and CAPI firing before spend scales.
Event prioritization checks confirm AEM ordering and domain verification status.
Attribution window consistency enforces 7-day click / 1-day view comparisons for stable reporting.
Monitoring and issue triage
Daily pacing audits prevent budget over-exhaustion and spend drift.
Delivery audits identify learning resets, unstable CPM swings, and placement breakdown anomalies.
Disapproval triage captures policy reason codes and routes fix options for approval.
Risk notes document brand safety threats and escalation triggers.
Reporting and audit trail
Optimization audit trail records edits, approvals, and timestamps.
Test ledger records hypothesis, variant, audience, result, and next action.
Weekly reporting produces a decisions-needed list tied to evidence, not opinions.
Workflow with data flow logic
Step 1: Intake → control rules
Owner inputs define offer, claims guide, budget ceilings, target customer, exclusions, and approval rules.
Assistant outputs include a campaign map, taxonomy, and reporting baseline.
Step 2: Measurement readiness → valid signals
Signal checks validate Pixel, CAPI, AEM ordering, and domain verification.
Valid signals prevent false negatives inside attribution and conversion reporting.
Step 3: Build + QA → stable launch
Build QA verifies placements, URLs, UTMs, creative specs, and policy-sensitive claims.
QA completion prevents learning resets caused by immediate hotfix edits.
Step 4: Learning monitoring → delivery stability
Learning monitoring tracks volatility, frequency growth, overlap, and spend pacing.
Stability signals trigger controlled iteration instead of random edits.
Step 5: Iteration loop → controlled optimization
Iteration loop runs through test queue, creative refresh, and audience hygiene.
Audit trail preserves causality between edits and outcomes.
30 to 60 day deliverables
Day 1 to 14
- Taxonomy and metadata system for campaigns, ad sets, and ads
- Measurement checklist: Pixel, CAPI, AEM priority, domain verification
- Reporting template with attribution window standardization
Day 30 to 60
- Operating SOP for launches, edits, pauses, and escalation thresholds
- Creative test library: hooks, formats, claims boundaries, refresh cadence
- Optimization audit trail with clean change history
- Risk patterns report: disapprovals, overlap, fatigue, tracking gaps
Ownership split
Owner scope
- Offer strategy, landing page claims, budget ceilings, targeting direction
- Approval authority for creative, copy, and major structural edits
Assistant scope
- Build execution, QA, monitoring, documentation, reporting
- Escalation routing with evidence: screenshots, reason codes, diffs, logs
Access and safety controls
Required
- Meta Business Manager access (role-based permissions)
- Ad account access
- Events Manager access (or collaboration with tracking owner)
- Brand claims guide and approval workflow
Recommended
- GA4 view access for UTM validation
- CRM routing map for Lead Ads (fields, consent, handoff rules)
- Shared tracker for tests and approvals
Paid advertising
Increase reach
Target audience
Social media channels
Frequently Asked Questions
iOS signal loss handling uses CAPI validation and AEM prioritization to stabilize conversion tracking under iOS constraints. iOS attribution windows use 7-day click and 1-day view to keep reporting comparable.
Advantage+ Shopping runs when catalog eligibility and offer fit exist. Manual campaign structures run when control, exclusions, or segmentation rules dominate.
Learning phase reset prevention uses edit discipline, QA gates before launch, and change batching. Learning phase stability improves because frequent micro-edits stop.
Ad disapproval handling captures reason codes, applies fixes that match the claims guide, and relaunches only after approval. Policy risk control uses documented claim rules and pre-launch QA.
Weekly reporting includes spend pacing, delivery health, attribution view, top creatives, placement breakdown notes, test outcomes, and a decisions-needed list.
Day-to-day assistant management uses one owner for priorities and approvals. Marketing lead or founder ownership keeps decisions fast and prevents workflow drift.