[Official Census docs (sync lifecycle webhooks)]: Monitor syncs over webhooks, not polling. The key events: sync.triggered, sync.started, sync.completed (status is 'ok' on success, 'emergency' on failure), sync.success, sync.failed, plus sync.alert.raised and sync.alert.resolved. An alert payload includes alert_type (for example FailureAlertConfiguration), the failure message and details (for example 'Sync has failed with error: A mapped source column has been deleted: email'), and a followup_url pointing straight at the sync history in the app. Wire these into your incident pipeline so a deleted source column or broken connection pages someone instead of sitting silent.

Context: Official docs (Census/Activations sync lifecycle webhooks): documents the webhook event model for sync observability. A failed run surfaces as sync.completed with status 'emergency', and sync.alert.raised carries the failure details plus a followup_url to the sync history.