Skip to main content
Data & Reporting

Monthly Performance Report

mx-monthly-report

Generate the full MoM and YoY narrative in MixShift’s analytical voice: H-Bridge efficiency, item-group highlights, forecast beat/miss, Looking Ahead.

Run it in chat
/mixshift-ai:mx-monthly-report <brand>

or just say generate monthly report for <brand>

Comes with the plugin, one install activates every skill. See the install flow. Needs brand setup first.

Why it exists

Assembling MoM and YoY numbers, item group highlights, and a forecast beat or miss into one client-ready narrative every month is slow, and it is easy for the voice or the causal claims to drift between writers.

What you get

A saved report in MixShift’s canonical voice with signed deltas, item group callouts, and a looking-ahead section, scoped to the right audience so the client version never leaks internal bid-action notes.

What your agent can do

  • 01

    Pull MoM and YoY metrics across spend, sales, ACoS, TACoS, and conversion

  • 02

    Run H-Bridge efficiency analysis to attribute change drivers

  • 03

    Highlight item-group winners and laggards with context

  • 04

    Forecast beat-or-miss commentary plus a forward Looking Ahead section

StatusLive
CategoryData & Reporting
Brand contextRequired
Hosts
Claude CoworkClaude CodeMixShift CLI
Get the plugin

New or existing MixShift customer, both paths start here.

Talk to us

Before you run

Requires brand setup

This skill reads a brand’s context to calibrate its output. Build it once per brand, then every teammate runs on the same shared context.

/mixshift-ai:mx-brand-context <brand>How brand setup works →
What it reads from your brand context
  • ACoS target: frames the efficiency narrative and the forecast beat or miss language
  • Audience (internal vs client): strips bid-action items and internal references for client-facing reports
  • Attribution window per campaign type: which sales get counted into each metric
  • Declared timeline events (promotions, stockouts, price tests, launches): the cause cited for an otherwise unexplained swing
Gets sharper over time

Each unexplained swing prompts a direct question to the brand owner, and any real answer gets logged as an event on the brand timeline, so the next month’s report already knows the story instead of re-asking or guessing at causality.