DV360 Floodlight Setup Without CM360: A Practical Guide

Can You Use Floodlight in DV360 Without CM360?

Short answer: yes — with one important caveat. Floodlight is technically a Campaign Manager 360 (CM360) feature, so a Floodlight configuration must exist in a CM360 network. But you do not need to traffic a single CM360 campaign, placement or ad to use Floodlight for conversion measurement inside Display & Video 360.

This distinction trips up a lot of teams. They assume adopting Floodlight means standing up a full CM360 trafficking workflow, duplicating effort and adding cost. In practice, many DV360 advertisers run entirely through DV360 for buying while using Floodlight purely as the conversion-measurement layer.

This guide walks through how that works, how to set it up, and the pitfalls to watch for.

Understanding the Floodlight and DV360 Relationship

Floodlight is the shared conversion-tracking system across the Google Marketing Platform. A Floodlight configuration is the container that holds your activities, counting rules and attribution settings. That configuration is anchored to a CM360 network — but access to it can be surfaced directly in the DV360 interface.

Think of it in layers:

• Floodlight configuration — the network-level container (lives in CM360).
• Floodlight activities — individual conversion events (purchase, lead, page view).
• DV360 advertiser link — the connection that lets DV360 read and act on those activities.

Once linked, you manage and reference Floodlight activities inside DV360 for conversion reporting, bid optimisation and audience building — no CM360 campaign trafficking required.

Why teams choose Floodlight over a pixel-only setup

DV360 can import conversions from Google Ads, Google Analytics 4 and Floodlight. Floodlight remains the most flexible option when you want:

• Granular, custom conversion activities (counter and sales types).
• Unified cross-channel measurement if you later add CM360 or Search Ads 360.
• Richer audience creation from on-site behaviour.
• Consistent attribution across the Google Marketing Platform stack.

If you want help deciding between Floodlight, GA4 import and server-side tagging, our DV360 managed services team can map it to your goals.

Step-by-Step: Floodlight Setup Without CM360 Trafficking

1. Confirm access to a Floodlight configuration

Your DV360 advertiser needs to be associated with a Floodlight configuration. This association is usually established when the advertiser is created inside a Google Marketing Platform organisation that includes a CM360 network. If you don't have one, your partner or Google representative can provision the configuration — you still won't need to run CM360 media.

Check in DV360 under Advertiser settings → Floodlight to confirm a configuration is attached.

2. Set configuration-level settings

Before creating activities, align the configuration defaults:

• Attribution model and lookback windows (click and impression).
• Conversion counting defaults.
• Cross-device conversions toggle.
• Enhanced attribution / data-driven settings where available.

Get these right first — changing them later can make historical reporting harder to interpret.

3. Create your Floodlight activities

Floodlight activities come in two types:

Activity type	Use case	Counts
Counter	Page views, leads, sign-ups, content engagement	Number of conversions and/or unique users
Sales	Purchases and transactions	Revenue and number of items/transactions

For each activity, define:

• A clear, consistent naming convention (e.g. Lead_Form_Submit, Purchase_Confirm).
• The counting method (standard, unique, per session, transactions, items sold).
• Any custom variables (u-variables) you want to capture, such as order value or product category.

4. Deploy the tags

You have several deployment options — none require CM360 campaign trafficking:

• Google Tag Manager (recommended): add the Floodlight tags via GTM with triggers mapped to each conversion event. Easiest to maintain and QA.
• Global site tag / gtag.js: deploy Floodlight using the global site tag framework for cleaner, consent-aware implementation.
• Direct tag placement: paste image or iframe tags into page templates (least flexible, avoid where possible).

Always implement with your consent management platform so Floodlight only fires with valid consent in applicable regions.

5. Verify firing and data flow

Before relying on the data:

• Use the Google Tag Assistant or your browser's network panel to confirm the tag fires on the right pages.
• Trigger a test conversion and confirm it appears in DV360 reporting (allow for processing delay).
• Validate that custom variables and revenue values pass through correctly.

6. Activate for optimisation and audiences

Once data is flowing, you can:

• Use Floodlight conversions as the optimisation goal for automated bidding.
• Build remarketing and conversion-based audiences.
• Report on post-view and post-click conversions across your DV360 line items.

Floodlight vs GA4 Conversion Import in DV360

Many teams ask whether they even need Floodlight when GA4 can share conversions and audiences with DV360. Both are valid — they solve slightly different problems.

Factor	Floodlight	GA4 import
Native to media stack	Yes (GMP)	Yes (linked)
Impression (post-view) tracking	Strong	Limited
Custom activity granularity	High	Moderate
Setup effort	Moderate	Low if GA4 already live
Cross-platform (CM360/SA360) reuse	Yes	Indirect

In practice, performance-focused advertisers often run both: Floodlight for media attribution and optimisation, GA4 for broader analytics. If you're unsure which to lead with, talk to an expert.

Common Pitfalls to Avoid

• Assuming you need CM360 campaigns. You only need the configuration, not the trafficking.
• Inconsistent naming. Messy activity names make reporting and optimisation painful at scale.
• Ignoring consent. Firing Floodlight without consent management risks compliance and data quality.
• Duplicate counting. Overlapping tags (e.g. GTM plus hard-coded tags) inflate conversions.
• Changing attribution windows mid-flight. This fragments your trend data and confuses stakeholders.
• No QA on custom variables. Missing revenue values quietly break ROAS reporting.

When to Bring in a Partner

Floodlight configuration access, GMP organisation structure and advertiser linking can be fiddly — especially if you're moving from a pixel-only or GA4-only setup. A certified partner can provision the configuration, validate your tagging architecture and ensure attribution settings match your reporting goals.

Explore how a DV360 partner account or co-managed services can give your team the right level of support — from full setup to ongoing optimisation. You can also review the full range of DV360 services to find the right fit.

Key Takeaways

• Floodlight requires a configuration, not CM360 media trafficking.
• Set configuration-level attribution and counting rules before building activities.
• Deploy via Google Tag Manager for the cleanest, consent-aware implementation.
• Use Floodlight for optimisation and audiences, and consider pairing it with GA4.
• Strong naming conventions and QA prevent most downstream reporting headaches.

Ready to Set Up Floodlight the Right Way?

If you want Floodlight configured cleanly in DV360 — without the overhead of a full CM360 trafficking workflow — our team can help you provision the configuration, build your activities and validate every conversion. Get in touch to scope your setup.