Abstract: Disclosed is a new approach for client-side contextual engagement with a website visitor. A browser loads a page containing a reference to a script file implementing a visitor client. The visitor client may store visitor client data including site rules and a visitor profile locally on the client device. The visitor client may include a context monitor for calling the decision engine, a decision engine for evaluating the site rules relative to a context defined at least partially by events occurring on the page and the visitor profile, and a widget manager for managing visitor client data persisted on the client device. The content monitor may call the decision engine when the context changes. The decision engine may determine, in real time and relative to the context, that proactive or reactive engagement(s) may be appropriate and call the widget manager to launch and display corresponding engagement channel(s) on the page.

Abstract: 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.

Abstract: Disclosed is a new approach for client-side contextual engagement with a website visitor. A browser loads a page containing a reference to a script file implementing a visitor client. The visitor client may store visitor client data including site rules and a visitor profile locally on the client device. The visitor client may include a context monitor for calling the decision engine, a decision engine for evaluating the site rules relative to a context defined at least partially by events occurring on the page and the visitor profile, and a widget manager for managing visitor client data persisted on the client device. The content monitor may call the decision engine when the context changes. The decision engine may determine, in real time and relative to the context, that proactive or reactive engagement(s) may be appropriate and call the widget manager to launch and display corresponding engagement channel(s) on the page.

Abstract: Disclosed is a new approach for client-side contextual engagement with a website visitor. A browser loads a page containing a reference to a script file implementing a visitor client. The visitor client may store visitor client data including site rules and a visitor profile locally on the client device. The visitor client may include a context monitor for calling the decision engine, a decision engine for evaluating the site rules relative to a context defined at least partially by events occurring on the page and the visitor profile, and a widget manager for managing visitor client data persisted on the client device. The content monitor may call the decision engine when the context changes. The decision engine may determine, in real time and relative to the context, that proactive or reactive engagement(s) may be appropriate and call the widget manager to launch and display corresponding engagement channel(s) on the page.

Abstract: Disclosed is a new approach for client-side contextual engagement with a website visitor. A browser loads a page containing a reference to a script file implementing a visitor client. The visitor client may store visitor client data including site rules and a visitor profile locally on the client device. The visitor client may include a context monitor for calling the decision engine, a decision engine for evaluating the site rules relative to a context defined at least partially by events occurring on the page and the visitor profile, and a widget manager for managing visitor client data persisted on the client device. The content monitor may call the decision engine when the context changes. The decision engine may determine, in real time and relative to the context, that proactive or reactive engagement(s) may be appropriate and call the widget manager to launch and display corresponding engagement channel(s) on the page.

Abstract: 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.

Abstract: Disclosed is a new approach for client-side contextual engagement with a website visitor. A browser loads a page containing a reference to a script file implementing a visitor client. The visitor client may store visitor client data including site rules and a visitor profile locally on the client device. The visitor client may include a context monitor for calling the decision engine, a decision engine for evaluating the site rules relative to a context defined at least partially by events occurring on the page and the visitor profile, and a widget manager for managing visitor client data persisted on the client device. The content monitor may call the decision engine when the context changes. The decision engine may determine, in real time and relative to the context, that proactive or reactive engagement(s) may be appropriate and call the widget manager to launch and display corresponding engagement channel(s) on the page.

Abstract: 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.

Abstract: 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.

Abstract: Disclosed is a new approach for client-side contextual engagement with a website visitor. A browser loads a page containing a reference to a script file implementing a visitor client. The visitor client may store visitor client data including site rules and a visitor profile locally on the client device. The visitor client may include a context monitor for calling the decision engine, a decision engine for evaluating the site rules relative to a context defined at least partially by events occurring on the page and the visitor profile, and a widget manager for managing visitor client data persisted on the client device. The content monitor may call the decision engine when the context changes. The decision engine may determine, in real time and relative to the context, that proactive or reactive engagement(s) may be appropriate and call the widget manager to launch and display corresponding engagement channel(s) on the page.

