Intermediary Server for Third-Party Tool Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Websites face performance slowdowns and security risks due to the loading of multiple third-party tools, which can lead to increased resource requests and the execution of potentially malicious scripts directly on the client, making it difficult for operators to manage and secure these tools effectively.
Innovation Solution
Implementing an intermediary server that manages the loading of third-party tools, allowing website operators to configure which tools to load and when, executing them remotely instead of on the client, and providing features like data loss prevention scanning and optimized script loading to enhance security and performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple third-party tools are loaded directly on the client, then the website can access various functionalities (analytics, chat widgets, maps), but the website experiences performance slowdown and security risks
Solution Approach 1:
The patent introduces a server-side intermediary system that acts as a mediator between the website and third-party tools. The server retrieves, executes, and manages third-party scripts remotely, preventing direct client-side execution of potentially malicious code while maintaining access to various third-party functionalities. This resolves the contradiction by enabling versatility through server-mediated access while improving security by isolating the client from direct exposure to untrusted scripts.
2Adaptability or versatility
If multiple third-party tools are loaded directly on the client, then various functionalities are available, but page loading time increases due to multiple resource requests
Solution Approach 1:
The patent merges multiple third-party tool functionalities into a single server-side execution environment. Instead of the client making separate requests to multiple third-party services, the server consolidates these interactions, retrieves necessary resources in bulk, and manages executions centrally. This reduces the number of client-side resource requests and page loading time while preserving access to diverse third-party functionalities.
3Productivity
If third-party scripts are executed directly on the client, then tools can collect and transmit information, but the client executes potentially malicious code and experiences resource burden
Solution Approach 1:
The server acts as a trusted intermediary that executes third-party scripts in a controlled environment. The server retrieves scripts from third-party sources, executes them server-side, and manages data collection and transmission. This eliminates the security risk of client-side malicious code execution while maintaining the productivity benefits of data collection and transmission capabilities.
4Ease of operation
If website operators use traditional tag managers to configure third-party tools, then tool loading can be controlled, but operators still cannot fully track or secure what is being included due to remote JavaScript resources
Solution Approach 1:
The server-side execution system serves as a transparent intermediary that provides operators with complete visibility into all third-party resources. Since the server retrieves and executes all scripts centrally, operators can track exactly what resources are loaded, from where, and how they are executed. This eliminates the opacity of client-side remote JavaScript execution while maintaining ease of tool configuration through the existing tag manager interface.
Data Source
AI summary
Managing the loading of third-party tools on a website is described. Configuration is received for loading the third-party tools. An intermediary server receives a request for a page that is hosted at an origin server. The intermediary server retrieves the page and modifies the page including automatically including a third-party tool manager to the retrieved page. The third-party tool manager includes a set of one or more client-side scripts that, when executed by the client network application, collects, and transmits information to the intermediary server for loading the third-party tools. The intermediary server loads the third-party tools based on the received information and the configuration. The intermediary server causes event data to be transmitted to third-party tool servers that correspond with the third-party tools.