Connector Improvement: Sailthru: key for some events should be event_id (per their documentation)
PlannedWe've been struggling to validate some of the Sailthru data, and one of the core issues we've discovered in the data is that Fivetran treats message_id as a primary key, but Sailthru insists it should be event_id.
A snippet from a recent update from them: "...reflect the usage of event_id as a primary key within open and click datasets. It is listed under Primary Key on both the Event Stream Overview and Event Stream Data Set pages..."
-
Official comment
Hi Kevin,
Thanks for raising this and for your help getting Sailthru to update their documentation.
We're going to pick this up in our next sprint. We should be ready to roll out the change in a few weeks. We'll need to trigger a resync of the affected tables to ensure we capture all missing rows.
Thanks,
Luke
Please sign in to leave a comment.
Comments
1 comment