Ad Ops Headaches: Common Complaints on Both Sides of the Auction
Ad ops headaches on the sell-side and the buy-side are not two careers with two playbooks. They are two lists of common complaints that meet at the same auction. Revenue moved. Two systems disagree. Coverage depends on who is online. The IO and the trafficking do not match. Creative never cleared and everyone called it underdelivery. This guide maps those complaints and what to try first - from someone who has lived in that operational layer for 19+ years.
The morning usually starts the same way. A number moved. Someone asks why. The wrong tool gets blamed first - a chat assistant when you needed a cause tree, a partner ticket when the clocks never matched, a bid bump when the creative was blocked. The work is not "care harder." The work is name the complaint, then run the checks that actually shrink it.
Whether you sit on a publisher stack, a retail media network, or an agency / advertiser campaign desk, the patterns below should feel familiar. Use this page as a map: find the headache that matches your morning, then dig into the deeper piece when it is live.
Same job, two complaint lists
Sell-side mornings usually sound like: fill, floors, partner numbers, weekend coverage, and "why did yesterday move." Buy-side mornings usually sound like: IO fidelity, trafficking, creative clearance, invoice fights, and "why is delivery behind when the DSP looks fine."
Both sides share three bad habits:
Treating a dashboard symptom as a root cause
Skipping definition and clock alignment before blaming a partner
Solving a process problem with another export nobody will open
You do not need the same product for every complaint. A publisher who needs yesterday's exceptions ranked before the stand-up has a different path than a buyer who needs process clarity and a second set of eyes. What you do need is the right name for the headache, so the next hour is not spent arguing about the wrong one.
Sell-side headaches
If you run a publisher or retail media ad server stack, start here. Each item is a complaint you have probably said out loud - plus the first move that usually helps.
Yesterday's revenue dropped and nobody can agree why. Do not escalate until you have ranked the cause classes: inventory, auction / yield, creative or policy, partner delivery, and reporting definitions. Guessing in Slack is not triage.
Publisher and partner numbers never match. Align definitions and clocks before you write the accusation email. Most "discrepancy" fights are two teams measuring different things and pretending they are the same report.
Coverage depends on who is in the office. If the only alert is whoever opened a report that morning, you do not have coverage. You have hope. Build a daily exception list that survives vacation and weekends.
Direct and programmatic are two jobs on one team. Name the dual-job failure mode before you hire or buy another tool. When the same people own IOs, trafficking, floors, and partner escalations, something always drops - usually the thing that looked "fine" in the dashboard.
Setup and naming drift quietly break reporting. Standards feel like bureaucracy until rollups stop rolling up. Line-item names, key-values, and order conventions are how you keep next quarter's analysis from becoming archaeology.
Auction and floor talk moves faster than the team can document. Headlines change weekly. Your checklist should not. Focus on what actually changes in daily work: which reports, which owners, which decisions you re-check when the market noise gets loud.
Buy-side headaches
If you live in agency or advertiser campaign ops, these are the ones that burn hours before the first useful impression.
Trafficking vs the IO. Spend can look "live" while nothing is delivering because the insertion does not match what was bought. Fix the map between the IO and the trafficking before you chase pacing.
Buyer and publisher numbers never match. Build a three-way definition sheet (buyer, seller, verification) before finance owns the fight. The invoice argument is almost always a definition argument that started weeks earlier.
Creative and policy rejects that look like underdelivery. Clearance problems wear a pacing costume. Check creative status and policy before you bump bids or blame inventory.
The deal type you bought is not the ops headache you planned for. Programmatic guaranteed, preferred, and buyer-direct each ship with a different ops load. Know which one you actually signed up to run - not which one the pitch deck named.
Screenshots and Slack are the system of record. If hand-offs between trading, trafficking, and finance live in chat threads, you will lose context every time someone is out. A short packet beats another "can you resend that screenshot."
Handovers that say "the usual." Coverage fails when the person who knows the stack is out and the notes say nothing useful. Write the handover for the person who was not in the last three stand-ups.
Which headache matches your morning
How to use this guide
Treat this page as the index for a growing set of deep-dives. Each headache above will get its own article with a direct answer up front, a short checklist, and an FAQ you can hand to a teammate who was not in the last stand-up.
You do not need to read every section. Match the complaint to your morning, run the first checks listed here, and come back for the longer piece when you want the full walkthrough. Platform names will show up in those deep-dives when they clarify the problem - they are not required for this map to be useful.
What to do next
If you are on the publisher side and the real gap is yesterday's exceptions before the stand-up, ProOps Ads Tracker is a read-only Chrome sidepanel daily coordinator for Google Ad Manager - $249/month per network, 3 seats included, extra seats $49, with a 30-day trial and no credit card. Get started here.
If you are buy-side, hybrid, or the headache is bigger than one report, book a consulting call. Most of the value after 19 years in this layer is naming the complaint correctly before anyone buys another tool.
Frequently Asked Questions
What are the most common ad ops headaches?
On the sell-side: unexplained revenue drops, partner discrepancy, thin coverage, dual direct/programmatic ownership, naming drift, and auction or floor noise that outruns documentation. On the buy-side: trafficking that does not match the IO, discrepancy fights, creative or policy rejects that look like underdelivery, deal-type surprises, Slack as the system of record, and weak handovers.
Do sell-side and buy-side ad ops face different problems?
The tools differ, but the pattern is the same: a number moves, two systems disagree, and the team escalates before definitions and clocks are aligned. Sell-side work leans inventory, yield, and partner delivery. Buy-side work leans IO fidelity, trafficking, creative clearance, and finance hand-offs.
Is this guide only for Google Ad Manager publishers?
No. It is written for ad ops professionals across the auction - publishers, retail media networks, and agency or advertiser campaign ops. Specific platforms show up when they clarify a complaint, not as the topic of every section.
What should I check first when yesterday's revenue dropped?
Rank cause classes before you escalate: inventory, auction / yield, creative or policy, partner delivery, and reporting definitions. Do not start with a bid change or a partner email until you know which class you are in.
When is a product the right next step vs a consulting conversation?
If the gap is daily publisher monitoring and coverage that survives weekends, a daily coordinator can help. If the headache is buy-side process, deal design, or a stack that needs a second set of eyes, start with a consulting conversation - not another dashboard.
Who wrote this?
Chris Quinn, founder of ProOps Consulting, with 19+ years in the ad ops operational layer across publisher and campaign work.