A trafficker is the person who takes a media buy that has already been agreed and makes it deliver. Sales closes the deal, planning decides where the money goes, and the trafficker builds the campaign inside an ad server: placements are created, creative files are uploaded, ads are assembled from the two, targeting and flight dates are set, tags are generated and sent to the publisher, and delivery is monitored until the flight ends. The role exists because a signed insertion order is a commercial document, not a machine instruction. Something has to translate one into the other, and until recently that something was always a person.

The word is inherited from broadcast. In radio and television, the traffic department sits between sales and the transmission chain, taking orders from sales, placing commercials into available breaks, and generating the daily log that defines what airs and when. After transmission an as-run report is reconciled against that log to determine what actually ran, and the reconciled record goes to accounting for billing. Digital kept the vocabulary and the function while replacing the log with an ad server database.

The buy-side workflow

On the advertiser side the canonical implementation is Campaign Manager 360, Google's third-party ad server, whose documentation names the role directly. According to the Campaign Manager 360 Help Center, the trafficker sets up creatives in ads, assigns those ads to placements, then generates tags, tests them, and sends them to publishers.

The hierarchy is narrower than it looks. An advertiser holds campaigns; a campaign holds placements, which represent the media buy on a given site; creatives hold the actual files; and an ad is the object that links a creative to a placement. Google's own developer documentation describes the ad in the simplest case as a one-to-one relationship between a creative and a placement, with rotations expressed as one ad carrying several creatives. Four ad types exist: standard ads deliver creatives, default ads serve when nothing else is eligible, tracking ads count impressions and clicks on inventory delivered elsewhere, and click trackers count clicks on hard-coded elements.

The failure modes are built into the same structure. Creative status in Campaign Manager 360 is global to the advertiser, so deactivating a file stops it serving in every ad it is assigned to, across campaigns; suppressing a single creative within one ad requires setting its rotation flag to no instead. Assigning several creatives directly to a placement causes the system to create several ads automatically rather than one rotating ad. Deactivating every ad on a live placement leaves the publisher with an empty slot. None of these are edge cases; all are ordinary trafficking errors.

Volume forces the work out of the interface. Campaign Manager 360 paginates lists in blocks of 100 rows, offers keyboard navigation for selecting and opening records, and supports importing and exporting an entire campaign as a spreadsheet, which is how large flights are actually built and amended. The same objects are exposed programmatically, and Google's developer documentation for the Trafficking API enumerates the resource set a trafficker manipulates: accounts, sites, advertisers, Floodlight configurations, activities, landing pages, campaigns, placements, ads, creatives and creative assets. Anything running at scale is built through the bulk path, not by clicking.

Video adds its own constraints. In-stream creatives are transcoded into multiple renditions, and the transcode set is controlled at placement level because some publishers accept only specific file types. Cookieless environments such as connected televisions accept VAST tags but will return blank responses to ads relying on cookie-based targeting, so Google's guidance is that every such placement carry at least one untargeted ad as a fallback. The files themselves are checked against format guidelines, and IAB Tech Lab opened a revised set of digital video and CTV specifications for public comment in December 2025, setting 1920 by 1080 as the standard fullscreen creative size.

The sell-side workflow

Publisher-side trafficking uses different objects and a different logic. In Google Ad Manager the container is the order, which carries the advertiser and the commercial agreement, and beneath it sit line items carrying pricing, targeting, creatives and delivery goals. The two hierarchies diverge at every level, with the buy side running campaigns, insertion orders and line items while the sell side runs orders and line items.

What distinguishes the sell-side job is priority. Ad Manager assigns each line item type a numeric priority, and lower numbers win: Sponsorship is priority 4, Standard splits into 6, 8 and 10, Network, Bulk and Price Priority all sit at 12, and House is 16. Sponsorship and Standard are guaranteed and are the only types included in forecasts, because non-guaranteed demand can be superseded without breaching anything. Within the same priority, remnant line items are ranked by CPM or by an assigned value CPM. A Price Priority line item with no rate and no value CPM is treated as House, which means a mis-keyed price silently demotes a paying deal to the bottom of the stack. Google's decision to impose account-level caps on line item counts, announced in January 2023, constrained how far publishers could push this structure.

Those objects are now machine-addressable. The Ad Context Protocol maps its packages onto Google Ad Manager orders and line items, and onto campaigns and flights in Kevel, letting an automated buyer address them without knowing which ad server sits behind.

Header bidding turned line items into a data problem. Prebid rounds returned bids into price buckets, and each bucket needs a corresponding line item in the ad server, which is why publishers running fine granularity maintain thousands of near-identical line items whose only purpose is to represent a price. Debugging that configuration remains manual work concentrated in a handful of specialists at each publisher.

Where the numbers stop agreeing

Buyer and seller almost never count the same impressions, because they count at different moments in the same delivery. The commercial handling of that gap is written into the 4A's/IAB Standard Terms and Conditions for Internet Advertising Version 3.0, finalized on February 22, 2010 and the first revision since 2002. The document nominates a Controlling Measurement and provides that where the difference exceeds 10% over an invoice period and the controlling number is the lower one, the parties facilitate a reconciliation effort. Where reconciliation fails, the agency may demand a makegood measured by the third-party ad server or pay on its own server's figures plus a 10% upward adjustment.

