← Back to all tipsOctober 10, 2026

What Tracker needs before it can recommend anything

Relatiq Tracker builds a behaviour profile per visitor from a single script. The setup is quick, but the useful recommendations take a little longer to show up — here's what actually happens in between.

The script does the heavy lifting

One snippet in your site template is enough: it captures pages, scroll depth, clicks and mouse movement for the whole visit, not a manually tagged subset of events. There's no event schema to design upfront, which is also why there's nothing to get wrong on day one.

Profiles start thin

A first-time visitor's profile is close to empty — a couple of page views, maybe a scroll signal. Recommendations at this stage are necessarily generic. This is expected, not a sign anything is misconfigured.

Returning visitors are where it gets useful

Profiles sharpen with each session. By the third or fourth visit, interest scores (0–1 per topic or category) start to separate cleanly, and recommended-next suggestions start reflecting actual browsing patterns rather than general popularity.

What to check in the first week

  • Events are flowing: check the profile for a test visitor shortly after adding the script.
  • Recommendations are requested per visitor from the API, not pre-computed in bulk — make sure your integration calls it at render time, not on a schedule.
  • Give it real traffic before judging quality. A handful of synthetic test sessions won't look like production behaviour.

If recommendations still look generic after visitors have built up a few real sessions each, that's worth a look — but give the data time to accumulate first.