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: Systems and methods for sharing content over a collection of social networks are disclosed. In one embodiment, a system comprises a first social network, a second social network, and at least one sharing table. The at least one sharing table is configured to share a first content from the first social network with the second social network.