Limits and freshness

The honest fine print for MixShift Intelligence.

Currency

Formatted figures assume USD today. If your account runs in another currency, read the envelope's own currency field rather than assuming the display units.

Vendor Central runs the comparability scan misses

Seller Central runs get the full comparability scan: dark-period, surge-window, and matched-window detection, described in Reading a bridge. Vendor Central runs do not include that scan today, so a Vendor Central bridge carries fewer of those caveats even where the same kind of gap exists in the underlying data.

Large accounts and async

On the retail-backed requests, a large account can answer account_too_large_use_async instead of computing inline. Retry the same request with "async": true and poll for the result, as covered in Run an insight from the command line.

Concurrency

Each account can have two requests computing at a time. A third answers busy (429); retry shortly rather than immediately.

Cache windows

Results are artifacts, not live queries: the same request, for the same merchant, period, and engine, returns the same figures. A closed month is cached for up to 24 hours. A period that is still open (the current month, for instance) refreshes every 15 minutes.

What is retail-only today

The year-over-year leg of the monthly read is retail-only: there is no year-ago advertising bridge yet, so a YoY comparison covers retail performance only.

Lost sales figures run on their own stamped methodology version, separate from the engine version. Every result, of any request, stamps the engine and evidence versions it was computed with, so you always know exactly what produced a given figure.