Skip to content
Privacy Requests
Guides
Email Configuration
Operator Notifications

Operator notifications

Operator notifications email your team when privacy request processing needs attention. Configure recipients in the Admin UI or through the API.

Operator notifications require an email messaging provider (Mailgun, Twilio Email, Mailchimp Transactional, or AWS SES) selected as the notification service. They are not sent over SMS. See our guide for configuring a messaging service.
Recipients apply across your whole Astralis deployment: the list is not scoped per organization, property, or integration. Disabling notifications stops all three notification types.

Configure recipients in the Admin UI

  1. Open Privacy Requests.
  2. Click the bell icon (Configure alerts) to open the Request notifications drawer.
  3. Turn on Enable email notifications and add the Email addresses that should receive notifications.
  4. Under Notification frequency, set how many privacy request errors trigger the error notification.
  5. Click Save. A "Notification settings saved successfully" confirmation appears.

To stop all operator notifications, turn off Enable email notifications and click Save. This clears the recipient list.

Configure recipients through the API

Send the recipients and the error threshold to the privacy request notification endpoint. This requires an access token with the privacy-request-notifications:create_or_update scope.

curl -X PUT "https://<your-astralis-host>/api/v1/privacy-request/notification" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "email_addresses": ["privacy-ops@example.com", "dpo@example.com"],
    "notify_after_failures": 5
  }'

The response echoes the saved configuration:

{
  "email_addresses": ["privacy-ops@example.com", "dpo@example.com"],
  "notify_after_failures": 5
}
  • email_addresses: every operator notification is sent to each address in this list. Send an empty list to stop all operator notifications.
  • notify_after_failures: how many unsent privacy request errors must accumulate before the error notification is sent. It applies to that notification only.

GET /api/v1/privacy-request/notification returns the current configuration and requires the privacy-request-notifications:read scope.

Notification types

The wording of these emails is fixed. They are not part of the email template types that can be customized in the Admin UI, and property-specific messaging does not apply to them.

NotificationTriggerRepeat behavior
Privacy request error notificationUnreported privacy request errors reach the Notification frequency thresholdOne email per batch of errors. Reported errors are not counted again.
Privacy request completed with skipped erasuresA privacy request completes, but erasure was skipped for one or more datasets, typically because their integration was disabled or deleted mid-requestOne email per request, naming the skipped datasets
DROP alert (enterprise)A step in California Privacy DROP (Delete Request and Opt-out Platform) processing failsMost persistent failures trigger another alert on each scheduled run, and a single run can send several alerts. Deadline alerts report newly overdue erasures and do not repeat for the same erasures.

Troubleshoot DROP alerts

Where DROP supplies a remediation hint, such as generating a new key from the Data Broker Portal, the alert includes it. For failures that originate in your warehouse or in Astralis itself, the alert names only the kind of error; the table shows where to find additional error details.

ProblemWhere to investigateNext action
Download fails with an invalid API keyDROP cycles tab, the failed cycle's detailsGenerate a new key in the Data Broker Portal and update the connector
Download fails with access deniedDROP cycles tab, the failed cycle's detailsConfirm payment is complete in the Data Broker Portal
Download refused because the previous batch is incompleteDROP cycles tab, earlier cycles still awaiting completionResolve rejected uploads or held erasures on those cycles; the next run uploads the outstanding responses
A response upload is rejectedDROP cycles tab, the cycle's file upload attemptsCorrect the file, then use Amend on the cycle
Held erasures pass the 45-day deadlineDROP cycles tab, the cycle's Pending erasures countCheck why the linked erasure privacy requests have not completed
The match-index backfill failsMapping tab, Backfill status (error text is truncated)Fix the gather query or the Snowflake connection, then run the backfill again
The connector is misconfigured (invalid secrets, no backfill configuration, match index not built)DROP cycles tab, the skipped cycle's details, and the Audit log tabFix the connector settings, or run the backfill to build the match index
The worker processing a cycle crashesDROP cycles tab, the failed cycle's detailsAmend the cycle to rerun it; contact support if it keeps failing