Campaign Manager 360 RFP Template

Before You Issue a Campaign Manager 360 RFP

Campaign Manager 360 engagements are operational at heart: trafficking discipline, naming conventions and QA processes determine whether your ad server is a source of truth or a source of arguments. The strategic asset is the floodlight architecture — conversion tagging that will feed DV360, SA360 and your analytics stack — so your RFP should treat floodlight design as the senior technical workstream, not an afterthought of trafficking.

If you are migrating ad servers or restructuring an existing instance, require a verification plan: parallel measurement during transition, discrepancy thresholds agreed in advance, and documented mapping from old structure to new. Ask specifically about attribution — how CM360's view of conversions will be reconciled with GA4 and platform reporting, because those numbers will disagree and someone must own the explanation.

What the Campaign Manager 360 Sections Cover

• Floodlight inventory, including tags nobody claims
• A naming taxonomy enforced across every advertiser
• Trafficking ownership: agency, in-house or shared
• Placement and creative migration off the current ad server
• Conversion counting rules finance has agreed
• Consent Mode and the signal loss it introduces

Writing the Campaign Manager 360 Scope of Work

Scope the account structure before the trafficking. Advertiser and campaign hierarchy, naming conventions and the placement taxonomy determine whether reporting can be aggregated the way the business thinks about itself, and they are difficult to change retrospectively because history follows the old structure. State how many advertisers, markets and agencies will operate in the account, who has trafficking permissions and who can create new advertisers. If several agencies work in the same instance, the scope must say how they are separated and who arbitrates the conventions between them.

Treat the floodlight architecture as the central design deliverable. It is shared measurement infrastructure that search, display and analytics all depend on, so the scope should cover the activity groups, the counting methodology for each activity, the custom variables carried, and the rules for who may create a new floodlight. Say which downstream platforms consume which activities. Tag deployment is a separate concern again: state whether floodlights deploy through your tag manager, whether the global site tag is already present, and how consent gating applies to conversion measurement in each market.

Scope the trafficking operation in volumes and service terms. State the number of placements and creatives per period, the formats involved including video and rich media, and the turnaround expected from asset delivery to live. Name who does quality assurance and what it covers: click-through destinations, tracking parameters, dimension correctness and creative rendering. If bulk operations through structured data files are part of the working method, say so, because that changes both the skills required and the risk profile of a mistake.

If this involves a migration or a restructure, scope the verification explicitly and define done accordingly. That means a parallel measurement period of stated length, agreed discrepancy thresholds against the previous configuration and against your analytics, and a documented mapping from old to new structure so historical reporting can be rebased. In steady state, define done per cycle: campaigns trafficked and quality assured before flight, floodlight coverage verified after every site release, and a named owner for explaining differences between ad server, analytics and platform reporting when they arise.

Requirements That Actually Separate Campaign Manager 360 Proposals

• Floodlight governance — require the rules for creating, naming and retiring activities, including who approves a new one, since uncontrolled floodlight creation destroys the comparability that makes the ad server useful.
• Counting methodology reasoning — ask them to justify the counting method chosen for each activity against the business question it answers, and to describe what breaks if it is changed after data has accumulated.
• Tag deployment resilience — require a process for verifying conversion tags remain present and firing after each website release, since silent floodlight loss is common and only discovered when reported conversions fall.
• Trafficking quality assurance — ask for the checklist applied before a placement goes live and what proportion of errors it catches, including landing page and tracking parameter verification rather than creative rendering alone.
• Data transfer file usage — require a position on whether raw event files are delivered to storage you own, what analysis they enable, and who is expected to work with them.
• Verification configuration — ask what viewability, invalid traffic and brand safety settings are applied and how they are audited, rather than accepting whatever the previous configuration left in place.
• Discrepancy explanation — require a documented account of why ad server, platform and analytics conversion figures differ structurally, written for a business audience rather than for the measurement team.

Common Mistakes in Campaign Manager 360 RFPs

• ✕ Floodlight architecture designed ad hoc per campaign instead of as shared measurement infrastructure.
• ✕ No naming conventions or trafficking QA, making reporting a manual reconciliation exercise.
• ✕ Ad-server migration without parallel measurement and agreed discrepancy thresholds.
• ✕ Verification vendors and settings inherited without review of what is actually being measured.
• ✕ Nobody owns explaining why CM360, GA4 and platform numbers differ — so every meeting relitigates it.

• ✕ Scoping a restructure without a rebasing plan for historical reporting, so the first quarterly review after the change has no comparable prior period and the improvement cannot be demonstrated.
• ✕ Assuming consent gating affects only site analytics, when conversion tags are gated by the same mechanism and reported conversions fall in ways that get misdiagnosed as media underperformance.
• ✕ Pricing trafficking by placement count while the campaign mix is dominated by dynamic and video creative, where the setup and quality assurance effort per placement is several times higher.
• ✕ Leaving custom variable usage undefined, so each agency invents its own conventions and the fields that should allow cross-campaign analysis carry incompatible values.

Questions Worth Asking Campaign Manager 360 Vendors

1. Show a floodlight architecture you designed that serves DV360, SA360 and analytics together.
2. What do your trafficking conventions and QA checklist look like in practice?
3. Describe an ad-server migration you ran: parallel period, discrepancy thresholds, and what surprised you.
4. How do you configure and audit verification (viewability, IVT, geo) rather than inheriting defaults?
5. Who on your team explains cross-system conversion discrepancies to stakeholders, and how?

How to Weight the Campaign Manager 360 Evaluation

Weight measurement architecture above trafficking capacity. Trafficking is a service that can be scaled or replaced; the floodlight and taxonomy design is a shared asset that everything downstream depends on, and correcting it later means losing comparable history. Proposals that treat the architecture as the senior piece of work, with design time allocated to it, are prioritizing the part with lasting consequences.

Score process discipline over platform knowledge. The characteristic failures in an ad server are operational: a placement trafficked to the wrong landing page, a tag not updated after a site release, a naming convention broken by one agency in one market. Evidence of a real quality assurance routine, including how errors are detected and how many get through, is more informative than depth of feature knowledge.

Give weight to independence from the media buying relationship. If the same organization buys the media, runs the ad server and reports on the results, the measurement layer is not a check on anything. Whether or not you separate them, weight a vendor's willingness to be measured against your own analytics and to deliver raw data into your control, because that is what makes the ad server a source of truth rather than a source of agreement.