Unknown targeting value

[Samir Sabri]

Hello

At the change history for targeting changes, we notice that we have unknown targeting value, as attached snapshot, as, the ids we have used are taken from the geo locations csv file version 2021-04-16 , while looking at https://developers.google.com/adwords/api/docs/appendix/geotargeting , current version is 2021-07-27, does that mean that we are using outdated locations ids?

Also, is there an API endpoint to download the latest CSV file?

Regards, Samir

[Google Ads API Forum Advisor]

Hi Samir,

Thanks for reaching out. Can you please privately provide us with the request and response logs so that we can look at which geo targets resulted in the unknown change? If you are aware of the geo targets that did result in an unknown value and provide an example, this will help our investigation. 

Thanks,
Matt
Google Ads API Team

Matt Google Ads API Team

ref:_00D1U1174p._5004Q2LUeZh:ref

[Samir Sabri]

Hello Matt

I have replied privately, can you please confirm that you got my reply.

p.s: I've searched for the unknown location value in the latest geo targets locations CSV file and found the id as ACTIVE, example: Postal Code 9030700

your support is highly appreciated.

Thank you,

[Zakwan Alhajjar]

I am facing the same issue. Any idea??

[Google Ads API Forum Advisor]

Hello,

It seems you may not be receiving some messages from our team. The last reply from our team was:

To answer your question on your initial post, I would also suggest to use the current version as there are updates to location and there might be locations that will no longer work.
"... the ids we have used are taken from the geo locations csv file version 2021-04-16 , while looking at https://developers.google.com/adwords/api/docs/appendix/geotargeting , current version is 2021-07-27, does that mean that we are using outdated locations ids?"

Moving forward to this question, I am afraid that there is no API endpoint to download the latest CSV. You will need to download it manually via this link.

"Also, is there an API endpoint to download the latest CSV file?"

As for the issue, could you provide the following details on this private thread to further investigate the issue?

• Complete SOAP request and response logs generated for uploading the location that resulted on this issue
• Screenshot of the whole UI where we can see the logs in Change History
• Customer ID

Regards,

[Samir Sabri]

Hello Matt, thanks for your response, I have sent a private reply with required details.

[Google Ads API Forum Advisor]

Hi Samir,

Thank you for providing the requested details.

Upon checking some of the IDs that have been uploaded using API and encountered the issue, it appears that it is existing in the updated CSV and the corresponding canonical name should be seen in the UI. However, there appears to be an issue with the UI that not showing the correct canonical name.

With this, I would suggest raising this concern to the product team via this link as the UI related issues are within their scope.

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2LUeZh:ref

[Samir Sabri]

Thanks Ernie for following up with me on this issue. So, do you mean that it's only a matter of UI issue? and nothing wrong with our used ids?

[Google Ads API Forum Advisor]

Hi Samir,

Thank you for the reply.

Yes, upon checking the account and some of the geo Ids, I can confirm that the Ids you've set are existing in the list but encountering an issue in the UI. With this, please try to reach out to the product team via this link for this UI issues.

[Samir Sabri]

Thanks Ernie