Ads are running, site's up, no inventory issues. Revenue is just down and has been for two weeks.
Where do you start?
I usually end up opening four tabs, Shopify, Klaviyo, GA4, ads manager, and none of them agree with each other, so I spend an hour reconciling numbers before I've learned anything.
Curious if you have an actual order you go in or if it's the same tab shuffle for everyone
Sessions by page is easy, it's sitting right there in GSC.
Revenue by page is where it falls apart for me. GA4 attribution is a mess, the numbers don't match what the store says, and stitching it to organic landing pages turns into a spreadsheet nobody wants to own.
So the refresh calendar ends up built off traffic, which is not the same list.
What's your setup for this?
Sessions by page is easy, it's sitting right there in GSC.
Revenue by page is where it falls apart for me. GA4 attribution is a mess, the numbers don't match what the store says, and stitching it to organic landing pages turns into a spreadsheet nobody wants to own.
So the refresh calendar ends up built off traffic, which is not the same list.
What's your setup for this?
Sessions by page is easy, it's sitting right there in GSC.
Revenue by page is where it falls apart for me. GA4 attribution is a mess, the numbers don't match what the store says, and stitching it to organic landing pages turns into a spreadsheet nobody wants to own.
So the refresh calendar ends up built off traffic, which is not the same list.
What's your setup for this?
Meta says one thing, Shopify says another, GA4 says a third. Everyone knows they measure differently. That doesn't help when you're deciding whether to keep a campaign on this afternoon.
So which one do you actually go with, and did you pick it for a good reason or just because it was the first one you learned to trust?
had a complex system at one point. tasks in one place, projects in another, all linked up. it decayed into a note called "stuff" and a slack channel we message ourselves in.
what became obvious is that most of what we were tracking was duplicated. campaign status, where something got stuck, what someone still owed. all of it already existed inside the tools where the work actually happened. the system was a hand-maintained copy of information that lived somewhere else, which is why it rotted the moment things got busy. copies always rot.
so now anything with steps in it lives in the thing that runs the steps, and it holds its own state whether anyone checks in or not. the notes file only holds things with no home, which is a much shorter list than we were designing for.
still messy. but it stopped decaying, which the elaborate version never managed
Ours is weirdly split. First drafts and research, huge difference. Anything that needs to be right the first time, still faster to do it myself than to check it.
The gap I didn't see coming is review time. Something that takes two minutes to generate can take twenty to verify, and nobody counts that when they're talking about time saved.
Everyone's writing about the sophisticated stuff. Meanwhile the thing that actually moved revenue for a lot of stores is something dumb like fixing the mobile checkout, or emailing people who bought once and never came back.
Curious what yours was. Specifically the one that worked and that you'd be slightly embarrassed to present as strategy.
had a complex system at one point. tasks in one place, projects in another, all linked up. it decayed into a note called "stuff" and a slack channel we message ourselves in.
what became obvious is that most of what we were tracking was duplicated. campaign status, where something got stuck, what someone still owed. all of it already existed inside the tools where the work actually happened. the system was a hand-maintained copy of information that lived somewhere else, which is why it rotted the moment things got busy. copies always rot.
so now anything with steps in it lives in the thing that runs the steps, and it holds its own state whether anyone checks in or not. the notes file only holds things with no home, which is a much shorter list than we were designing for.
still messy. but it stopped decaying, which the elaborate version never managed
because a dashboard only answers the questions someone thought of when they built it. anything outside that is a slack message to whoever owns the data and then you wait.
and the questions that matter are never the ones on there. not "what's revenue this week." more like why did returns spike in one region, or which of the four things we changed is the reason CAC moved. nobody builds a tile for that in advance.
so you check the dashboards every morning looking for something to be wrong, and when something is wrong the thing that flagged it can't tell you why. then you wait two days for an answer or just make the call without it.
bigger companies solve this by hiring an analyst, which is basically paying a person to be the query layer. no idea what you're meant to do below that headcount
noticing our comparison and "x vs y" pages get cited way more than anything else we've written. long guides basically never show up, which is a bummer given the time cost to produce.
wondering if that's a pattern or just our niche
Not something you never believed in. Something you actually did for a while, then dropped, and nothing bad happened.
Looking for inspo, and still working through some of of ours.
I've been working in the eCommerce/AI space and kept running into the same problem: everyone uses "AI" to mean something completely different. A chatbot wrapper, a standalone tool, a multi-agent platform — all called AI. That makes it nearly impossible to evaluate tools, compare approaches, or have a meaningful strategic conversation.
So I tried to build a clearer taxonomy. Here's what I landed on:
The AI System Spectrum — 7 Layers:
Layer 1 — AI Feature: A single AI capability inside a larger product. Smart autocomplete, grammar checkers, recommendation widgets. You don't buy the product for the AI — it's a detail.
Layer 2 — AI Wrapper: A user-facing interface on top of someone else's model (usually accessed via API). Wrappers make powerful tech accessible but don't own the intelligence. If the model provider changes terms, the wrapper has no leverage.
Layer 3 — AI Tool: A standalone product using AI to solve a specific task. Unlike a wrapper, it adds proprietary logic and workflows. But it still operates in isolation — no shared data across your other tools.
Layer 4 — AI Platform: Multiple AI tools unified under one system. Shared data, connected workflows, compounding returns. The output of one capability starts improving another.
Layer 5 — AI-Native System: Built from the ground up with AI at the core. The architecture and decision logic ARE the AI. Remove it and the product ceases to exist.
Layer 6 — Agentic System: AI that operates autonomously — perceives context, makes decisions, executes actions, improves from outcomes. Doesn't wait for human prompts.
Layer 7 — Agentic Platform: Multiple agentic systems orchestrated across business functions. Shared memory, cross-domain reasoning, autonomous coordination. AI as the operational layer, not just a tool.
The three dimensions I used to differentiate:
Most businesses I talk to in eCommerce are at Layer 2–3 (wrappers and tools) but describe themselves as being at Layer 4–5.
Curious what you think on:
I've been working in the eCommerce/AI space and kept running into the same problem: everyone uses "AI" to mean something completely different. A chatbot wrapper, a standalone tool, a multi-agent platform — all called AI. That makes it nearly impossible to evaluate tools, compare approaches, or have a meaningful strategic conversation.
So I tried to build a clearer taxonomy. Here's what I landed on:
The AI System Spectrum — 7 Layers:
Layer 1 — AI Feature: A single AI capability inside a larger product. Smart autocomplete, grammar checkers, recommendation widgets. You don't buy the product for the AI — it's a detail.
Layer 2 — AI Wrapper: A user-facing interface on top of someone else's model (usually accessed via API). Wrappers make powerful tech accessible but don't own the intelligence. If the model provider changes terms, the wrapper has no leverage.
Layer 3 — AI Tool: A standalone product using AI to solve a specific task. Unlike a wrapper, it adds proprietary logic and workflows. But it still operates in isolation — no shared data across your other tools.
Layer 4 — AI Platform: Multiple AI tools unified under one system. Shared data, connected workflows, compounding returns. The output of one capability starts improving another.
Layer 5 — AI-Native System: Built from the ground up with AI at the core. The architecture and decision logic ARE the AI. Remove it and the product ceases to exist.
Layer 6 — Agentic System: AI that operates autonomously — perceives context, makes decisions, executes actions, improves from outcomes. Doesn't wait for human prompts.
Layer 7 — Agentic Platform: Multiple agentic systems orchestrated across business functions. Shared memory, cross-domain reasoning, autonomous coordination. AI as the operational layer, not just a tool.
The three dimensions I used to differentiate:
Most businesses I talk to in eCommerce are at Layer 2–3 (wrappers and tools) but describe themselves as being at Layer 4–5.
Curious what the community thinks:
Full write-up with more detail on each layer: accessfuel.com/blog/the-ai-system-spectrum
I've been working in the eCommerce/AI space and kept running into the same problem: everyone uses "AI" to mean something completely different. A chatbot wrapper, a standalone tool, a multi-agent platform — all called AI. That makes it nearly impossible to evaluate tools, compare approaches, or have a meaningful strategic conversation.
So I tried to build a clearer taxonomy. Here's what I landed on:
The AI System Spectrum — 7 Layers:
Layer 1 — AI Feature: A single AI capability inside a larger product. Smart autocomplete, grammar checkers, recommendation widgets. You don't buy the product for the AI — it's a detail.
Layer 2 — AI Wrapper: A user-facing interface on top of someone else's model (usually accessed via API). Wrappers make powerful tech accessible but don't own the intelligence. If the model provider changes terms, the wrapper has no leverage.
Layer 3 — AI Tool: A standalone product using AI to solve a specific task. Unlike a wrapper, it adds proprietary logic and workflows. But it still operates in isolation — no shared data across your other tools.
Layer 4 — AI Platform: Multiple AI tools unified under one system. Shared data, connected workflows, compounding returns. The output of one capability starts improving another.
Layer 5 — AI-Native System: Built from the ground up with AI at the core. The architecture and decision logic ARE the AI. Remove it and the product ceases to exist.
Layer 6 — Agentic System: AI that operates autonomously — perceives context, makes decisions, executes actions, improves from outcomes. Doesn't wait for human prompts.
Layer 7 — Agentic Platform: Multiple agentic systems orchestrated across business functions. Shared memory, cross-domain reasoning, autonomous coordination. AI as the operational layer, not just a tool.
The three dimensions I used to differentiate:
Most businesses I talk to in eCommerce are at Layer 2–3 (wrappers and tools) but describe themselves as being at Layer 4–5.
Curious what the community thinks:
Full write-up with more detail on each layer: accessfuel.com
Not the hard stuff everyone mentions. The thing that turned out to be a bigger deal than anyone said.
Ours was competition. It's easy to think you're the only one in the woods until you walk in.
Direct's been climbing for months. Not from anything we changed. Best guess is AI answers and dark social, but totally a guess.
Is anyone actually breaking this down, or are we all just letting it sit there?
Single agent with good tools, fine. Chain three together and suddenly you're debugging a game of telephone where each one confidently passes along a slightly wrong version of what it got.
Is anyone else solving for this or is everyone just adding more validation steps and hoping?
Genuinely curious. Not asking which metrics are bad, but which one you personally still put in the deck every month while knowing it doesn't mean much.
Mine's blended CAC. Nobody's ever questioned it and I'd struggle to defend it if they did.
Half the traffic shows up as direct. The rest shows up as nothing.
If you've found another way to see it that isn't "our branded search went up so probably," we'd love to hear it.
