Patent Description:
Oftentimes, user feedback from a user is provided in a wrong location or the feedback is not supported by a review platform. For example, the user may provide feedback for an item or a merchant in a location that is configured for providing feedback for operations of a website. Additionally, the user may need to access different forms to provide different feedback types such as an item review form, a website operations form, a sale-not-as-described claim form, and so forth.

<CIT> discloses a method of enhancing search results posted on a social network including providing input elements such as a "like" or "dislike" button for search results and a comment box to enable a social network user to add comments.

The present invention provides a method and system as defined in the appended claims.

Various ones of the appended drawings merely illustrate example embodiments of the present invention and cannot be considered as limiting its scope.

The description that follows includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments of the present inventive subject matter. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide an understanding of various embodiments of the inventive subject matter. It will be evident, however, to those skilled in the art, that embodiments of the inventive subject matter may be practiced without some or other of these specific details. In general, well-known instruction instances, protocols, structures, and techniques have not been shown in detail. Examples merely typify possible variations. Unless explicitly stated otherwise, structures (e.g., structural components, such as modules) are optional and may be combined or subdivided, and operations (e.g., in a procedure, algorithm, or other function) may vary in sequence or be combined or subdivided.

Typically, a user may have a bad experience while interacting with a website and wants to provide feedback either with the website or on a review website. However, the bad experience can be related to many different issues such as bad service or user experience, item different from item description, user interface or technical issues, a merchant issue, quality of an item, warranty issues, or any combination of these or other issues. In some cases, the user is unsure where to provide the feedback or provides it in a wrong location. In other cases, the feedback is about something not supported by a platform of the system. Further still, the feedback may be provided correctly (e.g., in a correct location) but is not detailed enough. In some cases, a reviewer may not have the necessary tools to provide proper feedback. For instance, the reviewer is provided a textbox to provide comments, but the reviewer wants to reorganize components on the webpage, indicate components that are difficult to read, indicate visual changes to a component, and so forth. As a result, these feedbacks are not actionable by the system.

Example embodiments provide systems and methods that generate feedback from visual interactions on a webpage and distributes the feedback, sometimes with appropriate tags, to a proper entity. Accordingly, the system configures a webpage to receive user inputs in the form of visual interactions with components displayed on the webpage. For example, a user can select a component (e.g., image, text) on the webpage and make edits directly to the component or provide comments about the selected component. Additionally, a component can also be dragged and dropped to a different location on the webpage. The user inputs are received by the system and processed. Processing can include determining, based on (an identification of) the webpage and a location (e.g., coordinates) of the user input, a feedback type for each user input. For example, the feedback type may include site feedback, seller feedback, and item feedback. The user inputs can be organized based on the feedback type. A feedback preview that displays each of the user inputs can be organized based on feedback type and presented to the user. The user can then approve some or all of the feedback on the feedback preview, which causes the approved feedback to be transmitted to a corresponding entity associated with the feedback type.

Accordingly, the present disclosure provides, in one embodiment, a technical solution to the technical problem of generating and transmitting feedback to a proper entity that can act on the feedback. The generated feedback can be obtained in a single location (e.g., on the webpage) that provides a user-friendly context. This removes the need for a reviewer to navigate a website to find a proper form or location to submit feedback for different types of issues or context. As a result, resources used by one or more machines, databases, or devices (e.g., within an environment) may be reduced for such search systems. Examples of such computing resources include processor cycles, network traffic, memory usage, data storage capacity, power consumption, network bandwidth, and cooling capacity.

With reference to <FIG>, an example embodiment of a network environment <NUM> that provides a system for generating and providing user feedback based on visual interactions performed on a webpage is shown. A network system <NUM> provides server-side functionality via a communication network <NUM> (e.g., the Internet, wireless network, cellular network, or a Wide Area Network (WAN)) to a client device <NUM> and a third-party device <NUM>.

In example embodiments, the client device <NUM> is a device of a user that desires to provide a review or feedback (also referred to herein as the "reviewer") for a webpage that is associated with the network system <NUM> (e.g., managed or hosted by the network system <NUM>). The third-party device <NUM> may be a device associated with an entity that receives feedback provided by the reviewer. For example, the third-party device <NUM> may be associated with a seller, a store, or other entity that publishes information on the website that can be reviewed by the reviewer.

The client device <NUM> and the third-party device <NUM> interface with the network system <NUM> via a connection with the network <NUM>. Depending on the form of the client device <NUM> and the third-party device <NUM>, any of a variety of types of connections and networks <NUM> may be used. For example, the connection may be Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or another type of cellular connection. Such a connection may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1xRTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, or other data transfer technology (e.g., fourth or fifth generation wireless, <NUM> or <NUM> networks). When such technology is employed, the network <NUM> may include a cellular network that has a plurality of cell sites of overlapping geographic coverage, interconnected by cellular telephone exchanges. These cellular telephone exchanges may be coupled to a network backbone (e.g., the public switched telephone network (PSTN), a packet-switched data network, or other types of networks).

In another example, the connection to the network <NUM> may be a Wireless Fidelity (Wi-Fi, IEEE <NUM>. 11x type) connection, a Worldwide Interoperability for Microwave Access (WiMAX) connection, or another type of wireless data connection. In such an embodiment, the network <NUM> may include one or more wireless access points coupled to a local area network (LAN), a wide area network (WAN), the Internet, or another packet-switched data network. In yet another example, the connection to the network <NUM> may be a wired connection (e.g., an Ethernet link), and the network <NUM> may be a LAN, a WAN, the Internet, or another packet-switched data network. Accordingly, a variety of different configurations are expressly contemplated.

In various embodiments, the data exchanged within the network environment <NUM> may be dependent upon user-selected functions available through one or more client or user interfaces (UIs). The UIs are associated with the client device <NUM> and the third-party device <NUM> executing a web client (e.g., an Internet browser), which may be in communication with the network system <NUM>. The UIs may also be associated with one or more applications (e.g., an application provided by or through the network system <NUM>).

