Protect always records alerts in the app, under Brand → Incidents → Alerts. By default it also emails your rights contact. A notification policy sends chosen events somewhere else, on a schedule you set.
Create a policy
Open Brand → Notifications.
Choose the events
Event Sent when New discovery match (unverified) A monitor matches something for the first time. Verified detection A detection passes verification. Trademark alert A high-priority trademark filing matches. Possible social impersonation A social profile is flagged. Approval needed A notice is waiting for your approval. Owner action required A platform needs you to file. Notice submitted A managed filing was submitted. Platform reply The platform answered. Listing removed, Listing relisted A listing went down or came back. Counter notice The seller disputed the notice. Limit it to monitors (optional)
Select monitors to receive only their events. Leave it unscoped to receive events from everything.
Choose the destination
In-app, email or webhook. A policy’s email address is separate from your rights contact.
Choose the schedule
Immediate, or a daily or weekly digest in the time zone you pick.
Once a policy covers an event by email or webhook, the default email to your rights contact is no longer sent for that event. This still applies while the policy is paused.
Test a policy
Send a test from the policy. It uses the saved destination and a synthetic message with none of your case data. You can send one test per policy per minute.
A test that is accepted has been queued, not delivered. Check the delivery history for the result.
Delivery history and retries
Each policy lists its deliveries as Queued, Delivered, Failed or Stopped before delivery. Open one to see each attempt.
Protect tries a delivery up to five times. After that you can retry a failed delivery by hand, up to five more times.
Receive a webhook
Protect sends a POST over HTTPS with a JSON body:
| Field | Content |
|---|---|
| Envelope version | protect.notification.v1 |
| Event and delivery IDs | Stable across retries. Use the delivery ID to ignore duplicates. |
| Event kind, subject ID | What happened, and to which detection or match. |
| Title, body | The alert text. |
| Created time | When the event happened. |
Each request carries these headers:
| Header | Content |
|---|---|
Protect-Signature |
t=<Unix seconds>,v1=<hex HMAC-SHA256> |
Protect-Event-Id, Protect-Delivery-Id |
The same IDs as in the body. |
Protect-Key-Id |
Identifies the signing key. It changes when you rotate the key. |
To verify a request, compute HMAC-SHA256 with your signing key over the timestamp, a full stop and the raw request body (<t>.<body>), and compare the result with v1.
Your endpoint must:
- use HTTPS on a public address;
- answer within ten seconds;
- answer directly. Protect does not follow redirects.
A rejected request is retried after 60 seconds, with the delay doubling up to one hour.