Hmm, D seems like the way to go. I wonder if there's a way to set a global default retention policy instead of doing it manually on each data extension? That would be a real time-saver.
I'd go with D. Applying the retention setting during data extension creation is a proactive approach, and it's less likely to be overlooked than manually configuring each one later.
D seems like the most straightforward way to handle this requirement. Applying a row-based retention on each data extension ensures the inactive data is cleared consistently across the board.
I think option C) Set inactive data to be automatically cleared after one year, but is recoverable, strikes a good balance between data retention and manageability.
Tom
1 months agoJani
4 days agoKarma
5 days agoMerilyn
13 days agoTonja
19 days agoYaeko
21 days agoStanton
2 months agoEsteban
2 months agoAdelina
19 days agoLenna
20 days agoGregoria
1 months agoLong
1 months agoDelfina
2 months agoEdelmira
1 months agoIsadora
1 months agoGaston
2 months agoGerald
2 months agoEmilio
2 months agoFloyd
2 months agoRaymon
2 months ago