Google presented its October Demand Gen Drop on October 13, focusing on the data used to measure campaigns. The package highlights the Data Strength Uplift metric and the expansion of data connection tools into Google Analytics and Display & Video 360. The features have different access conditions, specified in each product's documentation.
Data Strength Uplift was first presented in September as part of Google's measurement updates. Google describes it as a measure of additional conversions recovered through an advertiser's first-party data setup. It tracks that setup's contribution to reporting. An increase in conversions observed by the system and evidence of additional sales generated by advertising are different measurements, for which Google presents separate tools.
First-party data becomes a focus of Demand Gen measurement
In the October announcement, Google says advertisers using Google Tag Gateway see an average increase of more than 20% in Demand Gen conversions. The figure comes from the company's internal global analysis covering June 3–17, 2026. It is an aggregate result attributed to Google, separate from the performance of an individual campaign or account.
Google tag gateway allows the Google tag to load through a website's own infrastructure. This can be a content delivery network, a load balancer or a web server. The documentation also covers configuration alongside server-side tagging. The feature concerns the infrastructure that collects measurement signals, using the domain of the website where it is implemented.
Another element of the package is Data Manager, which centralizes the connection and management of first-party data. The Google Ads documentation distinguishes between a source, a connection and a destination: a source can be a connected product, a file or an integration; a connection represents the imported data object; and a destination is the feature where that data is activated.
This structure allows a connection to be reused for multiple purposes supported by the product. For example, Google describes connecting BigQuery data for enhanced conversions for leads and using the same connection for Customer Match. Connection management, tag configuration and consent settings are available in the same administrative area, with the necessary data permissions.
Display & Video 360 access is being rolled out in phases
For Data Manager in Display & Video 360, the documentation specifies a phased rollout and current support for Customer Match audiences. Eligibility is checked through the Google account team. Listed sources include HubSpot, SFTP, Google BigQuery and Google Sheets. Connecting a source involves account authentication and mapping fields to the data used by the platform.
Enhanced conversions supplement existing measurement with information supplied directly by customers. Google uses SHA256 hashing for data such as email addresses before transmitting it in hashed form. Matching against users signed into Google accounts helps attribute conversions to earlier advertising interactions. The configuration used depends on where the result being measured takes place.
In Google Ads, enhanced conversions for web concern sales and events completed on a website. Enhanced conversions for leads connect information from forms with subsequent results that occur outside the website and are imported into the system. For businesses that receive inquiries online and complete a sale later, this distinction determines which data enters campaign measurement.
In Display & Video 360, the feature supplements Floodlight tags and is available for YouTube and eligible Demand Gen line items. The documentation separates web conversions and engaged-view conversions from other forms of measurement. View-through and in-app conversions are identified as future improvements, with a separate scope of use.
Google Analytics retains its own configuration requirements
The Google Analytics documentation describes enhanced conversions as an open beta feature. Activation uses user-provided data collection and, for use in Google Ads, the connection between the products. Google specifies that effects on models, attribution, reporting and bidding can take up to one month to appear after implementation.
Configuration in Analytics and configuration in Google Ads follow their own paths. The documentation explicitly covers a purchase measured through both products: only one conversion should be selected as the campaign's primary goal to prevent double counting. A new data flow therefore needs to be considered alongside the goals already used in the account.
Reporting separates data coverage from campaign results
Enhanced conversions diagnostics show the coverage of events containing sufficient data, the match rate and the uplift in reported conversions. These values describe different stages of measurement. Google includes statuses for an optimized setup, available improvements, issues needing attention and no recent data, giving implementation checks specific operational indicators.
Demand Gen uses visual formats distributed across YouTube, including Shorts, Discover, Gmail, Maps and the Google Display Network, depending on configuration and eligibility. The platform supports different goals and bidding strategies, including clicks, conversions and conversion value. Measurement relates to the selected goal, while information from the website and commercial systems forms part of Google Ads campaign management.
The Demand Gen API documentation describes retrieving performance by network and YouTube surface, alongside metrics including impressions, clicks, conversions and cost. Both segmentation dimensions are selected together in the query. This reporting level connects measured results with campaign distribution. The same documentation keeps the bidding strategy, budget and advertising formats as separate campaign settings, allowing a new data metric to be monitored in the context of the configuration that produced those results.
