Learn how to integrate your browser-based tag with Tealium iQ Tag Management.
How Tags Work
A tag in the tag marketplace provides a complete integration of the capabilities of your tag. This means that every option and tracked event expected by your tag is combined into a single configurable instance of the tag in a Tealium user’s account.
The load rule determines when the tag should load on a page or event. Load rule conditions are based on data layer values.
Learn more about load rules.
Data mappings determine which dynamic values the tag needs from the data layer and the corresponding variable name used by the vendor. Mappings also determine how to track in-page events.
Learn more about data mappings.
Loading in the Browser
As a vendor, you can expect to see your same tag library or image pixel in the DOM of the page. At Tealium, we make every effort to load your tag exactly to your specifications. In rare cases where we must alter the code, we will ensure that the final tracking beacon matches your requirements.
For e-commerce tags that collect product and order data, Tealium offers a convenience feature, called the E-Commerce Extension, to ensure that all standard e-commerce data is automatically integrated with your tag. When the E-Commerce extension is configured in an account, it acts as a global data mapping to every tag that requires those values. This helps to minimize the amount of work needed to set up a tag of this type.
In addition to implementing your tag solution, Tealium can offer additional integration options depending on your system capabilities.
The purpose of a cookie match tag is to use special requests to synchronize visitor identifiers between Tealium and your system. This allows you to share your system’s unique visitor ID with Tealium’s server-side platform and receive Tealium’s visitor ID in return. This type of integration is used in addition to your standard tag.
The following example demonstrates a cookie match request:
This request originates in the browser and sends the Tealium visitor ID to your system. The result is a forwarding request containing your system’s visitor ID and Tealium’s visitor ID back to Tealium. This indicates that Tealium is hosting the match table, which is preferred. The final request to Tealium includes all of the provided Tealium variables and the vendor matched ID.
The following is an example redirect back to Tealium:
The following cookie match example passes the redirect request as a URL parameter, if the DSP’s endpoint accepts it:
Server-side enabled tags have the added ability to send events directly to Tealium EventStream and AudienceStream. For example, a user experience vendor inferring user sentiment by tracking mouse movements could trigger specific events directly to Tealium Collect. This type of integration is included with your standard tag.
The following example function sends data to the Tealium event endpoint: