b object not synced with utag_data after a manual view call.

Bronze Contributor
Bronze Contributor

I have a cart which triggers a manual view call. I placed a break point in utag.js to debug this and below is the result in console.

 

When automatic view call happens and breakpoing is hit, the console shows below

 utag_data == b

true

 

I let the flow continue and then make a manual view call in console

 

utag.view();

 

breakpoint hits again and below is the result false.

 utag_data == b

false

 

 

Though b has all the variable values of utag_data any change to utag_data through an extension does not change b object anymore.

 

Any thoughts why b object is out of sync once a manual calll is made and how can it be fixed?

 

 

2 REPLIES 2
Highlighted

b object not synced with utag_data after a manual view call.

Tealium Employee

@rushikesh_naik

 

The first question, is which version of utag.js are you using? As this will determine the expected behaviour.

 

In the latest version of utag a view/link will do the following steps:

 

Merge in any default values that have been set (In the publish settings)

Merge in:

 - 1st Party Cookies

 - Query String Parameters

 - Meta Data

 - DOM properties

 - ut Values (Tealium variables)

 - JS Page Variables

 - Any Tealium Collect Visitor Attributes

 

This stops cross data object pollution. So that the object you pass in will only be what you passed in, and the data points that we collect, from the page.

 

In previous versions, we did have to merge the object passed in with utag.data (which is a reference to utag_data) for the loadrules. But with the release of utag v4.40, this has been stopped.

 

Your best bet is to raise a support ticket so that an engineer can walk through with you the what is happening, and more importantly why.

 

Adrian

Ask me anything Tealium related or Javascript, or NodeJS.
Please remember to mark solutions as accepted for future searchers.
Highlighted

b object not synced with utag_data after a manual view call.

Bronze Contributor
Bronze Contributor

Thank you @adrian_browning.

 

We are using v4.39 version.