Skip to main content
All Issues
Issue #10
September 29, 2026

Issue #10: DSP reporting past 90 days

DSP reports now reach past Amazon's 90-day window. Plus what shipped in 0.8.15.

amazon-practicalagency-operator-life

Same shape as always: one skill to try, what we shipped, one question for you.

Try this this week: a year of DSP in one ask

The problem. A client asks how DSP did last Q4 against this one. You go to pull it and the report comes back empty, because the DSP reporting Amazon exposes only keeps the last 90 days. So the year-over-year story gets rebuilt from old console exports, if anyone saved them.

The solution. As of Friday's release, MixShift also reaches Amazon's unified reporting, so a DSP report can cover months or years instead of one quarter, and a monthly history comes back in a single request. Before comparing to an old export: numbers will not match exactly, because Amazon changed what its conversion metrics count and which date they land on, and how far back you can go depends on when the campaigns started.

Try this: open Claude with the MixShift plugin and say:

"show me monthly DSP performance for [brand] since last September"

The mx-amazon-dsp skill picks it up. More at mixshift.ai/amazon-dsp.

This week in MixShift

What we shipped in 0.8.15 and the Builder Platform. Full notes at mixshift.ai/releases; deeper how-to lives in the knowledge base.

1. Retire a brand your team no longer works on

When a client leaves, say "retire [brand]" in chat. It stops showing as an active brand for your whole team, and nothing is deleted: context docs, history, accounts, reports and scheduled tasks stay as they are. Bringing it back is one line, and the reply tells you what it is.

Now you can: keep the brand list to the clients you actually run.

2. Claude and ChatGPT connectors get the same access as the plugin

A MixShift connector in claude.ai, Claude Desktop, or ChatGPT can now read brand context, run MixShift Intelligence requests, and make Ads and listing changes, with the same rails: Ads writes preview first and are logged. A connector added before this keeps its old read-only access; remove it and add it again to get the full set.

Now you can: do the same work from whichever Claude or ChatGPT window is open.

3. Updating now reaches the conversation you are already in

A resumed conversation kept running the MixShift version it started with. It now switches to the one you just installed.

Now you can: update mid-week without starting over.

Current version is 0.8.15. To check, open the plugin and say "update the plugin" and the mx-update skill walks you through the steps for your surface.

What can we solve for you?

Reply to this email. It goes to MixShift, and every reply gets a personal answer. If we already solve your problem, we point you at the skill. If we build it, we ship it with your name on the release note.


Don't have the plugin yet? Get it here.

Talk next week.

MixShift

The MixShift Build Log

Get this every week.

Join the Amazon brand owners and agency operators who read the MixShift Build Log every Tuesday.

No spam. Unsubscribe anytime.