Responses in CSV format for Google Ads API ?

[Zhisheng Zhou]

Hi. Is that possible to let Google Ads API(https://googleads.googleapis.com/v8/customers/{customerID}/googleAds:search) to return reports data in CSV format instead of json?

Thanks,

Sam

[Pete Lavetsky (AdWords API Guru)]

Hey Sam,

Currently I don't believe it is possible to get it back in CSV : https://groups.google.com/g/adwords-api/c/oBtx_3IKEEA/m/Uge9x6B-CwAJ

Pete

[Zhisheng Zhou]

Thanks, Pete!

[Google Ads API Forum Advisor]

Hi Sam and Pete,

@Pete, thank you for providing your insights here.

@Sam, the API response is indeed returned in JSON format only. With this, you will need to create a preprocess on your end that after receiving the API responses, it will transfer the data to a CSV.

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2Ixu7Y:ref

[Doron Hadar]

Hi Ernie,

Is there a plan to provide either CSV or some kind of compression of the responses? The data volume in the JSON response is between 10 to 20 times the CSV volume, and over 100 times of a compressed CSV. For instance, I''ve created a daily report in which the compressed CSV file weighs less than 40MB, but the JSON responses are over 4.5GB! 

There is a cost attached to the transfer of such volumes, and currently there is no other way to automate reports as the UI won't even attach compressed files in an email or place them in a repository like Drive.

Thanks,

Doron

[Google Ads API Forum Advisor]

Hi Doron,

Thanks for the reply.

Allow me to raise a feature request to my team about the concern on your latest reply, subject for review. For now, please follow our blog to receive updates and new releases.

In addition, since the Google Ads API does not support formatting or file output, I would suggest following the recommendation on this document for implement CSV formatting in your API.

[Doron Hadar]

Hi Ernie,

Thank you for the reply. I hope there will be a new feature for that.

Unfortunatly, the workaround you offered is not the answer we're looking for. We know how to parse and format the data once recieving it (and we actually insert it to a data warehouse). However, network traffic volume will still be the same (e.g. 4.5GB instead of 40MB), and this is what we're paying for (using a 3rd party SasS data pipeline platform).

Thanks,

Doron

[Google Ads API Forum Advisor]

Hi Doron,

Sorry to hear that the provided workaround is not applicable on your end.

I have already raised a feature request to my team for this, subject for review. Since our team doesn't have an access to the plan and timeline for this feature, then I would suggest to follow our blog as we will post there any relevant updates when become supported.