Reconciling that gap is trafficker work, and the asymmetry is not neutral: the buyer's ad server is normally the server of record, so the publisher starts from the weaker position and absorbs most of the cost of investigating. IAB's own 2013 study of mobile discrepancies found practitioners treating 10% to 20% as acceptable in that environment.

Why the role is under pressure

The strain is now measured. Fluency's 2026 Agency AdOps Benchmark Report, drawn from more than 170 United States agencies and in-house teams, found 71% of ad operations teams saying manual processes were putting client campaigns at risk, with 87% still pacing budgets by hand, average strategist workloads of 33 client accounts, and 39.75 hours per strategist each month spent on routine optimization and pacing. The prior year's edition recorded agencies seeking to lift portfolios from 35 to 64 accounts per strategist without adding headcount, and 46 hours a month on manual campaign changes. These are vendor-sponsored figures published by an automation supplier, and should be read as such.

The other direction of travel is outsourcing. Raptive launched Apex in July 2026, pairing its monetization stack with specialists working alongside publisher staff on ad operations, on the argument that in-house stacks built over the previous decade had become an operational burden.

Accuracy has also become a purchasable metric. Politico said in January 2025 that it had reached a trafficking accuracy rate of 99.6% using GeoEdge's SpecHub, eliminating external trafficking errors over six months. The figure is publisher-reported and vendor-promoted, but the framing is notable: trafficking error had become a number a media owner would publish.

Disambiguation

Media buyer or planner negotiates and allocates the spend. The trafficker implements what was bought and does not decide it.

Yield manager optimizes what unsold inventory earns, working on floors, demand partners and auction configuration rather than on the mechanics of a booked campaign.

Campaign Manager 360 is a Google product name, not a job title, and the Trafficking component inside it is where the work happens.

Trafficker in general English overwhelmingly means someone dealing in illicit goods or people. The advertising sense is a term of art confined to the industry, which is one reason job listings increasingly prefer ad operations specialist or campaign manager.

Recent developments

Automation has moved from bulk-edit tooling to systems that hold write access, and the industry has not settled on how much. Adform shipped 29 read-only skills for its FLOW demand-side platform in July 2026, with the read-only limitation stated repeatedly as a design choice; its taxonomy skill infers what a human trafficker originally meant from a malformed campaign name. Fluency said on August 11, 2026 that it reserves execution rights over live budgets to deterministic agents alone across $3 billion in managed spend. Two days later, Kochava added StationOne workspaces for Google, Meta, Reddit, Snap and TikTok covering campaign build and launch, bulk changes and creative operations, without disclosing write scope.

The tooling underneath is shifting too. The Campaign Manager 360 API gained a synchronous reporting endpoint on August 12, 2026, collapsing a four-step retrieval into one request, alongside a documentation change making conversion categories mandatory on Floodlight activities with attribution enabled.

Timeline

  • 1990s and earlier: broadcast traffic departments build daily logs and reconcile as-run reports against sales orders
  • End of 1996: DoubleClick launches DART, offering centralized ad serving and reporting to sites beyond its own network
  • October 1998: DoubleClick introduces DART for Advertisers, establishing the third-party ad server as a distinct product category
  • 2002: 4A's/IAB Standard Terms and Conditions Version 2.0 published
  • March 11, 2008: Google completes its $3.1 billion acquisition of DoubleClick
  • February 22, 2010: Version 3.0 of the Standard Terms and Conditions finalized, formalizing the 10% discrepancy threshold and the Controlling Measurement concept
  • September 2013: IAB publishes its study of common root causes of mobile ad discrepancies
  • June 2018: Google retires the DoubleClick brand, with DART for Advertisers becoming Campaign Manager 360 and DoubleClick for Publishers becoming Google Ad Manager
  • January 2023: Google introduces account-level limits on Google Ad Manager line items
  • July 2024: IAB Tech Lab publishes the VAST CTV Addendum, retrofitting registered ad identifiers into older VAST implementations
  • December 11, 2025: IAB Tech Lab opens revised digital video and CTV ad format guidelines for public comment
  • March 23, 2026: Fluency reports 71% of ad operations teams saying manual work puts campaigns at risk
  • August 12, 2026: Campaign Manager 360 API adds a synchronous reporting endpoint

Summary

Who: Traffickers, also titled ad operations specialists or campaign managers, working inside agencies, brand in-house teams, publishers and outsourced operations providers, alongside the sales, planning and yield colleagues whose decisions they implement.

What: The configuration of a booked media buy inside an ad server, covering placements, creatives, ads or line items, targeting, flight dates, priority, tag generation, quality assurance, delivery monitoring and discrepancy reconciliation.

When: The function transferred from broadcast traffic departments into digital with the arrival of ad servers in the mid-1990s, and has been progressively automated since, with the write-access question actively contested through 2026.

Where: Inside third-party ad servers such as Campaign Manager 360 on the buy side and publisher ad servers such as Google Ad Manager on the sell side, plus the demand-side and supply-side platforms adjacent to them.

Why: Contracts do not execute themselves. Between a signed insertion order and a served impression sits a set of configuration decisions where a single wrong field stops delivery, misprices inventory or produces an unbillable campaign, and the industry is currently deciding how much of that judgment can be handed to software.