# Find marketplace zero-result searches

> Identify marketplace searches with no matching supply so product and ops teams can fix demand-supply gaps faster.

## Agent adaptation contract

- Canonical human page: https://agentry.sh/workflows/marketplace-search-zero-results
- Execution mode: on_demand
- Immutable automation template: none
- Applies to: marketplace
- Required example events: marketplace_search_performed, listing_viewed, booking_started
- Required Agentry resources: none declared
- Do not use when:
  - Do not use until the example events are mapped to observed project signals, the current onboarding state is verified, and live event/property reads prove the required data is present.
  - Do not recommend this when the product has no distinct supply and demand sides with stable identities.
- Ask before using:
  - Which observed events map to marketplace_search_performed, listing_viewed, booking_started? Is the current onboarding state verified, and do live event/property reads show non-synthetic traffic for them?
  - Which live properties provide marketplace_search_performed.query, marketplace_search_performed.category, marketplace_search_performed.result_count, marketplace_search_performed.geography, listing_viewed.listing_id, booking_started.listing_id, and which stable user or account identifier joins the signals?

This is an adaptable workflow example, not an API recipe. Map event and property names to the project's saved signal map, require status: "verified" from GET /v1/projects/:project_id/onboarding, and confirm the required signals through live event/property metadata and rows. Fetch current OpenAPI or query-blueprint details before making calls. Do not infer unattended authority from this page.

## Why this matters

Zero-result searches are explicit demand with no available supply. They tell marketplace teams what inventory, geography, taxonomy, or search behavior needs attention.

## What you get

- Top zero-result queries by category and geography
- Result-count distribution for high-demand searches
- Whether users recover with another query
- Supply or taxonomy actions ranked by potential demand

## Walk through it

**You:**
> What are people searching for that we do not have?

**Agent:**
> I'll find searches with result_count equal to zero and group them by query, category, and geography.

```text
Endpoint: POST /v1/projects/:project_id/analytics/query
Exact shape: /v1/openapi.json?path=%2Fv1%2Fprojects%2F%7Bproject_id%7D%2Fanalytics%2Fquery&method=post
Custom HogQL goes in the OpenAPI-defined `query` field.
Concept fields:
  query: "SELECT properties.query AS query, properties.category AS category, properties.geography AS geography, count() AS searches, count(DISTINCT distinct_id) AS users FROM events WHERE event = 'marketplace_search_performed' AND toInt(properties.result_count) = 0 AND timestamp > now() - INTERVAL 30 DAY GROUP BY query, category, geography ORDER BY users DESC LIMIT 25"
```

## The output

The agent returns demand gaps ranked by user count and search volume. It should distinguish supply acquisition, category taxonomy, synonym handling, and geography coverage.

## Setting it up

Track every marketplace search with query, normalized category, geography, and result count. Include follow-up listing views or booking starts to measure recovery.

## Variations

- *"Show zero-result searches by city."*
- *"Which categories have demand but no supply?"*
- *"Publish weekly marketplace demand gaps."*