Different results in Web Interface and API

[zinch...@seo-studio.ua]

I have a problem with getting some url data by API.

Web GUI (Screenshot.png) says that domain have 27 words (and download only it to CSV).

Targeting setting on GUI and by API is same (region, language and other),

but API returns 800 results for the example domain

One from 10 urls show by API (or web) not valid words and words amount.

Does anybody know why data is different fo some urls on web gui and api?

/* part of php code */

...

$relatedToUrlSP = new RelatedToUrlSearchParameter();

$relatedToUrlSP->urls = array($url);

$selector->searchParameters[] = $relatedToUrlSP;

...

/* end code */

Api result:

object(TargetingIdeaPage)#30 (2) {

["totalNumEntries"]=> int(800)

["entries"]=> array(800) {

[0]=> object(TargetingIdea)#27 (1) {

["data"]=> array(3) { ....

[Joyce Lava]

Hi,

Could you please confirm if you set the NetworkSearchParameter as "targetGoogleSearch"?

If you confirmed you added it, please Reply Privately to Author the SOAP request and response.

Thanks,

Joyce, AdWords API Team

[Michael Cloonan (AdWords API Team)]

Hello,

We have heard reports of this issue in the past, where there is seemingly no way to get the API results from the TargetingIdeaService to match the results you get when using the web interface. I have contacted our engineering team who should hopefully be able to take a look soon and help us determine whether this is expected, and how to avoid it.

Regards,

Mike, AdWords API Team

[zinch...@seo-studio.ua]

Hello.

Is there any news about this issue?

четверг, 19 мая 2016 г., 18:19:04 UTC+3 пользователь Michael Cloonan (AdWords API Team) написал:

[Michael Cloonan (AdWords API Team)]

Hello,

I apologize about the lack of updates. The engineering team is still gathering information to determine the cause of the discrepancies. Unfortunately, this was a lower priority than some other items that have been ongoing, but I have contacted them again to let them know that you have been waiting for a response for some time now.

Regards,

Mike, AdWords API Team

[Leandro Pessoa]

There's some news about this issue?

[Michael Cloonan (AdWords API Team)]

Hello,

The good news is that engineering has confirmed that they see the issue and are beginning to look into it. Unfortunately, I don't actually have anything more than that to share. I will update this post when I do, although there is no specific timeframe I can give for when that update will be available.

Regards,

Mike, AdWords API Team

[zinch...@seo-studio.ua]

Hello,

Is there any news about this issue?

пятница, 15 июля 2016 г., 16:04:14 UTC+3 пользователь Michael Cloonan (AdWords API Team) написал:

[Michael Cloonan (AdWords API Team)]

Hello,

I apologize for the very slow turnaround on this issue. I have escalated internally again as much as I am able to, so hopefully someone will take a serious look soon. Until then, unfortunately, I have nothing more to share.

Regards,

Mike, AdWords API Team

[Владислав Соколенко]

Hello.

Can you tell me, is problem solved or not?

четверг, 15 сентября 2016 г., 17:14:20 UTC+3 пользователь Michael Cloonan (AdWords API Team) написал:

Hello,

[Michael Cloonan (AdWords API Team)]

Hello,

Not yet. The engineering team is still investigating. I will update here as I have more to share.

Regards,

Mike, AdWords API Team

[Владислав Соколенко]

Hi!

Michael, soon we will be celebrating 1 year since we wrote about the problem. It's very sad because this problem does not allow us to work normally with forecasts.
Please, tell us about the proggress in solving this problem?


четверг, 13 октября 2016 г., 17:44:49 UTC+3 пользователь Michael Cloonan (AdWords API Team) написал: