Additional signed-in signals may change credited conversions without changing the underlying business results.

PPC Land reports that Google updated its “Coming soon: Display & Video 360 updates in Q4 2026” help page on 16 October. It lists three changes for November 2026, each with a month and no day. The widest is: Google plans to use signals from signed-in users to connect web conversions across devices and environments in reporting for DV360, SA360 and CM360. The notice says advertisers do not need to take action.

The other two are an advertiser-level Brand Control Center page being deprecated and the audience data provider Amerilink being renamed “Open Audiences” in reporting. The page gives no figures on how many conversions will be recovered, and it does not say when the entries were first added. Reported conversions may change without a change in spend; the announcement does not quantify the effect.

In plain English

“Floodlight” is Google’s conversion-tracking tag. “Unattributed” conversions are sales the system could not link to an ad. “Cross-device” means the ad and the purchase happened on different devices.

Why it matters

Reported conversions may jump in November because of a measurement change, not better ads, so record a baseline now and read any November lift against your own order data.

An attribution change can alter a report without altering the underlying number of purchases. If a system connects an existing conversion to an earlier interaction more successfully, the advertising report can show additional credited conversions even when the business recorded the same total sales. That distinction is central to interpreting this announcement.

The reported change should therefore be annotated in dashboards when it reaches an account. Compare platform-attributed conversions with independently recorded orders or leads. If only the attribution total rises, that is evidence of a measurement change rather than sufficient evidence of improved campaign effectiveness. The announcement does not establish how large any increase will be.

This is especially relevant when teams compare periods across the rollout. A better reported cost per conversion could partly reflect the new measurement coverage. Budget decisions should consider whether the comparison uses consistent definitions, conversion windows and business outcomes.

The month-level timetable also leaves an operational uncertainty. A November announcement does not identify the exact day an individual report will change. Teams should watch the product notices and document what they observe rather than assuming the entire month uses one methodology. The other listed changes, including a renamed data provider and a deprecated interface page, are separate maintenance items and should not be confused with the attribution update.

Sources