When something changes on your site
After a routine change, a step can stop arriving while nothing on the site shows an error. These are the moments it happens, and what TraceLog shows in each.
In a store, a routine change can stop conversions being recorded
| When | What changes | What TraceLog shows | Plan |
|---|---|---|---|
| You change platform | Every event is installed again, on another checkout. | Whether each step arrives on the new platform: live while you install, then every day. | Every plan |
| You install or update a theme | A button or a page can stop sending its step. | If the step was arriving steadily, an alert names it and the figures it leaves incomplete. It comes the morning after a full day without it, or after seven days for a step under ten a day. | Every plan |
| You change the checkout or a payment method | A step of the checkout can stop sending its event. | Which step stopped arriving and since when, and which TraceLog figures it leaves incomplete. | Every plan |
| You change the consent banner | The browser can stop sending events, before or after consent. | If a step stops arriving, an alert with the days affected. Where the server confirms the order, the order still counts. | Every plan |
| You launch a campaign | New visitors arrive through new landing pages. | Each conversion's rate by campaign, channel and landing page, against the period before. | From Pro |
| Someone asks why sales fell | Perhaps nothing on the site, perhaps a change nobody noted. | Which conversion, step or segment fell against the period before, where the data supports the comparison. Never the cause. | From Pro |
For an agency, the same moments repeat across every client
| When | What changes | What TraceLog shows | Plan |
|---|---|---|---|
| You take on a new client | Another store whose tracking someone else installed. | You verify its installation live, in the same account and shared session limit as the rest. | Every plan; one limit on Agency |
| The portfolio on Monday | Any of the stores may have stopped recording a step. | Which client projects need attention, and the evidence for each. Never a rate, a ranking or a score. | Agency |
| You prepare the client report | A figure you present may rest on an incomplete record. | Which projects have an incomplete record, and beside a change you noted, what TraceLog observed afterwards. The order establishes no cause. | Agency |
It never says why
What TraceLog names
- What changed, where, and since when.
- Whether its own record is complete.
What it leaves to you
- Why it changed, and what to change: the decision is yours.
- What GA4, Meta or Google Ads received.
Start free before the next change
Free up to 10,000 sessions a month. No card.