# singer-tap-development


07/22/2021, 3:10 PM
Hey all, I'm working with a team on integrating a tap for Klaviyo into our data warehouse. For those unfamiliar, Klaviyo handles email metrics. Currently, we're looking to pull in the emails of list members and then update those tables by both appending and removing list members. The problem we're running into is in figuring out how best to update tables if a target doesn't support record removal or know the replication method of a tap. Would Target-Postgres be limited to having to make a brand new table and load it each time a list member is removed? Has anyone encountered a similar situation? Also, let me know how else I can clarify the problem if need be.