Forty client stores. One screen.

You get blamed when the numbers look wrong, even when it was a theme update at eleven at night. Trace watches every client store and tells you before the client does.

Nothing to install. No client access to ask for. Add forty stores in an afternoon.

A specimen portfolio
ClientCoverageOpen
NorthgateGA4 silent on product2
Feltham & CoKlaviyo silent1
OakleafMeta uneven
Brightsideall firing
Millhouseall firing
Carrowayall firing

A specimen portfolio. Three of forty-two need you this morning.

The problem is not that tracking breaks

It is that nothing tells you. The page still loads, orders still arrive, and the only signal is a number that looks slightly off three weeks later.

A theme update at 23:00

Drops one line from the product template. The script still downloads. Nothing errors. Your conversion data quietly stops being true.

A plugin the client installed

Nobody told you. It changed the consent banner, and now every tag sits behind a state that never resolves.

Ad spend carries on regardless

Campaigns do not pause when the pixel stops. They keep spending and keep learning from nothing, which is worse than spending nothing.

Built for someone with a portfolio, not one shop

Checking forty stores by hand is forty tabs and forty judgements. That comparison is written out. Trace exists for the case where you will not do it twice.

No client access needed

We read the public pages a customer would. Nothing to install and no awkward email asking for admin on someone else's store.

Your branding on the report

Monthly proof that the tracking you set up is still working, going out under your name. Clients rarely ask for it and always remember receiving it.

Nothing opens on one reading

We wait for a second check to agree before telling anyone. A monitoring tool that cries wolf gets muted, and a muted tool is worse than none.

A change log per client

Every script added, removed or altered, with a timestamp. Useful in the conversation that starts "we didn't change anything".

What a check can and cannot see

Two observations per vendor: the library returned successfully, and a request reached the collection endpoint. A page whose own first-party beacon did not fire is reported as unobservable, not broken. The method is written in full, including hosted checkout, logins, and server-side tagging.

Start with one client store, free

Daily checks and email when something changes. No card. Most agencies add the second store within a month — that is when a paid plan starts. See the catalog.

Watch a store