Thanks for the quick answer. Is it possible to get an idea of what we will find in that documentation? If postal codes will be represented as criterion, can we get a list? Can we at least get a range so that we can deal with them until we get the final documentation?
Thanks in advance, Richard On Wednesday, March 14, 2012 5:25:26 AM UTC-4, Anash P. Oommen wrote: > > Hi Richard, > > We are working on updating the API documentation. We will update this > thread when this is done. > > Cheers, > Anash P. Oommen, > AdWords API Advisor. > > On Wednesday, 14 March 2012 01:47:06 UTC+5:30, Richard wrote: >> >> Hello, >> >> We use the CampaignCriterionService to read the Location targets >> associated with a campaign. Last night we received for the first time an >> unknown code in the 9 million range; 9032621 to be exact. After looking >> in the AdWords web interface, we where able to identify this new code as a >> postal code. The problem is that we have no idea what 9032621 represents >> using the API. I reviewed the system codes in the API documentation to see >> if these where added but they where not. I tried calling the >> LocationService and specifying the criterion id but that failed stating >> that "Location info not available for 9032621". Back to the web >> interface: Of the many accounts we manage, only one that we found has the >> option to target by postal code. >> >> Why do some accounts have the ability to target zip codes while others do >> not? Is this an upcoming feature? >> When will the API properly document and support these location criterion? >> >> Thanks, >> Richard >> >> On Wednesday, March 14, 2012 5:25:26 AM UTC-4, Anash P. Oommen wrote: > > Hi Richard, > > We are working on updating the API documentation. We will update this > thread when this is done. > > Cheers, > Anash P. Oommen, > AdWords API Advisor. > > On Wednesday, 14 March 2012 01:47:06 UTC+5:30, Richard wrote: >> >> Hello, >> >> We use the CampaignCriterionService to read the Location targets >> associated with a campaign. Last night we received for the first time an >> unknown code in the 9 million range; 9032621 to be exact. After looking >> in the AdWords web interface, we where able to identify this new code as a >> postal code. The problem is that we have no idea what 9032621 represents >> using the API. I reviewed the system codes in the API documentation to see >> if these where added but they where not. I tried calling the >> LocationService and specifying the criterion id but that failed stating >> that "Location info not available for 9032621". Back to the web >> interface: Of the many accounts we manage, only one that we found has the >> option to target by postal code. >> >> Why do some accounts have the ability to target zip codes while others do >> not? Is this an upcoming feature? >> When will the API properly document and support these location criterion? >> >> Thanks, >> Richard >> >> On Wednesday, March 14, 2012 5:25:26 AM UTC-4, Anash P. Oommen wrote: > > Hi Richard, > > We are working on updating the API documentation. We will update this > thread when this is done. > > Cheers, > Anash P. Oommen, > AdWords API Advisor. > > On Wednesday, 14 March 2012 01:47:06 UTC+5:30, Richard wrote: >> >> Hello, >> >> We use the CampaignCriterionService to read the Location targets >> associated with a campaign. Last night we received for the first time an >> unknown code in the 9 million range; 9032621 to be exact. After looking >> in the AdWords web interface, we where able to identify this new code as a >> postal code. The problem is that we have no idea what 9032621 represents >> using the API. I reviewed the system codes in the API documentation to see >> if these where added but they where not. I tried calling the >> LocationService and specifying the criterion id but that failed stating >> that "Location info not available for 9032621". Back to the web >> interface: Of the many accounts we manage, only one that we found has the >> option to target by postal code. >> >> Why do some accounts have the ability to target zip codes while others do >> not? Is this an upcoming feature? >> When will the API properly document and support these location criterion? >> >> Thanks, >> Richard >> >> -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
