I'm currently working on a project to automate a weekly email in SF Marketing Cloud. The ideal process involves uploading a csv to a data extension and using it to populate a table within the email. This is working well.
What I'm struggling with is figuring out the best way to allow the team managing the email to use this functionality. The team consists of people who are not familiar with AmpScript and I would like for them to not have to deal with changing any of the code. Ideally they could just upload a file to the FTP and Automation Builder would handle the rest.
Currently, I have a single Data Extension and a single email template which includes the necessary AmpScript to pull the data. My thinking is that the responsible team will upload their data to the same data extension every week, then create a new email using the template and the new data will be pulled.
However, this raises two issues. 1.) If the data is always overwritten there's no way to have a good archive from week to week. Though this could be solved by always keeping the original csvs used to populate the DE each week. And 2.) Tracking data shows the AmpScript instead of the populated information.
I originally used specific dates in the data extensions by using the FormatNow() function so each week would have a unique data extension and tracking seemed to work fine. However, this may require more legwork on the team handling the distribution.
I'm just not sure I'm going about this the right way or maybe I'm trying to do something too crazy. Is there a better way to accomplish this goal?