In implementing an application that handles the aunthentication of a user and then redirects them to their application of interest, how might you maintain a consistent view of the user from unauthenticated to authenticated between multiple Tealium profiles?
In other words, how do you string together a user's session with two Tealium profiles as they pass through authentication?
The aunthentication application pages and actual application pages are both built in Angular, so we are using a service to handle the event logic and configure profiles. Image requests are sent to analytics platforms from each application.
The utag_main cookie does not hold a constant value prior to the user being authenticated.
I believe your best bet would be to use the "Cross Domain Tracking Using First-Party Cookie Sync and Iframes" functionality. This will allow you to share data across domains you own and operate, and are managed by Tealium.
My assumption is that you'll want to persist, for example, the Google Analytics _ga or the Tealium utag_main_v_id IDs between domains, and this will allow you to do so. It does require a little more effort than a typical Tealium deployment, especially since each domain will need to host a new file that can set a 3rd-party cookie, then will become a 1st-party cookie. The details of the above article should cover this part in more details.
Please let me know if this is what you're looking for, or if you need more guidance.