The client device <NUM> and the third-party device <NUM> may comprise, but is not limited to, a smartphone, tablet, laptop, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, a server, or any other communication device that a user may utilize to access the network system <NUM>. In some embodiments, the client device <NUM> and the third-party device <NUM> comprise a display module (not shown) to display information (e.g., in the form of user interfaces). In further embodiments, the client device <NUM> and the third-party device <NUM> comprise one or more of a touch screen, accelerometer, camera, microphone, and Global Positioning System (GPS) device.

The client device <NUM> and the third-party device <NUM> may include one or more applications (also referred to as "apps") such as, but not limited to, a web browser, messaging application, electronic mail (email) application, a network system application (associated with the network system <NUM>), third-party applications, and the like. In some embodiments, if a site application (e.g., the network system application) is included in the client device <NUM> and the third-party device <NUM>, then this application is configured to locally provide the user interface and at least some of the functionalities with the application configured to communicate with the network system <NUM>, on an as needed basis, for data or processing capabilities not locally available (e.g., to publish publications, access a database of published publications, to authenticate a user, to provide communications with other users of the network system <NUM>). Conversely if the site application is not included in the client device <NUM> and the third-party device <NUM>, the client device <NUM> and the third-party device <NUM> may use its web browser to access a website (or a variant thereof) hosted on the network system <NUM>.

Turning specifically to the network system <NUM>, an application program interface (API) server <NUM> and a web server <NUM> are coupled to, and provide programmatic and web interfaces respectively to, one or more application servers <NUM>. The application servers <NUM> host a publication system <NUM> and a feedback system <NUM>, each of which may comprise one or more modules, applications, or engines, and which can be embodied as hardware, software, firmware, or any combination thereof. The application servers <NUM> are, in turn, coupled to one or more database servers <NUM> that facilitate access to one or more information storage repositories or data storage <NUM>. In one embodiment, the data storage <NUM> is a device that stores content (e.g., publications or listings, user profiles including past feedback provided by the user) that is used by the network system <NUM>.

In example embodiments, the publication system <NUM> publishes content on a network (e.g., Internet) in the form of webpages. As such, the publication system <NUM> provides a number of publication functions and services to users (e.g., a user of the third-party device <NUM>) that publish content via the network system <NUM>. For example, the publication system <NUM> can host a marketplace application that provides a number of functions and services to users, such as publishing listing whereby a user (e.g., a seller) may list (or publish information concerning) goods or services (also referred to as "items") for sale, a potential user or buyer can express interest in or indicate a desire to purchase such goods or services, and a transaction pertaining to the goods or services is processed. However, it is noted that the publication system <NUM> may, in alternative embodiments, be associated with a non-marketplace environment such as an informational environment (e.g., search engine) or social networking environment that publishes articles, reviews, or other types of information.

The feedback system <NUM> comprises one or more components (e.g., servers) that manage generation and provisioning of user feedback based on visual interactions performed by reviewers on webpages. The feedback system <NUM> will be discussed in more detail in connection with <FIG> below.

While the publication system <NUM> and the feedback system <NUM> are shown in <FIG> to form part of the network system <NUM>, it will be appreciated that, in alternative embodiments, the publication system <NUM> or the feedback system <NUM> may form part of a separate service that is distinct from the network system <NUM>. Further still, one or more components of the feedback system <NUM> may, alternatively, be located within the publication system <NUM> or vice-versa. Furthermore, while the client-server-based network environment <NUM> shown in <FIG> employs a client-server architecture, the present inventive subject matter is of course not limited to such an architecture and could equally well find application in a distributed or peer-to-peer architecture system, for example. The publication system <NUM> and feedback system <NUM> can also be implemented as standalone software programs, which do not necessarily have networking capabilities.

In example embodiments, any of the systems, servers, or devices (collectively referred to as "components") shown in, or associated with, <FIG> may be, include, or otherwise be implemented in a special-purpose (e.g., specialized or otherwise non-generic) computer that has been modified (e.g., configured or programmed by software, such as one or more software modules of an application, operating system, firmware, middleware, or other program) to perform one or more of the functions described herein for that system or machine. For example, a special-purpose computer system able to implement any one or more of the methodologies described herein is discussed below with respect to <FIG>, and such a special-purpose computer may accordingly be a means for performing any one or more of the methodologies discussed herein. Within the technical field of such special-purpose computers, a special-purpose computer that has been modified by the structures discussed herein to perform the functions discussed herein is technically improved compared to other special-purpose computers that lack the structures discussed herein or are otherwise unable to perform the functions discussed herein. Accordingly, a special-purpose machine configured according to the systems and methods discussed herein provides an improvement to the technology of similar special-purpose machines.

Moreover, any two or more of the systems, servers, or devices illustrated in <FIG> may be combined into a single system, server, or device, and the functions described herein for any single system, server, or device may be subdivided among multiple systems or devices. Additionally, any number of network systems <NUM>, networks <NUM>, client devices <NUM>, and third-party devices <NUM> may be embodied within the network environment <NUM>. Furthermore, some components or functions of the network environment <NUM> may be combined or located elsewhere in the network environment <NUM>.

<FIG> is a block diagram illustrating components of the feedback system <NUM>, according to some example embodiments. In example embodiments, the feedback system <NUM> comprises one or more servers that include components that manage generation of feedback based on visual interactions performed by reviewers on webpages. To enable these operations, the feedback system <NUM> comprises a user interface (UI) module <NUM>, a processing engine <NUM>, and a transmission module <NUM>.

The UI module <NUM> manages the user interactions received on the webpages that are presented via the publication system <NUM>. In various embodiments, the UI module <NUM> receives an indication of a selection of an edit trigger that is shown on a webpage on which a reviewer wants to provide feedback. In response to receiving the indication, the UI module <NUM> configures the webpage to receive the feedback from the reviewer. Configuring the webpage to receive the feedback can include, for example, enabling the UI presenting the webpage to receive and display visual interactions or inputs applied directly to the webpage. For instance, the reviewer can move (e.g., drag and drop) a component (e.g., an image, text) from one location on the webpage to another. In other unclaimed example, the reviewer can free-hand draw on an image of an item and provide a comment (e.g., in a comment box located proximate to the free-hand drawing) regarding the free-hand drawing. Further still, in an unclaimed example the user can highlight text displayed on the webpage and provide a comment (e.g., in a comment box located proximate to the highlighted text) directed to the highlighted text or otherwise edit text originally displayed on the webpage. Alternatively, in an unclaimed example, the user input may simply be highlight text displayed on the webpage.

