Cookie Data Joining via Redirection Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in effectively combining data from multiple cookies for analytics and remarketing purposes, particularly when certain features are activated but not implemented in the resource code, leading to incomplete user interaction data.

Innovation Solution

A method and system that utilize a configuration-based redirection system to combine data from multiple cookies by transmitting a join identifier and configuration data, allowing for the association of data from various redirection destinations with a single identifier, enabling the collection and combination of analytics and remarketing data without requiring modifications to the resource code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If data from multiple cookies is combined using traditional methods, then data completeness improves, but system complexity increases due to requiring code modifications in resources

Engineering Contradiction:
Improvedata completenessVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent introduces a configuration-based redirection system that acts as an intermediary between the resource code and the cookie data collection process. This redirection system receives requests, determines which cookies to retrieve based on configuration data, and combines the data without requiring modifications to the original resource code, thereby reducing system complexity while maintaining data completeness

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the cookie data collection process into separate, independently configurable components. Each cookie retrieval is determined by specific configuration data rather than being hard-coded, allowing the system to manage multiple data sources through modular configuration rather than complex integrated code

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If features are activated in configuration data but implemented in resource code, then analytics capability improves, but ease of operation deteriorates due to requiring code modifications

Engineering Contradiction:
Improveanalytics capabilityVSAvoidease of operation
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements a dynamic configuration system where analytics capabilities can be activated or deactivated through configuration data without requiring code changes. The system adapts its behavior based on the configuration, allowing features to be enabled or disabled by simply modifying configuration parameters rather than rewriting code

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent performs preliminary configuration setup where all possible analytics features are pre-defined in the configuration data. This allows the system to be fully adaptable to different analytics needs while maintaining ease of operation, as users can simply select which pre-defined features to activate rather than implementing code from scratch

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10594820B2Conditionally joining data from cookies
Publication Date: 2020.03.17 GOOGLE LLC
  • US10594820B2 patent drawing
  • US10594820B2 patent drawing
  • US10594820B2 patent drawing

AI summary

Conditionally combining data from several sources may include retrieving data from several sources in response to a single request and using one or more redirection responses. The request from a client device may include a device identifier, a third-party identifier, a join identifier based, at least in part, on the device identifier, and first data from a first source, such as a first cookie, associated with the received request. A redirection destination may be determined based on configuration data associated with the third-party identifier, such as whether one or more services are selected and/or activated by a publisher of a resource. A redirection response is transmitted to the client device responsive to the received request and includes the redirection destination and the join identifier. The first data from the received request and second data received from the redirection destination may be associated based on the join identifier.