Docs

Fathom Event API Management Tracking

Fathom's API now sets event currency or deletes events by name. Track event naming and revenue values so your web analytics stay clean.

Revenue

Event names drift. A developer adds signup, another ships sign_up, and a test event called test2 makes it to production. Months later, your goal and revenue reports are full of duplicates and stray values, and nobody is sure which events can be safely removed.

On 20 September 2026, Fathom Analytics added the ability to manage events through its API using the name you already send from your site. You can set an event’s currency or delete its event record by name, without hunting for a separate identifier. That makes regular clean-ups practical, but only if you know what needs cleaning and can prove nothing broke afterwards.

Data Points to Track

Record these for every named event so API changes can be audited:

  • event_name – the exact string sent from your site, in one agreed case
  • event_currency – the currency set for the event, or empty if none
  • event_value – the monetary value sent with the event, in minor units where possible
  • first_seen and last_seen – dates showing whether an event is still live
  • daily_event_count – volume per event, to spot dead or duplicate names
  • environment – production, staging or test
  • change_type – currency set, event deleted, or renamed, with the date and author
  • source_page – where the event fires, so you can trace it back to code

Setup Steps

  1. Export a list of all event names from your Fathom site, with counts and last-seen dates.
  2. Group near-duplicates (signup, sign_up, Signup) and agree one naming convention.
  3. Update the site code so only the agreed names are sent, and deploy before touching any records.
  4. For revenue events, use the API to set the correct currency by event name, and send values in a consistent format.
  5. Mark events with no traffic for 90 days or more, and confirm with the code owner that they are unused.
  6. Delete the confirmed dead events through the API by name, logging each deletion in a change record.
  7. Re-run the export a week later and compare counts to confirm live events were unaffected.

Actionable Insights

Duplicate names with similar volume mean a rename happened without a clean-up. Merge reporting onto the new name and retire the old one.

Revenue events with no currency make your totals hard to trust. Set the currency first, then check the totals against your payment provider.

Events that stopped firing after a release are a tracking bug, not clutter. Investigate before deleting, because deleting the record removes the evidence.

Test events in production show gaps in your release process. An environment property lets you filter them out and fix the cause.

A quarterly audit built on these properties keeps your event list short, your revenue figures consistent, and your team confident about what each name means.

Expert help

Need help tracking this in your app?

Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.

Talk to an expert