Skip to main content

How sessions work

A session preserves the context of a Landbase search so you can refine an audience instead of starting over. The server-side session is identified by a UUID and contains the conversation and audience context needed for follow-up work.

The session model

A session has two parts:
  1. A server-side identifier — Landbase uses this identifier to associate requests with one conversation thread.
  2. Conversation state — the query history, audience context, and refinements that have been applied.
The server keeps the session state. It tracks:
  • The query history for the session.
  • The companies or people produced by earlier queries.
  • The filters and decisions applied in follow-up queries.
This means a follow-up such as “Narrow to 50–200 employees” can build on a previous search for “SaaS companies in London” without repeating the original criteria.

Refining a session

A refinement adds a new constraint or asks for a different view of the existing audience. It does not need to repeat the original search criteria because the session already contains that context. Good refinements are specific and incremental:
  • Narrow the geography or company size.
  • Add a role, industry, or technology requirement.
  • Request additional fields for the existing audience.
  • Ask for a smaller sample before exporting the full result.

Session lifetime

Sessions do not expire based on a fixed clock. A session remains accessible as long as the underlying data is retained on the Landbase backend. In practice, sessions from recent runs are reliably accessible. If a session is no longer available, a new search starts a fresh conversation rather than silently continuing from incomplete state.