Analytics/Archive/Pixel Service

=Kraken Pixel Service Considerations=

One of the basic starting points is that our pixel service will be dumb, it will make as few assumptions about the data you send as is possible and will likely not support any transformations at all. Initially, we aim the pixel service to be able to handle ~200,000 requests per second, which includes all traffic currently handled by all Wikimedia domains, plus ~30%.

=Frequently Asked Questions=


 * 1) What HTTP actions will you support? GET
 * 2) Can I do a JSON GET request? Yes, you could do GET /hai.png?json={"foo":1,"bar":[1,2,3]} but you'll have to encodeURIComponent(json), and handle parsing it yourself afterward. This is not really recommended. (Just use www-form-encoded KV pairs as usual.)
 * 3) Can I send multivalued keys?  No, only send  pairs.
 * 4) Does this mean I cannot use the HTTP POST action?  Yes it does. Other than content-length, there's no real justification for a POST and if you're sending strings that are greater than 2k, you kind of already have a problem.
 * 5) Can I send HTTP headers that you will parse? No. Please don't. This is exactly what we want to avoid.