Hybrid Tags

Those tags are similar to client-side tags but have all the advantages of server-side tags. Let's examine the data flow process here:

Data is first collected on the user's device and sent to the JENTIS server. There, the final data stream is built with all the capabilities of the JENTIS server, just as with Server-Side Tags. After this computation, the data to be sent to the receiver is again forwarded back to the client, which will execute the beacon call. This will, in turn, activate the capabilities of client-side executed data streams (e.g., third-party cookies).

However, this also has the drawback of client-side tags: the stream is from the client to the server (third-party), which means that, again, the client's IP address and other HTTP header fields will be exposed to the third party.

Some technical details on this communication:

The stream from client to server (C2S) is asynchronous. So, there is a constant pull from the client to the JENTIS server to get new streams back to execute. You may note that there is a "/commands" request in the network protocol after installing JENTIS on your website. This constant pulling enables communication between the previously described hybrid tags.

These streams, however, will only be used when mandatory, such as when a tag is to be executed in hybrid mode. If you do not implement any hybrid tags, JENTIS will not install the corresponding pulling service to save resources on your site.