Campaign Manager 360 trafficking and Floodlight measurement

Establish the measurement job before the buying job

Campaign Manager 360 is relevant when an advertiser needs coordinated ad-serving, trafficking and measurement across a fragmented media programme. That requirement is distinct from deciding where to buy impressions. Emerge separates the measurement architecture from the buying platforms so the team understands which system is responsible for each decision and report.

The engagement may cover a new advertiser setup, repair of an existing Floodlight configuration or a repeatable trafficking service. We begin with the publishers, platforms, creative formats and business outcomes in scope. The objective is a traceable chain from a campaign brief to the placement and conversion evidence the advertiser can review.

Create a taxonomy that survives handovers

Campaigns, placements, ads and creatives need identifiers that remain useful after files pass between agency, advertiser and publisher teams. We define the naming dimensions that matter, such as market, objective, format, audience concept and creative version. Stable platform identifiers remain part of the reporting model even when a display name changes.

The trafficking register records who supplies each asset, which placement receives it, the intended destination and the status of publisher implementation. It also captures replacement and expiry rules. This avoids an updated creative file being treated as interchangeable with an older approved version without a clear instruction.

A taxonomy is tested against actual reporting questions before rollout. If the commercial team needs to compare a message across markets, the mapping must support that question without manually decoding every placement name.

Design Floodlight around real outcomes

Floodlight provides a shared conversion-measurement foundation across relevant Google Marketing Platform products. Emerge defines the activities around the business events that matter and documents the counting method, value, currency and identifier handling for each activity. A purchase and a request for information have different acceptance criteria.

Configuration ownership and sharing arrangements are recorded explicitly. Changes in a shared conversion layer can affect more than the report visible to the person making the change. The release process therefore includes the connected buying teams and identifies which activities influence optimisation.

Custom variables are selected for an approved reporting or optimisation purpose. They are not used as an unrestricted channel for personal data or unreviewed CRM fields. Consent behaviour and permitted identifier use are tested as part of the tagging implementation, including the actual requests received by the measurement destination.

Coordinate ad-serving and tracking with publishers

Different publishers and formats have different implementation requirements. We confirm the supported tag or tracker approach, click handling, cache-busting or macro requirements where applicable, and the creative review process for the specific placement. The trafficking package gives the receiving team enough detail to implement and verify the intended setup.

Quality assurance checks the visible creative, destination, click-through behaviour and measurement request. It also checks dates, placement assignment and the behaviour when an asset is replaced. A tag accepted by a publisher is not by itself proof that impressions and clicks are recorded in the intended campaign structure.

Discrepancies receive a shared investigation path. The advertiser, publisher and buying platform may measure different stages of delivery and apply different filters or processing windows. We document the relevant definitions and compare equivalent scopes before identifying a fault.

Reconcile conversions without inventing a universal total

A shared measurement configuration can reduce inconsistent counting within its defined scope. It does not make every advertising platform’s attributed results directly additive. Click and view windows, consent, identity availability and model choices affect the observable result.

We compare Floodlight outcomes with the agreed business source, such as accepted orders or qualified leads. The reconciliation view identifies duplicate transaction references, missing events and delayed records. Offline outcomes are kept distinct from browser-fired activities where the design requires it, with an upload and correction process that can be audited.

Reporting communicates what was measured, what was attributed and what remains unknown. That distinction helps the team make budget decisions without representing attribution credit as proof of incremental sales.

Acceptance covers launch and change control

Before release, Emerge verifies the advertiser structure, placement mappings, creative versions, destinations and Floodlight activities using controlled test scenarios. The receiving teams confirm implementation, and a first reporting cycle is reconciled at a level that can reveal mapping errors rather than only aggregate totals.

The operating handover includes the trafficking register, naming standard, conversion dictionary and escalation responsibilities. Change control covers new activities, lookback changes, creative replacement and retired placements because each can affect historical comparisons or active optimisation.

The resulting service gives campaign teams a repeatable process for launching and maintaining measurable media. Product access and commercial terms are confirmed for the actual advertiser. Where buying operations are also required, the connected DV360 and SA360 journeys explain their separate implementation scope.