Hi Dian,
Thanks for sharing your solution. To summarize, you can generate a
list of only "additional" keywords be excluding the BROAD version of
your source keyword.
Best,
- Eric
On Feb 25, 5:32 am, "web.dev" <perl....@gmail.com> wrote:
> Hi Eric,
>
> thank you for your reply!
>
> I ended up with the same ideas you propose and I would like to share a
> possible solution with the community (perhaps you could comment it if
> anything is wrong).
>
> Althought your solution seems to be logical it doesn't exactly solve
> the problem. Here is an example:
> * I trigger a BROAD search on "gesetzliche krankenversicherung" (BROAD
> is set as type for the results too)
> * one of the results is "gesetzlich krankenversicherung" (a stemmed
> version of the keyword requested)
> * however the NGRAM GROUP is the strong keyword "krankenversicherung" ->
> following your ideas this should be an "additional" keyword
>
> * well - it's not (referencing the Google Keyword Tool :-)
>
> So I ended up thinking - why not using the stemmed version as a stop
> keyword?
> I use the ExcludedKeywordSearchParameter where I put my stemmed
> keyword. After a couple of tests the results match (more or less - at
> least there are no "related" keywords mixed in the "additional"
> keywords) the results from the keyword tool.
>
> In my opinion the real worthy keywords are generated after stemming
> the main keyword and trying to differentiate between "related" and
> "additional" based on it.
>
> Best regards,
> Dian
>
> On 22 Feb., 17:04, AdWords API Advisor <adwordsapiadvi...@google.com>
> wrote:
>
>
>
> > Hi Dian,
>
> > The NgramGroupsSearchParameter doesn't match your use case perfectly,
> > and that is because keywords can only belong to one ngram group. If
> > you include the requestedAttributeType NGRAM_GROUP you can see which
> > group a returned keyword is in. The keyword "betriebliche
> > altersvorsorge" is popular enough to have it's own ngram group, which
> > is why it doesn't show up when you filter for the "altersvorsorge"
> > ngram group.
>
> > If you want to split keywords by "related" and "additional", your best
> > bet may be to do the following:
>
> > - Don't use the NgramGroupsSearchParameter and return all types of
> > keywords.
> > - Request the NGRAM_GROUP attribute with your results.
> > - For all ideas where the NGRAM_GROUP contains the source keyword,
> > treat as "related".
> > - For all ideas where the NGRAM_GROUP doesn't contain the source
> > keyword, treat as "additional".
>
> > Best,
> > - Eric Koleda, AdWords API Team
>
> > On Feb 22, 9:58 am, "web.dev" <perl....@gmail.com> wrote:
>
> > > Unfortunately the results generated after using n-gram groups didn't
> > > work for me!
> > > I have tested using the NgramGroupsSearchParameter but the results did
> > > not fulfill my expectations - matching the way the external Keyword
> > > Tool generated "related" vs. "additional" keywords was not successful.
>
> > > The example (using the PHP lib):
> > > $selector->searchParameters = array($relatedToKeywordSearchParameter,
> > > $keywordMatchTypeParameter
> > > //, new NgramGroupsSearchParameter(array("altersvorsorge"))
> > > , new LanguageTargetSearchParameter(array(new LanguageTarget('de'))));
>
> > > The results are:
> > > 1) betriebliche altersvorsorge
> > > 2) altersvorsorge rentenversicherung
> > > ...
> > > If I uncomment the line regarding n-gram the first result is not
> > > returned - so it is an "additional" keyword (since it's ngram group is
> > > the keyword itself). But according to the Keyword Tool this is a
> > > "related" and not an "additional" keyword - it is even the most
> > > related one!
>
> > > Any suggestions on this topic? Google Team?
>
> > > Thanks in advance,
> > > Dian
--
You received this message because you are subscribed to the Google Groups
"AdWords API Forum" group.
To post to this group, send email to adwords-...@googlegroups.com.
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en.
