I'm trying to use
TargetingIdeaService to filter out low search volume keywords (actually, EAN numbers) before adding them to an ad group,
as I was previously advised.
I've been running this service on 1.3 million keywords, and it turned out that only 72,000 of them had the SEARCH_VOLUME attribute set.
If on the other hand, I add all these keywords to a few ad groups (which I did), I can see that 767,000 of them are eligible (systemServingStatus == ELIGIBLE).
I was hoping that TargetingIdeaService would help me identify which keywords are Low Search Volume, and which ones are Eligible, but as far as I can see, the presence of a search volume number in TargetingIdeaService, and the systemServiceStatus of this keyword in an ad group (given similar geo and language targets) seem to be very different matters.
Did I miss something? Can I accurately use TargetingIdeaService to identify low search volume keywords before adding them to my ad groups?
-----
For information, here are the parameters I sent to TargetingIdeaService:
IdeaType=IdeaType::KEYWORD
requestType=RequestType::STATS
requestedAttributeTypes=[KEYWORD_TEXT, SEARCH_VOLUME]
searchParameters=[RelatedToQuerySearchParameter([keyword1, keyword2, ...])]
I tried with and without additional searchParameters, such as LanguageSearchParameter, LocationSearchParameter, NetworkSearchParameter, and the numbers did not change much, to my surprise (just ~10% more keywords with search volumes when removing all parameters).
Thanks in advance for any insight!