Hi Oliver,
Thank you for the message and for bringing this up! I'd like to make sure I
understand your issue so I can bring it up with the rest of the team. Is
the problem that the API doesn't allow data to be downloaded in a .csv
format? Or is the issue that the structure of the data is different, for
example instead of retrieving a Campaign Performance report and seeing
AverageCpc in a column of a .csv file, now you need to select
metrics.average_cpc from the campaign resource using a GAQL query and
access average_cpc by iterating over the response?
If the latter, take a look at this guide
<https://developers.google.com/google-ads/api/docs/migration/reports>,
which outlines in great detail how to translate your AdWords Report
requests into Google Ads search requests. There's also this interactive
query builder
<https://developers.google.com/google-ads/api/docs/query/interactive-gaql-builder>
that
helps you construct GAQL queries before writing them into your application.
Both should be extremely useful when migrating your reports.
From a more general standpoint, we definitely recognize that migrating is
not a negligible amount of work, particularly migrating reporting
functionality. Because of this we're constantly trying to make improvements
to the API and client libraries to help make it easier. We currently have a
number of new guides and tools specifically intended to help with migration
that should be available soon.
At this point the exact EOL date for AdWords hasn't been determined, but
our planning does include consideration of where everyone is at with their
migration, as well as the current performance of the API and its level of
parity with the AdWords API. The main objective is to maintain a long
migration window so that everyone has time for a smooth migration.
Hope that helps! Please let me know if you have additional questions, or
further clarification on the problems you're having migrating report
requests.
Thanks,
Ben Karl, Google Ads API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
https://ads-developers.googleblog.com/search/label/google_ads_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
On 05/07/19 03:53:51 [email protected] wrote:
We find it very strange and frustrating that the new API does not provide a
standard way of downloading the data in CSV format. We're told to write our
own code to do this as mentioned here:
https://groups.google.com/forum/#!topic/adwords-api/L94G_cJax2g
The Adwords API documentation clearly encouraged users to try and get data
via reports as opposed to the Service API. It's now a massive blow to
users who followed your previous advice and built their apps around the
usage of reports.
Judging by the many complaints on this forum about the various limitations
and bugs in the new Ads API, and by the fact that a huge part of
downloading data via reports is no longer supported, having to migrate to
the new API in less than one year is a very significant challenge to us
and, as we can see here, to many users of the API.
1) Can we please ask you to consider supporting data download via reports
as this alone is a massive showstopper in the migration process?
2) Can we also please ask you to consider extending the period when the
Adwords API will stop working? One year is not enough to migrate large
apps especially when the new Ads API seems to have many serious issues
currently with performance and fundamental data structures as frequently
raised on this forum recently.
We've always found the Adwords API planning carefully took developers and
businesses needs into consideration more than any other similar API. We're
hoping you'll continue to listen to the many requests of other users on
this forum regarding the serious challenges we're currently facing with the
new API.
Regards
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/8c372244-f8df-450d-9bf4-45bb4ea6094c%40googlegroups.com
<https://groups.google.com/d/msgid/adwords-api/8c372244-f8df-450d-9bf4-45bb4ea6094c%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/ujqug27km00000000ak1le0006ikaky6gmjcc1j6go30c1g68r3achp%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
