What Changed? A Simple Framework for Diagnosing Revenue Drops

When revenue drops, most teams do one of two things:

• panic and change everything

• rationalize it as “seasonality” and do nothing

Both are expensive.

In most cases, a revenue drop is explainable in under an hour — if you use a structured approach.

This framework is designed for operators. It avoids overanalysis and ends with a decision.

Step 0: Confirm you’re looking at a real drop

Before diagnosing, rule out false signals:

• Are you comparing the right dates (same weekdays, promos, launches)?

• Are you using the same revenue definition (gross vs net)?

• Did refunds spike in one period?

• Was there a one-off order or influencer spike last period?

• Did tracking or attribution settings change?

Many “drops” disappear here.

Step 1: Decompose revenue into the three levers

Use:
Revenue = Sessions × Conversion Rate × AOV

Ask:

• Did sessions fall?

• Did conversion fall?

• Did AOV fall?

You’re not looking for perfection — just which lever moved most.

Step 2: Find where the drop is concentrated

Run three high-signal cuts:

New vs returning

• New customers down → acquisition or demand issue

• Returning down → retention, lifecycle, or brand demand issue

Mobile vs desktop

Mobile conversion often hides checkout friction or UX regressions.

Channel mix

Paid vs organic vs lifecycle reveals whether the issue is spend, traffic quality, or engagement.

Whichever cut shows the largest delta is where you focus.

Step 3: Cross-check the story across systems

Now validate the hypothesis.

If sessions dropped:

Check:

• paid spend changes

• CPM or auction pressure

• tracking issues (UTMs, GA4)

• site outages or errors

If conversion dropped:

Check:

• checkout errors or payment failures

• site speed or recent deploys

• inventory or variant availability

• unexpected fees or shipping changes

If AOV dropped:

Check:

• discount depth

• bundle or upsell performance

• product mix shifts

• shipping threshold changes

You’re confirming coherence, not hunting for every possibility.

Step 4: Generate 2–3 plausible hypotheses

Good analysis narrows.

Examples:

• “Mobile conversion fell after the theme update.”

• “Paid traffic dropped due to capped spend and higher CPMs.”

• “Discounting increased, pulling AOV down.”

If you have more than three hypotheses, you haven’t filtered enough.

Step 5: Run one proof check per hypothesis

Each hypothesis gets a fast validation:

• Theme change → compare conversion before/after deploy

• Spend cap → compare impressions, spend, and sessions

• Discounting → compare AOV and discount rate

If the data doesn’t support it, discard it.

Step 6: End with a decision and a measurement plan

Diagnosis without action is just anxiety.

Decisions might be:

• rollback a change

• adjust spend

• refresh creative

• fix checkout

• change offer or pricing

Then define what you’ll watch next week to confirm recovery.

A copy-paste revenue drop checklist

1. Confirm period and revenue definition

2. Decompose: sessions vs conversion vs AOV

3. Segment: new/return, mobile/desktop, channel

4. Cross-check across tools

5. Pick top hypotheses

6. Run proof checks

7. Decide next action

Respecting the tools

Each tool gives part of the truth:

• Shopify: orders, products, customers

• GA4: traffic and funnel behavior

• Ad platforms: spend and delivery

• Email: lifecycle engagement

The mistake is asking one tool to explain everything.

A clean next step

If you want to shorten the “tab-hopping” phase, Nurii is built for exactly these questions.

Try asking:

• “What changed that explains the revenue drop?”

• “Which lever drove it?”

• “Where is the change concentrated?”