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:- A server-side identifier — Landbase uses this identifier to associate requests with one conversation thread.
- Conversation state — the query history, audience context, and refinements that have been applied.
- The query history for the session.
- The companies or people produced by earlier queries.
- The filters and decisions applied in follow-up queries.
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.

