Google last month released version 1.7 of the Data Manager API, extending offline conversion event ingestion to the full Google Marketing Platform stack for the first time and introducing IP address support for Customer Match audience uploads through a new composite data structure.

GMP products receive offline conversion access

The update, published May 28, 2026, adds support for sending offline conversion events to three Google Marketing Platform products: Campaign Manager 360, Search Ads 360, and Display and Video 360. Until now, offline conversion event ingestion through the Data Manager API was limited to Google Ads and Google Analytics. This release closes a significant gap for organisations running campaigns across the broader GMP stack.

The mechanism is the IngestEventsRequest method, which the API already uses for Google Ads offline conversions. According to Google's release notes, the same request structure now routes to GMP destinations. Developers do not need a separate endpoint or a different ingestion pattern - the destination routing is handled by the API's existing fan-out logic, which allows a single request to reach multiple downstream products simultaneously.

A new account type accompanies the change. FLOODLIGHT_CONFIG has been added to the AccountType enum, giving developers a dedicated destination type for Floodlight-based measurement configurations. This is meaningful because Floodlight sits at the centre of conversion tracking in Campaign Manager 360 and flows attribution signals into both Display and Video 360 and Search Ads 360. Tagging a destination as a Floodlight config - rather than mapping it to an individual product - reflects how these platforms actually share data in production environments.

Four new fields have also been added to the AdIdentifiers resource: dclid, impression_id, match_id, and encrypted_user_ids. The dclidfield accepts a DoubleClick Click ID, which is the identifier appended to non-YouTube click events across the Google Marketing Platform. Its addition matters for GMP advertisers specifically: without a dclid field in the API schema, there was no clean way to associate an offline conversion event with a display or video click tracked through Campaign Manager 360. The impression_id field extends that logic to view-through attribution, allowing an offline transaction to be matched to an ad impression rather than a click.

A conversion_count field has been added to the Event resource. This enables tracking of conversion quantities - relevant for retail or lead-generation implementations where a single event represents multiple units or interactions rather than a single transaction.

Composite data and IP address ingestion

The second major addition in v1.7 is the composite_data field on the AudienceMember resource. This field accepts a CompositeData object, which allows an advertiser to bundle multiple types of identifiers in a single audience member record. The initial design of the Data Manager API handled audience identifiers through separate, distinct fields. CompositeDatachanges that by accepting both UserData - which holds hashed contact information such as email addresses, phone numbers, and postal addresses - and IpData in the same payload.

The practical addition is IP address ingestion for Customer Match in Google Ads. According to Google's documentation, sending IpData through the composite data structure enables IP address-based audience matching. This has not previously been supported in the Customer Match workflow. The IpData payload includes a required ipAddress field and two optional timestamp fields, observeStartTime and observeEndTime, which record the window during which the IP address was associated with a user. Advertisers can send IP data alone or alongside other identifiers.

This is the same CompositeData structure covered on PPC Land when the May 28 release was first noted, which also documented that Display and Video 360 does not yet support IP address ingestion through this field - only Google Ads is eligible at launch.

Two new status objects have been added to accompany composite data requests: IngestCompositeDataStatus and RemoveCompositeDataStatus. Both include diagnostics - specifically record_count and data_type_counts - giving developers visibility into how many records were processed and what mix of data types was present in a given ingestion job.

New error reasons and diagnostic granularity

Version 1.7 adds four new values to the ErrorReason enum: FIELD_VALUE_TOO_SHORT, TOO_FEW_ELEMENTS, BASELINE_LOCATION_AUTO_DETECTION_FAILED, and INSIGHTS_MISSING_FOR_DIMENSION. These expand the vocabulary available to developers when diagnosing ingestion failures. Previous versions already included FIELD_VALUE_TOO_LONGand TOO_MANY_ELEMENTS, so the short and too-few counterparts bring a degree of symmetry to the validation feedback layer.

