INDEPENDENT MINDS. SHARED AMBITION.
Back to the newsfeed
Strategy2 min read

Google Marketing Platform · Status at source date: Documentation

DV360's November changes: Brand Control Center retires and Floodlight uses signed-in signals for cross-device attribution

Written by Paid Media Collective
IN BRIEF

DV360's announcements page, updated on 16 October, lists November changes: the advertiser-level Brand Control Center is deprecated and its settings move to targeting rules; the "Amerilink" provider is renamed "Open Audiences"; and Floodlight will use Google signed-in data signals to recover unattributed cross-device and cross-environment web conversions across DV360, SA360 and Campaign Manager 360 reporting, with no action required. Separately, legacy mCPV and Video reach 1.0 line items are paused and archived from 26 October. For you, this means Floodlight conversion counts may rise in November without a tracking change, so annotate reports before comparing periods.

DV360's November changes: Brand Control Center retires and Floodlight uses signed-in signals for cross-device attribution. Source visual from the published Week 43 newsletter.
Source visual selected in Paid Media News Week 43. DV360 HelpView full-size image

What changed

What this means in practice

The November items affect different parts of the buying and reporting workflow. Moving a brand-control setting is a configuration change; a provider rename is a taxonomy change; additional signed-in signals concern measurement. Treating them as one performance improvement would make month-to-month analysis harder to interpret.

Before the reporting transition, document the conversion definitions and comparison periods used in client dashboards. If reported conversions change, assess measurement coverage alongside actual sales and qualified outcomes. A larger measured total does not by itself prove that a campaign generated more incremental business.

The 26 October line-item retirement is a separate operational deadline from the November changes. Inventory affected line items and inspect their current status before assuming that delivery will continue under the same setup. Preserve the previous settings and the dates of changes in the campaign log. The 16 October date identifies the announcements-page update cited in the newsletter; it should not be substituted for each feature's separate effective date.

A change log should identify the configuration migration, provider naming and measurement expansion independently. That makes it possible to explain a later reporting discontinuity without assuming a delivery failure or attributing every movement to the new signals. Confirm the applicable dates in the linked announcements page.

Sources & contributor credit

  1. Source referenced in newsletterDV360 Help

    Date, scope and credit reconciled with the published Week 43 newsletter.

  2. Newsletter coveragePaid Media Collective Week 43

    Date, scope and credit reconciled with the published Week 43 newsletter.

Official Source

Original creator unverified

Credits reflect the editor's latest changes. Original authorship has not been independently verified for this version.

Attribution evidence and limitations

Full attribution review pending.

A source link alone does not establish original authorship.

Original image and video creators have not yet been verified.

Published on this site
Article updated

This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.

Explore the source reporting