Handling UDO data across subdomains

[brian_greig]

I am curious how others handle this:

We have encountered a scenario where data is being populated in our Universal Data Object in Tealium which is being persisted across subdomains.  When switching from one application to another within the same domain (different subdomains) data persists in the subsequent applications (defined by a seperate profile) UDO.  Upon switching back to the original application values that were originally set have been modified.  Since the names that we use for our data layer variables are the same across profiles this results in data being mutated outside of our application.

What is the best practice in this scenario.  Would it be to purge all of the persistant values when your profile is loaded?  Or is there some other way to cleanse the data layer when switching across applications? 

[dan_george]

Hi @brian_greig 

Can you expand of the type of data that is persisting between domains? I presume that it's either cookie data or AudienceStream data layer enrichment which are set at the top level domain. I say this because the utag_data object declared in the webpage HTML refers to the current page only. Does that sound about right? Just want to make sure we have a clear understanding before supply a best practice.

Cheers,

-Dan

[brian_greig]

Maybe this is a one off issue but we are seeing instances of where data set in the UDO on one site persists when going back (hitting back on the browser) to another site.  Granted we are using Angular to persist data and we are using cookies for storing session data which may be the root cause. 

[dan_george · Accepted solution]

@brian_greig

I believe that newer versions of utag 4.4x handle data for Ajax pages different by not merging. Do you know what version of utag.js you are running? You might try to make a backup of your current uTag Loader (utag.js) and upgrade to the newest version to see if that helps.

I am also checking with other team members to see if they have any insight into other clients having this issue.

Cheers,

-Dan

[brian_greig]

@dan_george I updated the tag to the latest version and I am not seeing this behavior any more.  I will follow up if we see this behavior again

[kathleen_jo]

I look forward to hearing about update @brian_greig.