Hi Don,
There is a separate issue where currently KeywordText needs
KeywordMatchType to work correctly.
Hi Luka,
Do you have the SOAP XML you are using to create the report
definition?
Best,
- Eric
On Jul 8, 4:06 pm, Don Spaulding wrote:
> Eric,
>
> The library I depend on hadn't been updated
Eric,
The library I depend on hadn't been updated on the machine I was
testing from yet, but I don't think that was causing this problem.
Here's a call that received an identical response on the v201003 API
(for a different report entirely).
REQUEST:
https://adwords.google.com/api/adwords/
cm/v20
Hi Eric,
Just wanted to tell that I was testing Report Service and seams that
report
type CAMPAIGN_NEGATIVE_PLACEMENTS_PERFORMANCE_REPORT still makes this
error.
I checked that i have 201003 version. Every other report type works
with no
problem. If you could tell team to check that out.
Thanks
Hi Don,
It looks like your making your request to the v201002 version of the
API, which was not a public version and has been deprecated. Please
migrate your application to v201003 to ensure you are using the latest
functionality.
Best,
- Eric
On Jul 7, 1:27 pm, Don Spaulding wrote:
> Oops, pe
Oops, perhaps I spoke too soon. The majority of our reports are
working just fine, however, for every 50 or so reports that we submit,
one of them encounters this same error '!!!Unexpected exception|||
1113015'.
I've included the ReportDefinition call that created this report as
well as the exact
Sorry Eric, I bumped the thread before trying last time. Yes, the
Campaign Performance Reports are working again.
Thanks,
Don
On Jul 1, 2:39 pm, AdWords API Advisor
wrote:
> Hi Don,
>
> I believe a fix has been pushed out for this problem, and the report
> seems to be working on my account. Ca
Hi Don,
I believe a fix has been pushed out for this problem, and the report
seems to be working on my account. Can you try downloading a campaign
report again?
Best,
- Eric
On Jun 29, 1:40 pm, Don Spaulding wrote:
> Any update on this error?
>
> // Sorry, my long-polling timeout is 1 week.
>
Any update on this error?
// Sorry, my long-polling timeout is 1 week.
On Jun 21, 5:01 pm, Don Spaulding wrote:
> Thanks for the note Eric. I'm looking forward to your update.
>
> On Jun 21, 3:46 pm, AdWords API Advisor
> wrote:
>
>
>
> > Hi Don,
>
> > I am seeing the same problem with CAMPAIGN
Thanks for the note Eric. I'm looking forward to your update.
On Jun 21, 3:46 pm, AdWords API Advisor
wrote:
> Hi Don,
>
> I am seeing the same problem with CAMPAIGN_PERFORMANCE_REPORTs. I'll
> work with the core engineering team to investigate the problem and
> update this thread when I have mo
Hi Don,
I am seeing the same problem with CAMPAIGN_PERFORMANCE_REPORTs. I'll
work with the core engineering team to investigate the problem and
update this thread when I have more information.
Best,
- Eric Koleda, AdWords API Team
On Jun 21, 1:42 pm, Don Spaulding wrote:
> I didn't specify any
I didn't specify any client information when creating the report
definition. I assumed that a report definition was constant across
multiple clients, and that the clientEmail header I was passing across
in the HTTP request was used to determine which account to run the
report for. I assume based
Hi Don,
When you mention that you are using an arbitrary client's clientEmail
in the Authorization header, is this the same clientEmail for which you
generated the report definition?
Cheers,
Anash P. Oommen,
AdWords API Team
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on ou
Hi Adwords team,
I'm receiving ReportDefinitionError.INVALID_REPORT_DEFINITION_ID when
attempting to download a report for a previously defined report
definition. I'm using an MCC account and specifying a clientEmail
request header (although python's urllib2 module mangles the header
name to "Cli
13 matches
Mail list logo
