Product news
Whether an alert already happened on another client, in the alert itself
Published Nov 18, 2026
On the Agency plan, History lists the alerts of all your clients, grouped when they are the same, and an alert's page shows which of your other clients had it before. Where clients share what changed, it says so. It does not say why, predict a break or prevent one.
What you see
An alert opens on a client's store and you ask yourself whether you have seen it before. Until now the answer lived in your head or in a spreadsheet. On the Agency plan, TraceLog answers it from your own clients' alerts.
- On the alert. A block, On your other projects, says when the same alert already happened on another client, in the product's sentence: "The same alert on Clinic, Mar 1, 2026." (Clinic stands for one of your clients.)
- On the project's home. The same block lists the projects that share what changed with this one, three at most, while the alert is open and for seven days after it closes.
- In History. A page lists the alerts of all your projects, grouped when they are the same, with how many projects and how many times: "2 projects, 3 times". It shows the 50 most recent. Under its heading stands one line: the dates show the order, not the cause.
What the other clients share
When an alert opens soon after TraceLog saw a configuration change on a
client's store, it looks for another client that shares what changed: the
platform's version, the theme, the way consent reaches TraceLog or the
checkout. It says so under Sharing what changed: "This project and Clinic
share Storefront 4.6.1. On Clinic, add_to_cart stopped arriving on Mar 2, 2026." (The
names and dates are an example.)
It compares what the plugin or the module reports with what the other project reports, and what was entered in Installation and keys with what was entered there. Never one source against the other. With no change observed before the alert, it states nothing.
What to do with it is your decision. TraceLog places the dates; it does not read them for you.
What it does not do
It does not say why an alert happened, predict that another client will break or prevent a break. It sends no mail of its own and does not classify your clients. An alert that was TraceLog's own fault is left out. A client's contact, or someone with a link to a report, never reads it, and your notes on a client never leave your organization. What it adds to the month's report is for your team and stays out of the PDF and the CSV.
On which plans and channels
The Agency plan only. It is read by your organization's members who can read the portfolio.
A repeat needs the same alert on a project of the same channel: the match is on the alert's kind, its reason and the channel, so a WooCommerce store is not set against a Shopify one. A shared value needs the same channel too. It comes from what the WooCommerce plugin or the PrestaShop module reports, or from what was entered in Installation and keys.
Keep reading
Guide
Published Nov 18, 2026
GA4 custom insights can email you when conversions drop. Telling fewer sales from fewer recorded takes a second record, kept beside GA4.
Guide
Published Nov 19, 2026
Meta or Google Ads counting more purchases than orders? Your confirmation page may be sending some twice. How to find the repeat by hand.
Product news
Published Nov 18, 2026
Analytics marks the days your site changed and lists what changed under the chart. On WooCommerce and PrestaShop, TraceLog notes a new theme by itself.