Keyword status mismatch

[Kostas]

After the recent changes in keyword statuses, it appears there is a
problem with keyword statuses.

In the API, the KeywordStatus has not changed. So Keywords are either
"Normal" (corresponds to new status "Active"), "OnHold" (corresponds to
new status "Inactive"), Disapproved, or Deleted. I'm assuming this was
done so that existing code would not break.

But in the reports we generate through the API we are now seeing the
keyword status of "Active" (and I'm assuming we would also be seeing
"Inactive" if we had inactive keywords)

Are there any plans to change this so that the keyword statuses are
consistent between the reports and the KeywordStatus in the API? Or
should we simply convert one status to the other?

Several months ago I had notified Google about a mismatch in other
statuses between the API and the API-generated reports. Google said
that this should not happen and they would investigate, but I never
heard back from them. Is this something that you are still looking
into?

[Groople]

Hi Kostas

> Are there any plans to change this so that the keyword statuses are
> consistent between the reports and the KeywordStatus in the API? Or
> should we simply convert one status to the other?

As the AdWords API is still in "Beta" state converting states might be
the only workaround for the moment.

> Several months ago I had notified Google about a mismatch in other
> statuses between the API and the API-generated reports. Google said
> that this should not happen and they would investigate, but I never
> heard back from them. Is this something that you are still looking
> into?

For sure this should not happen and I think there will be a re-naming
offensive before the final "Production/Stable" release of the AdWords
API. This is why it is still "Beta"...

Regards,
Tom

[tomasvdb]

at the moment the mapping from the UI to the API seems as follows:
Active -> Normal
InActive -> Onhold
Disabled -> Disabled

[Richard Jones]

It'd be really nice if the column names in custom reports were in any
way related to the names given in the custom report options (eg.
Impressions vs "imps"). Having said that, it'd also be a pain for us
to transition, at least without warning.

Rich.

--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com

[Rajiv M]

>From what we've been told, tomasvdb's post is indeed the way to
translate between the UI and API keyword statuses. Further, we were
told NOT to expect the API statuses to change their values.

This actually helps us, as the updated WSDL doesn't break our dependent
code, but I can see how having two sets of statuses can cause
headaches.