In example, embodiments, the UI module <NUM> determines and associates various data with each user input provided on the webpage. When a user provides a user input (e.g., user input is received by the UI module <NUM>), the UI module <NUM> determines an identifier of the webpage and coordinates of a location of the user input within the webpage. The identifier and coordinates are associated with or linked to an edit (i.e., the user input) that indicates the feedback. The user input along with the identifier and coordinates are provided to the processing engine <NUM> for processing as discussed in more detail below.

The processing engine <NUM> is configured to analyze each user input, determine feedback types and feedback suggestions, and generate tags and feedback previews. To enable these operations, the processing engine <NUM> includes an analysis module <NUM>, a filter module <NUM>, an imaging module <NUM>, a suggestion module <NUM>, a tag generator <NUM>, and a preview module <NUM>.

The analysis module <NUM> analyzes each user input to understand the feedback and feedback type. The analysis can occur in real-time as the user is providing their inputs or immediately after the user completes entering a user input. In example embodiments, the analysis module <NUM> can determine, for example, if a user input is site feedback (e.g., to be directed to an administrator of the website), user feedback related to a publication or a transaction (e.g., to be directed to a seller or publisher of content on the website), item feedback, payment feedback (e.g., to be directed to a payment entity), or other type of feedback that will be directed to a corresponding entity that can act on the feedback. The analysis module <NUM> makes the determination based on where the user input is located on the webpage (e.g., based on the coordinates). In example embodiments, the analysis module <NUM> accesses a database that stores information for webpages including a corresponding identifier and components shown on each webpage along with coordinates of the components (e.g., images, text). Based on the component that corresponds to the location of the user input, the analysis module <NUM> can identify the feedback type. In one example, the database will indicate the corresponding feedback type for the component.

The analysis module <NUM> also determines the actual feedback that should be provided to the various entities based on analysis of the content of the user input. For example, in an unclaimed example, the analysis module <NUM> uses various natural language processing (NLP) algorithms to understand the user input and form the feedback. For example, in an unclaimed example, a reviewer may indicate an appropriate price by simply replacing a previous price with a suggested price. The analysis module <NUM> determines the actual feedback that will be provided to the reviewee, which may be, for example, "User thinks a better price is $<NUM>. " In another unclaimed example, a user can provide a comment in a different language and the analysis module <NUM> understands the language and generates the feedback. For instance, if the user provides in French, "Cette couleur est géniale," the analysis module <NUM> understands this means "this color is awesome" and generates that feedback.

Even a user input that appears irrelevant can have meaning associated with it. For example, in an unclaimed example, if the user input is "I am tired of the Covid-<NUM> lockdown" and the user did not make a purchase, it is possible that the purchase did not occur because of job issues. As a result, the analysis module <NUM> may generate feedback that indicates "User is tired of covid-<NUM> lockdown, might want to adjust listing to help" to a seller who may want to reduce the price of the item.

In an unclaimed example, the feedback is not limited to text generation. If feedback requires discreet values, like ratings in the form of "positive," "neutral," or "negative," those values can also be auto-generated by processing the user input by the analysis module <NUM>.

The filtering module <NUM> is configured to filter user input that is irrelevant. In unclaimed examples, the filtering module <NUM> applies machine learning (e.g., runs the user input through a machine learning engine) to filter out user inputs that do not make sense. For example, the user provides an input "Hello" instead of "Shipping and packaging were great" in a section for shipping or inputs " " (empty). These user inputs are irrelevant for generating the feedback resulting in the filtering module <NUM> filtering out these user inputs.

Further still, the filtering module <NUM>, in some embodiments, detects that two or more user inputs on a webpage are correlated. In these cases, the filtering module <NUM> can combine the correlated user input to provide improved feedback. For instance, in an unclaimed example, the user may provide "very sleek" for a highlighted image as well as in an item description section, thus providing the same user input twice. The filtering module <NUM> detects the correlation between these two user inputs and can generate "better" input by removing unnecessary text or consolidating the feedback. In another unclaimed example, if a shape of an item in an image is described as "this is not heavy" and elsewhere the user inputs "this is sleek and lightweight," the filtering module <NUM> may filter "not heavy" since it is the same as "lightweight. " In some cases, the filtering module <NUM> works with the analysis module <NUM> (e.g., for natural language processing) in performing the filtering. Alternatively, the correlation and improved feedback may be performed by the analysis module <NUM>.

The imaging module <NUM> is configured to analyze user inputs that involve an image. For example, in an unclaimed example, a reviewer may draw a circle around an item depicted in an image and provide a comment. In another unclaimed example, the reviewer may make a correction or adjustment to the item depicted in the image (e.g., using photoshop-like tools). In these cases, the imaging module <NUM> performs an image lookup based on the free-hand drawings to identify a similar item to the item in the image or to otherwise identify the item. Information associated with the (similar) item (e.g., image, details) may be retrieved or accessed and included in generating the feedback. In various embodiments, the imaging module <NUM> works with the analysis module <NUM> or is a part of the analysis module <NUM>.

The suggestion module <NUM> is configured to provide feedback suggestion(s) to the reviewer. In some embodiments, the suggestion module <NUM> works with the analysis module <NUM> to provide the suggestion(s). The suggestion(s) can be provided in real-time as the reviewer is providing their input. For example, in an unclaimed example, the reviewer selects an image or text on the webpage and starts to enter comments. While the reviewer enters the comments or shortly thereafter, the analysis module <NUM> detects the location of the user input. The suggestion module <NUM> then determines or generates suggestions that are presented to the reviewer. The suggestions may be determined on-the-fly by the suggestion module <NUM> based on data known or accessible by the suggestion module <NUM>. For example, the suggestions can be based on transaction data (e.g., known or accessed from a user profile of the reviewer). Further still, the suggestion module <NUM> may access suggestions from data sources. For example, one data source may be based on machine learning of how other reviewers have reacted to the same location on the webpage (e.g., other feedback provided from other reviewers for the same location). The suggestion module <NUM> can also suggest pre-defined phrases or even tags (e.g., from a data source) to help the reviewer provide feedback. The reviewer can select one or more suggestions to include in their feedback.

