What is a digital advertising trafficking sheet?

What does a trafficking sheet actually do?

A trafficking sheet sits between campaign planning and activation. A media plan may describe what is being bought, a creative matrix may describe which ads exist, and an activation platform may already contain placement names or IDs. The trafficking sheet reconciles those pieces into one reviewable setup.

Its purpose is operational clarity. The person trafficking or activating the campaign should be able to determine which creative belongs to which placement, which URL should be used, which platform identifier applies and whether the required campaign values are present before launch.

What information is usually in a trafficking sheet?

Not every campaign uses every field. The exact columns depend on channel, platform, agency process and client requirements.

Which source files feed a trafficking sheet?

There is no single universal template, but three source types are common in agency and in-house media workflows:

1. Media plan: planned markets, publishers, placements, formats, investment, rates, dates and delivery values.
2. CMM or creative matrix: creative names, sizes, formats, languages, markets, landing pages and asset-level instructions.
3. Platform or placement export: placement names, platform IDs and other setup identifiers already created in systems such as campaign-management or buying platforms.

The operational challenge is rarely copying one clean table into another. It is reconciling fields whose naming, order and level of detail can differ across those files.

For a side-by-side explanation, see Media Plan vs Creative Matrix vs Platform Export.

How a trafficking sheet is built

1. Confirm campaign scope. Identify the correct campaign, markets, channels and flight dates.
2. Read the approved media plan. Establish the planned placements and media values.
3. Join creative instructions. Match assets to markets, formats, placements or audiences using the creative matrix.
4. Add platform identifiers. Reconcile placement names and IDs where an export is available.
5. Validate URLs and required values. Check landing pages, tracking, IDs, sizes, names and other mandatory fields.
6. Surface exceptions. Keep unresolved or ambiguous rows visible rather than silently guessing.
7. Review before activation. A human operator signs off the operational output.

What should teams QA before trafficking?

A useful QA pass checks both completeness and consistency. Typical checks include whether every planned placement has the expected creative, whether IDs are present and unique where required, whether landing pages are correct, whether sizes and durations match the placement, and whether media values reconcile with the approved plan.

Cross-file mismatches deserve particular attention. For example, a placement may be labelled “UK Video 15s Prospecting” in one source and abbreviated differently in another. Matching solely on exact text can therefore fail even when the records logically refer to the same activity.

Can trafficking sheet creation be automated?

Yes, many repeatable preparation tasks can be automated: detecting likely fields, standardising values, matching records across source files, carrying through IDs and landing pages, and flagging missing data. The useful goal is not to remove human accountability. It is to reduce repetitive spreadsheet work so human attention is concentrated on genuine exceptions.

TraffiqGen's trafficking sheet automation is designed around that model. The current beta analyses campaign files in the browser, uses rules and schema inference to detect structure, cross-checks related records and produces a reviewable output with uncertain values kept visible.

Frequently asked questions