Radar vs Benchmark
Jsonify offers two products for competitive intelligence. Radar monitors public web pages. Benchmark simulates competitor quote journeys. Here's when to use each.
Two products, one platform
Jsonify Radar and Jsonify Benchmark solve different competitive intelligence problems. Some teams use one, some use both. The right choice depends on how your competitors expose their pricing and product information.
Radar — reading public pages
Radar continuously monitors publicly visible web pages and extracts structured data from them. It reads content that any visitor could see — product listings, pricing pages, promotional banners, category pages, review sites.
Best for:
- Tracking product pricing across retailer and marketplace sites
- Monitoring competitor catalogs, assortments, and availability
- Aggregating reviews and ratings across platforms
- Tracking promotional activity and marketing positioning
- Monitoring market changes like new entrants or product launches
How it works: Radar agents visit pages on a schedule (typically daily), read the content, and extract the fields you've defined. Data is delivered as structured datasets with full change history.
Benchmark — simulating quote journeys
Benchmark goes beyond reading pages. It interacts with competitor websites — filling out forms, selecting options, navigating multi-step flows — to extract pricing and offers that only appear after user interaction.
Best for:
- Insurance quote comparison (home, auto, travel, pet, business)
- Utility and telecoms tariff monitoring (broadband, energy, mobile)
- Configured product pricing (build-your-own bundles, custom configurations)
- Subscription and SaaS pricing tiers
- Any market where pricing requires filling out a form or completing a journey
How it works: Benchmark agents simulate real customer journeys at scale. They fill in postcodes, select coverage options, configure products, and extract the resulting quotes. You define the customer profiles to simulate, and Benchmark runs thousands of journeys simultaneously.
Comparison
| Radar | Benchmark | |
|---|---|---|
| Approach | Reads public pages | Fills forms and simulates journeys |
| Data type | Visible product/pricing data | Quote and offer data from interactions |
| Industries | Retail, ecommerce, F&B, real estate | Insurance, utilities, telecoms, SaaS |
| Update cadence | Daily or weekly | On-demand or scheduled runs |
| Scale | Thousands of pages per day | Thousands of journeys per run |
| Setup | Define sources and fields | Define journeys and customer profiles |
Using both together
Some teams use both products. For example, an insurance company might use Radar to monitor competitor marketing pages, product features, and promotional messaging, while using Benchmark to extract actual quote pricing across different customer profiles and coverage levels.
Both products deliver data through the same dashboard, API, and integration channels, making it straightforward to combine datasets.
More documentation