The tag generator <NUM> is configured to generate tags from the user feedback that indicate a descriptive aspect from the feedback. The tags can be used, for example, to highlight reviews in subsequent webpages. For example, in an unclaimed example, the tag generator <NUM> can take feedback such as "Color was awesome" or "Shipping and packaging were great" and create the tags. In various embodiments, the tags can be detailed and be any length.

The preview module <NUM> generates a feedback preview that is presented to the user for review. The feedback preview organizes the user inputs by feedback types. In order to generate the feedback preview, the preview module <NUM> accesses the user inputs and feedback types determined by the analysis module <NUM> and generates a display component that summarizes the user inputs (subject to any that are filtered out by the filter module <NUM>). The display component can be a pop-up interface or panel that is shown overlaid over the webpage or be a panel displayed on a side of the UI presenting the webpage. In one embodiment, the feedback preview can be presented on a side of the UI as the reviewer is providing their inputs (i.e., in real-time or substantially real-time). In this embodiment, the reviewer can see the analyzed feedback (from the analysis module <NUM>) and adjust/change it. In an alternative embodiment, the feedback preview can be presented to the reviewer when the reviewer has completed entering their inputs. Further still, the feedback preview can be displayed whenever the reviewer activates a preview icon or trigger.

In example embodiments, the reviewer reviews the feedback preview and can approve one or more (or all) feedback shown on the feedback preview. In one embodiment, the feedback preview may include a submit or approve icon for submitting all of the feedbacks. Alternatively, or in addition, the feedback preview can have a submit/approval icon associated with each feedback type or with each individual user input. Here, the reviewer can selectively submit their feedback. For example, the submit/approval icon can be a button labelled "create feedbacks," "create site feedback," "create feedback for seller," "generate all feedback and submit," and so forth. The reviewer can also edit their inputs.

In response to receiving an indication of a selection of one or more submit/approval icons, the transmission module <NUM> transmits feedback(s) corresponding to the selected submit/approval icon to a corresponding entity. For example, the feedback preview can present site feedback, user feedback, item feedback, payment feedback, and so forth. As such, approved site feedback can be transmitted to an administrator of the website, while approved user feedback related to a publication or an item is transmitted to a seller or publisher of content on the website, and approved payment feedback is transmitted to a payment service.

While the feedback system <NUM> is illustrated as having certain components in <FIG>, the feedback system <NUM> may also comprise other components (not shown) that are not pertinent to example embodiments. Furthermore, any one or more of the components (e.g., engines, modules, generators) described herein may be implemented using hardware (e.g., a processor of a machine) or a combination of hardware and software. Moreover, any two or more of these components may be combined into a single component, and the functions described herein for a single component may be subdivided among multiple components.

<FIG> is a screenshot of a webpage <NUM>, according to one example. The webpage <NUM> is displayed on a user interface (UI) and comprises content published by a publisher (e.g., content provider, seller, store). A user or potential reviewer can view the webpage <NUM> and decide to provide feedback. The user can trigger an edit mode by making a selection of an edit trigger that is displayed on the UI or otherwise associated with the UI. For example, right clicking on the UI may present a selectable trigger icon or option. Upon the user selecting the edit trigger, the feedback system <NUM> (e.g., the user interface module <NUM>) configures the webpage <NUM> to receive user inputs.

<FIG> is an example screenshot of the webpage <NUM> illustrating various user inputs provided via visual interactions with the webpage <NUM>, according to one example. In an unclaimed example, the visual interactions include a free-hand drawing <NUM> (shown in a dashed line) around an image (e.g., of a side of a phone) and a comment in a comment box <NUM> indicating that the reviewer thought the phone is sleek. In other unclaimed examples, the user can also edit a photo or image of an item. A "+" icon show adjacent to the comment box <NUM> can be selected to indicate that the reviewer is done inputting their comment (e.g., to submit the comment).

in an unclaimed example a second and third visual interaction includes a user change to text in the original website <NUM>. The reviewer can highlight a portion of the text that the reviewer wants to change and makes the changes directly to the text. Here, the reviewer highlighted text in a title and indicated that the title should be changed to reflect "all carriers" (i.e., user input <NUM>). The reviewer also highlighted and change a price (i.e., user input <NUM>) to indicate that $<NUM> is a more appropriate price for this item.

In unclaimed examples, further visual interactions include feedback on different aspects of related services associated with the item being sold on the website. The reviewer can highlight the component or element that the reviewer wants to provide the feedback on and provide a comment in a corresponding comment box. For example, the reviewer highlights a service plan component <NUM> and indicated that customer service is good in a corresponding comment box <NUM>. In another example, the reviewer highlights a free standard shipping component <NUM> and indicated that shipping was great in a corresponding comment box <NUM>. The reviewer also highlighted an estimated delivery component <NUM> and indicated that the item arrived early in a corresponding comment box <NUM>. Finally, the reviewer highlighted a money back guarantee component <NUM> and indicated that having the money back guarantee helped them decide to purchase the item in comment box <NUM>.

It should be noted that a "+" icon can be shown adjacent to any user input in order for the reviewer to indicate that the reviewer is done providing their input for that component or element on the webpage <NUM>. Additionally, any number of user inputs may be provided on the webpage <NUM>.

The reviewer can proceed to a next page or section of the webpage <NUM> to continue providing feedback. <FIG> is an example screenshot of a next section <NUM> of the webpage <NUM> illustrating further user inputs provided via visual interactions, according to one unclaimed example. In a related items portion of the next section <NUM>, the reviewer highlights an item that the reviewer has previously purchased (i.e., component <NUM>) and provides user input indicating that he purchased the item previously, that he does not like the recommended items, and that phone cases should be shown instead (i.e., user input <NUM>). This feedback is valuable feedback for the publication system <NUM> which uses machine learning on top of such feedback to recommend items to users.

In an unclaimed example, the reviewer can also indicate text that should be used to generate feedback simply by highlighting the text and submitting it. For example, the reviewer has highlighted "good working condition" and can select the "+" icon to generate feedback from the highlight text (i.e., user input <NUM>). Finally, the reviewer has highlighted "silver" text <NUM> and indicated that the color is awesome in comment box <NUM>.

