Adgroup Status Reason discrepancies from Web UI and API

[Jefferson Cechinel]

Hi there! I have an account with several campaigns and many Adgroups of these campaigns were paused due low activity. I got this information from the Web UI. I'm developing an implementation to re enable those Adgroups using the API. The problem is that when I fetch those Adgroups with primary status = PAUSED and primaryStatusReason = AD_GROUP_PAUSED_DUE_TO_LOW_ACTIVITY the results come with different primary status reasons and none of them shows a reason of low activity (ID 18).

Here is the query im using to fetch:

'SELECT
ad_group.id,
ad_group.name,
ad_group.status,
ad_group.primary_status,
ad_group.primary_status_reasons
FROM ad_group
WHERE ad_group.primary_status = PAUSED
AND ad_group.primary_status_reasons CONTAINS ANY (AD_GROUP_PAUSED_DUE_TO_LOW_ACTIVITY)
ORDER BY ad_group.id'

The query returns the exact same amount of PAUSED Adgroups due low activity that is shown in web UI but all the Adgroups returned from the query doesn`t have in its primaryStatusReasons list the ID related to AD_GROUP_PAUSED_DUE_TO_LOW_ACTIVITY which make impossible to determine the exact Adgroups that were paused due low activity.

I need some help with this. Can someone tell me why the AD_GROUP_PAUSED_DUE_TO_LOW_ACTIVITY (id 18) is not in the primaryStatusReasons list returned from the query? I see others reasons in the list of each Adgroup but none of them has the id 18.

Thank you in advance.

[Google Ads API Forum Advisor]

Hi,

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

Could you please provide us with the complete API logs (request and response with request-id and request header) generated at your end while fetching the report via API. Also, provide us with the uncropped UI screenshot of the same report so that we can investigate this issue further from our end.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.
 

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

Thanks,
 

Google Ads API Team