Tag Templates
  • 31 Mar 2022
  • 1 Minute to read
  • Contributors
  • Dark

Tag Templates

  • Dark

Every tag follows a certain template. Which will define what kind of event you will activate with that tag. Giving you basically different options to track an action and create the according data stream.

So a template is the interface and the parameters a tag configuration will hold.

Tag Sender Concatenation

The sender tag concatenation concept is a smart solution to combine multiple tags under special circumstances. Thus enabling your JTM configuration to combine data streams into one. Saving data bandwidth, your tools resources and creating more convenient data models for analytics.

Concept Details

Any tag in the JENTIS tag manager is determined to stream data as the final step. After checking if the tags trigger conditions are true and all parameter values are computed. This final stream however can consist of multiple tags, so two tag configurations are applied. Thus are merged into one single stream.

The main “sender” tag (or “parent”) is a generic tag. Complemented by a child tag (the more specific configuration). While the sender tag defines broad and generic configurations the child tag will specify details on certain events.

A common example is the configuration of a “pageview” as the generic tag. A second tag will then define details that only apply in some circumstances (trigger conditions; that are defined in the child tag), ie. ecommerce data that was part of this event (a “product detail view”, “transaction”, “conversion”, etc).

Tag Hierarchy

When two configurations apply to the same data stream an obvious conflict must be discussed. Both configurations can define the same parameter of a tool with different values assigned. In that case the more specific tag will override the more generic (parent) configuration.

Coming back to our example of a pageview tag and an ecommerce tag: lets imagine both define a “Page Title” property to be tracked with this tool.

Pageview Tag:

  • Page Title = “Main Page”

Ecommerce Tag:

  • Page Title = “Detail Page”

As both tags define the same property (“Page Title”) with different values we have a conflict. This is resolved via the generic approach to always keep the most specific definition. Thus the data stream will be “Detail Page”-value in the “Page Title”-attribute.

Was this article helpful?

What's Next