what's the number of times the letter "s" appears in:
q: workflow for dynamically populating an email from a data extension 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?

a: if you want an archive of the data, create a separate de with all the same fields, except add one more field as a second primary key "jobid'. i would also look at adding "senddate" into it.
then inside of the email  at the bottom of the for loop add the below ampscript:
%%[ upsertde(@yourarchivede, 2, "yourkey", @yourkey, "jobid", jobid, "senddate", now()) ]%%

this will leave your current structure in place, requiring no changes - but will provide you an archive de of all this information to reference if you need to.

****edit****
from your comments, it appears that you are more concerned with tracking the links than in the data. to solve for that:
you could add an alias on the a tag that is a variable, perhaps have it be the name of the product so when you look at your _click dataview, you can lookup by the alias and then differentiate the email sends by the jobid.

as far as for tracking image (issue #2) - you will never be able to get that to display a rendered version.  this is pulled from the raw email, prior to any ampscript or ssjs being processed.
your best bet is to either:


*

*store html of the send inside of a de and reference there for display - not recommended as it can get bulky and unweildy quickly.)

*utilize an api call to generate a preview for your team to view (email preview via api)


user
The text includes one hundred and eighteen "s"s in total.
assistant