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. Any thoughts?
... View more