Ask Commanders Act for a tc_vars per container

[amtins]

As a Pillarbox developer, I'd like to know if it's possible to have a tc_vars available per container so I can have control over my own container's values.

Acceptance Criteria

• Ask if it's possible with their API to remove container-specific keys.
  • if not, suggest improving their API
• Ask if it's possible to have one tc_vars per container.
  • if not, ask what other alternatives are available

Hints

Can be useful in cases where several independent teams integrate multiple containers, each with its own scope.

[jboix]

The Comanders Act support team has acknowledged the need for a function to clear external variables used in a given container. For the time being they provided a manual solution and have raised an internal request for an evolution but can't guarantee its acceptance or provide a timeline.

In conclusion: there is no native function in Tagcomander at the moment to automatically clear external variables associated with a specific container.

[amtins]

Description

Some BUs, i.e. IL, seem to return inconsistent data from one media to another.

Example

If media A has the properties {a,b,c,d} but media B only has the properties {a,b}, when transitioning between media A and B, the properties {c,d} will be applied to media B.

Cause

This is because TagCommander does not classify properties by container, but provides a global object containing the properties of all containers. This makes it "impossible" to delete properties linked to a specific tag and the SDK doesn't provide a proper function to clean the variables specific to a container. See #164 (comment)

Conclusion

It would be interesting to discuss this with the team in charge of analytics, in order to purge certain values and keep only what is really necessary.

Finally, the IL returns the analyticsMetadata object which is specific to tagComander and analytcsData object which is specific to Comscore, whereas everything should be sent to the tag manager for reconciliation.