You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user imports a csv with his campaign data like emails, names, companies etc
It can have any no. of columns and to store all of that we need a dynamic approach to create tables for that csv, every time a csv is imported it should be stored in dedicated table in db but if the columns are matching or it's is simply is an updation in data(rows) for previous import then it should be stored in already created table only.
Some more additional columns to track delivery, bounce, maybe replies, open and clicks etc. These cols should be optional for now.
The text was updated successfully, but these errors were encountered:
When a user imports a csv with his campaign data like emails, names, companies etc
It can have any no. of columns and to store all of that we need a dynamic approach to create tables for that csv, every time a csv is imported it should be stored in dedicated table in db but if the columns are matching or it's is simply is an updation in data(rows) for previous import then it should be stored in already created table only.
Some more additional columns to track delivery, bounce, maybe replies, open and clicks etc. These cols should be optional for now.
The text was updated successfully, but these errors were encountered: