Why does the tracking audit ask me to sign in?

Each scan opens a real browser session on the store, and its report names the store it read. A session keeps both out of reach of scripts, and the report saves at its own link for whoever you send it to.

Free tool

Analyze any Shopify store

One address, one report: the theme and apps it runs, its tracking, its ads and emails, and where its niche is heading.

Analyze a store Use it via MCP

Free to read, no account
27 fields from the index
41 tracking checks

The report

Every tab, field by field

Every field a report can hold, tab by tab, with the plan that reads it. A paid field shows locked in a free report, not missing.

Field	Plan
`framework`	Free
`theme_name`	Free
`theme_role`	Free
`theme_store_id`	Free
`theme_version`	Free
`theme_schema_name`	Free
`theme_schema_version`	Free
`theme_lineage`	Free
`apps`	Free
`pixels`	Free
`cdn`	Free
`has_subscription`	Free
`tracking_ids`	Free

Fields read from the indexStack, ads and email, each badged with its source.: 27
Tracking checks4 layers, graded from A to F.: 41
Probes in one deep scanWhat writes the record the report reads.: 34

Limits

What the report cannot prove

Three limits to know before you act on it.

It reads the last scan
A result is our last scan of the store, not a live visit. A theme changed this morning shows after the next scan.
Tracking is one visit, from outside
It reads one visit from the outside: it never logs in to GA4, Meta or Google Ads, so it cannot see what they recorded.
It hides stores that opted out
A store whose owner opted out answers exactly like one we never saw. The page never confirms that a record exists.

How it works

One record per store, with its source

Our deep scan writes one record per store. The report reads its sections and badges each field with the layer that produced it.

L1Read from the store's own API, when its owner connected it.
L2Observed on the public storefront or in an ad library.
L4Estimated by a model, with its confidence.

probes in one deep scan

They write the record behind the stack and signals tabs. The tracking tab runs its own live browser visit.

Follow a store, not a ranking

The Radar ranked the whole index. Following keeps the stores you care about in your Brand Tracker, with their changes over time, and the last button of a report adds one.

Free25 stores per shop
Pro200 stores per shop
Max 5x500 stores per shop

Go further

The index behind the report

The report reads one store. These pages say what the index holds, where it comes from and how an agent reads it.

Is it really free?

Yes for the stack and signals tabs: reading a store needs no account, and the JSON version allows 30 calls a minute per IP, 10 times that with an Intelligence API key. The tracking audit is free too, after sign-in, 10 scans an hour per IP. The market lenses and some ad figures need a paid plan.

How fresh is the answer?

As fresh as our last scan of the store. Each field keeps the time it was observed, so a change made today shows after the next scan.

Why does my domain return nothing?

We have not scanned it yet, or its owner opted out: the page answers both the same way on purpose. Start a live scan from the result, 8 an hour per IP, after sign-in or a quick check.

What does following a store do?

It adds the store to your Brand Tracker, under the store selected in your account, so its changes show over time. Each plan caps how many stores a shop follows, and a new follow counts against the day's budget of full reads.

Can an AI agent run it?

Yes. Point your agent at the BoostEcom Intelligence MCP, or call GET /api/intelligence/inspect/theme with a domain parameter: the same fields, as JSON.

Ask @Atlas what a store is doing

Type a domain and a question. @Atlas reads the whole record, within your plan, not one section.