What is the best way to store UTM tags of different entities in a database?

Question

Database design

I have:

1. Orders
2. Applications 3. Messages
from the contact page

etc).

The question arose, how best to organize their storage?

If I just needed to save them, then I would use JSON for example and write to the utm_data field, but I'm not sure if this is a good option if further manipulations with them are required.

Now I'm thinking about the following options:

Option 1. Create three different tables for each entity, for example, order_utm_params, request_utm_params, contactus_utm_params and use the hasMany() relationship

Option 2. Create one table for all entities, for example, utm_paramable and use the morphMany() connection

In the first option, everything seems to be OK, but there are too many tables, in the second there are not many tables, but it will turn out to be a big mess, since there can be a lot of UTM tags how would you do? And why?

Maybe there was a similar experience?

Do not offer separate analytics systems, since I don’t want to fence Yandex.Metrica from the site.

Answer 1

A one-to-many polymorphic relation or Many-to-many polymorphic relations