It's not quite as bad as that. You can find out whether a budget is able to
be shared or not, by attempting to share it. If you get an error ... it's
not able to be shared. If you don't get an error ... it is able to be
shared (remember to unshare it again ). Then set your flag accordingly.
Ele
Hi people. I've been fielding questions from users over discrepancies
between UI and API reports. I've found this
article:
http://adwords.blogspot.com.au/2012/11/impression-share-reporting-changes-are.html
that discusses changes that came into effect on October 1. In particular:
1) *Distinct
Hi all. Now that budgets are a separate object, there appears to be missing
functionality in the CustomerSyncService in that it doesn't return
information about changed budgets. From our perspective, budget is still an
attribute of the campaign, although obviously it now sits outside ( and
abov
.
On Thursday, 18 October 2012 10:02:44 UTC+11, dkasak wrote:
>
> .
>
> On Tuesday, 16 October 2012 15:05:28 UTC+11, dkasak wrote:
>>
>> .
>>
>> On Monday, 15 October 2012 10:44:55 UTC+11, dkasak wrote:
>>>
>>> .
>>&g
.
On Tuesday, 16 October 2012 15:05:28 UTC+11, dkasak wrote:
>
> .
>
> On Monday, 15 October 2012 10:44:55 UTC+11, dkasak wrote:
>>
>> .
>>
>> On Friday, 12 October 2012 11:15:02 UTC+11, dkasak wrote:
>>>
>>> .
>>>
>>>
.
On Monday, 15 October 2012 10:44:55 UTC+11, dkasak wrote:
>
> .
>
> On Friday, 12 October 2012 11:15:02 UTC+11, dkasak wrote:
>>
>> .
>>
>> On Thursday, 11 October 2012 12:08:12 UTC+11, dkasak wrote:
>>>
>>> Yo! Google! Anyone home? I ass
.
On Friday, 12 October 2012 11:15:02 UTC+11, dkasak wrote:
>
> .
>
> On Thursday, 11 October 2012 12:08:12 UTC+11, dkasak wrote:
>>
>> Yo! Google! Anyone home? I assume it's a known issue and you'll respond
>> "all in good time"?
>>
>&g
.
On Thursday, 11 October 2012 12:08:12 UTC+11, dkasak wrote:
>
> Yo! Google! Anyone home? I assume it's a known issue and you'll respond
> "all in good time"?
>
> On Wednesday, 10 October 2012 12:47:47 UTC+11, dkasak wrote:
>>
>>
>>
>
Yo! Google! Anyone home? I assume it's a known issue and you'll respond
"all in good time"?
On Wednesday, 10 October 2012 12:47:47 UTC+11, dkasak wrote:
>
>
>
> On Tuesday, October 9, 2012 3:29:34 PM UTC+11, dkasak wrote:
>>
>> Hmmm.
>
On Tuesday, October 9, 2012 3:29:34 PM UTC+11, dkasak wrote:
>
> Hmmm.
>
> OK Jayshree. Thanks for responding, but in all honesty, you're not
> helping. Please see the response I got back ( above ). For us, at least for
> certain accounts ( which have repor
running the awql
> query i mentioned previously
>
> On Fri, Oct 5, 2012 at 12:12 PM, dkasak
>
> > wrote:
>
>> I spent most of the day rewiring our code to make AWQL requests for this
>> report. This doesn't return any records either; just an XML with field
>&g
UniqueUserCountAsLong
>
> FROM ADGROUP_REACH_FREQUENCY_REPORT DURING LAST_7_DAYS";
>
>
>
> On Thu, Oct 4, 2012 at 7:26 AM, dkasak
>
> > wrote:
>
>> Hi.
>>
>> We noticed you have added an ADGROUP_REACH_FREQUENCY_REPORT report type.
>> We'd like to use
Hi.
We noticed you have added an ADGROUP_REACH_FREQUENCY_REPORT report type.
We'd like to use this data. When I create a report request:
https://adwords.google.com/api/adwords/cm/v201206";>
AdGroupId
AdGroupName
AdGroupStatus
CampaignId
CampaignName
dle such situation.
>
> Regards,
> Evgeniy.
>
> On Wednesday, September 26, 2012 10:42:40 AM UTC+4, dkasak wrote:
>>
>> Hi all. Our app support team asked me to look into an issue a client has
>> reported. The first step is usually to test up the client's account in
Hi all. Our app support team asked me to look into an issue a client has
reported. The first step is usually to test up the client's account in one
of our testing environments. For some reason I can't do that for this
account. We have tested the credentials from our production environment -
the
01206
> ";
>
> $curl = curl_init();
> curl_setopt($curl, CURLOPT_URL, $url);
> curl_setopt($curl, CURLOPT_HEADER, false);
> curl_setopt($curl, CURLOPT_POST, true);
> curl_setopt($curl, CURLOPT_POSTFIELDS, $params);
> curl_setopt($curl, CURLOPT_HTTP
Hi all. I'm working on updating our code to v201206 and I'm getting errors
when doing ad-hoc reports. An example of a request that works:
URL:
https://adwords.google.com/api/adwords/reportdownload/v201109
Definition:
https://adwords.google.com/api/adwords/cm/v201109";>
Hi all. Is there some documentation on the different criteriaType values we
can expect in the Criteria report? I had previously seen placement data
under "User Interest" ( at least I thought it was placement data ), but now
I'm seeing it under "Placement".
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Now that we're using the Criteria report ( as not all 'keywords' are in the
'keyword' report ), we're seeing some undocumented things like
boomuserlist:x appearing. Is there are way to get more information on
booms? If possible, we'd convert these to something useful that users could
unders
We hope in unison then. MmMmMmMmMmMmMmMm ( that's the sound it makes ).
On Wednesday, 23 November 2011 00:21:26 UTC+11, Danial Klimkin wrote:
>
> Hello HK,
>
>
> This feature is not yet available but we hope to introduce it in future
> releases.
>
>
> -Danial, AdWords API Team.
>
--
=~=~=~=~=~=
.
On Monday, 19 March 2012 13:58:40 UTC+11, dkasak wrote:
>
> I'm not talking about the URL of the downloads in this case.
>
> The page:
> http://code.google.com/apis/adwords/docs/guides/reporting.html
>
> ... used to have an example report definition, whic
I'm not talking about the URL of the downloads in this case.
The page:
http://code.google.com/apis/adwords/docs/guides/reporting.html
... used to have an example report definition, which STARTED with the line:
... and this has been changed to:
https://adwords.google.com/api/adwords/cm/v2011
I have just read that there are YET MORE changes to a production API:
http://googleadsdeveloper.blogspot.com.au/2012/03/specifying-version-when-requesting.html
The page:
http://code.google.com/apis/adwords/docs/guides/reporting.html
... has been quietly updated with the new namespace requirement
YAWN
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Gr
Further to the issues relating to the predicate changes on the Status
column, we are now seeing data being missed for different AdTypes. In
particular, we are seeing data for THIRD_PARTY_REDIRECT_AD ads being
dropped from the AD_PERFORMANCE_REPORT.
We will be looking into working around this is
.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Group
There are now at least 4 threads on the changes that accidentally went out
on the 25th of January ( at least we would HOPE it was accidental ).
There has not been a response from a Google representative for a number of
hours. This is not appreciated. Packing up for the day and resuming at your
I've also seen this issue appear, and it's only a very recent change. We
have NEVER specified a list of statuses for downloading
AD_PERFORMANCE_REPORT reports, and have always downloaded reporting data
for all ads.
This needs to be changed back to the old behaviour, as a matter of
priority. Fu
http://googleadsdeveloper.blogspot.com/2012/01/adwords-soap-header-validation-is-being.html
F'n clowns. Maybe more warning than NO WARNING AT ALL would be good? I
received the email corresponding to this change LAST NIGHT and it's rolled
out already ...
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=
Greetings.
I have discovered further issues with testing our patch for downloading
reports, and would like some clarification on the recommended method of
developing / testing these changes.
We will be whacking together a production patch based on our v201101
codebase. However we have been tol
As I've had a few people recommend to me that I make use of the client
libraries, I thought I'd download them and give them a go. The first task I
thought I'd throw at them was creating a new account in the sandbox, as
this is the only place to test the upcoming reporting changes. I copied the
While regressions testing our Google codebase, the vast majority of which
we assumed, based on the blogspot notes and release notes, we would not
have to touch for the upgrade from v201101 to v201109, we have instead seen
that most of our calls now fail. I assume this is what is cryptically mean
Hi Kevin. I will clarify my point further. Regardless of whether we do our
coding and unit testing against the sandbox or not, we do *NOT* do QA or
production verification against the sandbox. This has always been the case,
for all search engines that we support. It would require hacking with re
OK I have discussed with our QA and app support teams, and they are *not
OK*with releasing anything that we can't reasonably QA and verify
*against a production API* after a production patch. We don't do either QA
or production verification against sandboxes. Actually we rarely even code
agains
No response? There is actually a serious question here about testing this
change that is about to be fast-tracked into production.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwo
There have been a number of announcements recently about changes to an API
in production that I think are cause for concern. We are currently using
v201101. Just recently I accidentally stumbed over a blog announcement that
this version would be deprecated at the end of Feb 2012. With 3-4 month
Greetings. Is it possible to get an exclusion to the requirement that all
creatives go through an editorial process ... maybe for nominated accounts?
While developing / QAing changes to our code, this slows down things a LOT.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on o
OK now I don't think it's a case-mangling thing. I've just tested with curl,
and I'm getting the same error.
Here is my call:
curl \
-v \
-H "authorization: GoogleLogin auth=some_big_token" \
-H "clientCustomerId: a_numeric_id" \
-H "clientEmail: an_mcc_account_email" \
https://adword
Hi all.
I'm adding MCC login support, and I've hit an issue downloading reports. For
reports created with an MCC login, I'm getting:
ReportDefinitionError.INVALID_REPORT_DEFINITION_ID@selector.selector???
I have added the clientCustomerId header in the HTTP request. HOWEVER ...
our HTTP client
Greetings. I know people will think I'm jumping the gun on this one ... but
we're doing an analysis of our exposure to IPV4 / IPV6 risks, and we'd like
to know if there are any plans on sunsetting the Adwords API over IPV4.
Thanks :)
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also fin
Greetings. We have been running some tests against the v201101 report
service, and found that there is a very large window in which reporting data
for the previous day ( in an advertisers' timezone ) is completed. Basically
we are running the same report, a number of times an hour, and comparing
Unless I'm seriously mistaken ... you can get the AccountCurrencyCode in
many ( if not all ) v201101 reports. This column 'appeared' a little while
back with no announcement. Might help out people with a reasonably-sized DEV
/ QA cycle who can't wait until the final seconds before v13 sunset dat
This morning, one of our scheduled reporting jobs received 261 errors:
RateExceededError.RATE_EXCEEDED
... when making http requests to fetch reports. We have never seen this
error before. Was there an issue this morning? Or perhaps we have been close
to the threshold and this morning exceeded
Greetings.
I've just read here:
http://adwordsapi.blogspot.com/2011/03/adwords-api-v201101-launch-providing.html
that v201008 will be sunsetted in August. The way I read this, you're
planning on sunsetting ALL of v201008, correct? Or is it just the
ReportService?
I went to read up on v201101
Greetings.
There still seem to be outstanding issues with field names in v201008
reports. Further to
http://code.google.com/apis/adwords/forum.html?place=topic%2Fadwords-api%2FXxmdh4C4Q9A%2Fdiscussion
... there are some other worrying inconsistencies. For example,
getReportFields() for the KE
Greetings.
I've had more requests from users about 'impression share' via API reports.
This is something that used to be available in v13 reports, and hence we
'may or may not' have set expectations with our users that we would 'soon'
support this metric.
When recently prodded about impression
.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Group
Hi.
We're doing QA of code to run v201010 reports, and we're seeing random
UNEXPECTED_INTERNAL_API_ERROR errors in downloaded reports. Specifically,
when we download the report, instead of it being a gzipped XML file as
requested, it's a text file, with contents such as:
!!!1|||8045686|||Inter
Greetings.
We've seen discrepancies in average position figures between v13 and
v201008 reports. They are minor, but they exist, so I'm investigating.
Is this a known issue? If not, where should I send some example reports
we've downloaded that demonstrate the issue?
Thanks.
Dan
--
=~=~=~=~=~=
Our users are also asking for this metric. Any word on future
availability?
Dan
On Oct 28, 6:51 am, AdWords API Advisor
wrote:
> Hi Andy,
>
> Unfortunately impression share isn't available in v2010* reports yet,
> but I'll talk to the core engineering team about exposing it.
>
> Best,
> - Eric
>
I have just noticed that report definitions that are created via the
API are visible in the AdWords UI, and can be edited. For example, we
successfully changed a report's output from gzipped xml to pdf.
Our software ( and I believe the whole premise of the new 'report
definition ==> http get' mode
Hmm.
I've dumped the headers from my HTTP get, and I can only see a very
minor difference:
---
GET https://adwords.google.com/api/adwords/reportdownload?__rd={snipped}
Pragma: no-cache
Authorization: GoogleLogin auth={snipped}
ClientEmail: {snipped}
ReturnMoneyInMicros: true
(no content)
-
As per
http://adwordsapi.blogspot.com/2010/11/change-to-currency-formatting-in-report.html
I am trying to get v201008 reports to return currency in micros, which
it used to in v13, and which you are apparently switching back to. I
have set the HTTP header returnMoneyInMicros: true in the HTTP GET
r
Hi.
We used to call getAccountInfo() against the AccountService ( v13 ) and
parse the currency. This doesn't seem to be available in the new API
yet. It's essential that we're able to find out what currency an
account is using, otherwise currency figures are meaningless. Any clues?
Thanks.
Dan
We have found some more discrepancies between the columns returned by
getReportFields and those actually available.
f6d766aff713a9475564cd7b921680fb
... did NOT return HourOfDay, however we find that we can successfully
request an ADGROUP_PERFORMANCE_REPORT with this column included.
As before,
Hi Anash. Thanks for the response :)
The request ID that returned columns NOT including CampaignId:
ec40fba22bcd3c2105e95efcd2189909
As for what reporting columns we need that aren't now available in this
report ... ideally ALL columns that used to be available under v13
would be supported. But t
Further to this question, I have seen inconsistencies between the
fields that are advertised via the getReportFields call and what is
actually available in the report. I made the getReportFields API call
this morning for the AD_PERFORMANCE_REPORT, and it did NOT return
CampaignId in the list of ava
Greetings. I'm porting our software from the v13 ReportService to
v201008 ReportDefinitionService, and I've hit some problems that will
cause us a lot of pain. The v13 creative report (
http://code.google.com/apis/adwords/docs/developer/adwords_api_report_creative.html
)
used to give us a lot of I
Hi all.
I'm investigating porting our code to v2009. I've installed the google-
api-adwords-perl example code, including the patched version of
SOAP::WSDL. I've edited ~/adwords.properties and pointed it to the
sandbox API.
When I run either of the 2 scripts in the /example folder, I get
'Intern
; supported, but I'll communicate the desire for such it to the core
> engineering team.
>
> Best,
> - Eric Koleda, AdWords API Team
>
> On Sep 3, 3:12 am, dkasak wrote:
>
> > Greetings.
>
> > I've been doing some reconciliation of the results of the getA
Greetings.
I've been doing some reconciliation of the results of the getAllAds()
call, against what I can see in the AdWords UI. It looks like some
creative types aren't supported.
In the particular campaign / adgroup I'm looking at, there are 3
creatives. One is a text one. One is an image one.
Hi all.
I'm looking at expanding our reporting capability of content traffic.
The closest to what we want seems to be:
http://code.google.com/apis/adwords/docs/developer/adwords_api_report_contentplacement.html#aggr_AdGroupUrlDaily
- but this doesn't support aggregating by creative. Is there any
had a status of Active, a report
> run today will show that ad with a status of Paused, regardless of the
> date range requested in the report.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> On Aug 20, 11:10 pm, dkasak wrote:
>
> > Hi.
>
> > There are
Hi.
There are various status fields in reports. eg KeywordStatus,
CampaignStatus, AdGroupStatus, etc. Do these fields reflect what the
status was at the time in question ( ie the date being reported ), or
are they *current* statuses of objects.
Thanks.
Dan
--~--~-~--~~~-
Hi all.
I'm after detailed documentation on all fields available in reports.
For example, the docs at
http://code.google.com/apis/adwords/docs/developer/adwords_api_report_creative.html
list 'PreferredCPC' as a possible field to include in the report.
Where would I locate further documentation
Hi all. I couldn't find any mention of this; perhaps a decision has
not yet been made. With the release of the 2009 API ( yes, I know it's
still incomplete ), I assume v13's days are numbered. Does anyone have
an exact number, so we can plan our migration to 2009? Thanks.
Dan
--~--~-~--~-
Hi all.
I've been alerted to a significant drop in API performance over the
past 2 or so weeks. A snippet from our logs will tell the story. 2
weeks ago, a keyword report for a particular account was being
generated in around 10 seconds:
0120-060346 S Base.pm/1538 Requesting data for report type
Any word on a solution for this? I'm wondering whether I should bother
adding 'try again' logic as per Jeff Posnick's suggestion, or whether
the issue will be resolved sooner than I can get the fix into a
release.
--~--~-~--~~~---~--~~
You received this message beca
to scheduled it).
>
> > > > Assuming you haven't scheduled 15 other reports since then and bumped
> > > > the report you mention out of the queue in the Report Center, what
> > > > happens when you take a look at the report via the web interface? Do
> >
Hi all.
I posted this question ... somewhere else ... but I can't find where
now, so maybe I posted it in the wrong place? Anyway ...
I've been asked to look at an issue where some reports that we
download contain no information. The compressed file itself is valid
( ie not corrupted ), but when
Hi all.
In the Ad Group Performance Report we get an 'hour' column. Is this in
the account's designated timezone or GMT?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"AdWords API Forum" group.
To post to this grou
Hi all. I've been looking throught the docs at
http://code.google.com/apis/adwords/docs/developer/index.html and I
can't find what I'm after. Is there a page that details the fields
available in reports that we can schedule via the API?
--~--~-~--~~~---~--~~
You rec
I'm actually seeing this issue quite a bit - I've just been asked to
look into it because of the high number of 'URL not found' issues.
What could be causing this? Too many concurrent connections /
reports / logins / something?
As noted above, the URL we're getting is coming straight from
getGzip
73 matches
Mail list logo
