Best practice to stich together ALL different user IDs?


#1

I’ve been dealing with some different issues related to the different types of IDs - network, domain, session, user, etc. I believe I understand the purpose and logic of each, but it seems like each applies in a different case.

I see in this link here reference to working from a table of user_ids to build out a marketing touch model. For my example, I’m interested in plotting a UX path through our app.

Regardless!
Would it be considered best practice to always work from a master user-concordance sort of table, that matches up every ID value with every other? i.e. for a totally invented example, the single user_id (our customer id), with the two different domain ids we have for that person, and the two different network_ids, and their 6 different session_ids?