Find out what folks are buying and selling with "Google Checkout Trends":
http://checkout.google.com/trends |
Wow, cool on http://checkout.google.com/trends/results?q=xbox,+playstation,+wii you can see how Wii sales spiked slightly earlier and much higher in November, and grew very low as they became scare....the PS3 on the other hand stayed almost stagnant |
> However, queries for other products also seem to suggest > a similar trend, which could either mean people don’t spend > as much over the holiday period, or may just demonstrate that > the current data is inaccurate or incomplete.
Interestingly enough the "normal" Google Trends data is normalized in such ways that overall search activitiy increases or decreases (e.g. holiday periods) are not having an effect on the graphs, as Google told me. So if you see a curve for term X going down on period Y, than it does specifically not mean that there was an overall lower search activity at period Y – it was actually something in connection to a decreased interest in X. (At least according to what Google told me.)
Of course the case with Google Checkout Trends may well be different, I'm just saying in the context of normal Trends data. |
It's not working for me, not enough search volume for any keywords, including the examples on the front page |
same thing happened to me Dominic...seems that too many people are trying this new tool. sigh |
Same as Dominic and Francesco, looks good though |
Seems like the service is broken at the moment. |
Just came across more info on how this thing works!
// Sets the default length of time that will show up in the beginning for // the chart. Allowed values are number of seconds or 'max'. // If the value is 'max', the charts will display the whole data they // grab in the beginning. 'displaySeconds': 260 * daySeconds,
'labels': ['descDataLabel', 'ascDataLabel', 'firstLabel'], 'annotationLabels': ['some-annotations'],
// The following parameters are optional configuration parameters. // If absent, default behaviour will be assumed
// The fill transparency of the chart line, between 0 (no fill) and 100 // (full fill) 'fill': 0, // default value 0
// If specified, the size of the line (width) for each data series. 'lclt': '1',
// The names of the labels displayed. If present, they will be used as a // legend on the chart. Otherwise, the actual label identifiers will be // used. 'labelsDisplayNames': ['Custom Name', 'Revenue'],
// Specifies weather the main area of the chart will stretch vertically // to fit the visible data as best as possible ('maximize'), or if the // scale will range between 0 and MAX(dataValues), which is the default // behaviour if the parameter is missing. // Possible values: fixed, maximize, allfixed, allmaximize 'scaleType': 'allmaximize',
// Specify what data series to be used for each of the scales on the chart. // +-----------------------------------------------+ // | | // |_A1_____________________B1__________________C1_| // | | // |_A2_____________________B2__________________C2_| // | | // +-----------------------------------------------+ // In the case of the chart above: // + if scaleValues.length == 0 there will be no numbers on the chart // + if scaleValues.length == 1 the data label will be used for C // + if scaleValues.length == 2, scaleValues[0] -> C, scaleValues[1] -> A // + if scaleValues.length == 3, scalevalues[0] -> C, scaleValues[1] -> A // and scaleValues[2] -> B 'scaleValues': ['descDataLabel', 'ascDataLabel', 'firstLabel'],
// If present, forces the minimum value on the charts to always be zero, no // matter what the scale type is 'forceMinValue': 0,
// Specify weather the value displayed in the top right corner should be // an exact value. Otherwise, an approximation will be displayed (56.12k // instead of 56.123,12 'displayExactValues': 'false',
// The timeout for the getdataRequest after which the annotations (and // ideally the charts) consider the data as not coming back and give up // the request. 'getdataTimeout' : 15000,
// Possible values: {'off', 'on', 'sortOnOccurrence'} // // Controls the filter box on top of the annotations. // – off – removes that filter box. // – on – turns on the filter box with the default very simple filtering // (just matching substrings) // – sortOnOccurrence – Turns on filtering and sorts the results of the // filter based on the occurrence of the substring. // // ATTENTION: Enabling sortOnOccurence is not yet tested on large sets of // annotations. Before enabling, test to see how memory usage is affected // (lots of strings might be produced by the sorting of items) 'annotationsFilter': 'on' };
/** * Deploys the chart and annotations on page load.
and more at: http://checkout.google.com/trends/chartserver/ |
Working now, interesting insight into seasonsality for products, very useful indeed. Splitting out by region would be good, as per Google Trends |
>"Which idiot made that logo?" Lol I was wondering the same question :)
I don't understand why this new tool "looks interesting". It doesn't, for me. And I think there are no users enough using Google Checkout to be useful & reliable. |
You can still get this to work by searching "apps"
http://checkout.google.com/trends/results?q=apps
[edit-removed sig-Nate] |