Define abandonment scope
Agree whether the order is broad abandoned data or a narrower event/reason cohort.
Abandonment is a specific application lifecycle outcome. We build structured cohorts around the relevant USPTO status/event and date rather than treating every dead trademark record as a revival opportunity.
For a commercial dataset, “abandoned” should refer to an application record that matches the selected abandonment condition and the additional filters agreed for the order. The record must be bound to the correct USPTO case and checked at the required verification point.
A dataset can focus on recent abandonment, specific classes, states/countries, representation profiles or available public correspondence fields.
Our abandoned-application lead cohort uses the same USD $0.01 per-record starting rate as dead trademark leads, minimum 1,000 qualified records (USD $10). Choose abandoned applications when the specific application lifecycle outcome matters.
Not every DEAD record is an abandoned application, and not every abandoned application can or should be revived. Event window, public correspondence availability, applicant representation and source verification remain separate qualifying criteria.
Datasets are delivered after invoice settlement and final verification as CSV, XLSX or a private Google Sheet, via the agreed email or WhatsApp channel. No payment details are collected by this page.
USPTO states that some abandoned applications may be eligible for a petition to revive depending on why the application was abandoned and when the relevant notice/event occurred. A lead dataset does not determine legal eligibility for revival.
USPTO states that some abandoned applications may be eligible for a petition to revive depending on why the application was abandoned and when the relevant notice/event occurred. A lead dataset does not determine legal eligibility for revival.
Agree whether the order is broad abandoned data or a narrower event/reason cohort.
Choose a date window that matches the business use case.
Add class, geography, representation, filing-basis or contact requirements.
Check qualifying records and deliver the selected fields in a structured file.
| Field | Use in qualification or delivery |
|---|---|
| Serial number / mark | Binds the delivered row to the application. |
| Current status | Confirms the record-level state observed at verification. |
| Abandonment event / date | Defines the cohort and freshness when supported by the workflow. |
| Applicant / geography | Supports customer segmentation when requested and available. |
| Applicant-attorney fields | Supports a separate representation profile without confusing the examining attorney or Domestic Representative. |
| Public correspondence field | Can be included with provenance when available; it should not automatically be described as a verified owner email. |
| Verification metadata | Records when and under what profile the record qualified. |
A buyer may care about newly abandoned applications, a particular class, a state or country, representation conditions, contact availability or prior-delivery exclusions. Those requirements should be part of the order definition rather than added after a raw export is produced.
The same application can also move through earlier Office Action events before abandonment. Preserving lifecycle context lets the dataset answer a clearer business question and reduces the risk of treating every inactive application as the same type of opportunity.
No. Commercial qualification and legal eligibility are different questions. We provide data, not a case-specific legal conclusion.
Yes, where the selected source and workflow support the required status/event date logic.
Representation criteria can be added when supported by the selected profile. Ambiguous records can be excluded rather than guessed.
Describe the abandonment window, volume, geography, class and representation/contact requirements.