Though not illustrated, in an embodiment, the reviewer can also select a component and move it to a different location on the webpage. For example, the reviewer can select a "my orders" component <NUM> and move it before a "watchlist" component <NUM>.

<FIG> is an example screenshot of the webpage <NUM> illustrating a feedback preview <NUM>, according to one unclaimed example. The feedback preview <NUM> organizes the various user inputs by feedback type. In the example of <FIG>, the feedback types include feedback for seller on listing, feedback for seller on transaction, feedback for site, feedback for item, and feedback for a warranty provider. In some cases, the user input is formatted into natural language. For example, the reviewer indicated an appropriate price in <FIG> by simply replacing the previous price with a suggested price. The analysis module <NUM> determines the actual feedback, which is that "User thinks better price to be set is $<NUM>.

In an example, a single approval/submit icon <NUM> is presented at a bottom of the feedback preview <NUM>. Selection of the approval/submit icon <NUM> automatically submits all the given feedback which causes the transmission module <NUM> to forward the feedback to the appropriate corresponding entity (e.g., the seller, the site, the warranty provider). In an alternative embodiment, an approval/submission icon can be associated with each feedback type or each user input. This allows the reviewer to submit feedback for less than all feedback types.

While not shown, the feedback preview <NUM>, in alternative embodiments, may also be enabled to allow the reviewer to edit the feedback. For example, in an unclaimed example, the reviewer can change "silver" to "black" under the "feedback for item" feedback type. In another example, the reviewer can delete a portion of the feedback prior to submission.

<FIG> is a flowchart of a method for generating and providing user feedback based on visual interactions performed on a webpage, according to some example embodiments. Operations in the method <NUM> may be performed by the network system <NUM> using components described above with respect to <FIG>. Accordingly, the method <NUM> is described by way of example with reference to the network system <NUM>. However, it shall be appreciated that at least some of the operations of the method <NUM> may be deployed on various other hardware configurations or be performed by similar components residing elsewhere in the network environment <NUM>. Therefore, the method <NUM> is not intended to be limited to the network system <NUM>.

In operation <NUM>, a webpage is presented to a user (e.g., a potential reviewer). In some embodiments, the publication system <NUM> publishes content on a network in the form of webpages.

In operation <NUM>, the UI module <NUM> receives an indication of a selection of an edit trigger that is shown on a webpage on which the reviewer wants to provide feedback. In one embodiment, the reviewer right clicks and selects an option to provide feedback. In an alternative embodiment, an edit icon is displayed on a portion of the webpage.

In response to receiving the indication, the UI module <NUM> configures the webpage to receive the feedback from the reviewer in operation <NUM>. Configuring the webpage to receive the feedback can include, for example, enabling the UI presenting the webpage to receive and display visual interactions or inputs applied directly to the webpage. Additionally, image editing tools may be provided or accessible to the reviewer.

In operation <NUM>, the UI module <NUM> receives one or more user inputs. For instance, in an embodiment the reviewer can move (e.g., drag and drop) a component (e.g., an image, text) from one location on the webpage to another to indicate a viewing or ranking preference. In other unclaimed example, the reviewer can free-hand draw on the webpage (e.g., on an image of an item) and can provide a comment in a comment box located proximate to the free-hand drawing regarding the free-hand drawing. Further still, in an unclaimed example, the user can highlight text displayed on the webpage and provide a comment (e.g., in a comment box located proximate to the highlighted text) directed to the highlighted text or otherwise directly edit text originally displayed on the webpage.

In example embodiments, the UI module <NUM> determines and associates various data with each user input provided on the webpage. More specifically, the UI module <NUM> determines an identifier of the webpage and coordinates of a location of each of the user inputs within the webpage. The identifier and coordinates are associated with or linked to an edit (i.e., the user input) that indicates the feedback.

In operation <NUM>, the processing engine <NUM> processes the one or more user inputs. Operation <NUM> will be discussed in more detail in connection with <FIG> below.

In operation <NUM>, the results of the processing are presented in a feedback preview by the preview module <NUM>. In one embodiment, the feedback preview can be presented on a side of the UI as the reviewer is providing their inputs (i.e., in real-time or substantially real-time). In an alternative embodiment, the feedback preview can be presented to the reviewer when the reviewer has completed entering their inputs (e.g., after each completed user input or after all user inputs completed). Further still, the feedback preview can be displayed whenever the reviewer selects a preview icon or trigger displayed on the UI.

In operation <NUM>, approval of one or more feedback (e.g., analyzed user inputs) in the feedback preview is received by the feedback system <NUM> (e.g., the preview module <NUM> or transmission module <NUM>). In example embodiments, the reviewer reviews the feedback preview and can approve one or more (or all) feedbacks shown on the feedback preview. In one embodiment, the feedback preview may include a submit/approve icon for submitting all of the feedbacks. Alternatively, or in addition, the feedback preview can have a submit/approval icon associated with each feedback type or with each feedback (e.g., analyzed user input).

In operation <NUM>, the transmission module <NUM> transmits approved feedback to a corresponding entity. For example, approved site feedback can be transmitted to an administrator or host of the website, while approved user feedback related to a publication or an item is transmitted to a seller or publisher of content on the website.

The method <NUM> is exemplary and alternative embodiments may make some of the operations optional or remove some of the operations of the method <NUM>. For instance, the presenting of the preview (operation <NUM>) and receiving approval (operation <NUM>) may be optional or removed from the method <NUM>. In these embodiments, the processing engine <NUM> processes the one or more user inputs (operation <NUM>) and the transmission module <NUM> transmits the feedback to the corresponding entity (operation <NUM>) without user approval being required. Further still, in another alternative embodiment, the feedback may be provided to the corresponding entity as the user is providing the user input or as soon as each user input is received.

<FIG> is a flowchart of a method <NUM> for processing user inputs (e.g., operation <NUM>), according to some example embodiments. Operations in the method <NUM> may be performed by the feedback system <NUM> using components described above with respect to <FIG>. Accordingly, the method <NUM> is described by way of example with reference to the feedback system <NUM>. However, it shall be appreciated that at least some of the operations of the method <NUM> may be deployed on various other hardware configurations or be performed by similar components residing elsewhere in the network environment <NUM>. Therefore, the method <NUM> is not intended to be limited to the feedback system <NUM>.

