Why it moved,
not just what it did
MixShift Intelligence is deterministic attribution over your Amazon data, served as insights your reports, agents, and tools can call.
Sign in with your MixShift login
The Attribution service, available now
Five requests, each answering a different question about your business.
Ops Bridge
Why ordered sales moved between two periods, item by item: traffic, conversion, price, and mix, bridged to the total.
Ads Bridge
Why advertising results moved, at campaign, ad group, keyword or target, search term, or ASIN grain.
The combined read
Both bridges on the same period, joined: TACOS, attributed share, paid pressure, and ad AOV against ASP.
Lost Sales
Sales lost to stock-outs, sellable inventory, and weeks of cover. Evidence attachments on by default.
The Monthly Read
Month over month and year over year, retail and advertising, in one bundle. The substrate of Monthly Report Max.
Never a number the result can’t carry
Footing checks
Every leg of a bridge sums exactly to the headline change.
Caveats it raises on its own
Dark periods, promotions, surge windows, matched windows, restatements, and end-of-life exclusions are flagged by the engine, not by you.
What We Know statements
Turn on evidence and a result carries the measured facts and candidate explanations behind it, with the evidence attached.
Version stamps on every result
The engine and evidence versions a result was computed with are stamped on the result itself.
One method, every bridge
Every bridge Intelligence computes runs on HCAM, the Hierarchical Causal Attribution Model, patent pending. It reads a result two ways: the Horizontal Bridge asks through which declared metric levers performance moved, and the Vertical Bridge asks where across your business hierarchy the movement occurred.
Forecasting
Forecasting joins Intelligence when it ships. Until then, Attribution and the brand memory your team maintains carry the explaining.
No surprises in the fine print
Formatted figures assume USD today. For a non-USD account, read the result’s currency field.
Vendor Central runs do not include the comparability scan (dark-period, surge-window, matched-window detection) that Seller Central runs get.
A large account on a retail-backed request is asked to retry as async and poll. Each account can run two analyses at once; a third is asked to try again shortly.
A closed month’s result is cached for up to 24 hours. An open period refreshes every 15 minutes.
Common questions
See why it moved
Your data is already there. Run a bridge and read what changed.