Sequential Segment Analytics Engine for Pre-Post Event Correlation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional analytics engines struggle to efficiently identify and organize large volumes of data from high-traffic websites or applications, often requiring significant processing power and manual coding to create specific user segments, which is time-consuming and inflexible.

Innovation Solution

An analytics engine that creates sequential segments from analytics data to investigate events before or after a sequence of events, allowing for the identification of pre-sequence and post-sequence events by querying an analytics database and providing granular datasets for web administrators to analyze user behavior.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional analytics engines individually analyze billions of transactions to identify data representing segments defined by sophisticated query parameters, then measurement precision is improved, but productivity deteriorates due to the time-consuming nature of the process

Engineering Contradiction:
Improvesegment identification accuracyVSAvoidsegment creation speed
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The analytics engine performs preliminary actions by creating and storing intermediate results of transaction analyses in advance. When a segment query is received, the engine retrieves and combines these pre-computed intermediate results rather than analyzing all transactions from scratch, enabling fast segment identification while maintaining high precision through comprehensive transaction coverage.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If conventional analytics engines consume significant processing power to create specific segments that satisfy sophisticated query parameters, then measurement precision is improved, but use of energy worsens due to the computational intensity

Engineering Contradiction:
Improvesegment identification accuracyVSAvoidprocessing power consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The analytics engine performs preliminary actions by creating and storing intermediate results of transaction analyses in advance. When a segment query is received, the engine retrieves and combines these pre-computed intermediate results rather than analyzing all transactions from scratch, enabling fast segment identification while maintaining high precision through comprehensive transaction coverage.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If web administrators manually program code to generate segments, then adaptability is improved allowing easy changes and revisions, but productivity deteriorates due to the time-consuming manual process

Engineering Contradiction:
Improvesegment modification flexibilityVSAvoidsegment creation speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The analytics engine performs preliminary actions by creating and storing intermediate results of transaction analyses in advance. When a segment query is received, the engine retrieves and combines these pre-computed intermediate results rather than analyzing all transactions from scratch, enabling fast segment identification while maintaining high precision through comprehensive transaction coverage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The analytics engine provides self-service capabilities by automatically processing segment queries using stored intermediate results without requiring manual programming. Administrators can easily modify segment definitions through the interface, and the engine autonomously retrieves and combines the appropriate pre-computed intermediate results, delivering both flexibility and high productivity.

Inventive Principle:
Principle #25Self-service

4Device complexity

If conventional analytics engines lack the ability to identify and organize captured data in highly specified categories, then device complexity is reduced, but measurement precision deteriorates due to insufficient data organization capability

Engineering Contradiction:
Improveanalytics engine simplicityVSAvoiddata categorization accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The analytics engine applies segmentation by dividing the complex task of transaction analysis into multiple intermediate results organized by different dimensions (e.g., user behavior patterns, transaction types, time periods). Each intermediate result represents a specific category of analyzed data. When a segment query is received, the engine retrieves and combines the relevant pre-computed intermediate results, achieving high measurement precision through systematic data organization while keeping the engine architecture relatively simple.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11989242B2Generating sequential segments with pre-sequence or post-sequence analytics data
Publication Date: 2024.05.21 ADOBE INC
  • US11989242B2 patent drawing
  • US11989242B2 patent drawing
  • US11989242B2 patent drawing

AI summary

This disclosure generally covers systems and methods that create sequential segments from analytics data to enable investigation of events that occurred before or after a certain sequence of events—that is, pre-sequence or post-sequence events. In particular, certain embodiments of the disclosed systems and methods receive a segment query of certain analytics data to identify events that occurred before or after a defined sequence of events within a network and—in response to the segment query—provide a query result that identifies pre-sequence events or post-sequence events. By providing such query results, the disclosed systems and methods enable users to examine correlations between a sequence of events and any pre-sequence or post-sequence events, including any data associated with those events at a granular level.