Platform Comparisons
Part of Ad servers and creative delivery
Comparing advertiser and publisher ad servers
Compare who selects the placement, who delivers creative and how to assign tagging and reporting responsibilities.
The difference is whose decision each server makes. A publisher ad server manages a placement and selects an eligible ad source. An advertiser ad server may then select or deliver the advertiser’s ad and record advertiser-side activity. Both can choose a creative, but at different stages.
Compare the responsibilities
| Decision | Publisher ad server | Advertiser ad server |
|---|---|---|
| Inventory | Manages the publisher’s ad units and booked delivery | Works with placements agreed for the advertiser’s campaign |
| Selection | Chooses an eligible line item or demand source for a request | Chooses an eligible ad and assigned creative for its placement tag |
| Creative | Hosts content or returns code that calls another system | Hosts, rotates or redirects advertiser creative |
| Reporting | Records publisher-side delivery under its rules | Records advertiser-side activity under its rules |
Google Ad Manager illustrates the publisher role. Campaign Manager 360 illustrates the advertiser role. Other products can combine these functions differently.
Decide whether two servers are needed
In a direct display booking, the publisher can select its booked line item and return an advertiser tag. The advertiser’s server can then choose an eligible ad and creative. That second choice does not replace the publisher’s fill decision.
For Google Ad Manager and Campaign Manager 360, the documentation covers trafficking Campaign Manager 360 tags that use internal redirects. Confirm the exported tag and the publisher’s intended creative type; ‘redirect’ alone is not enough to identify the implementation.
A separate advertiser server is not required for every campaign. Establish where the asset lives, who can replace it and what each system will report.
Key Implementation Notes for Google Ad Manager & Campaign Manager 360
- Direct Booking FlowPublisher selects line item → returns advertiser tag → Advertiser server chooses ad/creative
- Tag Type Requirement‘Redirect’ alone is not sufficient to identify implementation — verify exported tag and creative type
- Server NecessityA separate advertiser server is not required for every campaign
- Asset OwnershipEstablish where the asset lives, who can replace it, and what each system reports
Assign the work before booking
Agree who controls the ad unit, size, dates and booked priority; who may rotate or replace a creative; who inserts required macros; and who investigates a publisher selection with no later advertiser-side delivery. Specify which report governs any commercial count and how a material difference will be examined.
Ask for the proposed trafficking setup and sample report. A provider feature list cannot establish an account’s permissions, a publisher’s implementation or the terms of a particular booking.
