Currently the "container" data collector is MVP-level basic, specifically built for Google Tag Manager. Tealium does not have container ID's to our knowledge, but we want to instead bring in other valuable metadata parsed from Tealium's network call.
Acceptance criteria
Convert the container parser to store more general data. It currently pulls in an ID property from the network call's query parameters. However, we can add a custom parser property to each individual container in the ContainerConfig, similar to how the QueryParserConfig works. The parser should return an object which the UI will then blindly display both key value pairs for each container. Note that UI work is separate from this issue.
Scope
background-page
Category
MVP
Description
Currently the "container" data collector is MVP-level basic, specifically built for Google Tag Manager. Tealium does not have container ID's to our knowledge, but we want to instead bring in other valuable metadata parsed from Tealium's network call.
Acceptance criteria
Convert the container parser to store more general data. It currently pulls in an ID property from the network call's query parameters. However, we can add a custom parser property to each individual container in the
ContainerConfig
, similar to how theQueryParserConfig
works. The parser should return an object which the UI will then blindly display both key value pairs for each container. Note that UI work is separate from this issue.GTM:
Tealium: