Client-Side Element Mapping for Contextual Engagement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing customer engagement systems require technical expertise to build and manage engagement rules, making them complex, error-prone, and non-user-friendly, as they rely on server-side implementations and require understanding of HTML and CSS selectors, which limits their effectiveness in providing contextual interactions with web site visitors.
Innovation Solution
A client-side decision engine and element mapping tool that allows non-technical users to map page elements and create site rules through a user-friendly interface, eliminating the need for CSS selector knowledge by generating user-friendly names for page elements, which can be used to define contextual engagements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If server-side engagement rules are used with HTML and CSS selector knowledge, then contextual visitor engagement can be achieved, but the system becomes complex and requires technical expertise
Solution Approach 1:
The patent introduces an intermediary layer between the user and the complex server-side engagement rules. This intermediary provides a visual interface that translates simple user actions into sophisticated engagement rules, eliminating the need for users to understand HTML and CSS selectors while maintaining the ability to create contextual visitor engagement.
Solution Approach 2:
The system enables non-technical users to independently create and manage engagement rules through an intuitive visual interface. Users can directly interact with page elements and define engagement conditions without requiring technical expertise, making the system self-service capable for rule creation and modification.
2Measurement precision
If CSS selectors and HTML knowledge are required for rule building, then precise element targeting is possible, but ease of operation deteriorates
Solution Approach 1:
The patent creates a visual copy or representation of the webpage elements that users can interact with directly. Instead of requiring users to work with abstract CSS selectors, the system presents a visual copy of the page structure where users can select elements through clicking or hovering, maintaining precision while dramatically improving ease of operation.
Solution Approach 2:
The patent replaces the mechanical system of typing and understanding CSS selector syntax with a graphical interaction system. Users interact with visual representations of page elements through clicking, hovering, or dragging operations, substituting the complex textual manipulation mechanism with simpler graphical operations that achieve the same targeting precision.
3Manufacturing precision
If technical expertise is required for authoring engagement rules, then rule accuracy can be maintained, but productivity decreases
Solution Approach 1:
The patent performs preliminary actions by automatically analyzing page structure, generating element hierarchies, and preparing engagement rule templates before the user needs to create rules. This preliminary processing maintains rule accuracy by ensuring proper element identification while increasing productivity by eliminating manual analysis and setup steps.
Solution Approach 2:
The system enables users to independently create accurate engagement rules without requiring technical expertise or time-consuming learning. The visual interface with automatic element recognition and template-based rule generation allows users to quickly create precise rules, simultaneously improving both accuracy and productivity.
Data Source
AI summary
A new element mapper is provided for mapping elements of a page using user-provided or automatically generated terms or names. Specifically, a user may direct an application displaying a page to enter into an in-context element mapping mode, in which page elements eligible for mapping may be identified and highlighted whenever one is moused or hovered over. Responsive to the user selecting a page element of interest, the element mapper may provide a dialog with an input field. The dialog may be displayed near the page element of interest or as part of the page. Based on a user-provided or automatically generated name, the element mapper may generate a mapping output and store it in association with a selector for the page element of interest. The mapping output can be used to build a site rule in context of the page element of interest.