TAGGRS Infrastructure

The TAGGRS Infrastructure offers a solid, proprietary server solution, independent of external parties like Google.

TAGGRS chooses its own path, separate from the big players, with a setup conceived and built by TAGGRS itself. This sets it apart from the common reliance on Google’s infrastructure, which many SST hosting providers use. TAGGRS servers are strategically distributed around the world and are not dependent on Google’s cloud servers. This independence ensures a solid foundation for continuous and fast tracking, regardless of server location.

The location and management of data are crucial for the privacy of European citizens. In the United States, data falls under the CLOUD Act, which grants U.S. government agencies access to data managed or stored by American companies. This also applies to data of European citizens. Storing data with American companies compromises a portion of the privacy of European citizens.

When a server approaches its capacity, TAGGRS' automatic migration system ensures a seamless transition to a less loaded server. This guarantees continuous fast tracking and balanced server load. The migration is carefully designed to provide every TAGGRS Server with the best possible performance, even during peak loads.

At TAGGRS, data is distributed across multiple servers, a strategy that ensures constant online tracking even if one server fails. The software is isolated into primary (Server Side Tracking) and secondary (viewing requests, analytical tools, etc.) components. If the secondary software fails, the primary continues to operate. This minimizes the risk of data loss and ensures a robust infrastructure.

Your TAGGRS server is activated directly in one of our data centers located around the world. Each rack within our TAGGRS Server and storage platform is equipped with redundant network connections and two independent power supplies (2N), each with its own Uninterruptible Power Supply (UPS) and diesel generator.

The TAGGRS data flow begins at the website, where data starts its journey to the subdomain, identified by a DNS with a unique IP address. From here, the data is routed to the load balancer, which acts as a distributor. This load balancer distributes the data across tracking servers that are spread worldwide, ensuring a balanced distribution and efficient processing. When one of these servers fails, the others take over, preventing data loss.

In the scenario where you are in the preview mode of Google Tag Manager, a separate server is activated to handle the data. Within the structure of the load balancer, there is also a syslog responsible for storing logs (storing anonymized data).

The load balancer also has the capacity to add extra data through the TAGGRS data enricher or to remove certain data, such as eliminating IP addresses when operating in TAGGRS's GDPR mode.

After these stages, the data is forwarded to Google Tag Manager, from where you can send the data to your favorite platforms like Google Analytics. This entire process forms the TAGGRS data flow, a streamlined process that ensures your data is transferred quickly and securely, ready to be analyzed for valuable insights.

The panel (dashboard) operates completely independently from the Server Side Tracking environment. So even if the panel goes down, Server Side Tracking continues to function.