Verify after a replatform

A theme, checkout, consent or platform change can interrupt or duplicate a declared event without a visible error: orders keep arriving while the purchase event stops. TraceLog checks the declared conversion path against the events it receives. After a change, check that each step still arrives before you read a figure over it.

What a change can break, and how it looks

• A theme. A snippet pasted into the old theme is not in the new one unless you add it again. Nothing on the page fails; the events stop leaving it.
• A checkout. The purchase may have fired on a page that no longer exists, or it may now fire twice. The steps before it keep arriving.
• A consent banner. The capture code can wait for a consent decision it never receives, and the whole path goes quiet at once.
• A platform. The old plugin's events stop, and the new platform's events may carry different names.

None of these has to show an error. Analytics and advertising platforms keep showing numbers, which may be lower, or higher when an event is duplicated.

How to check, in order

1. Open the project's Installation page. Every declared step and the conversion are checked once a day, in the project's time zone. After a change, the check either sees the whole path or names the element that stopped and the day it stopped.
2. Place a test order. On Shopify, through the Bogus Gateway; on WooCommerce, with a payment gateway in test mode; on a script or npm install, in the tab Open my site opens from the Installation page — an order placed in any other tab counts as real. The order is marked as verification traffic: the real path runs, and nothing is counted.
3. If you renamed a step on purpose, edit the plan (script and npm; on Shopify and WooCommerce the plan is the app's or plugin's and is not edited). Each edit creates a new plan version, which later checks use, so a deliberate rename is not reported as a fault.
4. Read data health. For each conversion, TraceLog says how many it saw in the browser, how many on the server, and how many only the server saw. If the browser path went quiet after the change and the server still confirms purchases, that count says so.

Any figure that would count the days the path did not arrive states those days in its place. Do not compare a conversion rate over them, and do not judge a campaign on them.

Shopify's checkout dates

Shopify published three dates on which code pasted into a store stops running (Shopify developer changelog):

• 26 August 2026. Every store outside Shopify Plus was upgraded to the new Thank you and Order status pages. The Additional scripts field stopped running on that day. Plus stores crossed the same date on 28 August 2025.
• 1 October 2026. Apps can no longer create or update a script tag.
• 1 March 2027. Script tags stop being injected into storefronts.

The TraceLog app on Shopify is a web pixel extension, created by the app when you install it. It never used the Additional scripts field or a script tag, so none of these dates changes what it captures. Install it on a store that crossed the first date and the purchase path verifies the same way it did before.

What TraceLog cannot tell you is whether another tool's code on those pages stopped. It does not inspect analytics or advertising platforms. What it shows is whether its own purchase event still arrives, and how many purchases only the server saw.

On WooCommerce the plugin, not the theme, emits the declared events, so a theme change does not remove them. A checkout or consent plugin change can, and the same daily check shows it.

For agencies

Before a client's old site is switched off, run the test order. Keep the Installation page open during the switch, and read the portfolio the next morning: it says which projects need attention, with the counts behind each one. One account holds every client project on one pooled session limit (agencies).

If the check reports a fault

What the product shows on the Installation page and in the alert, by case:

No signal from TraceLog's code on the page opened for verification.

Check that the TraceLog snippet is installed and that your consent setup is not preventing it from loading.

TraceLog's code has no consent.

Grant consent for this test, or check that your consent platform allows TraceLog for real visitors.

Steps arrive, but no conversion.

Trigger the declared conversion and check that its event is sent after the preceding steps.

The full matrix, with what each condition does to verification, is on install with a script tag.