Analytics
Analytics
Searches, vehicles, zero-result queries and coverage.
The dashboard answers three questions: what are shoppers searching for, which vehicles are they driving, and where is your fitment data letting them down.
What's recorded#
- Searches
- the query, whether a vehicle was detected, result count, and whether the rescue ladder fired.
- Suggestions
- autocomplete, counted separately so per-keystroke volume never swamps real searches.
- Vehicles
- which YMMS combinations were selected, and from which widget.
- Fitment coverage
- the share of indexed products with at least one vehicle mapped or judgeable.
- Zero results
- queries that returned nothing, or that only returned rescued results.
Nothing customer-identifying is ever stored: no customer ID, no IP, no session token. Queries are scrubbed of email and phone shapes before they are written. That is why the GDPR customer redact webhook has no analytics work to do — there is nothing keyed to a person.
The reports#
Overview — searches, vehicle selections and coverage over the window, with sparklines. The number to watch in week one is coverage.
Searches — top queries, zero-result queries, and the share of searches where a vehicle was involved. A store where under a fifth of searches involve a vehicle usually has its hero below the fold.
Vehicles — the vehicles your shoppers actually drive, ranked. This is the most commercially useful screen in the app: it is a stocking brief, a landing-page priority list and an ad-targeting list at once, whatever categories you sell.
Windows#
Starter keeps 30 days, everything else 90. Data older than the window is pruned by a rollup job; exporting before a downgrade is worth doing.
Reading it honestly#
A few traps worth naming:
- Bot traffic inflates searches, not vehicle selections. If searches climb and selections don't, check your traffic before you celebrate.
- Coverage is products, not revenue. 60% coverage that misses your bestsellers is worse than 40% that includes them. Sort the editor by revenue.
- Zero-result queries include your own staff. Someone testing SKUs shows up here.
Most stores are surprised by at least one vehicle in their top twenty. That is a stocking decision, a landing page and an ad set — from a report you get on every plan.
Support is answered by the people who wrote this code — not a ticket queue.