# Fix a tracking event that stopped firing after a UI change

An event that broke when the component around it changed, fixed and pinned by a browser check.

Category: Analytics and tracking
Source: https://letsship.ai/use-cases/fix-an-event-that-stopped-firing
Published: 2026-08-25

## Goal

Repair a tracking event that stopped firing and add a check that catches it next time.

## Acceptance criteria

- The event fires again with its expected properties
- A browser check captures it and asserts the payload
- The check runs in CI so the next redesign breaks the build
- The gap in the data is noted for anybody reading the historical numbers

## What lands as proof

A browser check capturing the outbound event, which is the first automated assertion this event has ever had.

## 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: Fix the {event} tracking event

Description: Repair a tracking event that stopped firing and add a check that catches it next time.

Acceptance criteria:
- The event fires again with its expected properties
- A browser check captures it and asserts the payload
- The check runs in CI so the next redesign breaks the build
- The gap in the data is noted for anybody reading the historical numbers

Before you create the issue, compare this repository's tracking plan against what is actually firing and replace {event} with one that stopped.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: repair a tracking event that stopped firing and add a check that catches it next time. 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 the event captured in a browser check, before and after, 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.