Customizable Website Notification Templates and Events
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques lack the ability to provide meaningful and flexible notifications to website visitors about similar behaviors from other users, failing to effectively encourage desired actions such as sales or social media sharing.
Innovation Solution
A method and system for generating customizable notifications using templates and events, where the server processes event data from a database, replaces template variables with user-defined or pre-defined values, and sends notification messages to browsers for rendering, allowing for dynamic and personalized messages based on user interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional notification techniques are used, then the system is simple to implement, but the notifications lack flexibility and personalization
Solution Approach 1:
The notification system is segmented into distinct components: templates define the structure and content patterns, events capture user interactions, and variables store dynamic data. This segmentation allows each component to be independently configured and reused, providing flexibility without requiring complex integrated systems.
Solution Approach 2:
Notification templates are pre-configured with message structures, variable placeholders, and styling before runtime. This preliminary action allows the system to quickly generate personalized notifications by simply substituting variables with event data, avoiding complex real-time processing while maintaining high flexibility.
2Productivity
If generic notifications are used, then the implementation is straightforward, but the notifications fail to engage users effectively
Solution Approach 1:
The notification system applies local quality by customizing specific portions of the notification message based on user context. Variables such as user name, product details, and interaction-specific information are inserted into template placeholders, ensuring that each notification is tailored to the individual user's experience while maintaining a consistent overall structure.
Solution Approach 2:
The system implements feedback by tracking user interactions as events and using this data to generate relevant notifications. User actions such as purchases, views, or social media shares are captured and fed back into the notification system, creating a continuous loop where user behavior directly influences the content and timing of subsequent notifications.
3Productivity
If real-time personalized notifications are generated, then user engagement increases, but the processing time and computational resources increase
Solution Approach 1:
Template compilation and variable validation are performed in advance during system setup or caching phases. This preliminary processing ensures that during runtime, the system only needs to perform simple variable substitution operations, dramatically reducing notification generation time while maintaining full personalization capabilities.
Solution Approach 2:
The system uses template copying where a pre-defined notification structure is replicated and then customized with specific user data. Instead of generating each notification from scratch, the system copies the appropriate template and substitutes variables, significantly reducing computational overhead while preserving personalization and real-time responsiveness.
Data Source
AI summary
In generating a customized notification on a website, a server receives a request for events from an events database from a browser. Each event includes event parameters for interaction(s) of a user with an instance of the website. The event parameters include a template reference, variable value(s), and a timestamp. The server retrieves an application identifier for the instance of the website from the request, finds events associated with the application identifier, and finds the referenced template. The template includes a message structure with template variables. For each event found, the server parses the event parameters and template variables in the referenced template and replaces the template variables with the variable values in the given event. The server sends an array of event objects to the browser, each including a message with the variable values, a link, and a timestamp.