Ingenious Technologies offers several GTM tags that can be used to add Ingenious Tracking to your pages using the tag manager.
Unfortunately, our templates are not available in the Google Template Gallery at the moment, as they are still under review. Nevertheless, it is possible to download the templates from our public Github repository and install them in your Google Tag Manger account.
https://github.com/i19s
We offer tags that can replace the Onpage Tag and the eCommerce Conversion Tag. These can be implemented on the client side as well as on the server side.
All tags process data from different sources to create the tracking calls.
The sources from which the tag data is used are:
Variables from the tag configuration
First party cookies
DataLayer/Event data
Furthermore, default values for some variables are stored in the tag.
The initialisation of a variable is performed as follows. If the variable is specified in the tag configuration, this value is used. If no value is specified, the tag will try to find the value in the DataLayer. If it does not find a value there, the tag default is used. This procedure makes it possible to implement complicated setups or to test a specific functionality.
The following is a description of the different tags with their variables and defaults.
Client-side GTM tags
Ingenious Technologies Onpage Tracking Tag
This tag replaces the Onpage tag. If it is a click-in with a clickId parameter, this is stored in a cookie. In addition, tsc and tsv cookies are written and used in tracking requests.
Fields | Description | Default |
|---|---|---|
Tracking Domain | The tracking domain can be a Third-Party Ingenious Tracking Domain, a First-Party Ingenious Tracking Domain or a GTM Serverside Domain. You can find it on the platform under "Partnerships -> Advertiser -> Settings". | |
Advertiser Id | You can find the advertiser ID on the platform under "Partnerships -> Advertiser -> Settings". Do not use the internal ID (mid). | |
Redirect Mode | Overwrites the corresponding partner-specific default setting. It controls the way in which forwardings are set up. | 0 |
Customer Id | This specifies the internal customer ID from your system. | |
User Value 1 | These fields are for free additional information. All formats are accepted. | |
User Value 2 | These fields are for free additional information. All formats are accepted. | |
Site Id | A short description of the page. | |
Product Id | The unique identifier of the product. Use this, if this is a page that displays a specific product. | |
Timestamp | Usage for cache invalidation. | A timestamp is generated when the tag is executed. |
Session Id | A session Id. The data type is string. | |
HTTP Referrer | The complete Browser-URL on which the user comes from. | The referrer header is used. |
HTTP Location | The complete Browser-URL on which the tag was fired. | The current full URL is used. |
Gdpr | Activates the general data protection regulation according to TCFv2.0 | |
Gdpr Consent | The actual tcfv2.0 string |
Ingenious Technologies ECommerce Conversion Tracking Tag
This tag replaces the Ecommerce Conversion tag.
Fields | Description | Default |
|---|---|---|
Tracking Domain | The tracking domain can be a Third-Party Ingenious Tracking Domain, a First-Party Ingenious Tracking Domain or a GTM Serverside Domain. You can find it on the platform under "Partnerships -> Advertiser -> Settings". | proxy.ingenious.cloud |
Advertiser Id | You can find the advertiser ID on the platform under "Partnerships -> Advertiser -> Settings". Do not use the internal ID (mid). | |
Conversion Id | Unique conversion identifier from your system | gtmss_{currentTimestampMillis} |
Conversion Target | Defines an event and its type, for example Sale, Appinstall, Newslettersignup. | sale |
Tracking Currency | Determines the currency for all amounts. | |
Unique Id | The unique ID is used to identify conversions during the validation process. | |
Discount Value | This is the total net discount value. '0.00' is allowed. | |
Discount Code | This is the applied discount code. | |
Basket | The contents of the shopping cart consist of items containing the following values in JSON format | |
Session Id | A session Id. The data type is string. | |
Click Ids | A comma-separated list of click IDs. | uses _iclid Cookie |
Gdpr | Activates the general data protection regulation according to TCFv2.0 | |
Gdpr Consent | The actual tcfv2.0 string | |
Site Id | A short description of the conversion page. | |
Timestamp | Usage for cache invalidation. | Current Timestamp in Millis |
HTTP Location | The complete Browser-URL on which the tag was fired. | |
Customer Id | This specifies the internal customer ID from your system. | |
Customer New | This specifies a new or existing customer. Use value 'true' for new customer or 'false' for existing customer. | |
Pay Method | Customer payment method, for example 'credit card' or 'paypal'. | |
User Value 1 | These fields are for free additional information. All formats are accepted. | |
User Value 2 | These fields are for free additional information. All formats are accepted. |
Example
The picture shows an exemplary implementation of the Ingenious Tags. The Onpage Tag and the ECommerce Conversion Tag are installed on the client side. These are configured in such a way that they send their tracking requests to a server-side GTM container, which is accessible via a first party subdomain. The server-side Ingenious client receives the tracking requests and converts the requests into events. Third-party tags can be triggered by the Ingenious events. Furthermore, the Ecommerce Conversion Tag fires server-side and the Onpage Tag fires server-side and forwards the requests to the Ingenious infrastructure.