Server-Side Storage Interface

With the JENTIS Server-Side Storage, we have introduced a powerful solution to mitigate tracking preventions and browser restrictions by moving cookies from the browser to the JENTIS Server-Side Runtime Environment. This approach extends the lifetime of user identifiers and improves ad attribution accuracy by ensuring a more stable and persistent tracking method.

How Does It Work?

Instead of relying solely on browser-based cookies, which are increasingly blocked or limited by modern tracking preventions, JENTIS maintains a stable User-ID within the browser environment. This User-ID is then linked to the JENTIS Server-Side Storage, allowing for seamless tracking and data persistence across different sessions and devices.

Accessing the JENTIS Server-Side Storage

To utilize the JENTIS Server-Side Storage, a dedicated runtime environment provides access to server-side variables that enable all necessary functionalities.

In the following sections, we will:

1. Explain the structure of the JENTIS Server-Side Storage in detail.

2. Demonstrate how to effectively implement and use it within your tracking setup.

By leveraging JENTIS Server-Side Storage, businesses can ensure data consistency, improve attribution modeling, and maintain compliance with evolving privacy regulations while still obtaining valuable insights.

Server-Side Storage Architecture

The JENTIS Server-Side Storage Architecture enables the persistent storage of information within the JENTIS Runtime Environment, similar to how cookies function in a browser. This allows for longer data retention, improved tracking reliability, and enhanced compliance with privacy regulations.

How Data is Stored in Server-Side Storage

To store data in the JENTIS Server-Side Storage, three key components are required:

• Name – The identifier for the stored data.

• Value – The actual data being stored.

• Expiration Timestamp – Defines how long the data should persist before being automatically removed.

Hierarchy of Server-Side Storage

JENTIS organizes Server-Side Storage using a hierarchical structure, ensuring data isolation and access control based on different levels:

1. User Storage per Tool-Instance

   • Stores data per user and per tool-instance.

   • Useful for tools requiring individual tracking per session or specific configurations.

2. Tool-Instance Level Storage

   • Storage is isolated per tool-instance (e.g., Google Analytics, Meta, TikTok).

   • Ensures that data remains separate for each tool instance, preventing conflicts between different integrations.

3. Global User Storage

   • Data shared across multiple tool instances for a single JENTIS User-ID.

   • Enables cross-tool data consistency while respecting storage limitations.

Using the Right Context for Data Access

When interacting with JENTIS Server-Side Storage, it’s crucial to use the correct storage context to retrieve and modify data. Depending on the implementation, data should be accessed and stored at the right level to ensure efficiency and security.

By leveraging JENTIS Server-Side Storage, businesses gain greater control over user data persistence, ensuring that tracking remains reliable, compliant, and resistant to browser-based tracking restrictions.

Read Next

User Storage per Tool-Instance

Tool-Instance Level Storage

Global User Storage