Why Do Deleted Bizzabo Registrations Persist in Snowflake After a Re-Sync?

Question

Why do some deleted Bizzabo registration records still appear in my destination after a historical sync? If Bizzabo deletes registration IDs because of ticket type changes or manual deletions, are those deletions reflected in my destination tables?

Environment

Connector: Bizzabo

Answer

We sync records that are available from the Bizzabo API. If you delete a registration in Bizzabo, the API may no longer return that record. When this happens, we can't detect the deletion and therefore don't delete the corresponding record from your destination. As a result:

• A historical re-sync doesn't remove these records from your destination.
• The deleted records remain in the destination unless the source API reports the deletion or provides a delete-tracking mechanism.
• The _fivetran_synced value updates only for records that are returned by the API. If a deleted source record is skipped during sync, its _fivetran_synced value remains unchanged.

For more information about _fivetran_synced, see System columns and tables.

Key considerations

• The Bizzabo API doesn't provide webhooks or endpoints for registration delete events. For more information, see the Bizzabo Registrations API documentation.
• If a registration is deleted or its ID is replaced after a ticket type change, the record may no longer appear in API results.
• We interpret missing API records as unavailable for sync. We don't automatically perform destination-side deletes unless the source API reports those deletions in a supported way.

Best practice

To identify possible deleted or orphaned registration records:

1. Compare _fivetran_synced timestamps across registration records.
2. Identify records with stale _fivetran_synced values.
3. Compare those records against the latest records returned by the Bizzabo API.
4. Archive or remove confirmed orphaned records from your destination as needed.

Historical re-syncs can help refresh active records, but they don't remove records that the source API no longer returns. This behavior is expected and reflects the Bizzabo API delete-tracking limitations.