Abstract: A system for providing play in a game includes one or more processors and memory configured to represent two or more users as a single player in an online game. The processor(s) and memory are configured to receive input, via one or more networks, from each of the users, the input relating to how the single player is to play the game; and based on the inputs from the users, determine an action by the single player in the game. The system can make collective play possible in a game that is structured by the game provider for play by individuals.

Abstract: A system for monitoring one or more transactions includes a memory, which stores first metadata, second metadata, and third metadata, communicatively coupled to one or more processors. The one or more processors receive the first metadata from a first transaction processing system, the second metadata from a second transaction processing system, and the third metadata from a third transaction processing system and determine attributes from each of the first, second, and third metadata. Each of the first, second, and third metadata are associated with a task performed by the first, second, and third transaction processing systems, respectively. The one or more processors associate the first metadata with a first transaction. The one or more processors then determine that none of the attributes from the second metadata are the same as any of the attributes from the first metadata and then associate the second metadata with a second transaction.

Abstract: A system for providing play in a game includes one or more processors and memory configured to represent two or more users as a single player in an online game. The processor(s) and memory are configured to receive input, via one or more networks, from each of the users, the input relating to how the single player is to play the game; and based on the inputs from the users, determine an action by the single player in the game. The system can make collective play possible in a game that is structured by the game provider for play by individuals.

Abstract: A system for providing game play. The system includes processors and memory configured to include users as players at a table in an online game and provide cards to the players for playing a first hand of the game. When a jump point is reached in the first hand, the following are provided to at least the players no longer playing the first hand: cards for playing a second hand at the table, and continued online access to play of the first hand. Strategic aspects of face-to-face poker play are retained while action-seeking players can see more hands per hour.

Abstract: A system for providing game play. The system includes processors and memory configured to include users as players at a table in an online game and provide cards to the players for playing a first hand of the game. When a jump point is reached in the first hand, the following are provided to at least the players no longer playing the first hand: cards for playing a second hand at the table, and continued online access to play of the first hand. Strategic aspects of face-to-face poker play are retained while action-seeking players can see more hands per hour.

Abstract: Methods and systems are described for enhancing applications, such as browser applications, to include contextual collaboration functionality within the application's user interface by providing a collaboration interface. The collaboration interface provides access to a group of collaboration data sets associated with a URL of the page displayed through the application according to user defined organization.

Abstract: Methods and systems are described for enhancing applications, such as enterprise applications, to include contextual collaboration functionality by providing a collaboration space which can be embedded or otherwise made visibly available from within the application's user interface. The collaboration space allows collaboration content from collaboration activities that are outside the application to be contextually viewed seamlessly within the application. For example, a user of an enterprise application accessing an account, an opportunity or other object of an enterprise system, can view the collaboration space associated with the accessed object through the enterprise application itself.

Abstract: A method for saving visual data that was captured from a data source is disclosed. Visual data is received via a network from a computing device coupled to the network. The visual data includes image data and non-image data. An item of content is generated based on the selected visual data from the data source for storage in a database coupled to the network.

Abstract: An anti-fraud token system is disclosed in which the authentication process is performed primarily on the client side. A client according is provided with an authentication list of websites for which authentication is required, and their respective authentic addresses. The client also asks a user to select a token, which may include graphics, text, and/or sound. When the user accesses an information source from the authentication list, the client notes that the address which the user is accessing is on the list. The client then displays the token as previously selected by the user to the user along with the accessed information, so that the user knows that the information he/she is accessing is authentic.

Abstract: A phishing detection agent is provided. In one embodiment, a user's browser includes a plug-in application or agent that may capture a visual record of a webpage and, with a cached copy of known, authentic websites provided to it via periodic updates, perform a series of image comparison functions to determine if the suspected website is attempting to deceive the user. The phishing detection agent is capable of performing an image recognition algorithm, such as logo recognition algorithm, optical character recognition, an image similarity algorithm, or combination of two or more of the above. If the suspected webpage corresponds to one of the authentic web pages, but the domain name of the suspected web page does not match the domain name of one of the authentic web pages, the suspected web page is flagged as a phishing web site.