Tracking Modes: Client Side, Server-Side, Hybrid
This is an overview of the tracking modes or types of tags within JENTIS. Choose the right model for your privacy, performance, and feature needs.
JENTIS Tags: Server-side, Client-side and Hybrid
JENTIS is a server-side tracking platform with every component designed to enhance server-side execution. However, that does not mean all our components must run on the server. Many roots of our framework are also grounded in client-side components. With many requirements arising from front-end capacities, we support most data schemes found in online marketing today. However, JENTIS recognizes the need for client-side tracking in a few specific cases and allows maintaining client-side tags, supporting most data schemes from current online marketing practices. In this article, we will talk about the different tags available on the JENTIS Platform - server-side, client-side, and hybrid.
Tag, Tools, and Data Runtimes
JENTIS offers different runtimes for your data flows. A runtime is a framework or setup that defines where and how the data processing occurs and is key to privacy, security, and data availability (i.e., third-party cookies).
If you execute the same data stream (HTTP-based) from a server to a server, it will have different header and meta (user agent, IP address, etc.) parameters than when the same request is sent from the client to the receiving server. That impact is one of our backbones in data privacy and security architecture. At the same time, it affects your data flows with JENTIS and your desired tools.
Therefore, all data streams to the tools we have in our list support different schemes. In general, we have three groups:
CLIENT-SIDE TAGS: are executed on the device (browser) of the website visitor - C2S (Client to Server) communication.
SERVER-SIDE TAGS: are executed on the server (JENTIS) - S2S (Server to Server) communication.
HYBRID TAGS: are built server-side but executed on the device (browser) of the website visitor: C2S (Client to Server) communication.
Not all tools support all three schemes - it is also bound to what a tool provider supports as a receiver. In some cases, some tools are specifically designed not to receive data in S2S communication.
Here is a short summary of the benefits, strengths, and drawbacks of each of these three options
Full Data Privacy and Security Control
❌
✅
❌
Control of Third-Party Applications (loading external JS sources is restricted)
❌
✅
✅
Enhances Website Performance (Speed)
❌
✅
✅ (to a certain extent)
Server-Side Data Persistence (all variables available)
❌
✅
✅
Server-Side Functions (anonymization, pseudonymization of fields and values)
❌
✅
✅
Data Enrichment
✅
✅
✅
Third-Party Data Exchange (i.e. third-party cookies)
✅
❌
✅
Continue to learn more about the different tag types in JENTIS.
\
Last updated
Was this helpful?