Connector Improvement: Iterable Connector Event Deduplication
Answered
The event table currently drops rows when multiple events of the same type take place at the same time for the same user.
Deduplication should utilize a hash of the event's `additional_properties` in addition to event_name, campaign_id, email, createdAt to avoid dropping records with unique information (i.e., we're missing records when the same email is subscribed to multiple lists at the same time)
-
Official comment
Hi Lilli,
Luke from the Product team here. Thanks for submitting this request.
We investigated this issue and determined that Fivetran cannot resolve it without support from Iterable. We tried creating a synthetic hash using all columns returned by the API, and we still found duplicates. The root cause of the issue is that Iterable does not include milliseconds in its timestamps. We've submitted a feature request to their team asking for them to include milliseconds to resolve this issue. Until they make that change, we are blocked.
Best,
Luke
Please sign in to leave a comment.
Comments
1 comment