Additional diagnostic values have been added to ProcessingErrorReason to provide more specific feedback for failures during event ingestion. The release notes do not enumerate these individually, but the intent is to give developers more actionable information when an ingestion job fails partway through processing rather than at initial validation.

Context: a platform under rapid extension

The Data Manager API has moved quickly since its first release. Google published v1.0 on April 2, 2025, with audience ingestion support for Google Ads and Display and Video 360. By the time v1.3 reached general availability in October 2025, the platform had added offline conversions, enhanced conversions for leads, and a diagnostic retrieval method. As PPC Land documented at the December 2025 launch, the intent was to replace fragmented, product-specific pipelines with a single ingestion layer - one that would enforce a consistent schema and provide unified authentication across Google Ads, Google Analytics, and Google Marketing Platform.

Version 1.4, released November 2025, added Google Analytics purchase events as a supplementary data source for tag conversions. Version 1.5, released February 2026, introduced the UserList resource and UserListService, enabling the full audience lifecycle - creation, ingestion, and retrieval - through the API. Version 1.6, released May 7, 2026, added store sales conversion ingestion and expanded Analytics event support, and was described at the time as the most comprehensive feature update since general availability.

Version 1.7 arrives three weeks later. The pace reflects the degree to which Google has been systematically routing data operations toward this API. As covered by PPC Land in April 2026, the end of Customer Match uploads through the Google Ads API on April 1, 2026 created an immediate migration incentive. Developers managing audience data for Google Ads had no choice but to adopt the Data Manager API. The v1.7 expansion to GMP products now creates a parallel pressure point for teams whose measurement infrastructure is built on Campaign Manager 360 and its Floodlight configuration layer.

What changes for GMP-centric measurement teams

For teams using Campaign Manager 360 as their primary ad server and attribution system, the v1.7 release creates a new ingestion path that did not previously exist. Floodlight has historically received offline conversion data through a separate Campaign Manager 360 API. That API remains available, but the Data Manager API now offers an upgrade path for teams that want to consolidate their data pipelines. The benefits of the consolidated approach - a unified schema, a single authentication flow, multi-destination routing in one request - apply here just as they have applied to Google Ads.

The addition of dclid to the AdIdentifiers resource is particularly relevant for GMP workflows. As documented at the launch of enhanced attribution across the Marketing Platform, the DCLID identifier became the standard click identifier for non-YouTube display and video clicks in September 2024. Any offline conversion measurement that needs to attribute a physical transaction back to a display or video click depends on that identifier being present in the ingestion payload. Its absence from the Data Manager API until now was a functional gap.

For Search Ads 360 specifically, the ability to send offline conversions via IngestEventsRequest mirrors the path that Google Ads users have had since v1.2 in August 2025. Search Ads 360 manages paid search across multiple engines and uses Floodlight for conversion attribution. Having that attribution data flow into Search Ads 360 through the same API that handles Google Ads conversions reduces the number of separate pipelines a cross-channel team has to maintain.

EU political advertising compliance addition

One separate addition in the March 26, 2026 documentation update - which sits between v1.6 and v1.7 in the release history - deserves mention. Google added EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED to the ErrorReason enum to reflect obligations under the European Union Political Ads Regulation. Starting April 1, 2026, operations on accounts that have not provided the required self-declaration may be restricted or fail with this error. The affected operations include UserListService actions (create, update, and delete) and IngestionService.ingestAudienceMembers. Advertisers operating in the EU must provide the declaration through the Google Ads user interface to resolve the error.

Migration path from the Campaign Manager 360 API

Google's release notes point to a dedicated upgrade guide for teams migrating from the Campaign Manager 360 API to the Data Manager API for offline conversion events. The existence of that guide - rather than simply a pointer to the generic send events documentation - suggests Google is treating GMP migration as a distinct workflow with its own technical considerations, separate from the Google Ads migration path that has been the focus of most developer communications over the past six months.

