We sell facts with dates on them, not a score.
Most “intent data” is a number somebody assembled from behaviour you cannot see, about people you cannot name. Ours is the opposite: a clinician was newly credentialed last month, an organization took on four at once, an identifier was retired. Each one is a reason to call, each has a date, and each can be checked.
The changes worth a phone call.
The exact rule is published beside each one. A signal whose rule you cannot read is a signal you cannot argue with when it is wrong.
| Event | Why it matters | The rule |
|---|---|---|
| New providerA clinician was newly issued an identifier. | Somebody setting up. Every vendor decision is open, and nobody has been chosen yet. | An active identifier first issued inside the lookback window. |
| HiringAn organization gained several newly credentialed clinicians at once. | Capacity is growing, budget is moving, and the people arriving need equipping. | Three or more newly credentialed clinicians tied to one active organization, either by a practice address that exactly one organization files, or by a billing-group reassignment matched by name within the clinician's own state. The event reports what was seen — how many, and how each was tied — because a new credential is not proof of a hire. |
| DeactivatedAn identifier was retired. | Stop paying to reach somebody who is no longer practising. This one saves your customer money, which is its own kind of sale. | Keyed by identifier and date, so somebody deactivated, reactivated and deactivated again is two events. A later reactivation does not erase the first: it happened. |
| Practice movedA clinician's practice address changed to a different city or ZIP. | The strongest buying window there is: re-stocking, re-contracting, re-listing, new referral patterns. | A change of city or ZIP, dated by the record's own update date. A retyped suite number at the same address is not a move and is left out. |
| Ownership changeA facility's owners changed. | New owners re-open vendor decisions, often across the whole estate at once. | Captured at the moment of the change, because the previous owners are overwritten by the next refresh and cannot be recovered afterwards. |
| Rating changeA facility's published quality rating moved. | A facility under pressure is a facility looking for help — and one that improved is worth a different conversation. | Written in the same transaction as the overwrite, for the same reason as ownership: the old value is gone a second later. |
A number you cannot check is a number you cannot sell twice.
Checkable
Every event names what changed and when. If we say a practice moved in March, you can look at the record and see that it did. Nobody has ever been able to do that with a surge score.
Qualified, not inflated
A hiring event says how many clinicians were seen and how each was tied to the organization, because several new credentials at one address is evidence, not proof. We would rather be trusted on six events than doubted on sixty.
Nothing is ever rewritten
Events are append-only and de-duplicated by the fact itself, so detection can be re-run safely and a later reversal never erases what happened. Your campaign history stays explainable a year from now.
Caught before it vanishes
An old address, a previous owner and a former rating are all overwritten by the next refresh. They are written down at the moment they change, because a month without that is a month of history nobody can ever recover.
Asked by everyone who has been sold intent before.
Is this intent data?
It is event-based intent: dated, checkable changes that give you a reason to call. It is not behavioural intent — we do not track who read what article, and we do not sell a propensity score.
Why not sell a buying-propensity score?
Because a score cannot be checked. A number we assembled would be a claim a buyer could test and find hollow, and the first technical buyer would test it. A change with a date behind it is either true or it is not, and you can hold us to it.
How fresh are the events?
Detection runs against a rolling window, so what you see is a reason to call now rather than a year-old change nobody cares about. Each event carries both the date the change happened and the date we noticed it.
Will the same event appear twice?
No. Every event carries a key derived from the fact itself, so re-running detection — or retrying it after a failure — adds nothing that is already there. Events are never edited or deleted.
Can I get events for my own list?
Yes. Upload the identifiers you care about and get their events back against your own rows, or call the API for one provider, organization or facility and read its history.
Can I be told when something changes?
Yes. Standing alerts — tell me when a cardiologist is newly credentialed in my territory — run from a saved search and send a digest, and every plan includes some; how many an organization may keep is on the pricing page. You can also poll the API or pull a dated feed instead.
Put a reason to call in front of your team.
Search the records free. Sign in to pull events for your own list, or read them through the API.