In operation <NUM>, the analysis module <NUM> determines a feedback type for each user input. For example, the analysis module <NUM> can determine if a user input is site feedback (e.g., to be directed to an administrator of the website), user feedback related to a publication or a transaction (e.g., to be directed to a seller or publisher of content on the website), item feedback (e.g., to be directed to a seller or publisher of content on the website), payment feedback (e.g., to be directed to a payment system), warranty feedback (e.g., to be directed to a warranty provider), location feedback, service feedback, or other forms of feedback depending on the webpage and type of business being reviewed by the reviewer. The analysis module <NUM> makes the determination based on where the user input is located on the webpage (e.g., based on the coordinates). In example embodiments, the analysis module <NUM> accesses a database that includes information for webpages including a corresponding identifier (to identify the specific webpage) and components shown on each webpage along with coordinates of these components. Based on the component that corresponds to the location of the user input, the analysis module <NUM> can identify the feedback type. In some embodiments, a feedback type can be associated with each component (e.g., in the database).

In operation <NUM>, the analysis module <NUM> analyzes the one or more user inputs to understand the feedback. That is, the analysis module <NUM> determines the actual feedback that should be provided to the various entities based on analysis of the content of the user input. In some unclaimed examples, the analysis module <NUM> uses various natural language processing (NLP) algorithms or machine learning to understand the user input and form the actual feedback that will be provided to the corresponding entity. For instance, a change to text in a title of a publication (e.g., changing "Sprint" to "all carriers") can be formulated into feedback that indicates that the reviewer believes the new text is more appropriate (e.g., "user suggest item title be change from Sprint to all carriers").

Operation <NUM> may also include analyzing user inputs that involve an image. For example, in an unclaimed example, a reviewer may draw a circle around an item depicted in an image and provide a comment regarding the circled item. In another unclaimed example, the reviewer can make a correction or adjustment to the item depicted in the image (e.g., using image editing tools). In these cases, the imaging module <NUM> can perform an image lookup based on the free-hand drawings to identify a similar item to the item in the image or to identify the item. Information associated with the similar item or identified item (e.g., image, details, description) may be included in the feedback (e.g., analyzed user input).

In operation <NUM>, the filter module <NUM> filters the user input(s). In example unclaimed examples, the filtering module <NUM> applies machine learning (e.g., runs the user input through a machine learning engine) to filter out user inputs that do not make sense. For example, the user may highlight a component with text indicating a delivery option and provides a comment that the price of the item is too high. Because the comment does not appear to be directed to the highlighted text, the filter module <NUM> will remove (or otherwise not include) this user input in generating the feedback or feedback preview.

In operation <NUM>, the suggestion module <NUM> determines and provides suggestions for user inputs. In various embodiments, the suggestion module <NUM> works with the analysis module <NUM> to provide the suggestions. In some embodiments, the suggestions can be provided in real-time as the reviewer is providing their input. For example, in an unclaimed example, the reviewer selects an image or text on the webpage and starts to enter comments. While the reviewer is entering the comments or shortly thereafter, the UI module <NUM> detects the location of the user input and the analysis module <NUM> determines the component from the location. The suggestion module <NUM> can then generate suggestions (e.g., on-the-fly) for the same or similar component or search a database or data source of suggested feedback or previous feedback provided for that component or similar component. The suggestions can be based on transaction data (e.g., known or accessed from a user profile of the reviewer) or based on machine learning of how other reviewers have reacted to the same location on the webpage (e.g., other feedback provided from other reviewers for the same location). The suggestion module <NUM> can also suggest pre-defined phrases or even tags to help with the reviewer provide their feedback. The reviewer can select one or more suggestions to include in their feedback. Selected suggestions are received as part of a user input or as an additional user input by the feedback system <NUM>.

In operation <NUM>, the tag generator <NUM> generates tags from the user feedback that indicate a descriptive aspect from the feedback. The tags can be used, for example, as keywords or phrases that highlight aspects of the item or content in subsequent webpages displayed for the same (or similar) item or content. The tags can also be suggestions provided to future reviewers. In some embodiments, the tags may be generated after the transmission module <NUM> transmits the approved feedback to the corresponding entity in operation <NUM>.

In operation <NUM>, the preview module <NUM> generates the feedback preview that is presented to the user. The feedback preview organizes the user inputs analyzed in operation <NUM> by the feedback types determined in operation <NUM>, and generates a display component that summarizes the user inputs (subject to any that are filtered out in operation <NUM>). The display component can be a pop-up interface that is shown overlaid over the webpage or be displayed on a side of the UI presenting the webpage. In one embodiment, the feedback preview can be presented on a side of the UI as the reviewer is providing their inputs (i.e., in real-time or substantially real-time). In an alternative embodiment, the feedback preview can be presented to the reviewer when the reviewer has completed entering their inputs. Further still, the feedback preview can be displayed whenever the reviewer selects a preview icon or trigger.

The method <NUM> of <FIG> provides one embodiment for processing user inputs. Alternative embodiments may not include all the operations of the method <NUM> or perform the operations of the method <NUM> in a different order.

While example embodiments have been discussed with examples directed to webpages that display items for sale, alternative embodiments may cover reviews provided in other environments. That is, the reviewer can provide user inputs on a webpage of any content provider so long as the content provider (or an entity hosting the website that displays the webpage) has (or has access to) components or functionalities of the feedback system <NUM>. Additionally, the reviewer can review multiple, different webpages and submit all or a portion of the feedbacks after reviewing a single feedback preview.

