View in #general on Slack
@Dawid_Lisiecki: Hello Mautic community!
I’m new here and and first of all I would like to say hello everybody and admit that Mautic is indeed awesome software.
I’m starting my journey with adapting medium size project to Mautic and I have couple of concerns how to structure my contacts.
First of all - this project is kind of two same websites under two domains which are using one database, and I would like to track users activity in both of this websites in scope of one Mautic instance
- Each account also has list of sub accounts with their own unique email addresses, which are used lets say, by company workers to authorize and do limited stuff in scope of company account```
So my database structure looks like this:
```Accounts
- email address
...company data
PortalAccounts
- portal_id
- account_id
...data related to specific portal
Subaccounts
- email address
- account_id
...worker data```
I was thinking of structuring my contacts following way:
- each `Account (company)` is a contact with flag to determine if they have `Portal Account` in specific website (so flag like `has_domain1_account` and `has_domain2_account`)
- each `Subaccount (company worker)` would also be separated contact with some `parent_id` custom field to determine which company they belong to
- use `Mautic segments` to separate accounts for each website, separate companies from their workers (there’s plan to do campaigns separately for only companies, only workers, both of them)
Do you think this structure is correct? Do You see any future problems with that structure? Is there a better way?