Issue #6: Try this this week: find out why a DSP creative is not delivering

Sixth issue: one skill to try, what we shipped, one question for you.

Try this this week: read the DSP account, not just its numbers

The problem. A DSP line item goes quiet, or a creative you were sure was live turns out not to be, and the report cannot tell you why: it gives you what happened, not what produced it. So you click through the Amazon console, or ask whoever built the campaign, and they left in March.

The solution. MixShift can now read the DSP account itself: which line items exist, which creatives you have, including ones built in the console before MixShift, which creatives are attached where, whether each placement is running or paused, and whether one was rejected and why. It also tells you which creatives Amazon will accept on a line item, worth asking rather than guessing: an "online video" line item is served by creatives Amazon labels simply "video". This reads; changing a creative still happens in the console.

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

"audit the DSP account for [brand] and tell me which creatives are not delivering"

More at mixshift.ai/amazon-dsp.

This week in MixShift

What we shipped Friday in 0.8.11. Full notes at mixshift.ai/releases; deeper how-to lives in the knowledge base.

1. Build the Sponsored Brands ad without keying it into Amazon by hand

MixShift could build the whole Sponsored Brands plan, then hand the last step back for you to type into the console. Now you ask and it gets built: brand video, video, product collection, or store spotlight, ad group included. Amazon accepts it only if the video and logo already exist in your Creative Asset Library and every product appears on your Store page.

Now you can: go from plan to live ad in one place.

2. Get spend split by objective even though nobody filled the field in

Most accounts leave Objective and Item Group empty, so the daily health check put all the spend in one unclassified row. Accurate, and no use for deciding anything. When more than about a third of spend is unlabelled, the check now reads your campaign names, proposes buckets, and shows them to you to rename, merge, or reject first.

Now you can: answer where the money went by objective on an account that never labelled anything.

Current version is 0.8.11. To see if you are behind, open the plugin and say "what's new with MixShift?"

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