AdWords API Re: v13 Sandbox Report files defined.xml.gz and custom.xml
Ok, thank you, I'm going to move to that thread. best regards. On 28 апр, 00:41, AdWords API Advisor wrote: > This more recent thread has a bit more information: > > http://groups.google.com/group/adwords-api/browse_thread/thread/c911c... > > Though I have not had a chance to start working on the proposed web > tool for generating dummy report data yet. > > Cheers, > -Jeff Posnick, AdWords API Team > > On Apr 27, 10:29 am, GS wrote: > > > I get empty xml document with no data. Is there any information about > > the solution of this question? > > > First time this issue was in this > > thread:http://groups.google.com/group/adwords-api/browse_thread/thread/8ddbc... > > > Here is an example of generated xml document: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > pos="0.0"> > > > > > > > Is it possible to retrieve the structure of rows elements? > > > If file defined.xml.gz is just static file on your server, is it > > possible to modefy it, by adding all possible elements to it? > > > Tnx. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: Interest in web tool to generate custom "dummy" reports?
Hi there. > > > Another approach would be to compile a dozen or so sample reports and > > > post them somewhere for folks to download, but there are millions of > > > possible report type, aggregation, and column combinations, without > > > even getting into date ranges. It would be hard to come up with a > > > representative set of reports that would make everyone happy. I think this is the best way to resolve this problem in a first time. And not a dozen, just 1 or 2 files would be ok. Another solution could be publishing of DTD or schema of this XML file. I can generate report's myself if I know how this file should be done. For example element. What elements should it contain? value ... or maybe ... or: name value ... Maybe there are lots of other elements not only and . If this information is provided by any doc file I'm sorry for my inattention. --- Some keywords, so ppl could find this thread via search: defined.xml.gz custom.xml report sandbox Best regards to everyone. On 13 апр, 23:53, AdWords API Advisor wrote: > Hello Tom, > > The general process of scheduling and downloading a report as you > describe it is correct. Once the report is finished you can retrieve > the URL of a XML file (optionally gzip-ed) and use the relevant HTTP > client code in the language of your choice to retrieve the report > contents. At that point, it's up to you as to what to do with the > data--it's really a generic problem of how to best display XML data in > a web interface, and there's no single correct approach. Parsing and > then reading it from a database, using XSLT, or just parsing and > displaying it directly from your CGI/Servlet/ASPX code are all > possibilities. > > Cheers, > -Jeff Posnick, AdWords API Team > > On Apr 9, 1:01 pm, "acbcoo...@gmail.com" wrote: > > > Hi Jeff, > > Your idea of a sample report application is exactly what I was hoping > > would be available to test reporting. > > For now I will take your suggestion in creating a report from our > > Production campaign and use the XML as a test. > > > What our company is proposing is to have our clients log into our > > website and run reports (through the API) against the campaigns that > > we are administering for them. > > The reports would be pretty standard and we wouldn't allow much filter > > selection. > > From my understanding, the reports get generated and sent to a URL. I > > would then have to navigate to that URL to get the XML and parse it. > > We want to display the output in a grid (we use Telerik) so I would > > need to parse the XML into a database and have the grid bound to the > > data in the database. > > Is that pretty much the only way to accomplish displaying a report > > through the API into a grid? > > > Thanks > > Tom > > > On Feb 25, 3:25 pm, AdWords API Advisor > > wrote: > > > > Hey Folks, > > > > One of the things that we've heard a lot of feedback about is the > > > Sandbox's ReportService, and the fact that the "dummy" report returned > > > from the Sandbox is not particularly useful. I've also mentioned that > > > I'm going to try to do something to make more useful information > > > available. Unfortunately, we're not in a position to make > > > modifications to the Sandbox's ReportService at this time to have it > > > return more realistic dummy data. > > > > I've been thinking about different ways to allow developers to get > > > access to a wider range of sample reports against which they can then > > > test their code. One of the things I've been suggesting for a while is > > > that developers run an AdWords report in the Production environment > > > (via the API or the web interface) against their Production account > > > and use that resulting report XML data when testing their code. This > > > solution would work for developers who already have access to a real > > > AdWords account that receives traffic, but it doesn't work that well > > > for developers who are just starting out with AdWords and don't have > > > any Production traffic yet. > > > > Another approach would be to compile a dozen or so sample reports and > > > post them somewhere for folks to download, but there are millions of > > > possible report type, aggregation, and column combinations, without > > > even getting into date ranges. It would be hard to come up with a > > > representative set of reports that would make everyone happy. > > > > So what I was thinking of doing is writing a fairly simple web > > > application that would allow developers to specify a report type, > > > aggregation type, selected columns, date range, and the number of > > > campaigns/ad groups/keywords they'd like to simulate, and then output > > > report XML with random data that matches the format specified. It > > > would be roughly equivalent to the AdWords web interface's Report > > > Center scheduling options, without any real data being used. The idea > > > would be to use it a few times to generate reports with
AdWords API Re: keyword suggestion tool : Global Monthly Search Volume' column
Yes I read that post already, Just mentioned it ones more to push this feature request ;-) anyone else who needs this urgently? On 27 apr, 17:21, AdWords API Advisor wrote: > Hello, > > Changing the match type in your API requests will not change the > search volume information you get back from the API. Please see > > http://adwordsapi.blogspot.com/2009/01/keyword-match-type-and.html > > for a complete explanation. > > Cheers, > -Jeff Posnick, AdWords API Team > > On Apr 27, 4:28 am, keesjan wrote: > > > Thanks for your reply, we test it. > > The only thing is that the 'lastMonthSearchVolume' and > > 'avgSearchVolume' data does not differentiate for broad or exact match > > keywords. > > > On Apr 23, 9:41 pm, AdWords API Advisor > > wrote: > > > > Hello, > > > > I believe that the avgSearchVolume field in the KeywordVariation > > > object returned from a getKeywordVariations() call already (usually) > > > corresponds to the "Global Monthly Search Volume" column in the > > > KeywordToolExternal web app. The lastMonthSearchVolume field is the > > > equivalent of the "Local Search Volume: Month" column. Running a few > > > queries from the API and the web tool with the exact same parameters > > > bears this out. > > > > If you're seeing significantly different results with the same > > > keywords and all other settings, let us know. > > > > Cheers, > > > -Jeff Posnick, AdWords API Team > > > > On Apr 23, 11:30 am, keesjan wrote: > > > > > anyone? > > > > > On 22 apr, 17:58, keesjan wrote: > > > > > > In teh online keyword suggestion > > > > > toolhttps://adwords.google.com/select/KeywordToolExternal > > > > > I see a new 'Global Monthly Search Volume' column that replaces the > > > > > Average Monthly Search Volume' column. > > > > > The new one is the total worldwide search volume and not the locally > > > > > and language targeted one a sthe old one was. > > > > > > How is this implemented in the Adwords API? > > > > > > And can we now also get Search Volumes for excact matches? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API ReportService and SSL exception.
Hello, Since few days, I have the following exception "SSL peer shut down incorrectly" when I try to use ReportService for daily report on v13. Some days that works fine, and sometimes exception appears. But I don't understand why, because my code, and server configuration didn't change. Note that xml report's size is around 20Mo. Any ideas would be appreciated, Thanks in advance ! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API API Questions
Please excuse my lack of knowledge in asking these questions- 1. when posting a question to this group, can I address directly to the email address of this group or do I have to do it post a note on the web in Google Groups? 2. How can we get notified of pending API changes? 3. How can I invite others to this forum? 4. Is there someplace a list of vendors that are experienced in Google AdWords API? 5. Are there other Google AdWord API groups that we should be in? 6. Are the other forms of communications feeds about Google AdWords API? Thank you. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Site Exclusion API
Hello, I have a question about the site exclusions feature: it seems that this is a campaign level feature, yet you set it at the adgroup level. If I set the site exclusions for just one adgroup (out of many) in a single campaign, then this seems to work (using the Adwords GUI I can see all of the site exclusions that I set for the campaign that contains that adgroup). Is this a correct way of setting the site exclusions for a campaign? If I try to set the site exclusions for all of the adgroups in a campaign, then I get the following error: This request is attempting to exceed the limiton campaign website exclusions. Any help is appreciated. Thanks, Dennis --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: Exact Match - All Languages - All Countries - AvgSearchVolume
Jeff- I just wanted to add my voice to those calling for you to add Phrase & Exact match results. I rarely use broad match anymore in Adwords, because your 'Expanded Broad Match' technology returns way too many results, and drives down CTRs. I only use Exact and Phrase match, and really need the ability to look up data on search volumes for those via the API. Thanks! D On Apr 23, 11:55 am, AdWords API Advisor wrote: > Hello, > > The folks responsible for evaluating AdWords API feature requests are > aware of the demand for this. > > Cheers, > -Jeff Posnick, AdWords API Team > > On Apr 22, 12:01 pm, keesjan wrote: > > > Sorry this message is of coursenotfor Joe but for > > AdWords API Advisor, can you please answer? > > > On 21 apr, 14:20, keesjan wrote: > > > > HI Joe, > > > although you can't comment on whether > > > specific functionality will or willnotbe added to a future release > > > of the AdWords API, > > > a lot of developers are asking for thisexactmatch feature for the > > > Adwords API, including myself. > > > > Please can you discuss internally to add this to your roadmap, request > > > list? An api should handle all features and thisexactmatch data are > > > vital for any serious Adwords bidding tool. > > > > On Mar 5, 12:23 am, AdWords API Advisor > > > wrote: > > > > > Hello Joe, > > > > > As a matter of policy, I'm afraid that I can't comment on whether > > > > specific functionality will or willnotbe added to a future release > > > > of the AdWords API. > > > > > Cheers, > > > > -Jeff Posnick, Adwords API Team > > > > > On Mar 4, 5:19 pm, Joeyw wrote: > > > > > > Thanks for that - and I should have read the whole post properly! > > > > > > Do you have any plans to retrieve the phrase andexactsearch volumes > > > > > for the future? > > > > > > Cheers > > > > > > Joe > > > > > > On Mar 4, 8:50 pm, AdWords API Advisor > > > > > wrote: > > > > > > > Hello Joe, > > > > > > > The scenario you describe is exactly what I was describing in my > > > > > > blog > > > > > > post, and to quote from the last paragraph: > > > > > > > "The search volumes in the results returned from the API should > > > > > > roughly correspond to what you'd see with the Broad setting formatch > > > > > > type in the web tool, but retrieving search volumes for Phrase or > > > > > >Exactmatchtypes isnotpossible." > > > > > > > So to reiterate, you cannot retrieve search volumes that correspond > > > > > > to > > > > > > theExactmatchtype via the AdWords API. > > > > > > > Cheers, > > > > > > -Jeff Posnick, AdWords API Team > > > > > > > On Mar 4, 3:19 pm, Joeyw wrote: > > > > > > > > Hi Jeff, > > > > > > > > I am very much after what the orginal poster asked for and I got > > > > > > > quite > > > > > > > excited when I read your post: > > > > > > > 'KeywordMatchType and the > > > > > > > KeywordToolService'http://adwordsapi.blogspot.com/2009/01/keyword-match-type-and.html > > > > > > > > It appeared to solve my problem, but so far it hasn't. > > > > > > > > I would like the returned search volumes from the API to be > > > > > > > forexact > > > > > > >matchtype andnotbroad. I have used the following code for a UK > > > > > > > query: > > > > > > > > # Create seed keyword structure. > > > > > > > $seed_keyword = > > > > > > > 'false' . > > > > > > > 'google api' . > > > > > > > 'Exact'; > > > > > > > $use_synonyms = 'true'; > > > > > > > > # Get keyword variations. > > > > > > > $request_xml = > > > > > > > '' . > > > > > > > '' . $seed_keyword . '' . > > > > > > > $use_synonyms . > > > > > > > 'en' . > > > > > > > 'GB' . > > > > > > > ''; > > > > > > > > You can see I have specified the type to beexactand query the UK. > > > > > > > > The search volume returned for 'google api' is 33100 - checking > > > > > > > the > > > > > > > web keyword tool reveals this is the number for the > > > > > > > broadmatchtype, > > > > > > > theexactis actually 1,600. > > > > > > > > Could you explain why this is the case and if I am doing anything > > > > > > > wrong? > > > > > > > > Thanks > > > > > > > > Joe > > > > > > > > On Jan 5, 3:59 pm, AdWords API Advisor > > > > > > > > > > > > > > wrote: > > > > > > > > > Hello, > > > > > > > > > When I use the web tool to perform the actions you describe, I > > > > > > > > get > > > > > > > > the following result: > > > > > > > > > Keywords related to term(s) entered - sorted by relevance > > > > > > > > google api 1 - 3 $1.79 550,000 450,000 > > > > > > > > > I'mnotsure where you're getting the 27,100 number from, but > > > > > > > > 450,000 > > > > > > > > is the average search volume I'm getting. > > > > > > > > > When I make the following call to getKeywordVariations(), > > > > > > > > leaving out > > > > > > > > the countries and languages options so that all are selected: > > > > > > > > > > > > > > > > > > > > > > > > > false > > > > > > > > Google Api > > > > > > > > Broad > > > > > > > > > > > > > > > > false > >
AdWords API Re: Error while requesting data for the 24th of April 2009
We seem to have run into this problem as well.
To summarize, an attempt to retrieve performance data for 04/24 for
some of our accounts generate this strange error:
The day is in an unrecognized format. It must match the form
-MM-DD with an optional timezone offset.
Note: our request correctly contains ...
2009-04-24
2009-04-24
... even though the request appears perfect.
Is there anybody in Google that can respond to this issue?
Thanks in advance.
- Rohit
---
On Apr 27, 12:02 pm, SEM wrote:
> Hi There,
>
> We seem to be getting the following API error when we try to retrieve
> the daily creative report for 2 of our accounts. This seems to fail
> only for the 24th of April 2009.
> --
> xception in thread "main" AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}
> Server.userException
> faultSubcode:
> faultString: The day is in an unrecognized format. It must match the
> form -MM-DD with an optional timezone offset.
> faultActor:
> faultNode:
> faultDetail:
> {https://adwords.google.com/api/adwords/v13}fault:
> 70
>
> The day is in an unrecognized format. It must
> match the form -MM-DD with an optional timezone offset. ns1:message>
>
> 2009-04-24
> --
>
> I have also pasted the request and response below. Any help is greatly
> appreciated.
>
> ===
> = Elapsed: 4469 milliseconds
> = In message: xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next";
> soapenv:mustUnderstand="0" xmlns:ns1="https://adwords.google.com/api/
> adwords/v13">x...@xx.com xmlns:ns2="https://adwords.google.com/api/adwords/v13";>xx ns2:password>http://schemas.xmlsoap.org/
> soap/actor/next" soapenv:mustUnderstand="0" xmlns:ns3="https://
> adwords.google.com/api/adwords/v13">xx ns3:useragent> xmlns:ns4="https://adwords.google.com/api/adwords/
> v13">gDZ7WLMPARyNmO2Iu7Oc6w soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next";
> soapenv:mustUnderstand="0" xmlns:ns5="https://adwords.google.com/api/
> adwords/v13">xx soapenv:Header> xsi:type="ns6:DefinedReportJob" xmlns:ns6="https://adwords.google.com/
> api/adwords/v13">2009-04-24 xsi:type="xsd:string">CMReportDetail-New {AID=-1} xsi:type="xsd:date">2009-04-24 xsi:type="xsd:string">Daily xsi:type="xsd:string">CampaignId xsi:type="xsd:string">Campaign xsi:type="xsd:string">AdGroupId xsi:type="xsd:string">AdGroup xsi:type="xsd:string">MaxContentCPC xsi:type="xsd:string">KeywordId xsi:type="xsd:string">Keyword xsi:type="xsd:string">KeywordTypeDisplay selectedColumns>KeywordStatus selectedColumns>KeywordMinCPC selectedColumns> xsi:type="xsd:string">DescriptionLine1 selectedColumns> xsi:type="xsd:string">DescriptionLine2 selectedColumns> xsi:type="xsd:string">DescriptionLine3 selectedColumns>VisibleUrl selectedColumns>DestinationURL selectedColumns>CreativeId selectedColumns>CreativeType selectedColumns>AdStatus selectedColumns>AdWordsType selectedColumns>DailyBudget selectedColumns>MaximumCPC selectedColumns> xsi:type="xsd:string">KeywordDestUrlDisplay selectedColumns>AdGroupStatus selectedColumns> xsi:type="xsd:string">CreativeDestUrl selectedColumns>CampaignStatus selectedColumns>Impressions selectedColumns>Clicks selectedColumns>CTR selectedColumns>CPC selectedColumns>Cost selectedColumns> xsi:type="xsd:string">AveragePosition selectedColumns>TopPosition selectedColumns>BottomPosition selectedColumns>FirstPageCpc selectedColumns>QualityScore selectedColumns>Creative selectedReportType> soapenv:Envelope>
> = Out message: http://www.w3.org/2001/
> XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
> http://schemas.xmlsoap.org/soap/actor/
> next" soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/
> adwords/v13">523
> http://schemas.xmlsoap.org/soap/actor/
> next" soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/
> adwords/v13">1
> http://schemas.xmlsoap.org/soap/actor/next";
> soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/
> adwords/v13">500
> http://schemas.xmlsoap.org/soap/actor/
> next" soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/
> adwords/v13">0da372dbf7d6ef4def274ce064f7f129
>
>
>
> soapenv:Server.userException
>
> The day is in an unrecognized format. It must match
> the form -MM-DD with an optional timezone offset.
>
>
> https://adwords.google.com/api/adwords/
> v13">
> 70
>
> The day is in an unrecognized format. It must
> match the form -MM-DD with an optional timezone offset. ns1:message>
>
> 2009-04-24
>
>
>
>
>
>
>
>
> ===
>
> Thanks,
> Hari
--~--~-~--~~~---~--~~
You received
AdWords API Re: Saving Placements in sandbox
Hello Pratap, The lack of support for placements and keywords in the same ad group in the AdWords API Sandbox has been a longstanding bug. I just spoke to one of the engineers about it earlier today and it's back on his radar; I'm hopeful that it will be resolved. In the meantime, you'll get the error message you describe when trying to add both placements and keywords to an ad group in the Sandbox. Cheers, -Jeff Posnick, AdWords API Team On Apr 27, 10:44 am, Pratap Halder wrote: > Hello All, > > I am using the Google AdWords API V13 Sandbox. > > I created a campaign with network type as Google network and Content > network. > The content targeting is set to SelectedPlacements which gets changed > to AllPlacement in the object returned by the Sandbox API. > I created an AdGroup for the same Campaign and then tried to add > Placement Ads using Criterion Service. > I have been struggling to save a placement. Below is the error I am > facing. > > Error Code: 122 > Error Message: One or more input elements failed validation.This > criterion type is invalid. Acceptable values are 'Website' and > 'Keyword'. Websites and keywords may not be used in ad groups in the > same campaign. > > Would appreciate a quick help. > > Regards, > Pratap --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: ReportService and SSL exception.
Hello Thomas, I haven't heard of any similar reports from other developers (if anyone else is running into recent SSL errors, let us know). Googling around a bit, it sounds like it may be an issue with a specific Java runtime when used with an HTTP proxy (http://forums.sun.com/ thread.jspa?threadID=5100030&start=15)... or, it may be something else entirely. Is there any additional details in the stack trace you get along with the exception? Cheers, -Jeff Posnick, AdWords API Team On Apr 28, 9:10 am, TompiT wrote: > Hello, > > Since few days, I have the following exception "SSL peer shut down > incorrectly" when I try to use ReportService for daily report on v13. > Some days that works fine, and sometimes exception appears. But I > don't understand why, because my code, and server configuration didn't > change. Note that xml report's size is around 20Mo. > Any ideas would be appreciated, > > Thanks in advance ! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: creating adwords account with api
Hello, I'd recommend getting in touch directly with your AdWords Reseller contact at Google. Cheers, -Jeff Posnick, AdWords API Team On Apr 28, 2:26 am, ilkerburak wrote: > Thanks for your interest. > My company is participating in the AdWords Reseller Program.Is there > any special versions of this api for participating for the AdWords > Reseller Program members,and how can accomplish to use > createAdWordsAccount method with api? > Regards, > > On 27 Nisan, 18:49, AdWords API Advisor > wrote: > > > Hello, > > > No, it's not possible to create new AdWords accounts using the > > publicly available AdWords API. > > > Cheers, > > -Jeff Posnick, AdWords API Team > > > On Apr 27, 4:04 am, ilkerburak wrote: > > > > Hi, > > > Is it possible to create an adwords account and linl to an mcc accout > > > with api for latest adwords api version? > > > Thaks for yoru interest > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: API Questions
Hello Todd, Your questions are a good excuse to share all our info--I'm sure you're not alone in your curiosity. 1. You can post to this Google Group via email (addressed to adwords- a...@googlegroups.com) or via the web interface (http:// groups.google.com/group/adwords-api). 2. Pending API changes are posted in a number of places. This group should always receive notification of downtime and new releases. Our blog, http://adwordsapi.blogspot.com/, is another place we post similar information, and you'll also find longer how-to or best practice articles there. There's also a very low volume Announcements Google Group which you could subscribe to if you only want to receive important announcements--it's at http://groups.google.com/group/adwordsapi-announcements 3. Anyone can join this Google Group by visting http://groups.google.com/group/adwords-api/subscribe 4. Google doesn't maintain such a list at this time. I've seen some companies post in this group soliciting developers, which I don't have any objection to as a matter of policy. 5. See the answer to 2. In general, if you're in this group and you check the blog every so often (or subscribe to its RSS/Atom feed) you should be covered. 6. For the time being, that's it. If we do adopt new ways of keeping in touch with our developers, we'll be sure to announce them first via all the old channels :-) Cheers, -Jeff Posnick, AdWords API Team On Apr 28, 10:10 am, Todd wrote: > Please excuse my lack of knowledge in asking these questions- > > 1. when posting a question to this group, can I address directly to > the email address of this group or do I have to do it post a note on > the web in Google Groups? > 2. How can we get notified of pending API changes? > 3. How can I invite others to this forum? > 4. Is there someplace a list of vendors that are experienced in Google > AdWords API? > 5. Are there other Google AdWord API groups that we should be in? > 6. Are the other forms of communications feeds about Google AdWords > API? > > Thank you. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: Site Exclusion API
Hello Dennis, There are two ways to exclude specific sites using the AdWords API. You can use the setCampaignNegativeCriteria() call: http://code.google.com/apis/adwords/docs/developer/CriterionService.html#setCampaignNegativeCriteria which will add a campaign-level negative criteria to a specific campaign. The negative criteria will apply to all ad groups in that campaign. You can also exclude sites by adding negative criteria to a specific ad group using addCriteria() http://code.google.com/apis/adwords/docs/developer/CriterionService.html#addCriteria and passing in as a parameter a Website criterion object that has its "negative" property set to true. Does that clear anything up? If not, could you please pass along the requestId (found in the SOAP response header) for the API call that results in the error message you're reporting? Cheers, -Jeff Posnick, AdWords API Team On Apr 27, 7:05 pm, "dpha...@nextag.com" wrote: > Hello, > > I have a question about the site exclusions feature: it seems that > this is a campaign level feature, yet you set it at the adgroup level. > If I set the site exclusions for just one adgroup (out of many) in a > single campaign, then this seems to work (using the Adwords GUI I can > see all of the site exclusions that I set for the campaign that > contains that adgroup). Is this a correct way of setting the site > exclusions for a campaign? If I try to set the site exclusions for all > of the adgroups in a campaign, then I get the following error: > This request is attempting to exceed the limiton campaign website > exclusions. > > Any help is appreciated. > > Thanks, > Dennis --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: Sandbox DB Refresh: Friday, April 24
This refresh was apparently delayed, and did not take place on Friday, April 24 as originally planned. It took place a few minutes ago, on April 28, and the Sandbox is in the process of coming back up following the database refresh. Cheers, -Jeff Posnick, AdWords API Team On Apr 21, 10:58 am, AdWords API Advisor wrote: > I wanted to give everyone advanced warning that the AdWords API > Sandbox's database is scheduled to be refreshed on Friday, April 24. > Following the refresh all data stored in the Sandbox will be cleared, > and you will have to recreate your client accounts with a call to > getClientAccounts(). > > More information on the Sandbox environment and our periodic refreshes > is available at > > http://code.google.com/apis/adwords/docs/developer/adwords_api_sandbo... > > Cheers, > -Jeff Posnick, AdWords API Team --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: Sandbox DB Refresh: Friday, April 24
Thanks Jeff! We appreciate the update. Approximately how long does the sandbox take to come back up? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: Site Exclusion API
Hello Jeff, Thank you for your reply. Yes, I am using the setCampaignNegativeCriteria(), and I was setting the site exclusions for the whole campaign just using one adgroup that belongs to that campaign, and although it seemed like this worked fine, I wasn't totally sure if this would apply to all of the adgroups in that campaign. But it seems like you're saying that it does. Thanks again, Dennis On Apr 28, 12:30 pm, AdWords API Advisor wrote: > Hello Dennis, > > There are two ways to exclude specific sites using the AdWords API. > You can use the setCampaignNegativeCriteria() call: > > http://code.google.com/apis/adwords/docs/developer/CriterionService.h... > > which will add a campaign-level negative criteria to a specific > campaign. The negative criteria will apply to all ad groups in that > campaign. > > You can also exclude sites by adding negative criteria to a specific > ad group using addCriteria() > > http://code.google.com/apis/adwords/docs/developer/CriterionService.h... > > and passing in as a parameter a Website criterion object that has its > "negative" property set to true. > > Does that clear anything up? If not, could you please pass along the > requestId (found in the SOAP response header) for the API call that > results in the error message you're reporting? > > Cheers, > -Jeff Posnick, AdWords API Team > > On Apr 27, 7:05 pm, "dpha...@nextag.com" wrote: > > > Hello, > > > I have a question about the site exclusions feature: it seems that > > this is a campaign level feature, yet you set it at the adgroup level. > > If I set the site exclusions for just one adgroup (out of many) in a > > single campaign, then this seems to work (using the Adwords GUI I can > > see all of the site exclusions that I set for the campaign that > > contains that adgroup). Is this a correct way of setting the site > > exclusions for a campaign? If I try to set the site exclusions for all > > of the adgroups in a campaign, then I get the following error: > > This request is attempting to exceed the limiton campaign website > > exclusions. > > > Any help is appreciated. > > > Thanks, > > Dennis --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API "Connect Failure" within XML Response
>From time to time I've been getting weird parsing errors in XML returned from the adWords API. Today I found the following: I sent a getAllAds request to the adService, and got back an HTTP status of 200, but the HTTP response content contained nothing but the words "Connection Failure" instead of the usual XML document. There have been other times when I've received the "Connection Failure" as the actual HTTP status code, but this seems pretty strange that it would be in the body of the message that came back with a 200 status code. I'm running on Java/Axis, and would figure that if I got the 200 status then the GET to the adWords API at least got out of my server and to the adWords server, so I don't think that the problem is in something that Axis is doing. There's no easy way to reproduce this, sometimes it happens & sometimes it doesn't, but since I probably do thousands of calls to the API every night, it's bound to happen more often than I'd like. Is there logic behind this behavior that I'm not aware of? I don't recall ever seeing mention of this before. thanks -reed --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Google AdWord API Developers
Is there anyone who performs contract consulting services for Google API AdWords UIs in PHP and is looking for more business? If so, contact commerce9...@gmail.com. Thank you --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: Site Exclusion API
Hello Dennis, The part that's confusing me is when you say "I was setting the site exclusions for the whole campaign just using one adgroup that belongs to that campaign". What do you mean by that? setCampaignNegativeCriteria() doesn't take an ad group as a parameter. It takes a campaignId as a parameter. Cheers, -Jeff Posnick, AdWords API Team On Apr 28, 5:01 pm, "dpha...@nextag.com" wrote: > Hello Jeff, > > Thank you for your reply. Yes, I am using the > setCampaignNegativeCriteria(), and I was setting the site exclusions > for the whole campaign just using one adgroup that belongs to that > campaign, and although it seemed like this worked fine, I wasn't > totally sure if this would apply to all of the adgroups in that > campaign. But it seems like you're saying that it does. > > Thanks again, > Dennis > > On Apr 28, 12:30 pm, AdWords API Advisor > > wrote: > > Hello Dennis, > > > There are two ways to exclude specific sites using the AdWords API. > > You can use the setCampaignNegativeCriteria() call: > > > http://code.google.com/apis/adwords/docs/developer/CriterionService.h... > > > which will add a campaign-level negative criteria to a specific > > campaign. The negative criteria will apply to all ad groups in that > > campaign. > > > You can also exclude sites by adding negative criteria to a specific > > ad group using addCriteria() > > > http://code.google.com/apis/adwords/docs/developer/CriterionService.h... > > > and passing in as a parameter a Website criterion object that has its > > "negative" property set to true. > > > Does that clear anything up? If not, could you please pass along the > > requestId (found in the SOAP response header) for the API call that > > results in the error message you're reporting? > > > Cheers, > > -Jeff Posnick, AdWords API Team > > > On Apr 27, 7:05 pm, "dpha...@nextag.com" wrote: > > > > Hello, > > > > I have a question about the site exclusions feature: it seems that > > > this is a campaign level feature, yet you set it at the adgroup level. > > > If I set the site exclusions for just one adgroup (out of many) in a > > > single campaign, then this seems to work (using the Adwords GUI I can > > > see all of the site exclusions that I set for the campaign that > > > contains that adgroup). Is this a correct way of setting the site > > > exclusions for a campaign? If I try to set the site exclusions for all > > > of the adgroups in a campaign, then I get the following error: > > > This request is attempting to exceed the limiton campaign website > > > exclusions. > > > > Any help is appreciated. > > > > Thanks, > > > Dennis > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: Error while requesting data for the 24th of April 2009
Hello,
This is, unfortunately, the same issue that cropped up last October
and is described here:
http://groups.google.com/group/adwords-api/browse_thread/thread/d1f6486ca383b23a
I took a look at Hari's request, and the account in question is in
Cairo's time zone, which just had DST kick in at what would have been
midnight on April 24. I'm assuming that Rohit's account also falls in
a time zone that just had a DST event.
There really should have been a resolution between last October and
now, but unfortunately there hasn't been. I've made sure that our
engineering team knows that this is once again affecting our
developers. Until the issue is resolved, though, I'd recommend working
around the issue by, for example, scheduling a report with Daily
aggregation and a start day of 2009-04-23 and end date of 2009-04-25.
Apologies,
-Jeff Posnick, AdWords API Team
On Apr 28, 12:56 pm, rohitc wrote:
> We seem to have run into this problem as well.
>
> To summarize, an attempt to retrieve performance data for 04/24 for
> some of our accounts generate this strange error:
>
> The day is in an unrecognized format. It must match the form
> -MM-DD with an optional timezone offset.
>
> Note: our request correctly contains ...
>
> 2009-04-24
> 2009-04-24
>
> ... even though the request appears perfect.
>
> Is there anybody in Google that can respond to this issue?
>
> Thanks in advance.
>
> - Rohit
>
> ---
>
> On Apr 27, 12:02 pm, SEM wrote:
>
> > Hi There,
>
> > We seem to be getting the following API error when we try to retrieve
> > the daily creative report for 2 of our accounts. This seems to fail
> > only for the 24th of April 2009.
> > --
> > xception in thread "main" AxisFault
> > faultCode: {http://schemas.xmlsoap.org/soap/envelope/}
> > Server.userException
> > faultSubcode:
> > faultString: The day is in an unrecognized format. It must match the
> > form -MM-DD with an optional timezone offset.
> > faultActor:
> > faultNode:
> > faultDetail:
> > {https://adwords.google.com/api/adwords/v13}fault:
> > 70
>
> > The day is in an unrecognized format. It must
> > match the form -MM-DD with an optional timezone offset. > ns1:message>
>
> > 2009-04-24
> > --
>
> > I have also pasted the request and response below. Any help is greatly
> > appreciated.
>
> > ===
> > = Elapsed: 4469 milliseconds
> > = In message: > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next";
> > soapenv:mustUnderstand="0" xmlns:ns1="https://adwords.google.com/api/
> > adwords/v13">x...@xx.com > xmlns:ns2="https://adwords.google.com/api/adwords/v13";>xx > ns2:password>http://schemas.xmlsoap.org/
> > soap/actor/next" soapenv:mustUnderstand="0" xmlns:ns3="https://
> > adwords.google.com/api/adwords/v13">xx > ns3:useragent> > xmlns:ns4="https://adwords.google.com/api/adwords/
> > v13">gDZ7WLMPARyNmO2Iu7Oc6w > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next";
> > soapenv:mustUnderstand="0" xmlns:ns5="https://adwords.google.com/api/
> > adwords/v13">xx > soapenv:Header> > xsi:type="ns6:DefinedReportJob" xmlns:ns6="https://adwords.google.com/
> > api/adwords/v13">2009-04-24 > xsi:type="xsd:string">CMReportDetail-New {AID=-1} > xsi:type="xsd:date">2009-04-24 > xsi:type="xsd:string">Daily > xsi:type="xsd:string">CampaignId > xsi:type="xsd:string">Campaign > xsi:type="xsd:string">AdGroupId > xsi:type="xsd:string">AdGroup > xsi:type="xsd:string">MaxContentCPC > xsi:type="xsd:string">KeywordId > xsi:type="xsd:string">Keyword > xsi:type="xsd:string">KeywordTypeDisplay > selectedColumns>KeywordStatus > selectedColumns>KeywordMinCPC > selectedColumns> > xsi:type="xsd:string">DescriptionLine1 > selectedColumns> > xsi:type="xsd:string">DescriptionLine2 > selectedColumns> > xsi:type="xsd:string">DescriptionLine3 > selectedColumns>VisibleUrl > selectedColumns>DestinationURL > selectedColumns>CreativeId > selectedColumns>CreativeType > selectedColumns>AdStatus > selectedColumns>AdWordsType > selectedColumns>DailyBudget > selectedColumns>MaximumCPC > selectedColumns> > xsi:type="xsd:string">KeywordDestUrlDisplay > selectedColumns>AdGroupStatus > selectedColumns> > xsi:type="xsd:string">CreativeDestUrl > selectedColumns>CampaignStatus > selectedColumns>Impressions > selectedColumns>Clicks > selectedColumns>CTR > selectedColumns>CPC > selectedColumns>Cost > selectedColumns> > xsi:type="xsd:string">AveragePosition > selectedColumns>TopPosition > selectedColumns>BottomPosition > selectedColumns>FirstPageCpc > selectedColumns>QualityScore > selectedColumns>Creative > selectedReportType> > soapenv:Envelope>
> > = Out message: http://www.w3.org/2001/
> > XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> >
AdWords API Re: Sandbox DB Refresh: Friday, April 24
Hello Jeff, It normally would be back by now, but the engineering team is in the process of addressing a discrepancy between the Sandbox database and the Production version. It's being actively worked on, but I don't have an exact time for when it will be back. Cheers, -Jeff Posnick, AdWords API Team On Apr 28, 3:41 pm, Jeff Theroux wrote: > Thanks Jeff! We appreciate the update. Approximately how long does the > sandbox take to come back up? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Re: Sandbox DB Refresh: Friday, April 24
Ok, please post here when it's back up so we can resume using it. Thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API v2009 Sandbox Launched
Hello all, As we mentioned in our December blog post "A preview of 2009 API changes," we've been hard at work on re-building the AdWords API to offer our developers improved speed, functionality, and flexibility. Today, we're announcing the launch of the API 2009 sandbox, so you can begin experimenting with the latest version of the AdWords API. We're using a new version naming convention to highlight the significant differences between this version, called AdWords API v2009, and v13. There are several key differences in how API v2009 works: - More operations in a single call: We're changing the way services are constructed so that you'll be able to accomplish more work per call. Specifically, operations will accept a variety of modifiers acting on elements across ad groups. For example, you'll be able to add, update, and delete keywords across ad groups, all within a single call. - Lower costs: We will reduce API units consumed for the new asynchronous methods, and are exploring other ways to improve the value you get from the AdWords API by lowering costs and increasing efficiency of quota use. The v2009 sandbox is free to use, and once these services are in production, they will be tied to a new rate sheet that lowers the average cost of an operation. The new rate sheet will apply only to API v2009, and will be launched when v2009 goes into production. Most AdWords functionality is available in the core services we exposed today: - AdGroupAdService - AdGroupCriterionService - AdGroupService - CampaignCriterionService - CampaignService - CampaignTargetService Forthcoming features include: - Asynchronous calls: We'll offer asynchronous calls, which will allow you to work with large sets of data faster and more easily. Instead of having to wait for our system to fully complete your request before you can make another one, you'll be able to make another call as soon as the API service confirms that it's received your previous call. No more waiting for large requests to be finished. (Synchronous methods will still be supported as well). - Partial failure acceptance: We plan to support partial failure, so large posts aren't rolled back due to a few errors. This allows you to keep moving forward with development and not have to re-do the same posts. We'll release the remaining features needed for full AdWords parity in the coming months. Forthcoming features include: Reporting, Keyword tools, MCC functionality, and change history. How to access the API v2009 Sandbox: The API v2009 Sandbox does not charge for quota, and will accept your current Google account login. In addition, the backend database for the v2009 Sandbox is shared with the v13 Sandbox environment. This means that any existing campaigns, ad groups, ads, and keywords that you created under your login email using the v13 Sandbox will exist in the v2009 Sandbox. Please remember that the sandbox is a testing and development environment. The changes made here will not impact your live AdWords account. You can read more about Sandbox best practices here: http://adwordsapi.blogspot.com/2009/03/adwords-api-sandbox-best-practices.html What comes next: We plan to launch the core functionality of API v2009 on our production servers in about 2 months, with the remaining functionality needed for AdWords parity released over the following 3 months. During that time, both AdWords API v13 and v2009 will be fully supported. We'll begin the sunset period for v13 once we've reached feature parity in API v2009. Since we're introducing more changes than usual, we'll extend the normal 4-month sunset period for v13, so it won't sunset until sometime in early 2010. Documentation for the API v2009 sandbox is available on our codesite at: http://code.google.com/apis/adwords/v2009/docs/ We hope you'll kick the tires of our new API and give us plenty of feedback. We've established a special email address for you to share your thoughts: adwordsapi-relau...@google.com. We look forward to your comments, suggestions and questions. Thank you, Doug Raymond Product Manager, AdWords API --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
AdWords API Adding Placements using Live API V13
Hello, I now ran the application on Google AdWords LIVE API V13 and faced a scenario explained below. Is it a valid scenario? I created a Keyword Campaign and then an AdGroup to it using LIVE API. Now I tried to add a placement to the AdGroup, I face the same error as mentioned previously in the thread. I went back to AdWords site at https://adwords.google.com/ and successfully added a placement to the same AdGroup. When I come back and try to add a placement using LIVE API, I was successful. Regards, Pratap --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~--~~~~--~~--~--~---
