Multilevel Application Configuration for User Engagement

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing content delivery systems struggle to effectively retain and engage users by segmenting them based on demographic information, which often fails to meet the desired user retention and engagement levels.

Innovation Solution

A server device segments users based on their engagement with an application, generating predictive models from user event data to determine user engagement segments and configure the application accordingly, allowing for personalized content presentation and dynamic configuration updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users are segmented based on demographic information, then content can be customized for user groups, but user retention and engagement results are insufficient

Engineering Contradiction:

Improvecontent customizationVSAvoiduser retention

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments users into distinct groups based on their engagement behaviors rather than demographics. The system divides the user population into segments such as 'highly engaged,' 'moderately engaged,' and 'at-risk' users based on measurable engagement metrics, allowing for targeted content delivery to each segment that directly addresses their specific engagement patterns and needs.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system dynamically changes content delivery parameters based on user engagement behavior. Instead of static demographic-based content selection, the system adjusts content type, frequency, and presentation based on real-time engagement metrics, transforming the content delivery approach from demographic-based to behavior-based parameter adjustment.

Inventive Principle:

Principle #35Parameter changes

2Extent of automation

If content is selected based on demographic segments, then content delivery can be automated, but the precision of matching user interests is insufficient

Engineering Contradiction:

Improvecontent selectionVSAvoiduser interest matching

Core Design Contradiction:

Extent of automationVSMeasurement precision

Solution Approach 1:

The system implements a feedback loop where user engagement with delivered content is continuously measured and fed back into the segmentation model. Engagement metrics such as time spent, interactions, and content consumption patterns are tracked and used to refine user segment assignments and improve future content selection accuracy, creating a self-improving automated system.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary segmentation and content preparation based on predicted user engagement patterns before actual content delivery. By pre-analyzing engagement data and preparing targeted content for different user segments in advance, the system ensures that when content is delivered, it is already optimized for the specific engagement characteristics of each user group.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If user engagement segments are determined and applied, then user engagement improves, but system complexity increases

Engineering Contradiction:

Improveuser engagementVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal engagement tracking and segmentation framework that can be applied across multiple content types and delivery channels. The same engagement measurement and segmentation logic works for different user groups, content categories, and delivery platforms, reducing the need for separate complex systems for each content type while maintaining high engagement effectiveness.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11232171B2Configuring applications using multilevel configuration

Publication Date: 2022.01.25 APPLE INC

AI summary

In some implementations, a user device can generate configuration data for an application on the user device using multilevel configuration data. For example, an application on the user device can obtain application level configuration data from a server device. The application level configuration data can be generated based on user engagement segments associated with the user of the user device, for example. The application can obtain publisher level configuration data generated by a content publisher. In response to requesting a content item, the application can receive content level configuration data. The application can combine the application level configuration data, the publisher level configuration data, and/or the content level configuration data to generate dynamic configuration data. The dynamic configuration data can be used by the application to determine, among other things, what content to present to the user of the application on the user device.