
Hi,
Thanks for reaching out to Google Ads API Support.
With regards to your concern, as mentioned on our Blog post, on April 24, 2023, we will start performing any necessary auto-migration of fields to the new default values until no more invalid combinations exist. The auto-migration will occur on a per-campaign basis. You can confirm that the migration is complete for a Google Ads account by checking that these two queries return zero rows.
This means that Google Ads will auto migrate the data with PRESENCE_OR_INTEREST to PRESENCE on the negative_geo_target_type report field until there’s no data consisting the PRESENCE_OR_INTEREST found on the Google Ads account. The invalid combination is when the data consists of the PRESENCE_OR_INTEREST on the negative_geo_target_type report field, thus migrating this said data to PRESENCE.
This also states that you may check if the migration is done or complete when you query the given example on the blog and the response to the request body is zero rows or empty results. Upon checking this on our end the PRESENCE_OR_INTEREST still works and doesn't return zero rows. This is because migration is still ongoing, however you cannot set the negative_geo_target_type report field since it will return SettingError.SETTING_VALUE_NOT_COMPATIBLE_WITH_CAMPAIGN error.
Let me know if this clarifies your concern.
Links included in this email:
Regards,
![]() |
Google Ads API Team |
Hi,
Thanks for getting back with us.
With regards to your concern, there is no specific date mentioned on the Blog post as to when the migration will be done. Unfortunately, we also don’t have the specific information related to this concern. You can confirm that the migration is complete for a Google Ads account by checking that these two queries return zero rows:
SELECT campaign.id, campaign.geo_target_type_setting.positive_geo_target_type, campaign.advertising_channel_type FROM campaign WHERE campaign.advertising_channel_type IN ('DISPLAY', 'SEARCH', 'SHOPPING') AND campaign.geo_target_type_setting.positive_geo_target_type = 'SEARCH_INTEREST' LIMIT 1
SELECT campaign.id, campaign.advertising_channel_type, campaign.geo_target_type_setting.negative_geo_target_type FROM campaign WHERE campaign.geo_target_type_setting.negative_geo_target_type = 'PRESENCE_OR_INTEREST' AND campaign.advertising_channel_type IN ('DISPLAY', 'PERFORMANCE_MAX', 'SEARCH', 'SHOPPING') LIMIT 1
Additionally, as mentioned on the blog you may start setting the location target settings of negative_geo_target_type to PRESENCE to avoid the errors.
Links included in this email:
Regards,