Personyze Wiki Personyze Wiki docs
Open Personyze
Docs/ Recommendation Setup & Feeds/ Reviewing the Data Behind Recommendations
Recommendation Setup & Feeds

Reviewing the Data Behind Recommendations

Personyze recommendations are not only powerful in what they can output to users to increase engagement and revenue, but also in the data you can derive from them, to learn about your products, segments,…

1 min read Updated 7 days ago
×

Click anywhere to close

Before trusting a recommendation widget, look at what it has learned. Four places show you the data behind recommendations:

  • Campaign readiness — every recommendations campaign’s side panel scores the pipeline live: catalog in place, interactions arriving (view / add-to-cart / purchase each shown separately), and whether the engine is still in its collecting phase — with an Expedite option to upload historical transactions.
  • The catalog viewer — Settings → Recommendations: the items themselves, their fields and images, exactly as the engine sees them (feed setup).
  • Live eventsLive visits shows interactions as they arrive, per visitor — the fastest way to confirm tracking end to end (tracking setup).
  • Visitor interests — the inferred interest profile each visitor accumulates, which interest-based algorithms rank by: interests for recommendations. Also readable per user over the REST user_interests object.
Interactions arriving
The Interactions step: each event type with live arrival status. Click to enlarge.

What the engine learns from what

  • Views and add-to-carts drive the ranking — they say what attracts.
  • Purchases close the loop — they attribute revenue and teach bought-together patterns.
  • Category views build interests, powering “more from what they care about” logic.

Once data flows, results appear in the campaign’s Performance step and the recommendations reports — metric definitions in the analytics glossary.

Did this page answer your question?
Thank you — that goes to whoever maintains this page.