How should we design the statistical tables of various data in the crm system?

The company is building a crm system. There is a lot of data statistics that need to be recorded in the database. For example, record the number of customers per employee per day, the number of tracking records, whether the number of customers per day is up to standard, and whether the number of tracking records is up to standard. There are two solutions: 1. these statistics... the company is working on a crm system. There is a lot of data statistics that need to be recorded in the database.
For example, record the number of customers per employee per day, the number of tracking records, whether the number of customers per day is up to standard, and whether the number of tracking records is up to standard.
Currently, two solutions are proposed:
1. these statistics are recorded in a table.
2. Each statistical data item is recorded separately in a table.
I don't know. which method is better? Or are there other better and more complete implementation methods?
I would like to thank you for your comments.

Reply content:

The company is building a crm system. There is a lot of data statistics that need to be recorded in the database.
For example, record the number of customers per employee per day, the number of tracking records, whether the number of customers per day is up to standard, and whether the number of tracking records is up to standard.
Currently, two solutions are proposed:
1. these statistics are recorded in a table.
2. Each statistical data item is recorded separately in a table.
I don't know. which method is better? Or are there other better and more complete implementation methods?
I would like to thank you for your comments.

We recommend that you enable timed statistics in the background.

If the data volume in the later stage is large, it is recommended to put it in each table separately. because the data volume in the later stage is large, the table still needs to be split, so it is better to split it now. Do not forget to create related indexes.