negative_geo_target_type, trigger: DONT_CARE

[FW API]

Hi.

Upon creating a search campaign, we received the following error.

_______________

setting_error: SETTING_VALUE_NOT_COMPATIBLE_WITH_CAMPAIGN } message: "The value of this setting type is not compatible with the campaign type." trigger { string_value: "DONT_CARE" } location { field_path_elements { field_name: "operations" index: 0 } field_path_elements { field_name: "create" } field_path_elements { field_name: "geo_target_type_setting" } field_path_elements { field_name: "negative_geo_target_type" } }

________________

What we don't understand. DONT_CARE is not even a member of `NegativeGeoTargetTypeEnum.NegativeGeoTargetType`.

So how can that be the trigger?

In fact our Application uses `NegativeGeoTargetTypeEnum.NegativeGeoTargetType.PRESENCE_OR_INTEREST` throughout.

That is part of the current API version.

https://developers.google.com/google-ads/api/reference/rpc/v13/NegativeGeoTargetTypeEnum.NegativeGeoTargetType

So what happens there?

This error is replicable and happens for different customer accounts since yesterday.

Your Stefan

[Google Ads API Forum Advisor]

Hello,

For us to investigate your concern further, could you please provide to us the complete API request and response logs with request-id and login-customer-id that are generated on your end? Kindly share the requested information via reply privately to author option.

Links highlighted on this thread.

• request - https://developers.google.com/google-ads/api/docs/concepts/field-service#request
• response - https://developers.google.com/google-ads/api/docs/concepts/field-service#response
• request-id - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id
• login-customer-id - https://developers.google.com/google-ads/api/docs/concepts/call-structure?hl=en#cid

Regards,

Google Ads API Team

 

ref:_00D1U1174p._5004Q2kqSQn:ref

[Google Ads API Forum Advisor]

Hello All - 

The presence of DONT_CARE in the error response appears to be a bug, and I'm working to get this fixed in the API.

Meanwhile the reason these errors are being returned is that PRESENCE_OR_INTEREST is no longer an acceptable value for the negative_geo_target_type field. See this blog post for more details as to why.

Please let me know if you have further questions.

Best,

Ben Karl Google Ads API Team

ref:_00D1U1174p._5004Q2kqSQn:ref

[姚飞虎]

I am using negative_geo_target_type  = PRESENCE_OR_INTEREST,but I don't konw whether I need handle that.

What's the meaning of the word in red line ? Is it google will fixed that ? is that will donnot handle the parameter by developer ?

[Google Ads API Forum Advisor]

Hello - 

That section is saying that any existing Campaign that has negative_geo_target_type = PRESENCE_OR_INTEREST will be modified automatically by our systems so that negative_geo_target_type is set to PRESENCE.

Campaigns will be modified gradually over time, so you can use the two queries to check whether your existing campaigns have been modified or not.

Hope that helps.

Thanks,