What runs with an ad
Banners, video, audio, and their 1×1 trackers travel with or measure an advertising experience.
Ad tags can look similar in a trafficking sheet while doing very different jobs. This visual guide explains what they carry, what they measure, and where they normally run.
Banners, video, audio, and their 1×1 trackers travel with or measure an advertising experience.
Site tags and Floodlights observe visits, actions, and conversions on a brand’s website or landing page.
IAS, DoubleVerify, and similar vendors measure signals such as viewability, fraud, suitability, and verification events.
APIs can support trafficking, reporting, asset management, measurement, or many other platform-to-platform uses.
A landing page is the destination a person reaches after selecting an ad. It is not an ad tag, but its URL is part of the campaign experience: click trackers may redirect to it, and its parameters can carry UTMs, attribution values, or other campaign information.
A tiny image request—often visually invisible—used to tell a server that an impression or event happened. The URL can carry campaign IDs, cachebusters, consent signals, and other macros.
HTML or JavaScript that renders a display creative in a fixed-size ad slot. It may call an ad server, load external scripts, fire trackers, and send clicks through a tracker before reaching the landing page.
VAST is an XML response that tells a video player what media to play and which events to track. It can include multiple renditions, duration, click-through URLs, quartile trackers, and wrapper URLs.
VPAID adds executable creative code and interaction logic to video advertising. It was commonly delivered through VAST, but support has declined because of security, performance, and cross-device limitations.
An audio ad delivers a sound file to a compatible player, often through VAST. The same response can include a companion creative—usually an image or HTML banner displayed beside the player while the audio is playing.
A site tag runs on a webpage to measure visits, actions, or conversions. A CM360 Floodlight is one type of site-measurement request, identified by advertiser and activity values such as src, type, and cat.
Verification technology measures how and where an ad was delivered. Vendors such as Integral Ad Science (IAS) and DoubleVerify can be included through JavaScript, pixels, VAST verification elements, wrappers, or server-to-server integrations.
An API is not usually a creative tag. It is a structured way for platforms or servers to exchange campaign data, assets, reporting, or event information. Server-to-server measurement can reduce the amount of visible code inside a tag.
| Format | Main job | Usually contains | Best TagCheck workflow |
|---|---|---|---|
| 1×1 pixel | Measure an event | A tracking URL and parameters | Banner or video analysis |
| Banner | Render display creative | HTML, JavaScript, images, click tracking | Banner |
| VAST | Describe a video ad | XML, media files, events, clicks, wrappers | Video workflow matching the ad server |
| Audio | Deliver an audio ad | Audio files, events, clicks, optional companions | VAST/audio analysis |
| VPAID | Run interactive video code | Executable creative unit referenced by VAST | Video analysis + VPAID check |
| Floodlight/site tag | Measure site activity | Activity identifiers and event data | Detected inside submitted tags |
| Verification | Measure delivery quality | IAS, DoubleVerify, verification scripts, pixels, or events | Wrapper, pixel, script, and VAST checks |
| API | Exchange data server-to-server | Requests, responses, authentication, JSON | Not a paste-in creative format |
Important: One ad can use several of these at once. For example, a VAST response can contain 1×1 impression trackers, a click-through URL, verification code, and multiple video files.