V17 prompts an error: Setting the page size is not supported. Search Responses will have fixed page size of '10000' rows.

[zhiwei hu]

When I use the googleAds:search method in version 17, I get the error Setting the page size is not supported. Search Responses will have fixed page size of '10000' rows. I see in the documentation that the pageSize parameter can be set, and I want to know why. The requestId is 9E0j5J9m3Qmjne_uyVRCKQ

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

Kindly note that it's an intended behavior, As starting with version 17 of the Google Ads API, setting the page_size to a value other than 10,000 will return a PAGE_SIZE_NOT_SUPPORTED error. I would suggest that you refer to the Paging Through Results for more information.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02tJb4z:ref" (ADR-00245132)

Thanks,
 

Google Ads API Team

Register for the upcoming workshop: Performance Max and the Google Ads API!
 

[zhiwei hu]

Thanks for your reply. You said that setting more than 10000 will return this error, but I set the pageSize to 2000 and it still prompts an error.

[Google Ads API Forum Advisor]

Hi,

Kindly note that whatever the value you have set for page_size in v17 it will throw a PAGE_SIZE_NOT_SUPPORTED as setting the page size is not supported from v17, and will be unavailable in a future version. I would suggest not to use the page_size field from v17.

[Andrei Simonov]

How do I limit the number of query results now? Let's say I want to display the first 10 campaigns to the user. Later, if the user wants, they can load the next 10 campaigns, but they might not want to load them. If the page_size is always 10000, I will have to load all the campaigns and parse them regardless of the user's desire, right?

[don....@gmail.com]

Hello same issue, but we also do query like

SELECT ad_group.status, campaign.id,campaign.name,ad_group.id,ad_group.name,segments.ad_network_type,click_view.keyword_info.match_type,click_view.keyword_info.text,metrics.clicks,click_view.ad_group_ad,click_view.keyword,segments.click_type,click_view.gclid
            FROM click_view

            WHERE ad_group.status IN ("ENABLED","PAUSED") AND segments.date = "2024-08-10"

using PHP SDK for v17 and we get

Fatal error: Allowed memory size  error because 10000K rows with a lot of string values just too much of the data especially after its processed by PHP SDK mapper

Please advise what to do in cases like this? SDK becomes unusable...

[Google Ads API Forum Advisor]

Hi,

Kindly note that it's an intended behavior of API, starting with version 17 of the Google Ads API, setting the page_size to a value other than 10,000 will return a PAGE_SIZE_NOT_SUPPORTED error. I would suggest that you refer to the Paging Through Results for more information.

As an alternative way you can try using next_page_token. If your account contains 50,000 keywords, the result set will contain 10,000 GoogleAdsRow objects in the first response, along with a next_page_token.

To retrieve the next 10,000 rows, send the request again, but update the request's page_token to the response's next_page_token. Note that next_page_token is not populated in the response that contains the last batch of rows. Hope this helps. 

[Tjerk Ameel]

Hi, did you find a solution for this?

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

Kindly note that it's an intended behavior of API, starting with version 17 of the Google Ads API, setting the page_size to a value other than 10,000 will return a PAGE_SIZE_NOT_SUPPORTED error. I would suggest that you refer to the Paging Through Results for more information.

As an alternative way you can try using next_page_token. If your account contains 50,000 keywords, the result set will contain 10,000 GoogleAdsRow objects in the first response, along with a next_page_token.

To retrieve the next 10,000 rows, send the request again, but update the request's page_token to the response's next_page_token. Note that next_page_token is not populated in the response that contains the last batch of rows. Hope this helps. 

Thanks,

 

Google Ads API Team

Feedback
How was our support today?

               
[2025-02-19 22:18:35Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02tJb4z:ref" (ADR-00245132)