# Server-Side Tags (S2S - Server to Server)

Those tags will be executed on the JENTIS server runtime. They fully profit from the data privacy and security of the JENTIS architecture. You completely control what data will be transmitted to the third party. **Additionally, you can use all the components in the JENTIS framework: server-side variables, transformation functions for anonymization and pseudonymization, server-side data persistence, and enrichment**.

Further, two methods of S2S are available in individual tags with JENTIS:

* **Twin-Server Native Implementation:** in this mode, a third-party library is executed on the JENTIS server, and the operation mimics the original execution the same as it would on the client side (though executed on a server and not on a user's device).
* **Protocol-Based Implementation:** In this mode, JENTIS will leverage a documented API from the provider (the receiver of the data) and send data accordingly, i.e., following a Measurement Protocol with Google Universal Analytics.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.jentis.com/core-concepts/tracking-modes-client-side-server-side-hybrid/server-side-tags-s2s-server-to-server.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.