Hi all.
Same point here: I'm surprised that it is by Label ID, not Label name.
Anyway, thank you Michael for your reply!
regards
/e
Em terça-feira, 11 de outubro de 2016 15:41:50 UTC-3, Michael Cloonan
(AdWords API Team) escreveu:
>
> Hello,
>
> I will look into how we can improve this to
Hello,
I will look into how we can improve this to be more discoverable. That is a
good point that the field name represents different pieces of data
depending on the context.
Thanks for the feedback.
Regards,
Mike, AdWords API Team
On Tuesday, October 11, 2016 at 1:52:53 PM UTC-4, Tyler
That's surprising. All other fields I know of filter on the same values
you'd get if you included the field in your SELECT clause. There are both
"Labels" and "LabelIds" fields for the CAMPAIGN_PERFORMANCE_REPORT
Hello,
The current behavior is the intended behavior. I was under an incorrect
impression when I was first trying to diagnose the issue.
Regards,
Mike, AdWords API Team
On Tuesday, October 11, 2016 at 12:52:17 PM UTC-4, Tyler Murphy wrote:
>
> Will the behavior be changed so that it works the
Will the behavior be changed so that it works the way it's supposed to?
On Wednesday, September 21, 2016 at 2:46:17 PM UTC-4, Tyler Murphy wrote:
>
> Yep, that works. Thanks for the help.
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
Yep, that works. Thanks for the help.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this
Hello,
I have learned that in CONTAINS_ALL queries for labels, you have to specify
the Label ID, not the string. Please try again with the ID for "PLAs" and
let me know if that works.
Regards,
Mike, AdWords API Team
On Wednesday, September 21, 2016 at 1:39:15 PM UTC-4, Tyler Murphy wrote:
>
>
I think I'm having a similar issue. The following query for customer ID
763-523-8060 and API version v201607, without a label filter, works:
SELECT Cost,Labels FROM CAMPAIGN_PERFORMANCE_REPORT DURING 20160912,20160918
And this one, with a label filter, doesn't work:
SELECT Cost,Labels FROM
n you send me the customer ID you're running the query
>>>> against so I can try running it on the account where it's actually
>>>> happening?
>>>>
>>>> Regards,
>>>> Mike, AdWords API Team
>>>>
>>>> On Monday, July 18,
tually
>>> happening?
>>>
>>> Regards,
>>> Mike, AdWords API Team
>>>
>>> On Monday, July 18, 2016 at 7:53:46 PM UTC-4, Sabri Karagönen wrote:
>>>>
>>>> Hi, I'm trying to download a report using KEYWORDS_PERFORMANCE_REPORT.
>&g
; On Monday, July 18, 2016 at 7:53:46 PM UTC-4, Sabri Karagönen wrote:
>>>
>>> Hi, I'm trying to download a report using KEYWORDS_PERFORMANCE_REPORT.
>>> Normally, I can download this report succesfully. However, when I add
>>> labels to filter this report, I ge
d this report succesfully. However, when I add
>> labels to filter this report, I get error below:
>> ERROR_GETTING_RESPONSE_FROM_BACKEND- Unable to read report data.
>>
>> My XML output is below, so you can examine it with details.
>>
>>
>>
error below:
> ERROR_GETTING_RESPONSE_FROM_BACKEND- Unable to read report data.
>
> My XML output is below, so you can examine it with details.
>
>
>
>1. in ReportUtils.php line 202
>2. at ReportUtils::DownloadReportFromUrl('
>https://adwords.google.com/api/adw
Hi, I'm trying to download a report using KEYWORDS_PERFORMANCE_REPORT.
Normally, I can download this report succesfully. However, when I add
labels to filter this report, I get error below:
ERROR_GETTING_RESPONSE_FROM_BACKEND- Unable to read report data.
My XML output is below, so you can
Hi David,
We haven't seen the related backend issue.
If it still persists, please let us know.
Best,
- Takeshi, AdWords API Team
On Friday, July 19, 2013 5:31:02 PM UTC+9, david wrote:
Last couple of nights we've been getting the above error when download a
large keyword performance
Last couple of nights we've been getting the above error when download a
large keyword performance report.
If I rerun the report in the morning it tends to work OK.
We have moved to v201306 3 days ago and have only seen this after the move.
Any ideas whether there's any backend issues causing
16 matches
Mail list logo
