Deletes Are Not Captured in the CONVERSATION Table

Issue

In the destination, the _fivetran_deleted column of the CONVERSATION table is not set to TRUE for the records that are deleted in Kustomer.

Environment

Connector: Kustomer

Resolution

When you delete a conversation in Kustomer, Fivetran marks it _fivetran_deleted = TRUE in the destination depending on how the conversation is deleted:

• If the conversation is deleted using the Kustomer UI, the data is available in the Conversation Events API response and we mark it _fivetran_deleted = TRUE.
• If the conversation is deleted using the API, the conversation and all associated events are hard deleted and cannot be accessed using the API. As a result, we do not mark it _fivetran_deleted = TRUE.