Demand Gen Campaign – Third-party Measurement API Support Inquiry

[Rajat Singh]

Hello Google Ads Team,

We are working on Demand Gen campaign creation and management through the Google Ads API and would like clarification regarding Third-party Measurement configuration shown in the Google Ads UI for Demand Gen campaigns.

Specifically, in the Google Ads UI, under Campaign → Third-party measurement, there is an option to:

- Select Measurement type (e.g., Viewability)
- Choose a Vendor (e.g., DoubleVerify)
- Provide Client ID and Reporting ID

We would like to understand the API support and limitations for this functionality.

### Our questions:

1. API Creation / Update

   - Is it possible to create or update Third-party Measurement settings for Demand Gen campaigns using the Google Ads API?
   - If yes:

     - Please specify the API resource(s) involved (e.g., Campaign, CampaignExtensionSetting, CustomMeasurement, etc.).
     - Please share sample mutate requests or field mappings.
     - Please confirm whether this is supported for Demand Gen campaigns specifically.

2. API Retrieval / Read

   - Is it possible to retrieve existing Third-party Measurement configurations (vendor, client ID, reporting ID) via:

     - Google Ads API resources, or
     - GAQL queries?
   - If yes:

     - Please provide the GAQL query or resource fields that expose this data.

3. If Not Supported

   - If Third-party Measurement for Demand Gen campaigns cannot be created, updated, or retrieved via the Google Ads API, please confirm:

     - That this feature is UI-only (Google Ads dashboard).
     - The reason (e.g., limited Demand Gen coverage, vendor-side integration, policy or product limitation).
     - Whether this limitation applies to all third-party vendors (e.g., DoubleVerify, IAS, MOAT).

4. Documentation Confirmation

   - If available, please share official documentation or release notes confirming the API availability or lack of support for Third-party Measurement in Demand Gen campaigns.

This information is important for us to determine whether this feature should be:

- Fully supported in our application,
- Marked as UI-only, or
- Explicitly excluded from API-based workflows.

Thank you for your guidance.