How Landbase work fits into the platform
Landbase uses shared workspace objects for datasets, runs, sessions, and workflows. Different supported interfaces expose different ways to create and inspect those objects, but the underlying platform model is shared.Shared platform objects
Datasets
When you run a search, upload a file, or process existing data, Landbase creates or updates a dataset in your workspace. Datasets are the core data objects in the platform. A dataset can be inspected, enriched, transformed, published, or downloaded. When a processing operation starts from an existing dataset, Landbase records the relationship between the input and output.Runs
Every search or processing operation creates a run. A run represents one invocation of Landbase work: what was requested, what it produced, and the dataset or workflow state associated with it. Runs provide an operational record that can be inspected when you need to understand what happened or recover from an interrupted operation.Sessions
Sessions group related search runs together. A session preserves the conversation and audience context needed to refine a search without repeating the original criteria. See How sessions work for the conceptual model and interface-specific session guidance for implementation details.Workflows
Workflow runs process datasets through repeatable steps such as matching, enrichment, qualification, transformation, or publishing. A workflow can create a child dataset and record its status and lineage. The web platform shows workflow state, errors, and the child datasets produced. Supported interfaces can also inspect or continue workflow work when they expose the relevant operation.Why the shared model matters
The shared model makes it possible to move from exploration to repeatable processing:- Search for or upload an initial audience.
- Inspect the resulting dataset and run.
- Process the dataset through one or more workflows.
- Review lineage and output datasets.
- Download or send the final result to the next system.