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%.

1. What HTTP actions will you support?
.

2. Can I do a JSON request?
Yes, you could do    but you'll have to , and handle parsing it yourself afterward. This is not really recommended. (Just use  KV pairs as usual.)

3. Can I send multivalued keys?
No, only send (key, value) pairs.

4. Does this mean I cannot use the action?
Correct. Only. No. Other than content-length, there's no real justification for a, and if you're sending strings that are greater than 2k, you kind of already have a problem.

5. Can I send headers that you will parse?
No. We will not parse anything other than the query string. Custom headers are exactly what we want to avoid.