# Stop an event that double-fires

An event emitted twice per action, inflating every number computed from it.

Category: Analytics and tracking
Source: https://letsship.ai/use-cases/stop-a-double-firing-event
Published: 2026-08-25

## Goal

Fix an event that fires more than once per action.

## Acceptance criteria

- One action produces exactly one event, proven by a browser check
- The cause is identified rather than patched with a guard
- Historical inflation is quantified for anybody reading past numbers
- The check runs in CI

## What lands as proof

A browser check counting emissions per action and asserting exactly one.

## 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: Stop {event} firing twice

Description: Fix an event that fires more than once per action.

Acceptance criteria:
- One action produces exactly one event, proven by a browser check
- The cause is identified rather than patched with a guard
- Historical inflation is quantified for anybody reading past numbers
- The check runs in CI

Before you create the issue, compare event counts against a known action count in this repository's analytics and replace {event}.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: fix an event that fires more than once per action. 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 a single emission proven by a browser check, 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.