Skip to main content
Data → Events has two views:
  • Events (the default) shows the behaviour arriving from your integrations, as it arrives.
  • Configure signals is where you define event types, their weights and the templates that models train from.
To send events from code, see Events.

​
The event log

Each row is one event: its type, user, item, placement, session and time. Use it to confirm that an integration is working before you look at recommendation quality.
  • Search finds events by user, item or event type.
  • The filter buttons (All, Event, User, Item, Placement, Session) narrow the table to one value. Select a value in a row to filter by it, and Clear filter to go back.
  • Analyze opens the current filter in Analytics for a fuller breakdown.
A Sample label means no real events have arrived yet.

​
Configure signals

Select Configure signals to manage the event types your workspace accepts and how much each one counts.

​
Event types

The table lists each event type with its value (weight, 0 to 100), how much data exists for it (Data availability), and a link to its analytics. The integer shown with each event is the ID your code sends as event_id.
  • Event library adds standard event types with sensible default weights, grouped into browsing, recommendation strips, engagement, commerce, media and negative signals. See the full list with defaults.
  • Add Custom… creates your own: give it a name, an initial value and a polarity. Negative signals, such as skip, hide or report, teach the ranker to suppress similar items.
  • Edit changes a label, value or polarity. The ID never changes, so your integration keeps working.
  • Change several values in the table, then Save Values.
Every workspace starts with View, Click and Purchase. The number of custom event types depends on your plan.

​
Signal templates

A signal template is the input to model training: which event types count, their weights, and the minimum data required. Start from an NSL preset or from Your templates: Editing a template loads its events into the table. Change them there, then Update Template. Reset to default restores the preset’s weights.

​
Integration signals

Integration signals shows what the embed, order connectors and history imports record, and which of your event types receives each one. Change the event type to send a signal somewhere you already track. See Integration signals.

​
Import history

Import history uploads a CSV of past behaviour: a user, an item (your SKU, the NSL item ID or a page URL), an event and a timestamp. You choose which event type each event name in the file becomes, or leave it out. See Import history.

​
Training settings

Training settings starts a training run from the selected template.
1

Choose recommenders

Add one or more recommenders. Each runs as an independent job against one shared snapshot of your data.
2

Check readiness

Signal readiness shows whether each selected signal meets the template’s minimums. Recommenders with unmet data requirements are flagged.
3

Review cost

The estimated training cost and the data snapshot are shown before you start.
4

Start training

Select Start training. Follow progress in Model Training and review results in Models.
Recommenders that support tuning expose these settings. The defaults suit most workspaces. Custom training is available on the Pro plan and above.