How it works

How ObituaryMonitor turns funeral-home obituaries into alerts, feeds, and API results.

Every product runs on the same sources, parser, and matching engine. Here’s what happens between a funeral home posting an obituary and it reaching you.

The pipeline

From a funeral-home page to a record you can use.

COLLECT

We read where obituaries are published first

17,565+ funeral-home websites and newspaper obituary sections across all 50 states and DC, checked daily.

STRUCTURE

Every notice becomes clean fields

Name, date of death, city, county, state, funeral home, source link, and the family members named in the obituary.

MATCH

Scored, not guessed

Name, location, age, and relatives are compared. Each result gets a confidence score or band.

DELIVER

Sent where you work

Email alerts, the Daily County Intelligence portal, CSV, REST API, or signed webhooks.

What we capture

What a structured notice contains.

Source on every recordA link to the original obituary, so you can read it yourself before acting.
Family named in the obituaryRelatives and their relationship, as written in the notice.
First-indexed timestampWhen the notice first entered our system.
No private dataNo government death registries, no SSDI or Death Master File, no phone or email contact data.
One structured noticeSample · fictional
full_nameMargaret A. Ellison
date_of_death2026-09-30
county · statePalm Beach · FL
funeral_homeLakeside Family Funeral Home
related familyDaniel (son) · Caroline (daughter)
source_urlhttps://…/obituaries/…
Three products

Same engine, different starting points.

You have names

Monitoring

We compare every new notice against your watch list and email you when one matches at or above your threshold (90% by default).

How Monitoring works →
You have a market

Daily County Intelligence

Every new notice in your counties lands in your feed usually within a day, with related family, category filters, and property matching in 43 states, with county and field availability varying.

How it works →
You have records

Verification API

Send a name and a location or birth year and get found, possible_match, or not_found with the source obituary. Batch, async, or ongoing watches.

How the API works →
Sources

Where the data comes from.

What we use

  • Funeral-home websites and newspaper obituary sections
  • Public memorial pages that link back to a source
  • Every record linked to its source

What we don’t use

  • Government death registries, SSDI, or the Death Master File
  • Private or restricted databases
  • Phone numbers, emails, or other contact data