Perf issue when downloading AD_PERFORMANCE_REPORT for Responsive Search Ad

[binbin yang]

Hi,

We noticed that downloading ad performance report for RSA was much slower than downloading other types of Ad (e.g. ExpandedTextAd). Sometimes it took more than 45min to retrieve the performance data for RSAs under 5 campaigns. Is there any known perf issue with the RSA performance report download?

[Google Ads API Forum Advisor Prod]

Hi Binbin,

Thank you for reaching out. Please give it a try to query the ad_group_ad resource via the Google Ads API instead.

Thanks and regards,
Xiaoming, Google Ads API Team
 

Xiaoming Google Ads API Team

ref:_00D1U1174p._5004Q2EqJ7A:ref

[duca...@gmail.com]

Hello Xiaoming,

As suggested here, we switched to Google Ads API and performance is still bad. It took more than 3 hours to download RSA from 3 campaigns. This seems too slow. 

Here is the query which you can try out. Please let us know if any optimization we can do from our side. Thanks !

Downloading via delegate: SELECT ad_group_ad.ad.final_urls, ad_group_ad.ad.final_mobile_urls, ad_group_ad.ad.id, ad_group_ad.ad.responsive_search_ad.descriptions, ad_group_ad.ad.responsive_search_ad.headlines, ad_group_ad.ad.responsive_search_ad.path1, ad_group_ad.ad.responsive_search_ad.path2, ad_group_ad.ad.tracking_url_template, ad_group_ad.ad.url_custom_parameters, ad_group_ad.ad.final_url_suffix, ad_group_ad.status, ad_group.id, ad_group.name, campaign.name

FROM ad_group_ad

WHERE campaign.id IN (88845851, 105682211, 105682451)

AND ad_group_ad.ad.type = 'RESPONSIVE_SEARCH_AD'

AND ad_group.status != 'REMOVED'

AND ad_group_ad.status != 'REMOVED'

ORDER BY ad_group_ad.ad.id ASC

Caihua.

[Google Ads API Forum Advisor Prod]

Hi Caihua,

Thank you for reaching out. From your report definition I could tell you have many fields. However, to improve the performance I would suggest you try to query part of the fields for each of the campaigns in one query instead of querying them all in one single query. 

Thanks and regards,
Xiaoming, Google Ads API Team

[Google Ads API Forum Advisor]

Hello Caihua,

Both my colleagues (Peter & Ernie) have already responded to you. It seems that you're not able to receive their response. For reference, I'm pasting its contents below :

"Our team will be needing the complete request and response logs especially with request ID instead generated for this report and where the issue occurred to further investigate. We would not be able to view our backend without the said information.

That being said, if you haven't enabled the logging of API transactions yet, then please do so by following this guide for .Net client library. If the issue that is mentioned on that Github tracker will occur, then I would suggest following up the author of the client library there as the request ID is important detail for checking this issue on our side.

That said, could you also share the requested details so our team can take a closer look at the issue?"

Please send those requested details via Reply privately to author option or via this email address (googleadsa...@google.com).

Regards,

Mark Kevin Albios Google Ads API Team

ref:_00D1U1174p._5004Q2EqJ7A:ref

[Caihua Du]

Hi team,

Let me know if anyone can help here, please. 

I can repost this question to the main forum if that helps. Thank you.

On Tue, Jun 15, 2021 at 11:59 PM Caihua Du <duca...@gmail.com> wrote:

Hi Team,

Gentle ping here if you have any update on this case. Thanks. 

On Wed, Jun 9, 2021 at 9:52 PM Caihua Du <duca...@gmail.com> wrote:

Hi Ernie and team,

If you have any update on this issue, please let us know. Thanks again for your help.

Caihua

On Mon, Jun 7, 2021 at 11:11 PM Caihua Du <duca...@gmail.com> wrote:

Thank you Ernie! Yes, it's really weird that if there is no Responsive Search Ad, I agree those calls should return immediately. 

Currently our logging level is set at summary level, which is to reduce our log volume from our end. We don't enable verbose/Information log yet. 

It looks like there was a bug in the dotnet client library as there is no request id in case of failure:Search Stream Logging: Request Id Empty? · Issue #283 · googleads/google-ads-dotnet · GitHub

For the requests I have shared earlier, I don't see the request id in the request. 

Would it be possible to correlate the data based on the customer id and request body to find the corresponding request from the backend? If Devtoken is needed, I can provide that info too. Thanks!

On Sun, Jun 6, 2021 at 8:39 PM Google Ads API Forum Advisor Prod <adsapifor...@gmail.com> wrote:

Hi Caihua,

I work with Xiaoming and let me provide support to your concern.

Upon checking the provided logs and your account, I can say that the error shouldn’t have happened because the campaign IDs specified in the query don’t have any responsive search ad, therefore querying of this API request should be faster. Also for this reason, the error should not occurred as it usually happens when the data being processed by the API is large, but this is not the current situation.

With this, so that our team can further investigate, could you provide the complete request and response logs especially with request ID generated on your end? If you haven't yet, logging can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link.

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2EqJ7A:ref

[Google Ads API Forum Advisor]

Hi Caihua,

It appears that you did not receive the replies of our team that were sent privately. With this, allow me to reiterate the reply that we sent and you can see it below:

Our team will be needing the complete request and response logs especially with request ID instead generated for this report and where the issue occurred to further investigate. We would not be able to view our backend without the said information.

That being said, if you haven't enabled the logging of API transactions yet, then please do so by following this guide for .Net client library. If the issue that is mentioned on that Github tracker will occur, then I would suggest following up the author of the client library there as the request ID is important detail for checking this issue on our side.

You can provide it via Reply privately to author option. If this option is not available, then you can send it on this email alias instead googleadsa...@google.com.