Web Content Management A/B Testing via Object-Level Variant Definition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing web content management systems face difficulties in implementing A/B testing and multivariate testing due to the need to alternate between object-oriented and markup language representation levels, making it inefficient and inconvenient, especially for dynamic websites and multiple devices.

Innovation Solution

Defining differences between webpage versions at the object-oriented level using content objects, allowing for efficient and reliable implementation of A/B testing without requiring transformations between levels, enabling consistent testing of complete websites and adaptive rendering for various devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If A/B testing is implemented at the markup language representation level, then testing functionality can be achieved, but it becomes difficult to implement in an object-oriented web content management system and requires alternating between different data levels

Engineering Contradiction:
Improveease of implementationVSAvoidsystem complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent creates a copy of the webpage structure at the object-oriented level by defining multiple website variants that reference the same content objects. Instead of manipulating markup language directly, the system works with object-level representations that can be rendered into different markup variants, thereby simplifying the implementation of A/B testing within the existing object-oriented architecture.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent shifts the A/B testing functionality from the markup language representation level to the object-oriented level, effectively moving the operation to another dimension of the system architecture. This allows the testing mechanism to work within the native data structure of the web content management system, eliminating the need to alternate between different data levels.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If webpage variants are defined using markup language representations, then A/B testing can be performed, but it requires manual adaptation for each device and channel

Engineering Contradiction:
Improvetesting coverageVSAvoidoperational convenience
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent defines website variants at the object-oriented level using content objects that can be universally rendered across multiple devices and channels. By working with abstract content objects rather than device-specific markup, the system achieves multi-functionality where the same variant definitions automatically adapt to different rendering contexts, eliminating the need for manual adaptation for each device and channel.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent performs preliminary definition of webpage variants at the object-oriented level before rendering. By pre-defining the structure and content relationships using content objects, the system prepares the variant configurations in advance, allowing automatic adaptation during rendering without requiring manual intervention for each device or channel scenario.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If A/B testing is implemented on dynamic websites, then testing can be performed, but changes need to be manually adapted across all affected webpages

Engineering Contradiction:
Improvetesting efficiencyVSAvoidtime for manual adaptation
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements A/B testing on dynamic websites by defining variants at the object-oriented level using reusable content objects. This universal approach allows the same variant definitions to automatically apply across all affected webpages and dynamic content instances, eliminating the need for manual adaptation and significantly improving testing efficiency while reducing the time investment required.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments the webpage into reusable content objects that can be independently managed and referenced. By breaking down the webpage structure into discrete, reusable objects, the system can efficiently apply variant changes across multiple webpages by simply reconfiguring object relationships rather than manually editing each webpage, thereby reducing the time required for adaptations.

Inventive Principle:
Principle #1Segmentation

4Reliability

If multiple website variants are defined, then comprehensive A/B testing can be performed, but the burden on web servers increases

Engineering Contradiction:
Improvetesting accuracyVSAvoidserver processing load
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent performs preliminary rendering of multiple website variants and stores the rendered markup language representations in advance. By pre-rendering the variants and caching them, the system reduces the real-time processing burden on web servers during A/B testing, as the server can serve pre-generated variant content rather than dynamically rendering multiple versions on each request, thereby maintaining testing accuracy while reducing server load.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates rendered copies of website variants and stores them for efficient serving. Instead of generating multiple variant versions dynamically during each user request, the system creates and caches rendered copies of the variants in advance, allowing the web server to serve these pre-generated copies with minimal processing, thus reducing server energy consumption while maintaining the ability to perform comprehensive A/B testing.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP2648106B1Method and web content management system for A/B testing or multivariate testing of websites on computers being connected to a web content management system
Publication Date: 2019.04.03 COREMEDIA AG
  • EP2648106B1 patent drawingFigure 1
  • EP2648106B1 patent drawingFigure 2
  • EP2648106B1 patent drawingFigure 3

AI summary

The present invention relates to a method and a system for A/B testing of a website on a computer 201 being connected to a web content management system 100, wherein the method comprises receiving S101, at the web content management system 100 from a requesting computer 201, a webpage data request directed to a webpage of a website for which at least two website variants including a first website variant and a second website variant are defined, and selecting S102 one website variant of the at least two website variants of the website. If the second website variant is selected, the method further comprises creating S106, S107, S109, at the web content management system 100, first markup language representation data of the webpage on the basis of the first website variant and content objects indicated by the first website variant, second markup language representation data of the webpage on the basis of the second website variant of the website and content objects indicated by the second website variant, and webpage difference data on the basis of determined differences between between the first and second markup language representation data of the webpage. Then, the requesting computer 201 is provided S110, S111 with the first markup language representation data of the webpage and with the created webpage difference data for post-processing of the first markup language representation at the requesting computer 201 on the basis of the webpage difference data.