What is real-time intent?
Real-time intent is what a customer is trying to do right now, read from what they are doing in this session. It is observed from current behavior rather than predicted from history, so it changes as the session changes.
Intent as current behavior
Real-time intent is what a customer’s behavior right now shows they are trying to do: comparing two products, stuck on a step, ready to buy. It is read from the current session rather than inferred from a profile computed earlier. The evidence is what they are doing as they do it, not a prediction about what they usually do.
Why real-time matters
Intent changes on almost every action. A visitor who was browsing a minute ago can be comparing now and stuck a minute later. A value computed before this visit describes who they were then, not what they are doing now, so acting on it means acting late. Intent is only useful while the session it describes is still open.
What you need to act on it
To act on intent in the moment you need the current state of the session available when the page renders, not minutes later. Signals computes what a customer is doing right now and serves it to your own systems; your code reads that state and decides what to do with it. The deciding and the acting stay in your stack.
See it on your own traffic
Add the SDK, define one attribute, and see an attribute updating against your own traffic in the first session. The free tier runs on the real engine: no card, no sales call.