Hello Team,
Issue Summary
I am working on automating programmatic proposal creation in Google Ad Manager using the SOAP API. My key requirement is to map an external Seat ID (for example, 1256788) to its corresponding Buyer ID in Ad Manager—for instance, to get “MEC Ireland (Display&Video 360)(DV360 ID:1256788)” programmatically just as the GAM UI lookup allows.
Network Code: 20346936
Current Process
I am using the following SOAP request through the PublisherQueryLanguageService to extract Buyer and Seat IDs:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns1="https://www.google.com/apis/ads/publisher/v202505">
<soapenv:Header>
<ns1:RequestHeader soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0">
<ns1:networkCode>20346936</ns1:networkCode>
<ns1:applicationName>[my-app-name]</ns1:applicationName>
</ns1:RequestHeader>
</soapenv:Header>
<soapenv:Body>
<ns1:select>
<ns1:selectStatement>
<ns1:query>
SELECT BuyerAccountId, Name, PartnerClientId, EnabledForPreferredDeals, EnabledForProgrammaticGuaranteed, IsAgency, ParentId
FROM Programmatic_Buyer
LIMIT 500
</ns1:query>
</ns1:selectStatement>
</ns1:select>
</soapenv:Body>
</soapenv:Envelope>
Problem
For Seat IDs (like 1256788), the GAM UI instantly finds and displays the buyer (“MEC Ireland (Display&Video 360)(DV360 ID:1256788)”).
When querying via the API as shown above, the mapping between the seat ID and Buyer ID is missing. seat ID is not present in the PartnerClientId field, making it impossible to map them programmatically.
I have also reviewed the dimensions available in ReportService (PROGRAMMATIC_BUYER_NAME, PROGRAMMATIC_BUYER_ID, DSP_SEAT_ID), but these do not provide a reliable universal mapping.
Request
Can you please confirm if there is any supported API method or recommended process to map an Seat ID to its Buyer ID in Ad Manager via API or reports, reliably for all buyers?
If such a mapping exists in the UI, is it possible to expose it via API, or is there a hidden endpoint or workflow that can be leveraged?
Any best practices or future roadmap to bridge this mapping gap would be greatly appreciated.