Events
An action happens.The context stays.
Page views, attention to a section and target actions form a sequence of signals. Psssst preserves it so the visitor journey can be understood.
From task to outcome
A click is a fact.A journey gives it meaning.
An event belongs to a page, visitor and session. History shows what happened before an important action; current session state helps explain what matters during the visit.
How it works
- Arrival
- The landing page, referrer and first view establish the initial context of a visit.
- Sequence
- Views and actions are linked to the visitor and session. Signals can be considered together instead of as isolated counters.
- Continuation
- Events support analytics, interests and the work of consumers permitted to use the context.
In practice
A visitor arrives from an ad, explores several models and opens a form. Understanding that journey requires the preceding views and source, alongside the final click.
Boundaries and context
An event describes what happened. Creating a lead, a deal or a business workflow is a decision for the corresponding product using the context available to it.
In brief
Is only the final action retained?
The visit history matters too: arrival, page views and actions within the session.
Does an event automatically become a lead?
An event and an enquiry are different entities. The CRM product decides how the signal fits its own process.
Where do we start?
Start with your task, data sources and expected result. Then we can agree on configuration and connection.
Start with your task.
Tell us what your website or product needs. Together we can define the right connection.
Discuss a connection