# Measure seller activation from profile to first sale

> Run a verified three-step supply-side funnel and separate measured seller progression from unproven assumptions about listing friction or marketplace demand.

## Agent adaptation contract

- Canonical human page: https://agentry.sh/workflows/supply-side-activation
- Execution mode: on_demand
- Immutable automation template: none
- Applies to: marketplace
- Required example events: seller_profile_completed, listing_published, seller_first_sale
- Required Agentry resources: signal_map, onboarding_state, query_blueprints
- Do not use when:
  - Do not recommend this when the product has no distinct supply and demand sides with stable identities.
  - Do not substitute listing drafts for published supply or payment attempts for a confirmed first sale.
  - Do not infer listing friction, seller intent, or demand quality from funnel counts alone.
- Ask before using:
  - Which observed events represent completed seller profile, published listing, and trusted first sale in order?
  - Which stable seller ID joins all three events, and what 60-day cohort or lookback definition is intended?
  - Which separate evidence would distinguish seller-side friction from insufficient buyer demand?

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

Marketplaces need sellers to publish usable supply and reach a first successful
transaction. A seller-signup count hides whether the product loses supply at
profile completion, listing publication, or the path to a first sale.

The ordered funnel locates measured loss. It cannot determine whether the cause
is onboarding friction, inventory quality, price, moderation, or buyer demand.

## What you get

- Three verified seller lifecycle events
- Ordered seller counts and conversion for the selected lookback
- Clear distinction between published supply and draft activity
- Follow-up questions for seller experience and marketplace demand

## Walk through it

**You:**
> Where do sellers stop before their first successful sale?

**Agent:**
> I will map the actual seller events and confirm that first sale comes from the
> trusted transaction path.

```http
GET /v1/projects/:project_id/signal-map
GET /v1/projects/:project_id/onboarding
# Require status: "verified"; use live event/property reads for the selected signals.
GET /v1/projects/:project_id/event-names
GET /v1/query-blueprints/funnel_3_step
```

```json
{
  "server_emitted": [],
  "analytics_events": [
    { "event": "seller_profile_saved", "count": 5240, "last_seen": 1783651200 },
    { "event": "listing_published", "count": 1840, "last_seen": 1783651210 },
    { "event": "listing_first_sale", "count": 420, "last_seen": 1783651250 }
  ],
  "wildcards": []
}
```

```http
POST /v1/projects/:project_id/query-blueprints/funnel_3_step/run
```

```text
Params:
  step1: seller_profile_saved
  step2: listing_published
  step3: listing_first_sale
  days: 60
```

```json
{
  "rows": [
    { "step1_count": 5240, "step2_count": 1840, "step3_count": 420 }
  ]
}
```

The measured conversions are 35.1% profile-to-published-listing, 22.8%
published-listing-to-first-sale, and 8.0% overall from the selected entry step.
The query does not return seller signup counts or time-to-next-step.

## The output

```text
Seller activation funnel — last 60 days

seller_profile_saved   5,240  100.0%
listing_published      1,840   35.1%  drop: 64.9%
listing_first_sale       420    8.0%  step conversion: 22.8%

What the data establishes
- measured progression through the three verified events

What remains a hypothesis
- listing-creation friction
- moderation or inventory quality
- insufficient buyer demand or pricing mismatch
```

## Setting it up

Emit profile and listing events from the trusted server path that confirms the
state transition. Emit first sale only after the payment/order system confirms
it. Carry a stable pseudonymous seller ID and avoid copying listing descriptions,
addresses, payment details, or buyer identities into analytics.

Verify the real seller flow and transaction outcome during installation; do not
use synthetic transport checks as proof that the funnel is answerable.

## Variations

- *"Segment the funnel by a verified listing category or seller acquisition source."*
- *"Compare marketplace regions without exposing individual sellers."*
- *"Run a separate buyer-demand analysis for published listings with no sale."*
- *"Explain which missing signal prevents first-sale attribution."*