<FIG> illustrates components of a machine <NUM>, according to some example embodiments, that is able to read instructions from a machine-storage medium (e.g., a machine storage device, a non-transitory machine-readable storage medium, a computer storage medium, or any suitable combination thereof) and perform any one or more of the methodologies discussed herein. Specifically, <FIG> shows a diagrammatic representation of the machine <NUM> in the example form of a computer device (e.g., a computer) and within which instructions <NUM> (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine <NUM> to perform any one or more of the methodologies discussed herein may be executed, in whole or in part.

For example, the instructions <NUM> may cause the machine <NUM> to execute the flowchart of <FIG> and <FIG>. In one embodiment, the instructions <NUM> can transform the general, non-programmed machine <NUM> into a particular machine (e.g., specially configured machine) programmed to carry out the described and illustrated functions in the manner described.

In alternative embodiments, the machine <NUM> operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine <NUM> may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine <NUM> may be a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, a smartphone, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions <NUM> (sequentially or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include a collection of machines that individually or jointly execute the instructions <NUM> to perform any one or more of the methodologies discussed herein.

The machine <NUM> includes a processor <NUM> (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), or any suitable combination thereof), a main memory <NUM>, and a static memory <NUM>, which are configured to communicate with each other via a bus <NUM>. The processor <NUM> may contain microcircuits that are configurable, temporarily or permanently, by some or all of the instructions <NUM> such that the processor <NUM> is configurable to perform any one or more of the methodologies described herein, in whole or in part. For example, a set of one or more microcircuits of the processor <NUM> may be configurable to execute one or more modules (e.g., software modules) described herein.

The machine <NUM> may further include a graphics display <NUM> (e.g., a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT), or any other display capable of displaying graphics or video). The machine <NUM> may also include an alphanumeric input device <NUM> (e.g., a keyboard), a cursor control device <NUM> (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instrument), a storage unit <NUM>, a signal generation device <NUM> (e.g., a sound card, an amplifier, a speaker, a headphone jack, or any suitable combination thereof), and a network interface device <NUM>.

The storage unit <NUM> includes a machine-storage medium <NUM> (e.g., a tangible machine-readable storage medium) on which is stored the instructions <NUM> (e.g., software) embodying any one or more of the methodologies or functions described herein. The instructions <NUM> may also reside, completely or at least partially, within the main memory <NUM>, within the processor <NUM> (e.g., within the processor's cache memory), or both, before or during execution thereof by the machine <NUM>. Accordingly, the main memory <NUM> and the processor <NUM> may be considered as machine-readable media (e.g., tangible and non-transitory machine-readable media). The instructions <NUM> may be transmitted or received over a network <NUM> via the network interface device <NUM>.

In some example embodiments, the machine <NUM> may be a portable computing device and have one or more additional input components (e.g., sensors or gauges). Examples of such input components include an image input component (e.g., one or more cameras), an audio input component (e.g., a microphone), a direction input component (e.g., a compass), a location input component (e.g., a global positioning system (GPS) receiver), an orientation component (e.g., a gyroscope), a motion detection component (e.g., one or more accelerometers), an altitude detection component (e.g., an altimeter), and a gas detection component (e.g., a gas sensor). Inputs harvested by any one or more of these input components may be accessible and available for use by any of the modules described herein.

The various memories (i.e., <NUM>, <NUM>, and/or memory of the processor(s) <NUM>) and/or storage unit <NUM> may store one or more sets of instructions and data structures (e.g., software) <NUM> embodying or utilized by any one or more of the methodologies or functions described herein. These instructions, when executed by processor(s) <NUM> cause various operations to implement the disclosed embodiments.

As used herein, the terms "machine-storage medium," "device-storage medium," "computer-storage medium" (referred to collectively as "machine-storage medium <NUM>") mean the same thing and may be used interchangeably in this disclosure. The terms refer to a single or multiple storage devices and/or media (e.g., a centralized or distributed database, and/or associated caches and servers) that store executable instructions and/or data, as well as cloud-based storage systems or storage networks that include multiple storage apparatus or devices. The terms shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors. Specific examples of machine-storage media, computer-storage media, and/or device-storage media <NUM> include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magnetooptical disks; and CD-ROM and DVD-ROM disks. The terms machine-storage media, computer-storage media, and device-storage media <NUM> specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term "signal medium" discussed below. In this context, the machine-storage medium is non-transitory.

The term "signal medium" or "transmission medium" shall be taken to include any form of modulated data signal, carrier wave, and so forth. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a matter as to encode information in the signal.

The instructions <NUM> may further be transmitted or received over a communications network <NUM> using the transmission medium via the network interface device <NUM> and utilizing any one of a number of well-known transfer protocols (e.g., HTTP). Examples of communication networks <NUM> include a local area network (LAN), a wide area network (WAN), the Internet, mobile telephone networks, plain old telephone service (POTS) networks, and wireless data networks (e.g., WiFi, LTE, and WiMAX networks). The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions <NUM> for execution by the machine <NUM>, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied on a machine-storage medium or in a transmission signal) or hardware modules. A "hardware module" is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.

In some embodiments, a hardware module may be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware module may include dedicated circuitry or logic that is permanently configured to perform certain operations. For example, a hardware module may be a special-purpose processor, such as a field programmable gate array (FPGA) or an ASIC. A hardware module may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware module may include software encompassed within a general-purpose processor or other programmable processor.

Accordingly, the term "hardware module" should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. As used herein, "hardware-implemented module" refers to a hardware module. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where the hardware modules comprise a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different hardware modules at different times. Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.

Example <NUM> is a method for generating feedback for a webpage based on visual interactions on the webpage. The method comprises receiving, by a server associated with a webpage over a network, an indication of a selection of an edit trigger displayed on a user interface (UI) that is displaying the webpage; in response to the receiving of the selection of the edit trigger, configuring, by the server, the webpage to receive feedback from the user, the feedback comprising one or more user inputs applied directly to the webpage; receiving, by the server, the one or more user inputs applied directly to the webpage, each user input being associated with an identifier of the webpage, coordinates of a location of the user input within the webpage, and a user edit that indicates the feedback; processing, by one or more hardware processors of the server, the one or more user inputs, the processing comprising generating a feedback preview that displays each of the one or more user inputs organized based on a corresponding feedback type; and causing presentation of the feedback preview on the device of the user, the feedback preview including one or more selectable elements to approve and submit a corresponding portion of the feedback.

