Follow for free plugins, new theme releases and theme news
Plugin Description
JENTIS is the European tech pioneer in server-side tracking. The Austrian scale-up’s innovative technology ensures better data quality and enables full compliance with privacy regulations. The solution delivers up to 50% more data to web analytics tools and advertising systems and provides website operators with sovereignty over their raw data for advanced analytics and AI applications.
LEGALLY COMPLIANT TRACKING
Become GDPR-compliant without changing your existing marketing tech stack
FUTURE-PROOF FIRST-PARTY DATA
Prepare for the cookie-less future and capture first-party data
OPTIMIZED PAGE SPEED
Improve page speed and Google rank with just a single pixel on your website
MANAGED SERVICE
Support and performance monitoring following the highest security standards
SERVER-SIDE TRACKING from the EU
Keep your data collection compliant and under control with Server Side Tracking from the heart of the EU
How does JENTIS tracking work?
As JENTIS is built around privacy, nothing will be tracked without a consent from the user. Furthermore, no behavioral data is tracked without a tracking tool in use, as tracking tool(s) will define what data points are needed to be tracked with the help of JENTIS.
Both consent bar and tracking tool(s) can be configured manually in JENTIS Tag Manager (JTM).
Without these steps not a single point of data will be tracked.
As our product is privacy and tracking tool based, there are 3 levels of situations that can happen after the Webpage owner adds the JENTIS plugin to their webpage.
-
WordPress’ web page owner adds JENTIS plugin. The plugin implements the JENTIS Tracking Code (javascript snippet) to every page.
-
WordPress’ web page owner adds the JENTIS plugin and configures the consent bar (CMP) in JENTIS Tag Manager (JTM).
After CMP is configured in JTM by the web page owner or an authorized Tracking agency, JENTIS will still not track user behavior as there is no Tracking
tool configured, but will track the consent status upon user interaction with the consent bar.
Status of accepting / denying vendors is tracked now for later usage.
Datapoints: User ID – Unique ID generated by JENTIS, Consent ID – Unique ID generated by JENTIS, Last update timestamp – Unix timestamp, indicated time when the interaction happened, Information about the tracking tools – which tools are denied or accepted
- WordPress’ web page owner adds JENTIS plugin and configures the consent bar and configures 1 or more tracking tools in JENTIS Tag Manager. After CMP and 1 or more tracking tool(s) is/are configured, JENTIS still won’t track anything other than the consent status as there is another missing piece in the system, which enables JENTIS to track behavioral data. In general the web page owner has to implement small javascript code snippets manually to the web page. These are signals in the browser to the JENTIS Tracking Code. These signals tell JENTIS what interactions performed by the visitor. If consent is given by the Visitor and signals are provided by the Web page, JENTIS will track data points, which are necessary for the Tracking tools
Datapoints
Following events are pushed automatically into JENTIS Datalayer object, when the page loads or visitor interacts with the webpage:
Page view:
Triggers on all webpages. Gives the information that the visitor visited a specific webpage. This document does not carry any additional data points. It is only a signal for JENTIS
Search: Triggers on pages, where the visitor sees the results after typing in the search words into the search input field. Datapoints pushed into Datalayer:
* Signal of a search
* Search term
* Count of the results
If the search result in 1 or more products
* Product’s ID
* Product’s name
* Product’s brutto
* Product’s netto
Product list: Triggers on pages, where a list of products are displayed, such as product category pages. Datapoints pushed into Datalayer:
* Signal of a product list
* Product list’s name (if any),
* Products on the page
* Products’ ID
* Products’ name
* Products’ brutto
* Products’ netto
* Products’ affiliation (if any)
* Products’ variant (if any)
* Products’ position
* Products’ quantity
Product list click: Triggers upon visitor interaction, when the visitor clicks on a product in a product list.
Datapoints pushed into Datalayer:
* Signal of a product list click
* Product list’s name (if any)
* Product the visitor clicked on
* Product’s ID
* Product’s name
* Product’s position
Product view: Triggers on single product detail pages. Datapoints pushed into Datalayer:
* Signal of a product view
* Product related:
* Product’s ID
* Product’s name
* Product’s brutto
* Product’s netto
Add to cart: Triggers when the visitor clicks on the add to cart button. Datapoints pushed into Datalayer:
* Signal of a addtocart
* Product related:
* Products’ ID
* Products’ name
* Products’ brutto
* Products’ netto
* Products’ affiliation (if any)
* Products’ variant (if any)
* Products’ position
* Products’ quantity
Remove from cart: Triggers when the visitor clicks on the remove from cart button. Datapoints pushed into Datalayer:
* Signal of a removefromcart
* Product related:
* Products’ ID
* Products’ name
* Products’ brutto
* Products’ netto
* Products’ affiliation (if any)
* Products’ position
Cart view: Triggers when a visitor is viewing the cart. Datapoints pushed into Datalayer:
* Signal of a cartview
* Brutto value of the cart
* Netto value of the cart
* Product related:
* Products’ ID
* Products’ name
* Products’ brutto
* Products’ netto
* Products’ quantity
Checkout: Triggers on all pages of the checkout phase. Datapoints pushed into Datalayer:
* Signal of a cartview
* Checkout step – On how many steps the visitor is on currently.
* Brutto value of the checkout
* Product related:
* Products’ ID
* Products’ name
* Products’ brutto
* Products’ quantity
Checkout Option: Triggers on a checkout page upon visitor interaction. When a visitor clicks on the “place order” button. Datapoints pushed into Datalayer:
- Signal of checkoutoption
- Type of the payment
Order: Triggers on the so-called “Thank you page”, when the order is placed. Datapoints pushed into Datalayer:
* Signal of order
* Order ID
* Netto value of the order
* Brutto value of the order
* Zip (if any)
* Country (if any)
* Type of the payment
* Shipping cost
* Tax amount
* Vouchers name, type, value, code (if any)
* Product related:
* Products’ ID
* Products’ name
* Products’ brutto
* Products’ netto
* Products’ quantity
* Products’ affiliation (if any)
* Products’ position
Screenshots
Jentis WooCommerce Settings
