Conversions dropped suddenly: sales or tracking?
Last updated Oct 22, 2026
A sudden drop in conversions has two very different explanations: fewer people bought, or your site stopped recording a step of the purchase while they kept buying. The second usually follows a change — a theme, a checkout, a consent banner or a platform — and shows no error. Compare the drop with your store's own orders first.
Fewer sales, or fewer recorded
- Fewer sales show in your store's admin too: the paid orders fall on the same days, and visits or carts usually fall with them.
- Fewer recorded shows only in the tools that count from the page: the store's admin keeps its usual orders while GA4, Meta or Google Ads report fewer conversions, often from one day to the next.
Conversions that stop being recorded can look like a change in your business.
What a change can stop
- A theme. A tag or snippet added to the old theme is not in the new one unless you add it again.
- A checkout. The purchase may have fired on a page that no longer exists, or now fires only for one payment method.
- A consent banner. A tag waiting for a consent decision it never receives sends nothing, and every step it sends goes quiet at once.
- A platform. The old plugin's events stop, and the new platform's may carry other names.
The replatform guide walks through each check after a change.
How to check it by hand
- Note the first day of the drop, and look for a change that day: a theme, a plugin, a checkout setting, a consent banner or a release.
- For the days before and after, compare your store's paid orders with the conversions each tool reports. If the orders hold and the conversions fall, the recording changed, not the sales.
- Place a test order and follow it through every step, checking that each tool records it.
- Check whether the drop is on one device or browser only: a step that stops on mobile alone points to the mobile theme or checkout.
What TraceLog sees and what it does not
TraceLog keeps its own record of your conversion path, beside the tools you already run, and reads nothing from GA4, Meta or Google Ads. It checks every declared path once a day, in the project's time zone.
When a step has been arriving steadily — present on five of the last seven days — TraceLog alerts you the morning after a full day without it, or after seven days in a row for one that arrives fewer than ten times a day. That alert is on every plan, the free one included (alerts).
TraceLog says what changed and where, never why, and never what to change.
Questions
Does TraceLog tell me why my conversions dropped?
No. It says which step stopped arriving and since when, in its own record. Why it stopped, and what to change, stay your decision.
Can it tell a real fall in sales from tracking that stopped?
Not on its own. Its record is a second one, beside the tools you already run: if your store's orders and TraceLog's conversions hold while another tool's fall, the sales did not fall. Why that tool counts less, TraceLog does not see.
Does the alert need a lot of traffic?
No. The stop alert needs a step that arrives steadily, and one that arrives fewer than ten times a day is alerted after seven days in a row without it. Statistical detection of smaller falls needs more volume and is on the paid plans.
Try it on your store
Define your conversion path, and TraceLog checks it while you install.
Free up to 10,000 sessions a month. No card.