The blocking of new offline conversion imports through the Google Ads API from June 15, 2026 for developer tokens without active recent use adds urgency for Google Ads teams, and the v1.7 release extends that strategic direction to GMP. The pattern across 2025 and 2026 has been consistent: Google establishes a capability in the Data Manager API, deprecates or restricts the equivalent functionality in the older product-specific API, and provides migration documentation. The v1.7 release follows the same structure.

For the marketing community, the practical question is timing. Teams that have already migrated Customer Match and offline conversions to the Data Manager API now have a clear path to add Floodlight-based GMP conversions without building a new integration. The infrastructure is the same; only the destination account type changes.

Timeline

  • April 2, 2025 - Data Manager API v1.0 launches with audience ingestion support for Google Ads and Display and Video 360, using REST and gRPC protocols.
  • June 25, 2025 - v1.1 adds the IngestEvents method as an additional data source for tag conversions.
  • August 6, 2025 - v1.2 adds support for offline conversions and enhanced conversions for leads to Google Ads destinations.
  • October 6, 2025 - v1.3 reaches general availability for all users; audience member threshold for targeting eligibility drops from 1,000 to 100 members.
  • November 5, 2025 - v1.4 adds Google Analytics purchase events as a supplementary signal source and adds the GOOGLE_ANALYTICS_PROPERTY account type.
  • January 7, 2026 - Google restricts session attributes and IP address imports in the Google Ads API, effective February 2, directing developers toward the Data Manager API.
  • February 10, 2026 - Sending conversions with multiple data sources reaches general availability for all Google Ads accounts.
  • February 17, 2026 - v1.5 introduces the UserList resource and UserListService, completing the end-to-end audience management workflow including creation, ingestion, and retrieval.
  • March 4, 2026 - Google notifies developers that Customer Match uploads via the Google Ads API will fail from April 1.
  • March 26, 2026 - EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED added to the ErrorReason enum ahead of April 1 enforcement under the EU Political Ads Regulation.
  • April 1, 2026 - Customer Match uploads via OfflineUserDataJobService and UserDataService in the Google Ads API cease functioning; all new implementations must use the Data Manager API.
  • April 2, 2026 - Google's Ads DevCast episode dedicates full runtime to Data Manager API migration from audience and conversion pipelines.
  • May 7, 2026 - v1.6 adds store sales conversion ingestion to Google Ads and expands Analytics event support across web and app data streams.
  • May 28, 2026 - v1.7 extends offline conversion event ingestion to Campaign Manager 360, Search Ads 360, and Display and Video 360 via IngestEventsRequest; adds FLOODLIGHT_CONFIG account type; introduces composite_data for Customer Match with IP address ingestion support through IpData.

Summary

Who: Google's Data Manager API Team, addressing developers, agencies, and marketing technology vendors who manage conversion data and audiences across Google Ads, Google Analytics, and the Google Marketing Platform - specifically teams using Campaign Manager 360, Search Ads 360, and Display and Video 360.

What: Version 1.7 of the Data Manager API, released May 28, 2026, adds offline conversion event ingestion for Campaign Manager 360, Search Ads 360, and Display and Video 360 via IngestEventsRequest; introduces the FLOODLIGHT_CONFIG account type; adds dclid, impression_id, match_id, and encrypted_user_ids to AdIdentifiers; introduces a composite_data field on AudienceMember that accepts both UserData and IpData, enabling IP address-based Customer Match matching in Google Ads; and expands error and diagnostic reporting.

When: The release was published May 28, 2026, the same date Google separately confirmed IP address ingestion for Customer Match through the composite data structure.

Where: The changes affect the Data Manager API, accessible via both REST and gRPC protocols, and their downstream effects reach Campaign Manager 360, Search Ads 360, Display and Video 360, and Google Ads Customer Match.

Why: Google has been systematically redirecting data operations away from product-specific APIs toward the Data Manager API since the platform launched in April 2025. The v1.7 release extends that consolidation to the Google Marketing Platform's Floodlight measurement layer, creating a unified ingestion path for teams whose conversion tracking architecture is built on Campaign Manager 360 rather than Google Ads alone.