- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi,
Here are a few solutions I've seen, in descending order of personal preference:
- Interpolate current data into the message when retrieving it, which may be fine depending on your use cases and constraints
- Extend nms:broadLog* table to capture personalization values at send, and interpolate, yielding accurate info at the cost of significant complexity and db space
- If email, use archiving feature to capture materialized copies of each delivery
- If email, use curl to archive mirror pages or otherwise extend their validity period and use directly in a csr tool
- Use a post-processing workflow to dump personalization data into csv files to be archived
- Replicate the db on every delivery sent (we're essentially doing this at a current client actually)
Thanks,
-Jon