Supply Chain
Ad servers and creative delivery
Understand publisher and advertiser ad-server handoffs, creative delivery, counting differences and checks before a tag goes live.
An ad server selects an eligible ad, returns creative code or content, and records delivery under its own counting rules. A publisher and an advertiser may use separate servers. Publisher selection, advertiser-side delivery and a recorded impression are related events. None alone proves a person saw the ad.
Follow the creative after selection
For a web display placement, the publisher ad server may select a booked line item and a compatible creative. If that creative carries a third-party tag, the browser may then call the advertiser’s ad server.
| Stage | Question to answer | Useful evidence |
|---|---|---|
| Publisher selection | Which line item and creative were chosen? | Placement settings and publisher delivery record |
| Advertiser handoff, if used | Did the intended tag or integration return content? | Final trafficked tag and relevant trace or platform record |
| Asset and tracker loading | Which expected requests completed? | Browser or player trace and error details |
| Reporting | What event does each system count? | Metric definitions and aligned reports |
A publisher can select a creative even if a later third-party call fails. An asset request alone does not establish a billable or viewable impression.
Ad Creative Delivery Workflow: Key Stages and Checks
- Publisher selectionLine item and creative chosen based on targeting criteria
- Advertiser handoff (if used)Third-party tag or integration returns content; verify with trace records
- Asset and tracker loadingBrowser/player traces confirm successful asset and tracking requests
- Reporting alignmentEnsure metric definitions and counting rules are consistent across systems
Understand what each server selects
In Google Ad Manager, an ad request carries information to the server, which builds a list of line items matching the targeting criteria. It then selects a line item and a creative within that line item before serving.
Campaign Manager 360 uses different objects: a placement represents where creatives can appear, and standard ads are assigned to placements. For a site visit, it uses targeting criteria and other settings to choose an ad for the placement, then one of that ad’s assigned creatives.
Google Ad Manager vs Campaign Manager 360: Selection Logic
- Selection methodAd Manager: line items matched by targeting → creative selected within line item
- Object hierarchyCampaign Manager 360: placement → standard ad → creative rotation
- Creative assignmentMultiple creatives can be assigned to one ad in Campaign Manager 360
Choose the delivery arrangement
The publisher controls its placements and booked obligations. An advertiser may use its own server to manage creative across publishers and record advertiser-side delivery. If both systems are used, agree on the tag type, creative owner, click handling and troubleshooting responsibility before trafficking.
Google Ad Manager has a Campaign Manager 360 internal redirect creative type. Google says that tag is processed within the two systems, not sent to the browser as an ordinary third-party tag. A conventional third-party creative can generate browser requests to another server. The word ‘redirect’ alone does not identify which path is in use.
Check the format. Display, HTML and VAST video executions have different rendering and tracking paths. Confirm the proposed placement or player supports the actual tag and creative.
In a VAST video handoff, the player makes an ad request, receives a response containing or identifying the video creative, retrieves and plays the asset, and triggers configured tracking calls during delivery. Unlike a display creative rendered on a page, video delivery depends on the player interpreting the response.
VAST Video Delivery: Player-Based Handoff Process
- Player makes ad requestInitiates delivery for video placement
- Response receivedContains or identifies the video creative asset
- Asset retrieval and playbackPlayer downloads and plays the video content
- Tracking triggersConfigured calls fired during delivery (e.g., start, mid-roll, completion)
Distinguish content delivery from tracking
In Campaign Manager 360, a standard ad displays a creative on a site. Tracking ads and click tracker ads deliver no visible content; they track clicks and impressions instead.
Standard ads can have multiple assigned creatives. Campaign Manager 360 can rotate them according to the ad’s settings, so the creative shown may vary between impressions. Confirm the assigned creative and intended tracking arrangement match the ad’s role.
Account for internal redirect fallback
A Campaign Manager 360 internal redirect is hosted by Campaign Manager 360 and processed within Campaign Manager 360 and Google Ad Manager, not sent to the user’s browser. Google describes this creative type as simplifying trafficking and reducing latency.
If the other network has nothing to serve, Ad Manager can roll back the internal redirect, re-run selection while excluding that creative, and choose another creative or line item. This fallback can help avoid a blank ad; it is distinct from a conventional third-party tag making a browser request.
Internal Redirect vs Third-Party Tag: Trade-offs
- Pros of internal redirectReduces latency; processed within Ad Manager and Campaign Manager 360; fallback available if no creative is served
- Cons of internal redirectNot sent to browser as a third-party tag; may not trigger external tracking unless configured
- Pros of third-party tagAllows direct browser-level tracking and integration with external systems
- Cons of third-party tagHigher latency; failure risk due to network or blocking; no automatic fallback
Keep counting stages separate
Google Ad Manager counts an impression after a creative sends its follow-up impression request; its code-served total can therefore exceed its impression total. Its rules also vary by format. Reports can differ because of implementation, event definitions, filtering, timing or reporting cut-offs.
Align placement, creative, format, date range and time zone before comparing totals. Keep clicks separate: a click tracker follows a user action and can fail independently of creative delivery.
Key Counting Differences Between Systems
- Google Ad Manager impression count
- Based on follow-up impression request; may differ from code-served total
- Campaign Manager 360 initial impression
- Counted at ad serving when creative calls server post-impression
- Mobile app visibility rule
- At least one pixel must be visible for an impression to count
Read counts in their product context
Campaign Manager 360’s initial impression count occurs during ad serving: the delivered creative contains code that calls the server once the impression standard is met. Its reported counts have already been filtered, so distinguish the initial serving event from the figures shown in reports.
Google Ad Manager’s impression methodology depends on the format. For some mobile app impressions, including Ad Exchange creatives, certain Ad Manager creative formats and Open Bidding, the count is based on at least one pixel of the creative being visible.
Check before release
Record the final tag, format, size, destination, owner and intended placement. Preview where the creative will run, inspect the requests and test an authorised click.
Preview delivery can include third-party tracking URLs, which may receive calls. Treat preview as a configuration check and confirm publisher-side delivery separately.
Pre-Release Creative Delivery Verification Checklist
- Final tag format confirmedMatches intended delivery type (HTML, VAST, etc.)
- Size and destination verifiedTag size matches preview and live placement
- Preview testedRendered correctly in preview environment
- Click tracking validatedAuthorised click test confirms tracking works
Know the limits of a preview
Google Ad Manager previews can run before a creative’s start date, but on-site preview is not supported for creatives with size overrides or web interstitials. The tag size must match the preview creative’s size.
Creative preview is also not supported for native video, Dynamic Ad Insertion or Programmatic Direct. Where available, preview helps check how the creative renders, but does not replace confirmation of live publisher delivery.
In this guide
- Comparing advertiser and publisher ad serversCompare who selects the placement, who delivers creative and how to assign tagging and reporting responsibilities.
- Understanding ad serving discrepancies between systemsAlign ad-server reports, identify where counts separate and investigate tags and tracking without assuming a universal tolerance.
- Testing a creative tag before traffickingCheck rendering, tracking, clicks and format compatibility on the final tag before publisher trafficking.
- Documenting ad server redirect chainsRecord creative, click and VAST handoffs, including what browser traces cannot show, so partners can locate delivery failures.
