# Add the events a funnel needs but nobody instrumented

A funnel that cannot be measured because two of its steps were never instrumented.

Category: Analytics and tracking
Source: https://letsship.ai/use-cases/add-the-events-a-funnel-needs
Published: 2026-08-25

## Goal

Add the missing events a funnel needs to be measurable end to end.

## Acceptance criteria

- Every step of the funnel emits an event
- Each event is verified arriving with its properties
- Names and properties follow the existing convention
- The funnel is built and returns plausible numbers

## What lands as proof

Each event verified arriving, plus a working funnel built on them.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Instrument the {funnel} funnel

Description: Add the missing events a funnel needs to be measurable end to end.

Acceptance criteria:
- Every step of the funnel emits an event
- Each event is verified arriving with its properties
- Names and properties follow the existing convention
- The funnel is built and returns plausible numbers

Before you create the issue, name the funnel and its steps, then check which already emit events. Replace {funnel}.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: add the missing events a funnel needs to be measurable end to end. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.

### How do I know the work is done?

The pull request carries the evidence, not only the diff. Here that means each event verified arriving with its properties, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.