In example <NUM>, the subject matter of example <NUM> can optionally include wherein the processing the one or more user inputs further comprises determining the feedback type based on the identifier of the webpage and the coordinates of the location of the user input within the webpage.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include wherein the receiving the one or more user inputs and the processing occurs in real-time; and the feedback preview is displayed on a side of the webpage on the UI as the user is providing the feedback.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include wherein the receiving the one or more user inputs comprises receiving the identifier of the webpage and the location of the user input in real-time; the method further comprising based on the identifier and the location of the user input within the webpage, determining suggested feedback; and causing presentation of the suggested feedback on the UI, the suggested feedback being selectable by the user.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include wherein the receiving the one or more user inputs comprise receiving a drag and drop operation to move a component displayed on the webpage to a different location, the feedback indicating a user preference for the component to be displayed at the different location.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include wherein the receiving the one or more user inputs comprise receiving an edit to text originally displayed on the webpage.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include wherein the one or more user inputs include a free-hand drawing made to an item in an image shown on the webpage and a comment entered in a comment box located proximate to the free-hand drawing; and the processing further comprises performing an image look up based on the free-hand drawing to identify a similar item to the item in the image.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include wherein a user input of the one or more user inputs is entered on the webpage by highlighting text on the webpage and providing a comment directed to the highlighted text, the comment being entered in a comment box located proximate to the highlighted text.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include wherein a user input of the one or more user input comprises highlighted text on the webpage.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include receiving an indication of the selection of a selectable element from the one or more selectable elements to approve and submit feedback corresponding to the selectable element; and in response to receiving the indication, transmitting feedback corresponding to the selectable element to a corresponding entity based on its feedback type.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include generating one or more tags based on the one or more user inputs, each tag indicating a descriptive aspect from the feedback.

Example <NUM> is a system for generating feedback for a webpage based on visual interactions on the webpage. The system includes one or more hardware processors and a memory storing instructions that, when executed by the one or more hardware processors, causes the one or more hardware processors to perform operations comprising receiving, over a network, an indication of a selection of an edit trigger displayed on a user interface (UI) that is displaying a webpage; in response to the receiving of the selection of the edit trigger, configuring the webpage to receive feedback from the user, the feedback comprising one or more user inputs applied directly to the webpage; receiving the one or more user inputs applied directly to the webpage, each user input being associated with an identifier of the webpage, coordinates of a location of the user input within the webpage, and a user edit that indicates the feedback; processing the one or more user inputs, the processing comprising generating a feedback preview that displays each of the one or more user inputs organized based on a corresponding feedback type; and causing presentation of the feedback preview on the device of the user, the feedback preview including one or more selectable elements to approve and submit a corresponding portion of the feedback.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include wherein the receiving the one or more user inputs comprises receiving the identifier of the webpage and the location of the user input in real-time; and the operations further comprise based on the identifier and the location of the user input within the webpage, determining suggested feedback; and causing presentation of the suggested feedback on the UI, the suggested feedback being selectable by the user.

In example <NUM>, the subject matter of any of examples <NUM>-<NUM> can optionally include wherein the operations further comprise receiving an indication of the selection of a selectable element from the one or more selectable elements to approve and submit feedback corresponding to the selectable element; and in response to receiving the indication, transmitting feedback corresponding to the selectable element to a corresponding entity based on its feedback type.

Example <NUM> is a machine-storage medium for generating feedback for a webpage based on visual interactions on the webpage. The machine-storage medium configures one or more processors to perform operations comprising receiving, over a network, an indication of a selection of an edit trigger displayed on a user interface (UI) that is displaying a webpage; in response to the receiving of the selection of the edit trigger, configuring the webpage to receive feedback from the user, the feedback comprising one or more user inputs applied directly to the webpage; receiving the one or more user inputs applied directly to the webpage, each user input being associated with an identifier of the webpage, coordinates of a location of the user input within the webpage, and a user edit that indicates the feedback; processing the one or more user inputs, the processing comprising generating a feedback preview that displays each of the one or more user inputs organized based on a corresponding feedback type; and causing presentation of the feedback preview on the device of the user, the feedback preview including one or more selectable elements to approve and submit a corresponding portion of the feedback.

Some portions of this specification may be presented in terms of algorithms or symbolic representations of operations on data stored as bits or binary digital signals within a machine memory (e.g., a computer memory).

Unless specifically stated otherwise, discussions herein using words such as "processing," "computing," "calculating," "determining," "presenting," "displaying," or the like may refer to actions or processes of a machine (e.g., a computer) that manipulates or transforms data represented as physical (e.g., electronic, magnetic, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or any suitable combination thereof), registers, or other machine components that receive, store, transmit, or display information. Furthermore, unless specifically stated otherwise, the terms "a" or "an" are herein used, as is common in patent documents, to include one or more than one instance. Finally, as used herein, the conjunction "or" refers to a non-exclusive "or," unless specifically stated otherwise.

Although an overview of the present subject matter has been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of embodiments of the present invention. For example, various embodiments or features thereof may be mixed and matched or made optional by a person of ordinary skill in the art. Such embodiments of the present subject matter may be referred to herein, individually or collectively, by the term "invention" merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or present concept if more than one is, in fact, disclosed.

The embodiments illustrated herein are believed to be described in sufficient detail to enable those skilled in the art to practice the teachings disclosed.

Claim 1:
A method at a server associated with a webpage, the method characterized by:
causing (<NUM>) the display on a user interface "UI" of a webpage about which a user wants to provide feedback, the webpage comprising content published by a publisher;
receiving (<NUM>), over a network, an indication of a selection of the edit trigger displayed on or otherwise associated with the UI;
in response to the receiving of the selection of the edit trigger, configuring (<NUM>) the displayed webpage to be able to receive feedback about the displayed webpage from the user, to enable the UI presenting the webpage to receive and display the feedback comprising one or more user inputs applied directly to the webpage;
receiving (<NUM>) the one or more user inputs applied directly to the webpage, each user input being associated with an identifier of the webpage, coordinates of a location of the user input within the webpage, and a user edit that indicates the feedback, a said user input indicating the feedback comprising selecting a component of the webpage and moving it from one location to a different location on the webpage;
processing (<NUM>) the one or more user inputs, the processing comprising generating a feedback preview that displays each of the one or more user inputs organized based on one or more corresponding feedback types; and
causing presentation (<NUM>) of the feedback preview on the device of the user, the feedback preview including one or more selectable elements to approve and submit a corresponding portion of the feedback.