Issue #9: what a customer is worth after the first order

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

Try this this week: what a customer is worth after the first order

The problem. You can tell a client what last month's ads returned. You usually cannot tell them what the customer those ads bought is worth a year later. That second number decides whether a launch was worth running, and it sits in Amazon Marketing Cloud, behind a clean room, a paid dataset most people are not sure they have, and a query language nobody wants to learn.

The solution. AMC Retail Purchases dataset is free for all advertisers through the end of 2026 per Amazon. For the cohort and LTV analysis you've been missing, this is the answer. The plugin can now utilize your AMC data and subscriptions to pick the dataset the question needs, carries the column traps that quietly return a wrong answer instead of an error, and checks the paid dataset is switched on before it queries, so a subscription gap stops reading as broken SQL.

Try this: Subscribe to the Retail Purchases dataset in AMC, then open Claude with the MixShift plugin and say:

"what is a customer worth after their first order"

Name the brand and it works out the rest. Deeper how-to lives in the knowledge base.

This week in MixShift

What we shipped Friday in 0.8.14. Full notes at mixshift.ai/releases.

1. Lifetime value reads no longer stop at the date you subscribed

The guidance treated your Retail Purchases subscription date as the start of the data. Amazon holds around five years of purchase history behind it. On one account that was 60 months of customers instead of 13, and a new versus repeat read that overstated new customers by 18% a year later. The skill now measures the real start before it sets a window, and says so when it reports.

Now you can: trust a cohort read that runs longer than a year.

2. The two Amazon Ads failures that re-authorizing cannot fix, now named

Picking a merchant that is inactive in MixShift used to come back as a lost Amazon authorization, so people reconnected accounts that were working fine. It now says plainly that the merchant is inactive and that activating it is the fix. A separate message covers Amazon denying a merchant to the advertising login it is connected through.

Now you can: stop reconnecting accounts that were never the problem.

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

Going to Accelerate in Seattle?

You're invited to an AI Meet Up and Happy Hour with MixShift. We're bringing together the best minds in AI to share ideas, and a drink or two tonight, September 22nd. Find details and RSVP here.

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