While I'm rambling.. Do you remember before when I discovered in your other private api you had functions for retrieving lists of things that have changed.. I'm guessing for each ad/keyword/adgroup you have a "last_modified" element.
You know what would be truely awesome, well, not truely awesome, but nice at least.. Would be if I could do a *cross-client* structure report and specify: I only want items which have been modified after "such and so date".. (also fix the bugs in the structure report) That would basically reduce my report size down to near zero everyday.. instead now, I have to get each account in full, which is a gig or more of transfer and processing.. Also, I can't just stop getting paused stuff, cause people tend to upload things as paused, and then set them active. I can't just stop downloading deleted stuff.. Cause sometimes people create things and then delete them, after they get impressions, and those impressions would just end up as blanks.. And that would be bad. But I do know exactly when I synchronized last. -tim On Sep 17, 3:08 pm, timprepscius <[EMAIL PROTECTED]> wrote: > Actually a new record for xml size! > 699692080 > > I don't know why you guys don't have a tsv direct mechanism.. oh > well.. > 699692080 xml = 303004310 tsv > > On Sep 17, 1:34 pm, timprepscius <[EMAIL PROTECTED]> wrote: > > > Just wondering.. Do you guys see a bell curve during the day for when > > reports are requested, or is it pretty much randomly distributed.. I'm > > having problems with some of my reports running just super slow > > today.. > > > And I could probably switch to running a large report at night and > > then small chunks during the day.. (if you knew that a certain time > > was better) > > > On Sep 17, 1:17 pm, AdWords API Advisor <[EMAIL PROTECTED]> > > wrote: > > > > Hello Tim, > > > > Thanks, that clarifies things. I'll pass that along. > > > > Cheers, > > > -Jeff Posnick, AdWords API Team > > > > On Sep 17, 10:29 am, timprepscius <[EMAIL PROTECTED]> wrote: > > > > > umm, just so you know the report was not compressed.. > > > > > I got an uncompressed report- > > > > but I requested it over an zip-http connection (whether or not this > > > > was actually executed this way, only curl knows) > > > > > The report size was about 403m.. I don't have it around anymore > > > > unfortunately.. (I didn't mean to request that date range).. > > > > > -tim > > > > > On Sep 16, 3:42 pm, AdWords API Advisor <[EMAIL PROTECTED]> > > > > wrote: > > > > > > Hello Tim, > > > > > > Do you happen to have the size of the original gzip-ed download > > > > > handy? Or if you have the 400mb report still around, could you gzip it > > > > > (with the default compression level, I guess) and let me know what the > > > > > compressed size is? > > > > > > There are some limitations that are probably coming into play here on > > > > > the size of the file that actually gets transferred to your HTTP > > > > > client, but they would apply to the size of the gzip-ed file, not the > > > > > uncompressed report size, so I'm interested in finding that out. > > > > > > Cheers, > > > > > -Jeff Posnick, AdWords API Team > > > > > > On Sep 13, 10:30 am, timprepscius <[EMAIL PROTECTED]> wrote: > > > > > > > xml over zip http connection.. > > > > > > > On Sep 12, 4:08 pm, AdWords API Advisor <[EMAIL PROTECTED]> > > > > > > wrote: > > > > > > > > An update: the consensus is that while this truncating behavior > > > > > > > was > > > > > > > known, it wasn't really intentional--there's no explicit hard > > > > > > > limit on > > > > > > > reports size in the AdWords API or the reports center, and the > > > > > > > behavior is due to an infrastructure dependency. I'm afraid that I > > > > > > > can't go into too much detail about what's going on under the > > > > > > > hood, > > > > > > > but the takeaway is that we have some folks looking into whether > > > > > > > anything has changed in the relevant infrastructure recently that > > > > > > > might have increased the maximum download size. Once we have a > > > > > > > good > > > > > > > answer for that we'll get the limits added to the documentation > > > > > > > once > > > > > > > and for all. > > > > > > > > Tim, could you clarify whether the 400 megabyte report was > > > > > > > downloaded > > > > > > > as a raw XML document, or a gzipped file? If it was initially > > > > > > > gzipped, > > > > > > > how large was the gzip archive? > > > > > > > > Cheers, > > > > > > > -Jeff Posnick, AdWords API Team > > > > > > > > On Sep 11, 11:34 am, AdWords API Advisor > > > > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > > > Hello Tim, > > > > > > > > > Looking back in the archives of this group, it looks like that > > > > > > > > cut- > > > > > > > > off has always been something of a mystery, with empirical tests > > > > > > > > placing it at around 260 megabytes for the uncompressed report. > > > > > > > > I > > > > > > > > haven't heard anything myself, so I'll see what I can do to get > > > > > > > > an > > > > > > > > official word about this from the engineering team and have it > > > > > > > > documented somewhere if there is still a hard limit or if there > > > > > > > > is any > > > > > > > > sort of dynamic cutoff now. > > > > > > > > > Cheers, > > > > > > > > -Jeff Posnick, AdWords API Team > > > > > > > > > On Sep 10, 3:38 pm, timprepscius <[EMAIL PROTECTED]> wrote: > > > > > > > > > > I just did a report that's >400 megabytes.. So obviously the > > > > > > > > > old cut > > > > > > > > > off does not apply.. > > > > > > > > > Is there a cut off? > > > > > > > > > > Thanks! > > > > > > > > > > -tim --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
