Change status service is not returning any change

[Julian Matias Grilli]

Hello! 

I am working on the migration from https://developers.google.com/adwords/api/docs/reference/v201809/CustomerSyncService#get to get the campaign changes to https://developers.google.com/google-ads/api/docs/change-status#java using GAQL to get that information but I am not able to get the changes I madre in the Google Ads UI.

Does the changes take too much time to be reflected and available to be query from "change_status" resource? 

I know that I am creating the query in the correct way since I was able to get some of the expected changes in only one test I made.

This is my GAQL query:

SELECT change_status.campaign, change_status.last_change_date_time, change_status.resource_status, change_status.resource_type, change_status.ad_group, change_status.ad_group_ad, change_status.ad_group_bid_modifier, change_status.ad_group_criterion, change_status.ad_group_feed, change_status.campaign, change_status.campaign_criterion, change_status.campaign_feed, change_status.feed, change_status.feed_item FROM change_status WHERE change_status.last_change_date_time DURING LAST_14_DAYS AND change_status.campaign = 'customers/{customerId}/campaigns/{campaignId}' LIMIT 10000.

The tests I made:

- Change Campaign name

- Remove Campaign Negative Keyword

- Add new Keyword

- Change Adgroup name

- Updated Campaign Type

- Updated Budget

- Update Campaign Status

After the mentioned changes above I didn't get any response after exectute: 

 GoogleAdsClient googleAdsClient = googleAdsClientFactory.getGoogleAdsClient();

        try (GoogleAdsServiceClient client = googleAdsClient.getLatestVersion().createGoogleAdsServiceClient()) {

            GoogleAdsServiceClient.SearchPagedResponse response = client.search(customerID, query);

            return response;

        }

According the documentation, after that we should iterate over the response wich means

response.iterateAll() to get each row, but we get an empty list of changes..

Questions:

1) Is there something that is not working properly at Google Ads API or maybe am I doing something wrong? Please Let me know if you need more details about how I am implementing this.

2) Sometimes while I am trying to debug it (for the only case I mentioned that it worked for me, I mean, I got only some changes that I made) it got an outOfMemory error:

Exception in thread "http-nio-8080-exec-1" java.lang.OutOfMemoryError: Metaspace

is that a known issue for you? 

Thanks in advance.

Julian

 

[Google Ads API Forum Advisor]

Hi Julian,

Thank you for raising your concern.

Please see my response below to the questions you've mentioned on this concern:

Does the changes take too much time to be reflected and available to be query from "change_status" resource? 

-When the changes is already available in the Change History, then it can also be retrieved using change_status.

Is there something that is not working properly at Google Ads API or maybe am I doing something wrong? Please Let me know if you need more details about how I am implementing this.

-You can inspect this document to check the configuration of your API request for change_status. However, so that I can further investigate the issue, could you provide the following details?

• Complete request and response logs with request ID generated on your end where data is being returned before the changes that you've made
• Complete request and response logs with request ID generated on your end without data
• Screenshot of logs in the Change History that you are expecting in the API response of change_status

If you haven't enabled the logging of the API transactions for the specific client library that you are using, then please refer to this guide.

2) Sometimes while I am trying to debug it (for the only case I mentioned that it worked for me, I mean, I got only some changes that I made) it got an outOfMemory error:

Exception in thread "http-nio-8080-exec-1" java.lang.OutOfMemoryError: Metaspace

-You can try the workaround provided on this document. You may just note of this part of the document "The timeout currently cannot be increased beyond a maximum value of 1 hour. If this becomes an issue, it is usually best to split the query up and execute the chunks in parallel; this avoids the situation where a long running request fails and the only way to recover is to trigger the request again from the start.".

You can provide the details that I am requesting via Reply privately to author.

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2JByw4:ref