The Tealium approach is to only send data to the tag vendor that is mapped and has a value set. We also "abstract" the individual tag vendor tracking functions with utag.view and utag.link functions.
This call:
utag.link( {"key1" : "value", "key2" : "value2", "unwantedKey1" : "" , "unwantedKey2" : ""} );
Has the same effect as this:
utag.link( {"key1" : "value", "key2" : "value2"} );
Then you would have key1, key2, unwantedKey1, unwantedKey2 mapped in the Webtrends mapping toolbox (inside Tealium.) The tag template will detect that unwanted is not set and it will *not* pass it along to Webtrends.
Using Extensions and/or controlling what is set in the "Data Layer" object passed to utag.link is how you control what is then passed along to Webtrends.
utag.link(my_object); // my_object has all the data that should be sent
... View more