Multi-currency

A store selling into several markets produces conversions in several currencies, and the two halves of a result behave differently. A conversion is a conversion whatever it was paid in, so conversion counts and conversion rates are computed across all of them. Revenue is not, because adding kronor to euros gives a meaningless total.

So revenue needs one currency chosen, and the console asks for it rather than silently picking one. Choosing a currency scopes the money figures to the orders placed in it, which is what makes the number comparable between variants.

The all-currency aggregate is written deliberately rather than appearing by accident. On a multi-currency experiment the aggregate bucket is always emitted; on a single-currency one there is exactly one bucket, because "all currencies" and that currency are the same figure and a second key would create an ambiguity that does not exist.

One historical detail is worth knowing if you look at raw data. Where a payload carries no currency the platform keeps the marker its own analytics source uses rather than remapping it, so the value passes through untouched from your data layer to the reporting queries.