V13 data discrepancy between the API data and the Google Ads console

49 views

Skip to first unread message

laila ribke

unread,

Apr 13, 2023, 4:55:57 AM4/13/23

to Google Ads API and AdWords API Forum

Hi all, I´ve just modified my connector to use the API V13.

Before the V11 sunset, with the V11, the data extracted from the API matched 1:1 to the data displayed in the Google Ads console.

But since we switched to the V13, I get les costs and I have a lot of discrepancies between the data pulled from the API and the Google Ads console.

I didn´t find the source of the problem.

Did it happen to anyone else, any clues or tips?

Thanks

Laila

Google Ads API Forum Advisor

unread,

Apr 13, 2023, 9:54:56 AM4/13/23

to laila...@gmail.com, adwor...@googlegroups.com

Hi Laila,

Thanks for reaching out to the Google Ads API Team. I hope you are doing well today.

It appears that you have already opened an email thread with the subject title “data discrepancy between v11 and v13” to us and we have already responded. Let me reiterate below for reference.

Kindly note that we have limited knowledge on third-party tools like Airbyte as our team specializes in Google Ads API related concerns only.

Are you able to provide us with complete request and response logs with the request-id generated when you encountered this error? This is so we can check on our end as well and investigate further. Additionally, you may also check with Airbyte if they can help you with your concern.

Reference links:

Google Ads API: https://developers.google.com/google-ads/api/docs/start
request: https://developers.google.com/google-ads/api/docs/concepts/field-service?hl=en#request
response: https://developers.google.com/google-ads/api/docs/concepts/field-service?hl=en#response
request-id: https://developers.google.com/google-ads/api/docs/concepts/call-structure?hl=en#request-id

In line with this, we recommend using that thread instead to avoid confusion and for better tracking.

Have a great day.

Regards,

Google Ads API Team