Hi Sven,
Thank you for reaching out to Google Ads/AdWords API support with your API discrepancies issue. Unfortunately, we have no visibility on your 3rd party Ads API access provider and cannot support their platform directly. For full support you can ask from your 3rd party Ads API access provider could you send us a 'DEBUG' log level request and response log of raw API communications showing the reports that have a discrepancy?
The request and response appears similar to the
JSON Mappings in our REST documentation with additional headers and information such as
request Id. Here are logging instructions for our
Java,
.NET,
PHP,
Python,
Ruby and
Perl Ads API Client Libraries.
If you are using our
REST interface then the full multi line curl command line is a request log and adding curl command line option '-i' will also generate a response log.
Once you have the logs, you can try to match them to a report screen in the Ads UI that has the same same row segmentation and filters. If you are experiencing a discrepancy between the Ads API output and the equivalent Ads UI screen then we are the support channel to pursue. If the reports from the Ads API match the Ads UI then I suggest you reach out to our
product support team for further assistance.
With that being said, I can guess that the AdWords API worked differently, the
Keywords Performance Report was a
single attribution report that included more than just keywords, in your old non Performance Max campaigns the totals would be higher than in than in the equivalent Ads API
keyword_view. The
keyword_view resource will only show metrics that are associated with keywords.
Moreover, Performance Max campaigns don't yet support keywords nor do they have Ads objects and if you have recently changed over to Performance Max campaigns then the keyword reports and ads reports won't have any metrics from Performance max campaigns. The logs will give us certainty on my educated guesses.
Regards,
 |
Aryeh |
Google Ads API Team |
|
|
|

ref:_00D1U1174p._5004Q2d4OuL:ref