In-Application Message Delivery via Remote Trigger Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing customer engagement systems are limited in delivering in-application messages as they can only utilize triggering events within the software application or user's device, failing to incorporate events from external servers, which restricts the ability to send messages based on comprehensive user data and behavior analysis.
Innovation Solution
The system integrates a customer engagement service that utilizes a customer engagement service to manage and orchestrate message delivery, incorporating user data from various sources, including external servers, to generate and deliver in-application messages based on up-to-date user-specific information and trigger conditions, using conditional statements and boolean logic to personalize messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the system uses only internal triggering events within the software application or user's device, then the system complexity remains low, but the message personalization and timing precision are insufficient
Solution Approach 1:
The patent introduces a customer engagement service as an intermediary component that bridges the software application and external data sources. This service receives trigger events from multiple sources including internal application events and external server events, processes them centrally, and determines message delivery. The intermediary architecture allows the system to access comprehensive user data without requiring complex integration logic to be distributed throughout the application codebase.
2Adaptability or versatility
If the system incorporates external server events for trigger conditions, then the message personalization capability improves, but the system complexity increases due to additional integration requirements
Solution Approach 1:
The customer engagement service is designed as a universal platform that handles multiple functions: receiving internal application events, processing external server events, maintaining user profiles, determining trigger conditions, and orchestrating message delivery across multiple channels. This multi-functional design consolidates what would otherwise require separate specialized components, reducing overall system complexity while enhancing personalization capabilities.
Solution Approach 2:
The system performs preliminary actions by pre-configuring trigger conditions and message templates in the customer engagement service before actual events occur. User profiles and preferences are established in advance, and trigger rules are defined beforehand. When events occur from internal or external sources, the service simply evaluates them against pre-defined criteria, avoiding the need for complex real-time decision logic during event processing.
3Productivity
If the system delivers messages based on comprehensive user data from multiple sources, then the user engagement effectiveness improves, but the data processing time and system resource usage increase
Solution Approach 1:
The customer engagement service performs preliminary data processing by maintaining up-to-date user profiles that consolidate information from multiple sources before trigger events occur. User preferences, behavior patterns, and contextual information are pre-processed and stored in ready-to-use formats. When a trigger event is received, the service can quickly retrieve and apply relevant profile data without performing complex queries or aggregations in real-time, thus reducing message delivery latency.
Data Source
AI summary
Systems and methods for presenting an in-application message to a user of a software application make use of trigger conditions that occur on remote servers. When a remote server notes the occurrence of activity relating to a user that comprises a trigger condition, the remote server sends information about the activity to a customer engagement service. The customer engagement service causes a push notification to be sent to a user's computing device that is running a software application. Receipt of the push notification causes a campaign within the software application to log a trigger condition as satisfied, which in turn causes the campaign to present the user with an in-application message.