What is Event Types?

API & Technical5 min readUpdated Mar 25, 2026

Categorized triggers in a trademark monitoring system that define which trademark lifecycle changes generate alerts and webhook notifications.

Event types in a trademark monitoring system define the categories of trademark lifecycle changes and activities that can trigger alerts and notifications. Each event type represents a specific kind of change that may be relevant to trademark owners, such as a new conflicting filing, a status change on a watched mark, an approaching deadline, or a change in ownership. By configuring which event types they want to receive alerts for, users tailor the monitoring system to their specific needs, ensuring they receive relevant notifications without being overwhelmed by noise.

Trademark event types can be broadly categorized into several groups. Filing events are triggered when new trademark applications are filed that match monitoring criteria, such as similar mark text, overlapping classifications, or specific jurisdictions. Status events are triggered when a monitored mark undergoes a lifecycle change, such as moving from examination to publication or from registration to expiration. Deadline events are triggered as key dates approach, such as opposition windows, renewal deadlines, or response due dates. Ownership events are triggered when a mark is assigned or transferred to a new owner. Conflict events are triggered when analysis identifies a new potential conflict between a monitored mark and another filing.

The specificity of event types varies by system. A basic system might offer only "new filing" and "status change" events. A sophisticated system may offer dozens of specific event types, such as "published for opposition," "opposition filed," "registration granted," "renewal due in 90 days," "assignment recorded," and "cancellation petition filed." This granularity allows users to filter notifications precisely, receiving alerts only for the events that require their attention.

Why It Matters

Event types are the control mechanism that determines the signal-to-noise ratio of a trademark monitoring system. Too few event types force users to receive all notifications and filter manually, which is time-consuming and risks important alerts being overlooked amid irrelevant ones. Too many event types create configuration complexity that can lead to important events being accidentally excluded.

The right set of event types reflects the practical workflow of trademark management. Different stakeholders need different events. A litigation attorney needs to know about opposition filings and cancellation actions. A portfolio manager needs to know about renewal deadlines and registration grants. A brand protection specialist needs to know about new conflicting filings and potential counterfeits. An in-house counsel at a large corporation needs all of these events but filtered to specific brands and jurisdictions.

Event types also enable automation workflows. When a monitoring system supports specific, well-defined event types, downstream systems can implement targeted responses for each type. A "published for opposition" event can trigger an automated clearance analysis and create a time-sensitive task. A "renewal due" event can trigger a renewal instruction workflow. A "new conflict detected" event can trigger a risk assessment and notification to the responsible attorney.

The consistency and reliability of event type definitions across jurisdictions is a significant technical challenge. Different trademark offices may report events at different levels of granularity, use different terminology, and have different lifecycle stages. A monitoring system must harmonize these differences into a consistent set of event types that users can configure once and apply across all jurisdictions.

How Signa Helps

Signa uses one set of trademark event types for every office it covers. Watches trigger on five of them:

  • trademark.created: a matching mark is seen for the first time, such as a new filing.
  • trademark.updated: tracked fields changed, none of them status fields.
  • trademark.status_changed: any of the status fields changed, such as a move to registered, abandoned or a pending opposition.
  • trademark.retracted: the office's feed pulled the record (opt-in).
  • trademark.corrected: a retracted record reappeared, or Signa corrected a status it had published (opt-in).

Each watch chooses its trigger_events; by default it alerts on the first three. A matching event produces an alert, delivered to webhook endpoints as an alert.created event that carries the trademark event type, the watch, the matched trademark and, for similarity watches, the match tier. Alerts on published marks can carry the opposition window Signa computes for the office.

For marks in an organization's own portfolios, webhook endpoints can also subscribe directly to trademark.status_changed and office_action.issued. Deadlines such as renewals and declarations of use are computed on each trademark record and available through the portfolio deadline calendar rather than as reminder events.

Example

A pharmaceutical company sets up Signa monitoring for three purposes, each with its own webhook endpoint.

For defense, it creates similarity watches on its core drug brand names that trigger on trademark.created, so new filings resembling its brands produce alerts. Those alerts go to the legal team's threat assessment workflow.

For its own portfolio, it subscribes a second endpoint to trademark.status_changed and office_action.issued for the marks in its portfolios. These feed its IP management system, which updates portfolio records and opens tasks. Renewal reminders come from the portfolio's deadline calendar.

For competitive intelligence, it creates owner watches on its main competitors that alert on their new filings, feeding a dashboard of their filing patterns.

Each endpoint receives only the events relevant to its purpose, so each downstream system handles only what it is designed for.