Radar or Benchmark?
Choose the approach based on how a source exposes the information you need.
Benchmark Enterprise
Jsonify launches with Radar. Benchmark quote journeys are available through enterprise and have not launched in self-serve.
Start with the source
If the information is already visible in a listing, product page or mobile app, start with Radar. If the offer only appears after providing a set of inputs, Benchmark is available through enterprise for that workflow.
| Radar | Benchmark (enterprise) | |
|---|---|---|
| Starting point | A page, listing or app screen | A defined form or quote journey |
| Typical data | Prices, stock, catalogs, menus, reviews | Premiums, tariffs, rental rates, configured offers |
| What you define | Sources, fields and collection scope | Journey inputs, comparable scenarios and output fields |
| Example | Compare the listed price of the same product | Compare motor quotes with the same cover and driver profile |
Radar: observe what is available
Radar collects visible public information and turns it into a dataset you can monitor over time. It is useful for prices, promotions, product availability, menus and listings.
Keep identifiers and source context with the output. Two items with similar names may have different sizes, variants or terms; matching is part of the pipeline, not something to assume from the price alone.
Benchmark: run a comparable journey
Benchmark Enterprise follows forms and configuration steps to collect the resulting offer. The brief needs to define the inputs consistently so the results can be compared.
For example, an insurance comparison should keep cover, excess and relevant scenario inputs aligned. A rental comparison should specify location, dates and vehicle class. Record the terms that materially affect the price.
Combining the approaches in enterprise
A market can contain both listed prices and personalized offers. An enterprise deployment can combine the two approaches, provided it keeps enough context to distinguish the results.
Both approaches use pipelines that collect, process, verify and publish data. Sources, schedules and delivery are defined around your use case. Explore the solution examples or talk to us about a managed deployment.