TiQ Code optimization

Michael_Kim_shc
Silver Contributor
Silver Contributor Michael_Kim_shc

Any chance that Tealium iQ is going to give more flexability around some of the container code and backend code it fires around the various extensions and tags in order to help optimize the code a bit?

 

Also, will we be able to customize how much of th enhanced data layer gets populated in the datalayer object?  There's a ton going in there now - and it'd be nice to be able to pick and choose whcih AS attributes get pushed there.

2 REPLIES 2

TiQ Code optimization

kathleen_jo
Employee Emeritus
kathleen_jo

Great questions @Michael_Kim_shc. What kind of flexibility were you looking for in the container and backend code?

 

Again, what customizations were you looking for in the data layer? I look forward to your reply. 

Remember to give me a kudo if you like my post! Accepting my post as a solution is even better! Also remember that search is your friend.

TiQ Code optimization

Michael_Kim_shc
Silver Contributor
Silver Contributor Michael_Kim_shc

The most important (and urgent) customization I'd like would be to be able to disable any AudienceSTream attribute from being a part of the enriched data layer.  That's possible now for String Attributs via the "Personal Info" flag.  

2 main reasons:

1 - a TON of data is pumped into our datalayer object with the enrichment, and beacuse of that it takes longer to reference the data layer object every time that we do since the object is larger.  Ideally, data would by default NOT be shared.. and we'd simply have an easy option to click a box to have it be shared.  that way we'd push out only what we want.. erring on the side of performance and privacy.

 

2 - visitor IDs are currently shared with no option for keeping invisibile as 'personal info".  

 

 

For Backend Code, .. i'll have to get back to you in a bit:)