Connector Improvement: MARKETO _FIVETRAN_DELETED column
CompletedPlease enhance the Marketo Connector to include a _FIVETRAN_DELETED column in destination tables, regardless of whether a row has already been deleted. It's not practical for us to wait until rows have been deleted before adding predicates to our data warehouse ETL processes. We would like to add the predicate "WHERE _FIVETRAN_DELETED = 0" to our ETL code before any rows are actually deleted so that we can avoid using these rows to populate our data warehouse.
Ideally, all of the Marketo tables should include _FIVETRAN_DELETED. If you can only add this feature to a limited number of tables, then please use this list of tables.
ACTIVITY_ADD_TO_WEBCASTS_ATTENDEE_DATA |
ACTIVITY_CLICK_EMAIL |
ACTIVITY_EMAIL_BOUNCED |
ACTIVITY_EMAIL_BOUNCED_SOFT |
ACTIVITY_EMAIL_DELIVERED |
ACTIVITY_FILL_OUT_FORM |
ACTIVITY_OPEN_EMAIL |
ACTIVITY_SEND_EMAIL |
ACTIVITY_TYPE |
ACTIVITY_UNSUBSCRIBE_EMAIL |
ACTIVITY_VISIT_WEBPAGE |
CAMPAIGN |
LEAD |
PROGRAM |
PROGRAM_TAG |
-
Official comment
Hi Morlin, Drew from the Product Team here.
Thanks for sharing this request. To my knowledge, data in the ACTIVITY_* tables is never deleted. We just get incremental activities during each sync.
We will consider adding deleted tags to the other tables if delete capture is supported. This change will be considered in a future quarter.
-
I've found myself needing this for the lead table this week too; upvoted.
-
We are now working on adding delete tracking to the Campaign, PROGRAM, and PROGRAM_TAG tables.
For reference, deleted leads can be tracked with the ACTIVITY_DELETE_LEAD table.
Please sign in to leave a comment.
Comments
3 comments