Edge-Based Site Analytics for Browser Performance Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing web page delivery systems require clients to execute scripts, such as JavaScript, to track user interactions, which increases browser overhead and reduces performance.

Innovation Solution

Implementing edge-based site analytics by using a CDN edge server to insert consumption tracking page elements at strategic locations within the page, allowing for the determination of consumption metrics without the need for script execution in the client browser.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If scripts are executed in the client browser to track user interactions, then user interaction tracking is enabled, but browser performance deteriorates due to additional overhead

Engineering Contradiction:
Improveuser interaction tracking accuracyVSAvoidbrowser performance
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent extracts the analytics tracking functionality from the client browser to the server side. Instead of executing tracking scripts in the browser, the system uses server-generated HTML tags that are processed by the analytics server, eliminating the performance overhead from client-side script execution while maintaining tracking capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary HTML tag system that acts as a mediator between the web page and the analytics server. These special HTML tags are inserted by the server and processed by the analytics server to extract analytics data, eliminating the need for direct client-side script execution while enabling tracking.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If analytics scripts are included in web pages, then user behavior can be monitored, but page loading speed decreases due to additional processing requirements

Engineering Contradiction:
Improveuser behavior data collectionVSAvoidpage loading time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-generating analytics tags on the server side before the page is delivered to the client. The analytics server processes these tags and extracts behavior data server-side, eliminating the need for time-consuming client-side script execution and reducing page loading time while maintaining data collection capabilities.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If complex tracking scripts are executed client-side, then detailed interaction metrics can be captured, but device complexity increases

Engineering Contradiction:
Improveinteraction metrics detailVSAvoidbrowser processing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts complex tracking logic from the client browser to the server environment. The analytics server handles all complex processing, data extraction, and metric calculation, while the client browser only needs to render simple HTML tags, significantly reducing device complexity while maintaining detailed measurement precision.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses HTML tags as a copy mechanism to transfer interaction data from the client to the server. Instead of executing complex scripts, the browser simply renders and transmits HTML tag data, which the server then processes to extract detailed interaction metrics, reducing client complexity while maintaining measurement precision.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12255968B2Edge-based site analytics
Publication Date: 2025.03.18 LIFE360
  • US12255968B2 patent drawing
  • US12255968B2 patent drawing
  • US12255968B2 patent drawing

AI summary

A request for a page is received. In response to the request, content comprising the page is provided. The content includes an element which when executed by a browser with which the page request is associated causes the page as rendered by the browser to send a request initiated by the page to obtain an associated requested content. The request initiated by the page is received. A metric associated with the request initiated by the page is determined. Data reflecting the metric associated with the request initiated by the page is stored.