On April 17, 2020, app ads and app engagement ads that do not serve will have their statuses changed automatically from
What do you need to do?
If you’re not interested in the disabled ads, you don’t need to take any action. Only beware that the number of report rows returned by your query may change. For example, if your queries have a condition to get only enabled ads, you may see fewer report rows.
If you still wish to see the performance data of the disabled ads, make sure your report queries also include the disabled ads. Note that as they don’t serve anymore, these ads won’t accrue any more performance stats beyond the above-mentioned date.
In case you need more information on reporting, follow the below links:
For the Google Ads API, For the AdWords API, As always, if you have any questions, feel free to reach out to us on the AdWords API and Google Ads API forum.
ENABLED
to DISABLED
. For each ad group in App campaigns, only the first created ad is ever eligible to serve, so we’re disabling other ads in the same ad group to prevent confusion. This means that you may see some changes in the number of report rows if your queries have a condition that includes ad_group_ad.status
for the Google Ads API or AdGroupAdStatus
for the AdWords API.What do you need to do?
If you’re not interested in the disabled ads, you don’t need to take any action. Only beware that the number of report rows returned by your query may change. For example, if your queries have a condition to get only enabled ads, you may see fewer report rows.
If you still wish to see the performance data of the disabled ads, make sure your report queries also include the disabled ads. Note that as they don’t serve anymore, these ads won’t accrue any more performance stats beyond the above-mentioned date.
In case you need more information on reporting, follow the below links:
For the Google Ads API, For the AdWords API, As always, if you have any questions, feel free to reach out to us on the AdWords API and Google Ads API forum.