That's what I was guessing would be the case. I've navigated around it by
writing a very simple processor (PHP) to parse a list of keywords and
attempt to identify the user's intention. Suggestions for improvement
welcome.
---
static function ProcessExpertKeywordList($keywords) {
Hi Stephen,
Stefan is 100% right, you'll need to do the parsing in your side and
appropiately use NegativeAdGroupCriterion vs. BiddableAdGroupCriterion
objects in combination with the Keyword.matchType.
Best,
-David Torres - AdWords API Team
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=
I don't think the API is aware of the mentioned notation. There are
individual data types for match types and biddable/negative keywords that
can be used. Also think about error handling in case the user gets the
syntax wrong. That should probably be dealt with in your client code, so you
need
Eric, et. al.
For a project, we are looking to provide a way for users to add keywords to
the system using the familiar notation for broad, phrase, negative, etc. The
trouble is that I can't simply pass these along to AdWords to interpret, as
I'm guessing that I need to set the proper flags on