Systems and methods for generating queries and responses based on application metadata

Abstract

Systems and methods are provided for generating queries and responses based on application metadata. The systems and methods can include a data processing system ("DPS"). The DPS can receive a request for content from a client device. The DPS can access metadata for one or more applications available for installation, the metadata for each application including a plurality of field-value pairs, the field-value pairs including values received from devices corresponding to a publisher of the application. The DPS can determine, from the metadata, entries associated with the application, including a query and a corresponding response. The DPS can select a content item including a subset of one or more of the entries and an actionable object that, when selected, causes the client device to access an information resource from which an application of the one or more applications can be installed. The DPS can send the content item for display on the client device.

Description

Technical Field

[0001] This application relates to systems and methods for generating queries and responses based on application metadata. Background Technology

[0002] In a computerized content delivery network, electronic content items can be distributed from a content server to a user device via content slots provided by the content provider. The content provider can supply one or more content items to the content server. The content publisher can provide one or more content slots (e.g., content item slots) configured to display at least one content item. The content server can select at least one content item and provide it to the content slot. The content publisher can display the content item in the content slot for display on the client device. Summary of the Invention

[0003] A content server can select content items of different styles or formats and provide them to client devices. Content items may include images, videos, or other playable formats. In some implementations, a content item may include one or more queries (sometimes called inquiries) and one or more corresponding responses (e.g., predetermined choices, options, or interactive elements). A user of the client device can provide input indicating a selection of at least one of the one or more responses. The content server may provide at least one content item to the client device. The user of the client device can select a response corresponding to at least one query within the content item. The content provider offering the content item may reward the user in response to successful interaction with one or more content items. In some cases, a content publisher displaying one or more content items via at least one corresponding content slot may provide a reward after a user successfully interacts with one or more content items. Rewards can incentivize users to increase their engagement with the content item (e.g., increase participation, viewing, or user interaction with the content item).

[0004] Traditionally, content providers can create or generate one or more queries for a content server to generate content items. For each query, the content provider can provide a set of responses (e.g., selections of responses) corresponding to that query. The content server can include the queries and responses into content items for display in at least one content slot provided by a content publisher among various content publishers. However, generating and storing queries and responses can be resource-intensive for the content server and time-consuming for the content provider offering queries, responses, or other content to generate content items. For example, traditionally, content providers can curate queries and responses, combinations or arrangements of responses for each query, or update queries and responses for generating content items, which can be time-consuming processes. Furthermore, because these queries and corresponding responses can be included in content items stored by the content server, they can consume significant storage resources from the content server.

[0005] To address the challenges associated with interactive content items—namely, the amount of time content providers spend generating queries and responses for such items and the amount of storage resources consumed by content servers storing them—the systems and methods described herein can automatically generate queries and responses for content items. In some implementations, interactive content items can be used to facilitate or increase user engagement with certain applications to be installed on client devices (e.g., directing queries to or based on information from that application).

[0006] For such interactive content items related to client applications, this disclosure may refer to one or more processors (e.g., a data processing system or content server) configured to automatically generate queries and responses based on application-associated metadata. The metadata may be accessible to the data processing system. By generating queries and responses from metadata accessible to the data processing system, the system can reduce the amount of data stored in databases and the amount of data sent to and received from content providers. Furthermore, the data processing system can reduce the amount of time spent by content provider administrators on generating such queries and responses, arranging the content of content items, or updating their lists of queries and responses.

[0007] Data processing systems can use interactive content items to teach users about an application and determine the accuracy of the application's metadata. These interactive content items are generated using the application's metadata corresponding to the content item. For example, depending on the user's response to certain queries (e.g., selection of at least one response from a list of responses), responses (or feedback) from the user can be used to confirm the accuracy of the application's metadata. Therefore, the systems and methods described herein can reduce resource consumption (e.g., by storing queries and interactive elements from content providers through generating content items using application-corresponding metadata), reduce network traffic (or network congestion), and reduce time consumption for content providers, as they will not need to send queries, responses, or content to the content server for generating content items.

[0008] At least one aspect relates to a method for generating queries and responses based on application metadata. The method may include a data processing system comprising one or more processors and memory. The method may include the data processing system receiving a request for content from a client device. The method may include the data processing system accessing metadata of one or more applications that can be installed, each application's metadata including multiple field-value pairs, the field-value pairs including values ​​received from a device corresponding to the application's publisher. The method may include the data processing system determining one or more entries associated with one or more applications from the metadata, the one or more entries including one or more queries and corresponding one or more responses. The method may include the data processing system selecting a content item comprising a subset of one or more entries and actionable objects, when the content item is selected, causing the client device to access information resources from which applications can be installed from one or more applications. The method may include the data processing system sending the content item to the client device for display on the client device.

[0009] In some implementations, the method may include receiving input from a client device by a data processing system corresponding to a correct response associated with a content item. The method may include terminating a content item on the client device by the data processing system. The method may include disabling the visibility of a content item on the client device by the data processing system. In some implementations, the application may be a first application, and the request for content may include an identifier of a second application, the second application including a content slot in which the content item is presented. In some implementations, to select a content item, the method may include selecting the content item by the data processing system based on the identifier of the second application and the type of the content slot.

[0010] In some implementations, the method may include a data processing system selecting a subset of one or more entries for inclusion in a content item. The data processing system selects each entry in the subset by identifying the priority of each field from multiple field-value pairs of the application's metadata, the priority assignment being based on i) the number of values ​​associated with that field, or ii) the number of incorrect responses previously received from a client device for a content item that includes a query targeting that field. In some implementations, a selection model may be used to select a subset of one or more entries for inclusion in a content item. The method may include the data processing system receiving interaction data from a client device with content items presented on the client device, the interaction data identifying the response selected at the client device. The method may include the data processing system updating a selection model for selecting multiple entries for multiple client devices based on the interaction data from the client devices.

[0011] In some implementations, a content item may include a script that, when executed on a client device, causes the client device to present a subset of one or more items within a content slot. The script may cause the client device to detect interactive data from the selection of one or more interactive elements associated with the subset of one or more items. The script may also cause the client device to provide the interactive data detected from the selection of one or more interactive elements within the content slot to a data processing system.

[0012] In some implementations, a content item may include an image and script corresponding to a reward. When executed on a client device, the script may cause the client device to present a subset of one or more items within a content slot. The script may cause the client device to detect first interactive data from the selection of one or more interactive elements associated with the subset of one or more items. The script may cause the client device to determine that the selection indicates an incorrect response. The script may cause the client device to provide a notification to its display device indicating that the selection is incorrect. The script may cause the client device to detect second interactive data from the selection of one or more other interactive elements associated with the subset of one or more items. The script may cause the client device to determine that the selection indicates a correct response. The script may cause the client device to present an image corresponding to the reward to its display device in response to determining that the second interactive data corresponds to a correct response.

[0013] In some implementations, the method may include determining that an interaction time exceeds a threshold after a content item is presented on a client device by a data processing system. The method may include a script triggered by the data processing system for the content item, causing the client device to present a reward corresponding to the content item in response to the interaction time exceeding the threshold. In some implementations, the content item may include a script that, when executed on the client device, causes the client device to present a subset of one or more items within a content slot. The script may cause the client device to detect interaction data from the selection of one or more interactive elements associated with the subset of one or more items. The script may cause the client device to determine that the selection indicates a correct response. The script may cause the client device, in response to determining that a correct response has been selected, to send an instruction to an entity associated with a content provider to update a value corresponding to the content provider, which corresponds to a performance metric of the content item comprising a subset of one or more items and an actionable object associated with the application.

[0014] At least one aspect points to a system for generating queries and responses based on application metadata. The system may include a data processing system comprising one or more processors and memory. The data processing system may receive requests for content from a client device. The data processing system may access metadata for one or more applications that can be installed, each application's metadata including multiple field-value pairs, the field-value pairs including values ​​received from a device corresponding to the application's publisher. The data processing system may determine one or more entries associated with the one or more applications from the metadata, the one or more entries including one or more queries and corresponding one or more responses. The data processing system may select content items comprising a subset of one or more entries and actionable objects, and when the content item is selected, the client device may access information resources from which applications can be installed from one or more applications. The data processing system may send the content item to the client device for display on the client device.

[0015] In some implementations, the data processing system may receive input from a client device corresponding to a correct response associated with a content item. The data processing system may terminate a content item on the client device. The data processing system may disable the visibility of the content item on the client device. In some implementations, the application may be a first application, and the request for content may include an identifier of a second application, which includes a content slot in which the content item is presented. In some implementations, to select a content item, the data processing system may select the content item based on the identifier of the second application and the type of the content slot.

[0016] In some implementations, the data processing system may select a subset of one or more entries to include in a content item. The system selects each entry in the subset by identifying the priority of each field from multiple field-value pairs in the application's metadata, the priority assignment being based on i) the number of values ​​associated with that field, or ii) the number of incorrect responses previously received from the client device for a content item that includes a query targeting that field. In some implementations, a selection model may be used to select a subset of one or more entries to include in a content item. The data processing system may receive interaction data from the client device and the content items presented on the client device, the interaction data identifying the response selected at the client device. The data processing system may update the selection model for selecting multiple entries for multiple client devices based on the interaction data from the client devices.

[0017] In some implementations, a content item may include a script that, when executed on a client device, causes the client device to present a subset of one or more items within a content slot. The script may cause the client device to detect interactive data from the selection of one or more interactive elements associated with the subset of one or more items. The script may also cause the client device to provide the interactive data detected from the selection of one or more interactive elements within the content slot to a data processing system.

[0018] In some implementations, a content item may include an image and script corresponding to a reward, which, when executed on a client device, may cause the client device to present a subset of one or more items within a content slot. The script may cause the client device to detect first interactive data from the selection of one or more interactive elements associated with the subset of one or more items. The script may cause the client device to determine that the selection indicates an incorrect response. The script may cause the client device to provide a notification to its display device indicating that the selection is incorrect. The script may cause the client device to detect second interactive data from the selection of one or more other interactive elements associated with the subset of one or more items. The script may cause the client device to determine that the selection indicates a correct response. The script may cause the client device to present an image corresponding to the reward to its display device in response to determining that the second interactive data corresponds to a correct response.

[0019] In some implementations, the data processing system can determine that an interaction time exceeds a threshold after a content item has been presented on a client device. The data processing system can trigger a script for the content item, causing the client device to present a reward corresponding to the content item in response to the interaction time exceeding the threshold. In some implementations, the content item may include a script that, when executed on the client device, causes the client device to present a subset of one or more items within a content slot. The script can cause the client device to detect interaction data from the selection of one or more interactive elements associated with the subset of one or more items. The script can cause the client device to determine that the selection indicates a correct response. The script can cause the client device to send an instruction to an entity associated with the content provider in response to determining that a correct response has been selected, to update a value corresponding to the content item's performance metrics, which includes a subset of one or more items and an actionable object associated with the application.

[0020] These and other aspects and implementations are discussed in detail below. The foregoing information and the following detailed description include illustrative examples of various aspects and implementations, and provide an overview or framework for understanding the nature and characteristics of the claimed aspects and implementations. The accompanying drawings provide illustration and further understanding of the various aspects and implementations, and are incorporated in and constitute a part of this specification. Attached Figure Description

[0021] The accompanying drawings are not intended to be drawn to scale. The same reference numerals and names in different drawings indicate the same elements. For clarity, not every component is labeled in every drawing. In the drawings:

[0022] Figure 1 It is a block diagram of a computer system according to an implementation method, including a network, resources, content providers, user devices, data storage devices, data processing systems, and content publishers;

[0023] Figure 2 A more detailed description of the implementation method is provided below. Figure 1 A block diagram of a data processing system;

[0024] Figure 3 This is an example table of field-value pairs for application metadata according to the implementation method;

[0025] Figure 4 This is an example illustration of an interactive content item according to the implementation method;

[0026] Figure 5 This is an example illustration of a client device displaying interactive content items within a first application according to an implementation method; and

[0027] Figure 6This is a flowchart of an example method for generating queries and responses based on application metadata, according to an implementation method. Detailed Implementation

[0028] The following is a more detailed description of various concepts and their implementations related to methods, apparatuses, and systems for generating queries and responses based on application metadata of content items. Since the concepts described are not limited to any particular implementation, the various concepts introduced above and discussed in more detail below can be implemented in any of a variety of ways.

[0029] A content server can select and provide content items in different styles or formats to client devices. Content items may include images, videos, other playable formats, or other elements configured to be displayed on the client device. When displayed on the client device, the content item may be interactive (e.g., including at least one interactive element) or playable. In some implementations, a content item may include one or more queries (sometimes referred to as inquiries) and one or more corresponding responses (e.g., predetermined choices, options, or interactive elements for a user to select). A user on the client device can provide input indicating a selection of at least one of the one or more responses. The content server may provide at least one content item to the client device. A user on the client device can select a response corresponding to at least one query within the content item. The content provider offering the content item may reward the user in response to successful interaction with one or more content items. In some cases, a content publisher displaying one or more content items via at least one corresponding content slot may provide a reward after a user successfully interacts with one or more content items. Rewards can incentivize users to increase their engagement with the content item (e.g., increase participation, viewing, or user interaction with the content item).

[0030] Traditionally, content providers can create or generate one or more queries for a content server to generate content items. For each query, the content provider can provide a set of responses (e.g., selections of responses) corresponding to that query. The content server can include the queries and responses into content items for display in at least one content slot provided by one of the various content publishers. However, generating and storing queries and responses can be resource-intensive for the content server and time-consuming for the content provider offering queries, responses, or other content to generate content items. For example, traditionally, content providers can curate queries and responses, combinations or arrangements of responses for each query, or update queries and responses for generating content items, which can be time-consuming processes. Furthermore, because these queries and corresponding responses can be included in content items stored by the content server, they can consume significant storage resources from the content server.

[0031] To address the challenges associated with interactive content items—namely, the amount of time content providers spend generating queries and responses for such items and the amount of storage resources consumed by content servers storing them—the systems and methods described herein can automatically generate queries and responses for content items. In some implementations, interactive content items can be used to facilitate or increase user engagement with certain applications to be installed on client devices (e.g., directing queries to or based on information from that application).

[0032] For such interactive content items related to client applications, this disclosure may refer to one or more processors (e.g., a data processing system or content server) configured to automatically generate queries and responses based on application-associated metadata. The metadata may be accessible to the data processing system. By generating queries and responses from metadata accessible to the data processing system, the system can reduce the amount of data stored in databases and the amount of data sent to and received from content providers. Furthermore, the system can reduce the amount of time spent by content provider administrators on generating such queries and responses, arranging the content of content items, or updating their lists of queries and responses.

[0033] Data processing systems can use interactive content items to introduce an application to a user and determine the accuracy of the application's metadata. These interactive content items are generated using the application's metadata corresponding to the content item. For example, depending on the user's response to certain queries (e.g., selection of at least one response from a list of responses), responses (or feedback) from the user can be used to confirm the accuracy of the application's metadata. Therefore, the systems and methods described herein can reduce resource consumption (e.g., by storing queries and interactive elements from a content provider through generating content items using application-corresponding metadata), reduce network traffic (or network congestion), and reduce time consumption for the content provider, as the content provider will not need to send queries, responses, or content to a content server for generating content items.

[0034] Now for reference Figure 1The diagram illustrates a block diagram of a computer system 100 according to an embodiment. The computer system 100 may include at least a network 102, a resource 104, a content provider 106, a user device 108 (sometimes referred to as a client device), a data storage device 110, a data processing system 112 (“DPS”), and a content publisher 114. The DPS 112 may be referred to as or include features and functions of a content server for generating content items. The network 102 may facilitate communication or connection between the resource 104, the content provider 106, the user device 108, the data storage device 110, the DPS 112, and the content publisher 114. For example, the user device 108 may request and receive resource content (e.g., web pages, documents, applications, etc.) from the resource 104 via the network 102. In some embodiments, the resource 104 may include content item slots for presenting third-party content items from the content provider 106. Information and data from the resource 104 (such as content slots, web pages, documents, application resources, application metadata, etc.) may be provided by the content publisher 114, which manages the resource 104. For example, content publisher 114 may send or provide data (e.g., metadata, information, scripts, code, etc.) related to an application, webpage, document, or other service to resource 104. One or more components of computer system 100 (e.g., content provider 106, user device 108, data storage device 110, or DPS 112) may access resource 104. DPS 112 may receive a request for a content item from user device 108, select an eligible content item or generate a content item in response to the request, and distribute the content item to user device 108 via network 102. A request for a content item from user device 108 may be in response to user device 108 accessing an application, webpage, or other resource 104 managed by at least one content publisher 114. Resource 114 may include at least one content slot for displaying content items. To distribute content items, DPS 112 may provide the selected or generated content item to the content slot provided by content publisher 114. Accordingly, the content item may be displayed in the content slot of the corresponding resource 114 (e.g., application, webpage, document, etc.). In some implementations, one or more generated content items may be stored in a data storage device 110 accessible by DPS112.

[0035] Network 102 can be a local area network (LAN), a wide area network (WAN), a cellular network, a satellite network, a radio network, the Internet, or any other type of data network or a combination thereof. Network 102 can include any number of computing devices (e.g., computers, servers, routers, network switches, etc.) configured to send, receive, or relay data. Network 102 can also include any number of hardwired and / or wireless connections. For example, user equipment 108 can wirelessly communicate with transceivers (e.g., via WiFi, cellular, radio, etc.) hardwired to computing devices in network 102 (e.g., via fiber optic cable, CAT5 cable, etc.). Network 102 can facilitate communication or connectivity between components of computer system 100.

[0036] Computer system 100 may include resource 104. Resource 104 may include any type of information or data structure available through network 102. In some implementations, resource 104 may be identified by a resource address (e.g., a uniform resource locator, URL) associated with each resource. Resource 104 may include web pages (e.g., HTML web pages, PHP web pages, etc.), applications (e.g., downloadable or installable software that can be executed locally or via a connection to network 102), word processing documents, portable document format (PDF) documents, images, videos, programming elements, interactive content, streaming video / audio sources, or other types of electronic information. Resource 104 may include content or user interfaces (e.g., words, phrases, images, sounds, videos, computer graphics (“CG”), etc.) with embedded information (e.g., metadata embedded in hyperlinks) and / or embedded instructions. Embedded instructions may include computer-readable instructions (e.g., software code, etc.) executable by user device 108 (e.g., by an application running on user device 108). wait).

[0037] In some implementations, resource 104 may include a content slot for rendering third-party content items. For example, resource 104 may include one or more inline frame elements (e.g., HTML "iframe" elements) for rendering third-party content items from content provider 106. <iframe>...< / iframe>Resource 104 may include content slots for presenting content items generated by DPS 112. Embedded frames may be “target” frames linked by other elements and may be selected by a user agent (e.g., user device 108, a web browser running on user device 108, an application executing on user device 108, etc.) as the focus for printing, viewing its source, or other forms of user interaction. Content slots may allow user device 108 to request third-party content items from DPS 112 in response to viewing first-party resource content from resource 104. For example, a user may launch an application (e.g., a local application, a web application, etc.) on user device 108. User device 108 may request application-related information (e.g., images, user interfaces, videos, interactive elements, content slots, etc.) from resource 104. Application content slots may allow user device 108 to request content items from DPS 112 (e.g., by sending a request for content to DPS 112). DPS 112 may receive the request for content and generate at least one content item accordingly. DPS112 can provide or send one or more content items to the content slot for display in an application running on user device 108.

[0038] Computer system 100 may include a content publisher 114. For example, content publisher 114 may be referred to as an application publisher, website publisher, or resource provider. Content publisher 114 may provide data, such as application data, web pages, documents, etc., to resource 104. Content publisher 114 may generate data to provide to resource 104. For example, content publisher 114 may create, modify, or delete web pages, applications, word processing documents, portable document format (PDF) documents, images, videos, programming elements, interactive content, streaming video / audio sources, or other types of electronic information from resource 104. Content publisher 114 may provide first-party resource content to resource 104. User device 108 may request first-party resource content via a corresponding application running on user device 108.

[0039] In some implementations, content publisher 114 may publish web pages or provide access to an application that includes slots for inserting supplementary content provided by content providers other than content publisher 114. For example, in such techniques, content publisher 114 may insert a script (e.g., in the form of a JavaScript file) into the application header. When the application is loaded, the script may trigger user device 108 to contact one or more content providers 106 to provide supplementary information for selecting or generating content to be included in the application (e.g., user device 108's relevance score, interaction rate, likelihood of user interaction, output value, etc., or any combination thereof). In some cases, the script may trigger user device 108 to contact DPS 112 to (e.g., using supplementary information provided by content provider 106) generate or select content items to be included in the slot.

[0040] In some implementations, content publisher 114 may incentivize user interaction with content items displayed in one or more content slots within a corresponding application of content publisher 114. For example, content publisher 114 may provide one or more inline frame elements or data indicating the type of content slot (e.g., banner, notification, or interstitial content slot) to be included in an application, a webpage executed on a web browser, or a document presented in a document processing application. Content publisher 114 may provide code, scripts, or computer-readable instructions to indicate the location or positioning of one or more content slots, the interval for displaying the content slots (e.g., a 10-minute cycle, a 20-minute cycle, etc.), conditions for disabling the visibility of content slots or terminating the display of content slots (e.g., interaction with interactive elements displayed in the content slots, timeout periods, etc.), or incentives (e.g., rewards) to be provided to the user device (e.g., a user account accessed in an executing application) when successfully interacting with the interactive elements of a content item. Content publisher 114 may provide incentives associated with an application running on user device 108, such as coins, points, cosmetics, objects, accessories, or other items from the application (e.g., available, fair, or collectable within the application). Content publisher 114 may instruct the user to meet one or more conditions for sending the incentive. For example, these conditions may include at least a successful response from user device 108 or engagement with a content item for a predetermined time threshold (e.g., 30 seconds, 1 minute, etc.).

[0041] In some implementations, content publisher 114 may register or opt-in to features or functionalities (e.g., services) provided by DPS 112. For example, content publisher 114 may provide or assign content slots for displaying content items. If content publisher 114 opts to join a service provided by DPS 112, DPS 112 may provide generated content items for display in content slots. Content publisher 114 may provide incentives or rewards when a user satisfies conditions of a content item (e.g., duration of engagement, successful interaction, or selection of one of the responses). The user may select at least one response from a predetermined list of responses corresponding to a query. DPS 112 may monitor user interactions with content items. If the user provides a satisfactory or successful response to a query, DPS 112 may access resource 104 to retrieve a reward to provide to user device 108. DPS 112 may send, display, or present the reward to user device 108, which is reflected in an application running on user device 108 (e.g., the application of content publisher 114).

[0042] Computer system 100 may include content provider 106. Content provider 106 may include one or more electronic devices representing an administrator, resource operator, business owner, or other entity using services provided by DPS 112. Content provider 106 may include at least application 116 and at least metadata 118. Application 116 may include software, code, scripts, hyperlinks, and other information to direct user device 108 to the application's installation page, install the application, execute the application, etc. DPS 112 may access data of application 116 to, for example, provide user device 108 with an executable file for installing application 116 of content provider 106. In some cases, at least a subset or at least a portion of the information of application 116 may be provided to resource 104 for user device 108 to access and execute the application associated with content provider 106. Metadata 118 may include various field-value pairs associated with application 116. At least a portion or at least a subset of metadata 118 may be presented in the installation page of application 116 (e.g., a store page) to indicate a description or backend information of application 116. In some implementations, the application's metadata may be provided by the content provider 106. In other implementations, the application's metadata may be determined by the DPS or another system communicating with the DPS. For example, the total number of application downloads or statistics related to devices that have downloaded the application may be determined by the DPS or other systems, rather than being received by the content provider 106.

[0043] For example, fields in a field-value pair may include a title, description, genre or category, search terms or keywords, at least one image, the address of the App116 page, rules or policies, app size, total downloads, the latest version of App116, release date, at least one video (e.g., a preview or initial presentation of App116 content), one or more content creators, reviews, ratings, or at least one other topic related to or associated with App116. Values ​​in a field-value pair may include descriptions, text, data, or files corresponding to the fields, such as text for the title, descriptive text for App116, image data, hyperlinks or Uniform Resource Locators (“URLs”), or indications of the App116 genre from the category field (e.g., in text form).

[0044] Content provider 106 may transmit data or metadata 118 of application 116 to DPS 112. In some cases, DPS 112 may access application 116 or metadata 118 to generate content items. For example, DPS 112 may use field-value pairs to generate one or more queries and corresponding responses. DPS 112 may use at least one query and at least one response associated with that query. DPS 112 may identify or generate one or more responses not included in the field-value pairs of application 116 (e.g., from other metadata from other applications). In a further example, DPS 112 may select a category of application 116 as a query (e.g., "What is the genre of this application?"). If the categories of application 116 include action, adventure, and strategy, DPS 112 may select action as one of the responses. For other responses, DPS 112 may identify categories not listed in the metadata 118 of application 116, such as mystery, strategy, business, puzzle, or simulation. DPS 112 may select at least one category that is not part of the metadata 118 for other responses. Accordingly, DPS112 can generate at least one content item with queries and various responses.

[0045] In some implementations, content provider 106 may be one or more administrators or developers of application 116. Content provider 106 may register with DPS 112 to allow its application to be available through an app store or marketplace. As part of the registration process, content provider 106 may provide metadata about the application to the DPS. In some implementations, the DPS may generate one or more field-value pairs of metadata based on the application's content or based on data received from content provider 106. In some implementations, the DPS may generate one or more field-value pairs of metadata about the application based on analysis of devices that have the application installed or have requested access to the application. Content provider 106 may be an editor of metadata 118 for application 116. For example, if content provider 106 is a developer promoting application 116, it may provide metadata 118 to provide details of application 116 to users of user device 108. In some cases, content provider 106 may be a retailer promoting products (e.g., electronics, clothing, accessories, home furnishings, etc.). Each content provider 106 can transmit product information associated with different product sets to DPS112.

[0046] In some implementations, content provider 106 may register or opt-in to features or functionalities (e.g., services) provided by DPS 112, such as automatically generating content items using application metadata. For example, content provider 106 may allow DPS 112 to access and use application metadata provided by content provider 106. When opting in to a service, DPS 112 may access metadata 118 of application 116 to generate one or more queries and responses. Content provider 106 may not need to provide separate queries or responses corresponding to each query for DPS 112 to generate content items. In some implementations, content provider 106 may send instructions or rules for generating content items, such as background images for displaying content items, or the arrangement of optional responses (e.g., based on alphabetical order or response values). Response values ​​may refer to hexadecimal values, binary values, or the size of numbers displayed in the response. Content provider 106 may instruct DPS 112 which field-value pairs(s) are used to generate one or more content items.

[0047] In some implementations, after generating content items, DPS 112 may store the content items in at least one of various data storage devices 110. In other implementations, DPS 112 may not store the generated content items in the data storage device 110. For example, in response to receiving a request for content, DPS 112 may retrieve the latest metadata 118 from the content provider 106 (e.g., in an application page, store page, or installation page associated with application 116). In another example, DPS 112 may store a portion of the generated content items for use in generating other content items, such as background themes / images, the types of field-value pairs to be used, the dimensions of the content items, or other configurations that may be used as templates for generating additional content items.

[0048] In some implementations, content provider 106 may submit or configure activity parameters to DPS 112. These activity parameters can be used to control the distribution of content items to user device 108. Activity parameters may include keywords associated with the content item, bids corresponding to the keywords, application types that display the content item, application types that do not display the content item, content distribution budget, geographic restrictions, or other criteria used by DPS 112 to determine when content items can be presented to user device 108.

[0049] Content provider 106 can access DPS 112 to monitor the performance of content items distributed based on established activity parameters. For example, content provider 106 can access DPS 112 to view one or more behavioral metrics associated with a content item or set of content items. Behavioral metrics can describe the interaction between user device 108 and the distributed content item or set of content items (e.g., impressions, clicks, conversions, spending, etc.). In some cases, behavioral metrics can describe interactive elements selected by the user and the corresponding descriptions of those interactive elements, such as the display text of application 116, field-value pairs, or metadata 118.

[0050] Computer system 100 may include user equipment 108. User equipment 108 may include any number and / or type of user-operable electronic devices. For example, user equipment 108 may include a desktop computer, laptop computer, smartphone, tablet computer, mobile communication device, remote workstation, client terminal, entertainment console, or any other device capable of interacting with other components of computer system 100 (e.g., via a communication interface). For example, user equipment 108 may be able to receive resource content from resource 104 and / or receive third-party content items from content provider 106 or DPS 112. User equipment 108 may include mobile devices or non-mobile devices.

[0051] In some implementations, user equipment 108 includes applications (e.g., web browsers, resource renderers, etc.) for converting electronic content into a user-understandable format (e.g., visual, auditory, graphical, etc.). The applications may be installed on user equipment 108 or accessed via a communication interface to, for example, access a web application running on the device of DPS 112 or content publisher 114. For example, an application may be installed by accessing or browsing an application's store page, the application page of content publisher 114, or the application page of content provider 106 (e.g., application 116 linked within a content item). User equipment 108 may include user interface elements (e.g., electronic displays, speakers, keyboards, mice, microphones, printers, etc.) for presenting content to a user, receiving user input, or facilitating user interaction with electronic content (e.g., clicking on content items, hovering over content items, etc.). User equipment 108 may act as a user agent for allowing users to view HTML-encoded content. User equipment 108 may include processors capable of processing embedded information (e.g., metadata embedded in hyperlinks, etc.) and executing embedded instructions. Embedded instructions may include computer-readable instructions (e.g., software code) associated with content slots where third-party content items are presented. wait).

[0052] In some implementations, user device 108 may be able to detect interactions with distributed content items. Interactions with content items may include hovering over a content item, clicking on a content item (e.g., interactive elements within the content item), viewing source information for a content item, or any other type of interaction between user device 108 and the content item. In some cases, interaction with content items may not require explicit user action for a particular content item. In some implementations, impressions (e.g., displaying or presenting a content item) may be eligible for interaction. In such implementations, content items may be terminated or hidden after a predetermined time. The criteria used to define which user actions (e.g., active or passive) qualify as interactions may be determined by content provider 106 or by DPS 112 on an individual basis (e.g., for each content item).

[0053] User equipment 108 can be configured to execute computer-readable instructions (e.g., software code, ...) in response to detected interaction with content items. (etc.). Computer-readable instructions may be included in the distributed content item or otherwise provided to user device 108. In some embodiments, the computer-readable instructions cause user device 108 to present a personalized visual display in response to a detected interaction with the content item. The personalized visual display may refer to a visual display related to an application, web page, or document accessed by the user or the corresponding user. The personalized visual display may include multiple product images associated with a single content provider 106. If the visual display includes images, the images may be arranged in a collage, mosaic, or other visual presentation format, such that multiple images can be presented to user device 108 concurrently. The visual display may be associated with a user-facing application and may include images of the application or links to direct user device 108 to an application page (e.g., to install or view details of the application). The computer-readable instructions may cause user device 108 to present details or elements of the application (e.g., application summary, specifications, price, images, purchase information, release date, etc.) in the visual display in response to a detected interaction with an application image or application link associated with the personalized visual display.

[0054] Computer system 100 may include data storage device 110. Data storage device 110 may be any type of storage device capable of storing profile data, content item data, accounting data, or any other type of data used by DPS 112. In some cases, data storage device 110 may store data for use by other components of computer system 100, such as content provider 106 or user equipment 108. Data storage device 110 may include any type of non-volatile memory, media, or storage device. For example, data storage device 110 may include semiconductor memory devices (e.g., EPROM, EEPROM, flash memory devices, etc.), disks (e.g., internal hard disks, removable disks, etc.), magneto-optical disks, and / or CD-ROMs and DVD-ROMs. In some embodiments, data storage device 110 may be located locally at DPS 112 or content provider 106. In other embodiments, data storage device 110 may be a remote data storage device connected to DPS 112 via network 102.

[0055] Data storage device 110 can store various templates to generate content items for different types of content slots. For example, data storage device 110 can store templates for video content slots, banner content slots, static content slots, interstitial content slots, notification content slots, etc. Templates can have different sizes, and one or more content items can be stretched or shrunk to fit the template. Based on the type of content slot (e.g., the type of content item to be displayed in the slot), DPS 112 can use different templates to generate content items. Data storage device 110 can store data for application 116 for content provider 106. Data storage device 110 can store metadata 118. In some embodiments, data storage device 110 can store at least a subset of information from resource 104.

[0056] Data storage device 110 may store historical data of users (e.g., user accounts or user devices 108). Data storage device 110 may store historical user interactions with content items displayed in the application of at least one content publisher 114. For example, data storage device 110 may include, store, or maintain information related to user responses to queries, such as selections of interactive elements based on application metadata or randomly generated interactive elements. DPS 112 may use the interaction data to determine performance data or performance metrics of the application metadata (e.g., measuring performance). For example, if a majority of users select the same interactive element as a response to a query, DPS 112 may determine whether the query is incomprehensible (e.g., will not confuse users who select at least one response corresponding to the query), whether the application metadata is inaccurate in cases where a majority of users click on a first optional element provided in the content item, or other indications or implications that can be derived from the performance data of the content item. In some cases, DPS 112 may notify content provider 106 of performance metrics. For example, DPS 112 may indicate the overall trend or common response of users to one or more queries. Based on a shared response, content provider 106 can inspect, update, or maintain application metadata. Content provider 106 can provide instructions to DPS 112 to generate similar content items with high performance, avoid generating content items with low performance, or generate content items with a high interaction rate.

[0057] Data storage device 110 may store user information associated with user device 108. User information may include, for example, user-specific information (e.g., user demographics, user preferences, user behavior data, user profile data, etc.), contextual information (e.g., user location, webpage context, recent page views, etc.), keyword information (e.g., keywords associated with a specific webpage or search query, etc.), and / or other information that may be used to generate queries or responses relevant to or of interest to a specific user or user device. User information may include applications installed on user device 108, applications recently used by the user (e.g., within an hour, day, week, etc.), or the category (e.g., genre) of applications executed or installed by the user.

[0058] For situations where the system discussed here collects or may use personal information about a user, the user is given the opportunity to control whether the program or feature collects user information (e.g., information about the user's social networks, social actions or activities, occupation, user preferences, or the user's current location), or to control whether and / or how content that may be more relevant to the user is received from the content server. Furthermore, before storing or using certain data, it is processed in one or more ways (e.g., via DPS112) to remove personally identifiable information. For example, the user's identity is processed so that the user's personally identifiable information cannot be determined, or the user's geographic location is generalized (generalized to a level such as city, postal code, or country) where location information is obtained, making it impossible to determine the user's specific location. Therefore, the user can control how DPS112 collects and uses information (e.g., through an application, through user device 108, etc.).

[0059] In some implementations, data storage device 110 may be part of a data storage server or system capable of receiving and responding to requests from DPS 112. For example, data storage device 110 may receive requests from DPS 112 for application metadata or user information and provide the requested information to DPS 112. In addition to the data discussed above, data storage device 110 may also store other data that may be from any component of computer system 100 as described herein.

[0060] Computer system 100 may include DPS 112 (sometimes referred to as a content server, computing system, or processing component of computer system 100). DPS 112 may receive or retrieve application metadata from content provider 106 and / or data storage device 110. In some embodiments, the application metadata may be updated in real time or before being retrieved by DPS 112. For example, content provider 106 may provide an update to metadata 118. In response to this update, the application metadata associated with application 116 of content provider 106 stored in data storage device 110 may be updated. In some embodiments, metadata 118 may be provided directly from content provider 106 for DPS 112 to generate queries and responses. In some embodiments, metadata 118 may be determined by DPS 112 based on data collected by DPS 112 or another system communicating with DPS 112. For example, the total number of downloads or the application size of the application may be determined by DPS 112 without receiving data from the content provider. DPS112 can generate or select various queries or responses that are estimated to be most relevant to a specific user or user device (e.g., a user device on which a personalized visual display will be presented) or of most interest to a specific user or user device (e.g., a user device on which a personalized visual display will be presented). The generated queries can be based on, for example, the types of queries a user might query when seeking to install an application, such as the application's genre, what the application is generally about, the application's rules or policies, or what is generally expected when installing / using the application.

[0061] DPS112 can generate personalized content items for a user (e.g., based on user information, search history, cookies, queries, or applications executed by or installed on user device 108), and present these content items via content slots provided by content publisher 114 through a specific user device. Content items may include background displays (e.g., transparency, color, image, watermark, etc.) displayed in the corresponding content slot. Background displays may be based on or derived from application metadata, such as an image of the application or a color matching the background of the application page.

[0062] Content items may include interactive elements, such as links to application 116 of content provider 106 (e.g., a second application different from a first application running on user device 108 that has content slots and displays content items), or selections in response to queries. DPS 112 may make selections for the user based on at least one field-value pair of application metadata. DPS 112 may generate or select at least one selection using values ​​from the corresponding field-value pair, and generate other selections based on values ​​corresponding to that field but not in that field-value pair. For example, if a query instructs the user to select a response with rules from a second application (such as chess), DPS 112 may generate at least one selection with one of the rules from the second application (e.g., checkmate to win the game), and generate other selections unrelated to the second application (e.g., move up one level by collecting coins, swipe left or right to turn, move using the "w", "s", "a", "d" keys, etc.). DPS 112 may present content provider 106 with a portfolio including performance metrics or status of activities. The selection presented to content provider 106 can indicate conversion events (e.g., clicks, page views, etc.) from user device 108, conversion rates (e.g., click-through rate, number of views, app 116 installations following user interaction with interactive elements, etc.), or the cost of activities utilizing the services of DPS 112. (See reference) Figure 2 The DPS112 is described in more detail.

[0063] Now for reference Figure 2The diagram illustrates a block diagram of a DPS according to an embodiment. The DPS 112 may include a communication interface 120 and processing circuitry 130. The communication interface 120 may include a wired or wireless interface (e.g., jack, antenna, transmitter, receiver, transceiver, wired terminal, Ethernet port, WiFi transceiver, etc.) for data communication with local or remote devices or systems. The communication interface 120 may allow the DPS 112 to communicate with components of the computer system 100 (such as network 102, resource 104, content provider 106, user equipment 108, and data storage device 110). For example, the communication interface 120 may allow the DPS 112 to receive or retrieve communications from user equipment (e.g., user equipment 108), user information from data storage device (e.g., data storage device 110), application metadata provided by content provider 106, or resources provided by content publishers. The communication interface 120 may allow the DPS 112 to send or provide data to components of the computer system 100, such as providing generated content items to content slots provided by content publisher 114, sending performance metrics (e.g., conversion rates or historical user interactions with content items) to content provider 106, providing notifications, content items, or web applications to user device 108, or sending data to store or update data storage device 110.

[0064] Communication interface 120 can be configured to receive metadata (e.g., metadata 118) from content provider 106 and / or data storage device 110. Metadata may include, for example, application images (e.g., thumbnail images, low / medium / high resolution images, alternative application images, etc.), application details (e.g., application summary, application description, release date, reviews, application category, etc.), and / or other information from field-value pairs derived from application metadata. In some implementations, content provider 106 may provide additional information to incorporate when generating one or more content items, such as a custom logo, icon, image, or background (e.g., a business or company icon) representing content provider 106.

[0065] Communication interface 120 can be configured to receive user information from user device 108 and / or data storage device 110. User information may include, for example, user-specific information (e.g., user demographics, user preferences, user behavior data, etc.), contextual information (e.g., user location, webpage context, recent page views, etc.), keyword information (e.g., keywords associated with a specific webpage or search query, etc.), and / or other information that DPS 112 can use to generate or select queries and corresponding response selections related to or of interest to a specific user or user device 108 or the applications used by that user or user device 108 (e.g., queries related to applications installed on user device 108 or queries pointing to user preferences when seeking to install a new application on user device 108). Application metadata may be stored on data storage device 110 or the content provider device of content provider 106. Application metadata may be updated in real time, periodically (e.g., checked for updates every 10 minutes, every hour, etc.), or updated in response to queries or responses generated in response to requests for application metadata from DPS 112. For any application metadata update, if stored on data storage device 110, content provider 106 can communicate with data storage device 110 to update the stored metadata. In some implementations, application metadata can be stored locally on the content provider device, allowing DPS 112 to retrieve or request metadata from content provider 106.

[0066] DPS112 may include at least one processing circuitry 130. Processing circuitry 130 may include a processor 132 and a memory 134. DPS112 may perform the features and functions of processing circuitry 130, processor 132, or memory 134 described herein. Processor 132 may be implemented as a general-purpose processor, an application-specific integrated circuit (ASIC), one or more field-programmable gate arrays (FPGAs), a CPU, a GPU, a set of processing components, or other suitable electronic processing components.

[0067] Memory 134 may include one or more devices (e.g., RAM, ROM, flash memory, hard disk storage, etc.) for storing data and / or computer code to perform and / or facilitate the various processes, layers, and modules described herein. Memory 134 may include volatile or non-volatile memory. Memory 134 may include database components, object code components, script components, or any other type of information structure for supporting the various active actions and information structures described herein. In some embodiments, memory 134 is communicatively connected to processor 132 via processing circuitry 130 and includes computer code (e.g., data modules stored in memory 134) for performing one or more processes described herein. In short, memory 134 may include, but is not limited to, a request receiver 136, an application metadata manager 138, a query manager 140, a content item manager 142, a response collector 144, and an application registry manager 146. Components of memory 134 (e.g., request receiver 136, application metadata manager 138, query manager 140, content item manager 142, response collector 144, or application registration manager 146) may communicate electrically with other components of memory 134 to perform the features and functions described herein, including at least generating or selecting queries and interactive elements, generating content items, determining queries or responses to be included in content items, determining the performance of content items, providing activity information or statistics to content provider 106, etc.

[0068] Still referencing Figure 2 More specifically, request receiver 136 can be configured to receive requests from content publisher 114, content provider 106, user device 108, or other components of computer system 100. Request receiver 136 can receive requests for content from at least one of user device 108 or content publisher 114 that provides content slots for content items. For example, request receiver 136 can receive a request to access an application from user device 108. A request to access an application can include at least displaying or showing the application's user interface, one or more content slots within the user interface, or displaying a page within the application. For example, receiving a request to access an application can include a request for a content item. Furthermore, resource 104 can include configurations for content slots, such as the time interval for refreshing the content of a content slot, the time interval for displaying the content slot (e.g., interstitial content slots or notification content slots), or when to disable visibility or terminate the content slot. Content publisher 114 can adjust the configuration of the types of content slots to be provided in the application, the number of content items allowed to be displayed, the time interval for refreshing or displaying content, etc.

[0069] In another example, user device 108 may use data from resource 104 to access an application managed by content publisher 114 to update or execute the application. After accessing the application, user device 108 may display the application's user interface. The application's user interface may include one or more content slots. To populate a content slot, request receiver 136 may receive from content publisher 114 at least one request for one or more content items to be displayed in the content slot. In some implementations, request receiver 136 may simultaneously or concurrently receive requests for access to the application or webpage and requests for content to display or show the user interface of the application or webpage having one or more content items.

[0070] Content slots can be embedded in the application's user interface. Content slots may not be embedded in the user interface, allowing them to be removed, replaced, or moved to different locations on the user interface. Content slots can be configured to appear or disappear, such as enabling or disabling the visibility of the content slot (e.g., this, in turn, enables or disables the visibility of the content items within the corresponding content slot). For example, a content slot can be an interstitial content slot used to display interstitial content items. Interstitial content items can cover most of the user interface of the application displayed on user device 108. Most can refer to 70%, 80%, or 90% of the user interface (e.g., in a window displayed on the display of user device 108). In some implementations, content slots can be banner-type or notification-type content slots that appear after a predetermined time (e.g., 30 seconds, 1 minute, 5 minutes, etc.) following application access. Content slots can appear at the top, sides(s), bottom, or other locations of the user interface. In some implementations, content items or content slots can be transparent or at least partially transparent when displayed for display above a portion of the user interface. For example, content publisher 114 can configure content slots (e.g., the content items to be displayed in the content slots) to be transparent at a certain level of opacity (e.g., 80%, 70%, 60%, etc.). The level of opacity can be configured by content publisher 114. The opacity of the content slots can be reflected in the opacity of the content items displayed in the corresponding content slots.

[0071] Request receiver 136 may receive requests from content provider 106 regarding the activity status or performance of content items generated using application metadata provided by content provider 106. For example, request receiver 136 may receive a request from content provider 106 to generate a report (e.g., a summary report or overview) on activity performance. In response to receiving such a request, request receiver 136 may communicate with other components of content item manager 142, response collector 144, or DPS 112 to generate a summary report on at least conversion events, conversion rates, install rates, activity costs, and other performance data of content items generated using application metadata from the respective content provider 106.

[0072] In some implementations, the request receiver 136 may receive a request for content from either the user device 108 or the content publisher 114. The request for content may include an identifier for a second application, which includes a content slot in which at least one content item is presented. The identifier for the second application may differ from the identifier for the first application, which may be an application running on the user device 108. The first application may originate from the content publisher 114 (e.g., the data for the first application may come from resource 104), and the second application may originate from the content provider 106, such as application 116.

[0073] Request receiver 136 can receive requests to access information resources from user device 108. Information resources may refer to data storage device 110, application pages, store pages, or data accessed from application 116 of content provider 106. For example, a content item may include a link that redirects user device 108 to an installation page for installing a second application or directly installs a second application in response to an interaction received from user device 108. Therefore, request receiver 136 can receive requests to access information resources from user device 108 to install application 116 of content provider 106 when the user interacts with a link presented in the content item.

[0074] Application metadata manager 138 can access or retrieve metadata (sometimes commonly referred to as application metadata) that can be used for installation of one or more applications. Application metadata can be stored in data storage device 110 or on the local device of content provider 106. Metadata can include various field-value pairs, where the value of each field (e.g., description, data, etc.) can be provided, configured, or indicated by content provider 106. Metadata can be associated with content provider 106. Application metadata manager 138 can retrieve metadata from other components of DPS 112 (e.g., query manager 140 or content item manager 142) for generating queries, responses, or content items, for example, for displaying content items in content slots and on user device 108. In some implementations, application metadata manager 138 can access metadata of applications installed on user device 108. DPS 112 can partially use the metadata of installed applications to initiate or provide access to user device 108, where the application may include content slots for displaying content items. In this case, the metadata can be provided or configured by content publisher 114.

[0075] Application metadata manager 138 can receive metadata updates from content provider 106. For example, application metadata manager 138 can receive input values ​​in configuration field-value pairs from the device of content provider 106. In response to a save or application change, application metadata manager 138 can propagate or forward the updated field-value pairs(s) from content provider 106 to any storage device (e.g., data storage device 110 or metadata 118) that maintains outdated metadata for the application. Therefore, when retrieving application metadata, DPS 112 can generate content items with up-to-date query and response information. For example, if the application metadata is stored in a database used for a store page or install page, application metadata manager 138 can send updated metadata corresponding to the application to the database, thereby updating the application information in the store page.

[0076] Application metadata manager 138 can monitor traffic to the store page or install page. Traffic to the install page can include at least browsing, viewing, downloading / installing, timestamps (e.g., the time of browsing, downloading, viewing, etc., including peak or off-peak times), etc. Application metadata manager 138 can monitor traffic from users accessing the store or being redirected to the store, as well as content items displayed to user device 108. For example, application metadata manager 138 can estimate the conversion rate (e.g., click-through rate) or performance of content items to encourage users to browse the install page or download the application from content provider 106.

[0077] Application metadata manager 138 can determine the priority of each field-value pair. The priority of a field-value pair can be based on the likelihood of interaction with the content item when used as a query or response, based on the field-value pair's potential to generate an engaging (or noteworthy) query or response, or based on its relevance to the user (e.g., the context of the application or webpage in which the content item will be presented). For example, application metadata manager 138 can determine the likelihood of interaction for a content item based on historical interaction data indicating the field-value pairs used to generate the content item and the interaction rate (or conversion rate) of the content item determined by recording user interactions with it. In another example, application metadata manager 138 can identify field-value pairs such as the application's name (or title), image, keywords, category, version, or rules / policies. Application metadata manager 138 can prioritize field-value pairs that the user is likely to know or understand, such as images, names, keywords (e.g., for searching for the application on a store page), or categories. When using field-value pairs to generate content items, the prioritization of one or more field-value pairs can at least indicate the engagement, understandability, or prominence of the item (e.g., a query or response). In some cases, such as when prioritizing the application version to generate a query or response, the application version may not be prioritized, because most users may not know the specific version of the application provided by content provider 106. In other cases, application metadata manager 138 may prioritize the application version for generating queries or one or more responses.

[0078] Application metadata manager 138 can generate performance metrics or reports for content provider 106 or content publisher 114. In some implementations, application metadata manager 138 can generate performance metrics or reports for content provider 106 or content publisher 114 based on the performance of content items. For example, for content provider 106, application metadata manager 138 can generate a report that indicates at least the number of content items offered for display or presentation, conversion rates (e.g., visits to the application site after viewing at least one content item), install rates (e.g., user installs after at least one content item is presented), a list of queries and responses used to generate content items, the performance of each query and response pair (e.g., engagement or participation rate for each query), and other summary summaries. Application metadata manager 138 can send the generated reports to content provider 106 upon request (e.g., received from the respective content provider 106) or at predetermined intervals (e.g., daily reports, weekly reports, monthly reports, etc.). For example, the application metadata manager 138 can generate and send performance reports to the content publisher 114, which indicate the count of content items displayed in the content slot over a period of time (e.g., daily, weekly, monthly, etc.), the bids offered for displaying content items (e.g., the total amount from the content provider 106), or the rewards distributed to users (e.g., user accounts or user devices 108 that successfully interact with content items).

[0079] The query manager 140 may be referred to as an entry manager, query generator / selector, or response generator / selector. The query manager 140 can identify one or more entries associated with the application from the content provider 160. Entries may be based on the application's metadata. Entries may include at least one or more queries and one or more corresponding responses. Responses may be referred to as selections, interactive elements, options, or pre-defined buttons corresponding to the queries. Each query may correspond to multiple responses. Users can provide a response (e.g., a reply to a query) by selecting at least one response using their user device 108.

[0080] For example, query manager 140 can select or generate queries and corresponding responses based on field-value pairs of metadata. Using image and name fields as examples, query manager 140 can generate entries with the query "What is the name of this app?", while displaying an image associated with the app. Query manager 140 can generate responses corresponding to this query, such as the correct name of the app and at least one name of other similar apps. Query manager 140 can group the generated set of queries and responses into entries. In another example, using the category field of metadata, query manager 140 can generate the query "What is one of the genres of 'App Name'?". The query can utilize the app's image to display as a content item or input into a content item. Query manager 140 can generate responses with at least one value from the category field of the app metadata, as well as other responses with values ​​not included in the value field of the app metadata. For example, if the category values ​​include action and mystery, query manager 140 can generate responses with values ​​such as action, adventure, space, puzzle, and simulation. In some implementations, query manager 140 can store the generated entries in a database (e.g., data storage device 110). For example, if stored in a database, query manager 140 can select or retrieve entries from the database in response to a request for content received from user device 108 or content publisher 114. In some other implementations, query manager 140 may not store the generated entries in a database. Instead, query manager 140 may generate entries upon receiving a request for content.

[0081] Query manager 140 can identify the performance history of each query (e.g., performance metrics or historical statistics for each entry). For example, query manager 140 can determine the entries (e.g., queries or responses) used to generate content items. For each entry (e.g., each query or the response corresponding to that query), query manager 140 can determine the number of correct or incorrect responses provided by the user. A high percentage of incorrect responses (e.g., 80%, 90%, 95%, etc.) may indicate that the query (or intended response) is confusing or unclear, too difficult, or uninteresting or irrelevant to the user. A high percentage of correct responses may indicate that the query (or intended response) is not challenging, obvious to the user, or self-evident. In some embodiments, query manager 140 may not pick or may select entries with a high percentage of incorrect responses. In some embodiments, query manager 140 may select entries with a high percentage of correct responses. In some other embodiments, query manager 140 may select entries with a moderate level of correct or incorrect responses (e.g., 60%, 70%, or 75% correct).

[0082] In some implementations, for a large number of incorrect responses, query manager 140 may forward the performance history to content provider 106 to, for example, update metadata information (e.g., if the information provided in the metadata is incorrect). Furthermore, based on the performance history, query manager 140 may determine one or more entries to be selected or generated for display in the application's content slots. The metadata used to generate the entries may originate from a second application from content provider 106, rather than from a first application from content publisher 114 that provides the content slots for displaying content items with queries and corresponding responses.

[0083] In some implementations, query manager 140 may receive one or more responses provided by user device 108 from response collector 144. Query manager 140 may feed the responses into a machine learning engine or machine learning model to determine the next item (or query and response) to use. The machine learning model may be referred to as a selection model for selecting a query or corresponding response based on interaction data from user device 108. For example, query manager 140 may feed the user's response history to an item into the machine learning model. The machine learning model may be trained using training data samples (e.g., historical queries and responses, and sample data of user selections). The machine learning model may output an indication of the performance level of each query (e.g., conversion rate, correct selection of response, etc.), which may be sorted or listed as a report. Based on the performance level of each query and response pair, query manager 140 may prioritize the use of one or more items over other items to increase user engagement with content items. Prioritizing items may refer to DPS 112 selecting or generating items more frequently to generate content items for display in the content slot. In some implementations, based on the performance level of each entry, query manager 140 may not generate, retrieve, or provide one or more entries to content item manager 142 to generate content items. Query manager 140 may prioritize entries with higher performance levels (or rank them according to their higher tags). Based on the priority ranking of entries, query manager 140 may determine which entry to generate or select for content item manager 142. In some cases, based on priority ranking, query manager 140 may determine which entry not to generate or select for content item manager 142.

[0084] In some implementations, query manager 140 can select or generate queries or responses personalized to a user or user device 108. For example, query manager 140 can use a selection model (e.g., trained by a machine learning engine using one or more machine learning techniques) to determine the types of items a user is likely to interact with. The selection model can be trained using interaction data from various users associated with various content items generated from different application metadata, such as the type of field-value pairs used, the type of application (e.g., action, puzzle, mystery, adventure, simulation, etc.), the number of available responses, the font size of the queries and responses, and other formats and configurations of the application's content items, as well as the ratio of user interaction with content items. The selection model can be received from user device 108 or trained using user interaction data to determine the user's preferences or types of content items they are likely to interact with or transform. Accordingly, using the selection model, query manager 140 can select queries and responses from a database based on interaction data to personalize (or specialize) for the user. In this way, query manager 140 can provide entries to content item manager 142 to generate content items that can be transformed from user interactions.

[0085] Content Item Manager 142 can select or generate content items that include at least a subset of one or more entries and actionable objects. For example, an actionable object could be a link or hyperlink to the application of content provider 106 for installation. For instance, after receiving an instruction to interact from user device 108, DPS 112 can redirect user device 108 to access a store page or installation page associated with the application of content provider 106. In some cases, the actionable object can be a script that, when selected by the user device, allows the user device to access an information resource. From the information resource (e.g., a store page in a web browser), user device 108 can install the application associated with the content item and / or actionable object.

[0086] Content item manager 142 can generate content items based on entries (e.g., queries and corresponding responses) determined, selected, generated, or provided by query manager 140. Content item manager 142 can format content items based on the type of content slot used to display them. For example, content item manager 142 can shrink the size of entries (e.g., queries, responses, or images) to fit a banner-type content slot, or enlarge the size of entries to cover an interstitial content slot. Content item manager 142 can configure the layout and appearance of content items based on other types of content slots (e.g., notification content slots, playable content slots, etc.) so that the content items look natural to the application or webpage (e.g., similar themes, colors, fonts, text sizes, or seamless insertion). Content item manager 142 can customize the layout of entries in any configuration to fit the content slot and / or application or webpage. In some cases, content provider 106 can provide templates or specify the formatting of content items, allowing content item manager 142 to insert entries based on the template to generate content items. Content item manager 142 can send content items to user device 108, where user device 108 can display the content items. Content item manager 142 can also send content items to content slots provided by content publisher 114, where content slots containing content items can be provided to user device 108.

[0087] Content item manager 142 can make selections based on the identifier of the second application. For example, content item manager 142 can retrieve entries from a database generated using metadata of the second application (e.g., the application of content provider 106). Content item manager 142 can select content items with queries and corresponding responses that have information related to the second application. In the case of selecting a response, content item manager 142 can select one or more responses with information not included in the application's metadata, which can indicate an incorrect response if the user selects these responses. Content item manager 142 can include links or hyperlinks in the content items retrieved from the application's metadata. For example, a link or hyperlink can be referred to as an actionable object used to redirect user device 108 to information resources for installing the second application.

[0088] Content Item Manager 142 can select a subset of one or more items to be included in a content item. This subset may refer to at least one item from the list of items to be included as a query and response. To select items, Content Item Manager 142 can identify the priority of each field from the field-value pairs of the application's metadata. The priority of each field can be set by Query Manager 140 or other components of DPS 112 described herein. For example, the priority of each field can be based on the number of values ​​associated with that field (e.g., a category field may include 2-10 values, a version field may include 1 value, a name field may include 1 value, a rule field may include 5 or more values, a keyword field may include at least 10 values, and so on). The priority of each field can also be based on the number of incorrect (or correct) responses previously received from user device 108 for a content item that includes a query targeting that field. For example, each incorrect selection provided by at least one user when selecting fields for queries and responses to content items may lower the rating or priority of that field. On the other hand, when at least one user provides the correct selection for the response to a content item with a field, the rating or priority of that field can be increased so that the content item manager 142 can select entries to include in that content item.

[0089] In some implementations, the content item manager 142 can manage the visibility of content items. For example, the content item manager 142 can enable the visibility of content items displayed on the user device 108. In response to receiving a correct response from the user device 108, the content item manager 142 can disable the visibility of a content item or the content slot displaying the content item. In some implementations, if the user device 108 sends an indication of selection for an incorrect response, the content item manager 142 can enable visibility or provide a prompt for display on the display device of the user device 108. The prompt may appear in the content slot displaying the content item. The content item manager 142 can maintain the visibility of content items for the user to retry. In some implementations, the content item manager 142 can provide a second content item in response to receiving at least one incorrect response (e.g., a second content item may be provided after multiple attempts). For example, the content item manager 142 can select a second entry or a second subset of one or more entries for inclusion in the content item (e.g., which may replace the previous query and response). In some cases, the content item manager 142 may maintain the same query but select one or more different responses, for example, for a second user attempt. The content item manager 142 may rearrange or shuffle the responses, such as in response to an incorrect selection of a response.

[0090] In some implementations, the content item manager 142 may use a selection model to select a subset of one or more items for inclusion in the content items. For example, the content item manager 142 may use interaction data from user device 108 (e.g., interactions with content items having queries and corresponding responses) as input or a training dataset to train the selection model. Based on the interaction data, the selection model may output the performance of each field in the field-value pairs used to generate or select queries (or responses). The selection model may rate or configure the priority of each field for inclusion in the content items by the content item manager 142. Based on the output of the selection model, the content item manager 142 may select a subset of items based on at least one of, for example, performance, priority, and other information about the items.

[0091] In some implementations, the content item manager 142 may include one or more scripts within the content items. The scripts may execute on the user device 108, for example, in response to a content item appearing in a content slot or displayed on the user device 108 (e.g., 1 millisecond (“ms”), 10 ms, 50 ms, or shortly thereafter). The scripts may cause the user device to perform the features or functions described herein. For example, the scripts may cause the user device 108 to present a subset of one or more items within the content slot, such as at least one query and various responses corresponding to the query. The scripts may cause the user device 108 to detect interactive data from the selection of one or more interactive elements associated with a subset of one or more items. This selection may be initiated or provided by a user of the user device 108. The scripts may cause the user device 108 to provide the interactive data detected from the selection of one or more interactive elements within the content slot to the DPS 112. Sending or providing data to DPS112 can be directed to at least one component of DPS112 (e.g., request receiver 136, application metadata manager 138, query manager 140, content item manager 142, response collector 144, or application registration manager 146).

[0092] Content item manager 142 can include a termination icon or object within a content item. Content item manager 142 can configure the duration for which the object is visible to or interactive with the user device 108. For example, the termination icon may appear after a predetermined time period (such as 10 seconds, 12 seconds, 15 seconds, etc.) following the display of the content item. In some cases, content item manager 142 can include the termination icon with other elements of the content item, such as displaying it alongside other elements of the content item (e.g., queries, images, interactive elements, etc.). Content item manager 142 can terminate or disable the visibility of the content item in response to user interaction with the termination icon.

[0093] In some implementations, the content item manager 142 may include or provide an image corresponding to a reward in the content item (e.g., an incentive for participating in or interacting with the content item). In response to DPS 112 receiving a selection of a correct response displayed in the content item, the reward may be presented to user device 108. The content item manager 142 may include a script in the content item that enables user device 108 to detect first interaction data from selections of one or more interactive elements (e.g., responses) associated with a subset of one or more items. The interactive element associated with the subset of items may refer to an interactive element corresponding to a query included in the content item. In some implementations, the script may enable user device 108 to determine that the selection indicates an incorrect response or selection of an interactive element. The script may enable user device 108 to provide a notification indicating an incorrect selection to user device 108 (e.g., a display device electrically connected to user device 108). In some implementations, the script may enable user device 108 to detect second interaction data from selections of other one or more interactive elements associated with a subset of one or more items. The script may enable user device 108 to determine that the selection is correct or that the selection indicates a correct interactive element. The script can cause user device 108 to present an image corresponding to a reward in response to determining that second interaction data corresponds to a correct response. After presenting the reward, DPS 112 can communicate with resource 104 of a management application or content publisher 114, which provides a content slot for displaying the content item to user device 108. DPS 112 can instruct the user to provide a correct response to the content item. DPS 112 can retrieve or receive rewards from resource 104 or content publisher 114 to provide to the user account concurrently with or in response to the image of the reward being displayed. The type of reward provided to the user may vary depending on the application in which the content slot is presented or based on the configuration of content publisher 114. In some implementations, DPS 112 can execute one or more features and functions of user device 108 initiated by a script included in the content item, such as determining whether the interaction data indicates a successful (e.g., correct) or unsuccessful (e.g., incorrect) selection of an interactive element associated with the item.

[0094] In some implementations, the content item manager 142 may include scripts within the content items that enable user device 108 to send instructions to content provider 106, in response to determining that the correct interactive element has been selected, to provide application metadata for generating the entries included in the content item. For example, the instructions sent to content provider 106 may include updates to values ​​corresponding to performance metrics of the content item generated using metadata from the application of content provider 106. By sending these updates, content provider 106 may be notified of, for example, the performance of each field used to generate the content item, updated conversion rates, user device 108 that installed the application after the content item was presented, user impressions of the content item based on the metadata of content provider 106, or other information / reports that may be presented to content provider 106.

[0095] Response collector 144 may receive input or responses from user device 108. For example, response collector 144 may receive input indicating a selection of an interactive element of a content item (e.g., a predetermined response displayed in the content item). Response collector 144 may receive a selection of an actionable object included in the content item (e.g., for redirecting user device 108 to an application page or installation page). Response collector 144 may receive input that corresponds to a correct interactive element associated with the content item, or it may correspond to an incorrect interactive element associated with the content item. Response collector 144 may receive input indicating a selection corresponding to a pixel position or location displayed on the content item on user device 108. Each interactive element may be associated with a set of pixels displayed in a content slot as part of the content item. In this case, receiving a selection of an interactive element may mean receiving input at a pixel position corresponding to the set of pixels associated with the interactive element (e.g., a button press, finger press, or tap at the mouse pointer position). Accordingly, response collector 144 may identify the interactive element selected by user device 108.

[0096] The response collector 144 may receive input from the user device 108 to terminate, turn off, or disable the visibility of content items displayed on the user device 108. For example, the content item may include a stop button, icon, or element. The response collector 144 may receive input from the user device 108 indicating a selection of the stop button. Accordingly, the DPS 112 may terminate or disable the visibility of the content item in response to receiving such input. The input received by the response collector 144 may be referred to as interactive data from the user device 108.

[0097] Response collector 144 can receive interactive data (e.g., input, selection, or user engagement indications) from user device 108 that indicates the selection of an interactive element among various interactive elements corresponding to an entry or query. Response collector 144 can determine whether the interactive data indicates a correct or incorrect response to the query. Based on whether the response is correct or incorrect, response collector 144 can update the selection model used to select one or more entries for generating subsequent content items, such as selecting entries based on the interactive data from user device 108. For example, based on the interactive data, the selection model can select one or more entries where a moderate number of users select correct responses (e.g., 70%, 75%, or 80% correct responses). In some cases, such as a large number of incorrect responses received from users, the selection model can select one or more entries, such as to increase user understanding of the application or to determine whether to notify content provider 106 of potential errors in the metadata used to generate content items.

[0098] Response collector 144 may send response or interaction data received from user device 108 to other components of DPS 112. For example, response collector 144 may send interaction data to query manager 140 to generate or select one or more queries based on fields that the user is likely to interact with or engage with. Additionally, response collector 144 may send interaction data to query manager 140 to determine or update the priority of each query, or to identify the performance of fields. Response collector 144 may send interaction data for content item manager 142 to select one or more items to include in content items based on the performance of each item, the priority of the item, and other performance metrics of past content items and user interactions. In some implementations, response collector 144 may send interaction data to application registry manager 146 to determine amounts charged to content provider 106, amounts transferred to content publisher 114, etc.

[0099] Application Registration Manager 146 can manage the registration or enrollment of services, features, or functions provided by DPS 112 by content provider 106 or content publisher 114 (e.g., generating content items based on metadata from content provider 106, or presenting content items in content slots provided by content publisher 114). Through the registration service, DPS 112 can be authorized to access the metadata of applications managed by the registered content provider 106. Furthermore, through the registration service, DPS 112 can publish or provide generated content items to available content slots provided by content publisher 114. Through registration, content publisher 114 can configure what reward to provide after a user successfully responds to a query for a content item. Content publisher 114 can configure the type of content slot, the frequency of providing content slots, the time of providing content slots, etc.

[0100] In some implementations, the application registry manager 146 may be referred to as a rewards manager. The application registry manager 146 may provide rewards to a user. For example, the application registry manager may provide a reward to user device 108 or a user account in response to receiving a correct response from user device 108. To provide a reward, the application registry manager 146 may request that a reward from content publisher 114 be presented or entered in the user account associated with the user who provided the correct response (e.g., correct selection of an interactive element in a content item). In some implementations, the DPS 112 may provide a reward to the user after consecutive attempts, such as based on a predetermined time (e.g., 2 minutes, 5 minutes, 7 minutes, etc.) or a number of attempts (e.g., 3 attempts, 5 attempts, etc.).

[0101] For example, if a user interacts with a content item (or various content items) for a predetermined time, DPS112 may reward the user for their effort to respond to the query, even if the response is incorrect. In another example, DPS112 may reward the user after multiple attempts to provide a correct response. In some implementations, DPS112 may not provide any reward unless the user provides a correct response or selects the correct interactive element associated with the item. In some implementations, DPS112 may not reward the user even after the predetermined time or attempts if the user does not demonstrate an effort to provide a correct response (e.g., a quick click after providing a second content item, repeated clicks on the same interactive element, or no mouse movement). The reward may be provided to the appropriate application executing on user device 108. In some implementations, to present the reward, a script included in the content item may be executed on user device 108, allowing user device 108 to display the reward. The script may be executed in response to any of the above-discussed conditions for providing a reward.

[0102] Therefore, by generating queries and responses from the metadata accessible to DPS112 and using the metadata to generate content items, DPS112 can reduce resource consumption (e.g., reduce the amount of data stored in the database used to generate content items), reduce network traffic or network congestion (e.g., the amount of data sent to and received from content provider 106), and reduce the time consumption of content provider 106 (e.g., content provider 106 does not need to generate such queries and responses, arrange the content of content items, or update their list of queries and responses).

[0103] Now for reference Figure 3This illustrates an example table of field-value pairs for application metadata according to an implementation. The table of field-value pairs can be combined by one or more components of system 100 (e.g., resource 104, content provider 106, user device 108, data storage device 110, DPS 112, or content publisher 114). Figures 1-2 Or any other computing device described herein for use, configuration, or otherwise maintenance. Table 300 may include various field-value pairs of metadata from the application. The application may be managed by a content provider (e.g., content provider 106) or a content publisher (e.g., content publisher 114). In this example, Table 300 may include field-value pairs of metadata from the application (e.g., metadata 118 of application 116) from the content provider. Table 300 may include various fields 302A-302N (sometimes collectively referred to as fields 302) and associated values ​​304A-304N (sometimes collectively referred to as values ​​304).

[0104] For example, field 302 may include at least a name, category, keywords, image, description, URL, rules (or policies), app size, download count, latest version update, etc. Each field 302 may include corresponding pairs of values. The value of the name field may include various characters or text that identify the name of the app (e.g., "Call of Duty"). The value of the category may include a list of the app's genre or classification (e.g., action, adventure, puzzle, mystery, 3D, simulation, first-person shooter ("FPS"), multiplayer online ("MMO"), cooperative, romance, role-playing ("RPG"), etc.). The value of the keywords field may include one or more terms that one or more user devices (e.g., user device 108) may enter when trying to find the app, such as in resources (e.g., resource 104), websites, app stores, or other online locations (e.g., "Call of Duty", "Call of Duty", "Call of Duty", "Call of Action", etc.). The value of the image field may include image data or files, such as one or more JPGs, PDFs, GIFs, and other image files used for downloading and displaying app images (e.g., profile images, background images, etc.). The description field value can include a textual description of the application generated or provided by the application's administrator or developer (e.g., a content provider or publisher). The textual description can include a brief summary detailing the application's story or type when the application is executed. For example, the URL field value can include one or more links to at least one of the application's store page, install page, web page, or other pages or sites associated with the application.

[0105] In a further example, the value of the rules or policies field may include various descriptions of the rules for using the application, such as how to navigate the application's user interface, user agreements and privacy policies associated with installing or using the application, rules (or controls, instructions, or key bindings) for utilizing the application or controlling elements (e.g., characters or items) within the application, and other rules guiding users to use the application properly. The value of the application size field may include a numerical value indicating the file size or disk space consumed when downloading or installing the application (e.g., the size of a compressed or uncompressed file). The value of the download count may include numerical values ​​indicating the total number of user profiles that downloaded the application, the total number of users who purchased and downloaded the application, the total number of user devices to which the application was downloaded or installed, and other variables that may be used to determine the download count (e.g., whether a reinstallation or re-download from the same user profile or user device can or cannot be counted as an additional recorded download). The value of the latest version update field may include the current version number of the application. Content providers may update the version number in response to releasing updates to the application installation files (e.g., releasing updated files to the application page or store page for users to install before using the application).

[0106] The field-value pairs discussed in this article can be updated by content providers, such as by updating app metadata provided to store pages from which apps can be downloaded or installed. Any updates to app metadata can be reflected in field-value pairs, where at least some of these pairs can be displayed on the app page, such as at least the name, category, image, description, app size, number of downloads, or the app's current version number.

[0107] As discussed herein, one or more components of system 100 (e.g., DPS 112) can utilize field-value pairs of metadata to generate one or more queries, corresponding responses, or content items. For example, name field-value pairs (sometimes commonly referred to as pairs) can be used by the DPS to generate a query “What is the name of this application?” that simultaneously displays an application image from an image pair. Using the generated query, the DPS can generate multiple corresponding responses, including at least interactive elements with values ​​from the name pair (e.g., “Call of Duty”) and other interactive elements with other application names (e.g., “Flame App”, “Live Mission”, etc.). For example, other names for other applications can be selected based on other applications having one or more similar pairs (such as similar categories, keywords, names, developers, etc.). In some implementations, the selection of other names for other applications can be performed randomly by the DPS. In some implementations, similar techniques can be performed to select other interactive elements to be included as part of the response (e.g., when generating queries using other field-value pairs).

[0108] In another example, DPS can use combinations of name and category pairs to generate query "references". Figure 4 The illustration shows an example of an interactive content item according to an implementation. One or more components of system 100 (e.g., resource 104, content provider 106, user device 108, data storage device 110, DPS 112, or content publisher 114) are combined. Figures 1-2 Alternatively, any other computing device described herein may run, perform, or implement the example operations presented or otherwise described in Figure 400 that generate one or more elements. Example Figure 400 may include examples of content items, such as content items 410, 420, and 430. When describing Example Figure 400, these content items (e.g., content items 410, 420, or 430) may be referred to as a first content item, a second content item, or a third content item.

[0109] Each content item described herein may be generated or selected by a DPS (e.g., DPS112) using application metadata provided by or retrieved from one or more content providers (e.g., content provider 106). Each content item may include a query generated by the DPS and multiple corresponding responses. At least one response may correspond to a value paired with a corresponding field in a field-value pair from the metadata, while other responses may not correspond to a value from that field. Other responses may be values ​​excluded from or not included in the corresponding field-value pair from the metadata. Responses may be interactive elements that, when displayed in a content slot, allow a user to interact with the interactive element (e.g., within pixel coordinates identifying each interactive element) to select at least one response (e.g., mouse clicks, touch gestures, etc.). Examples of queries and corresponding responses that may be included in one or more content items are described herein.

[0110] In some implementations, content item 410 may be a quiz-type content item that includes one or more questions associated with one or more correct answers (or alternative answers). For example, content item 410 may include the query “What category does ‘App’ belong to?”. Instead of “App”, the query may include the name of the app. The DPS may retrieve the name from the app metadata (e.g., data from the value corresponding to the name field). In this example, the DPS may use at least the category field as part of content item 410. Since the query instructs the user (e.g., from the category field of the metadata) to select a category, the DPS may include at least one value corresponding to the category field from the metadata in content item 410. The DPS may include other values ​​that are not included in the metadata and are set to incorrect interactive elements or responses. For example, if “App” has the categories Puzzle and Mystery, the DPS may include Puzzle or Mystery as one of the responses (or interactive elements). Other interactive elements may include categories that are not Puzzle or Mystery, such as Adventure, Action, etc.

[0111] Content item 420 may include the query “Which developer does ‘App’ belong to?”. In this example, DPS may include a value from the developer field as part of content item 420. Because the query instructs the user to select or identify the developer of the “App”, DPS can select or generate at least one response to a developer associated with the “App”, and one or more other responses to developers mentioned in content item 420 that are not associated with the “App”. The app of content item 420 may differ from 410, depending on the content provider from which the metadata originates.

[0112] Content item 430 may include the query "Is 'App' a free app?". In this example, DPS may include a value from the price field (sometimes called the purchase field or cost field) as part of content item 430. The price field value may include pricing data for the app, such as the amount to be paid before downloading, installing, or otherwise utilizing the app's features. In this case, DPS may include a "yes" or "no" response. The total number of interactive elements can be set by the content provider or the DPS administrator. In some cases, the number of interactive elements may be based on the size of the content slot, allowing DPS to include fewer interactive elements in smaller content slots (e.g., 2 or 3) or more interactive elements in larger content slots (e.g., 4 or more).

[0113] In some implementations, the DPS may include "Maybe," "Skip," or "I don't know" as one of the responses or interactive elements that the user can choose. For example, the DPS may include one or more alternative responses (or alternative elements) that might be common when considering any query presented to the user. Alternative responses may include common responses that might be expected from the user when providing any query, such as "Maybe," "Skip," "Unsure," "Next," etc. In response to one or more of these alternative responses, the DPS may determine whether to provide any additional content items to be displayed to the user, terminate the content item, or provide a reward associated with the content item from the content publisher providing the content slot (e.g., different content items may provide different levels of reward). For example, if the user selects the "Maybe" interactive element, the DPS may provide the user with a second content item. If configured by an administrator, content provider, or content publisher, repeated selection of the "Maybe" interactive element may terminate the content slot without the user receiving any reward. In another example, a selection of "Unsure" may be a valid response in some cases, and the DPS may provide or execute a reward for the user in response to receiving one or more interactive element selections.

[0114] refer to Figure 5 This illustration shows an example of a client device displaying interactive content items within a first application according to an embodiment. One or more components of system 100 (e.g., resource 104, content provider 106, user device 108, data storage device 110, DPS 112, or content publisher 114) are combined... Figures 1-2 Or any other computing device described herein may run, perform, or implement the example operations of displaying, generating, or presenting one or more elements shown or otherwise described in Figure 500. Example Figure 500 may include a client device displaying a first instance 510, a second instance 520, or a third instance 530. Each instance may represent the state of a client device or the moment when a client device displays an application, content item, or rewards interface. For example, first instance 510 may include a client device displaying a first application. Second instance 520 may include a client device displaying a content item. Third instance 530 may include a client device displaying a rewards interface.

[0115] In the first instance 510, a user of the client device can launch or access a first application. The first application can be displayed on the client device's screen (e.g., in full-screen, borderless full-screen, or windowed mode). The first application can be any application, such as an application locally installed on the client device, a web browser application, a virtual desktop application, an application running on a server, etc. The first application can be provided by a content publisher (e.g., the data for the first application can come from the content publisher's resources). The first application can include one or more content slots displayed in a portion of the application interface. In some cases, such as for instantiated content slots, the content slots may be visible some time after the application is launched. In some implementations, such as in the second instance 520, the content slots can display instantiated content items, wherein the DPS managing the content items can enable the visibility of the content slots based on the configuration of the first application's resources.

[0116] In the second instance 520, the client device may display a content slot with content items. For example, the client device may display a content slot enabled based on a timer (e.g., a set time since the application configured by the content publisher and other technologies for presenting content items to the user was launched). The content slot may include a script that, when executed on the client device, causes the client device to send a request to the DPS for at least one content item. The DPS may provide the content item to the content slot displayed on the client device. In this case, the content item may include a section 522 with a query (e.g., a question) and one or more corresponding responses (e.g., a set of answers or options for the user to choose from), an exit icon 524, and an actionable object 526 (e.g., a button or other interactive element) with a link or hyperlink to a second application (e.g., a webpage or store page for installing the second application). In some cases, the content item may include a marker 528 that highlights the response or hovers over the response. The marker 528 may indicate that the corresponding response will be selected, for example, if the user clicks or presses a selection button (e.g., Enter, Space, and other buttons based on the settings of the first application or content item). In some implementations, marker 528 may not be part of the content item, but rather an indicator for navigating to select interactive elements, actionable objects 526, exit icon 524, or mouse icons for other areas to be displayed.

[0117] DPS can generate content items in the second instance 520 from metadata of an application (e.g., a second application) from a content provider. DPS can generate queries and one or more corresponding responses based on the application's metadata. For example, a content item could include the query "What genre is 'Second Application'?". In this case, "Second Application" could be replaced with the name or title of the application from the content provider. DPS can retrieve the application's name from the value of the name field in the metadata's field-value pairs. In this case, DPS uses the metadata's genre field (e.g., category field) and name field to generate the query. Because DPS uses the application's genre as a prerequisite for the user's choice of response, DPS can select at least one value from the genre field to include as one of the interactive elements. For other interactive elements, DPS can include other genres (or values) not indicated in the field-value pairs. For example, if the genre field from the second application's metadata includes adventure, mystery, and nonfiction, DPS can select action as one of the interactive elements. DPS can select genres not presented in the field-value pairs (e.g., action, mystery, etc.) to include as part of an interactive element (e.g., associated with an incorrect response).

[0118] Referring to the previous example, a user can interact with a client device to place a tag 528 in one of the responses (such as the "Adventure" genre). Since "Adventure" is part of the genre field of a second application (e.g., metadata of the second application), the DPS can determine that the user's selection (or response) is correct. Accordingly, in response to the user selecting the correct response, the DPS can provide a reward interface for display in a content slot. The reward interface can replace the content item used to display the content slot. In some implementations, the DPS can provide a content item that includes scripts for display in the content slot. In response to the user's selection of the correct response, the script of the content item can be executed on the client device, which can cause the client device to display an image corresponding to the reward, where the reward can be provided to the user's account in the first application. In some implementations, if the user selects an incorrect response, the script can cause the client device (e.g., in the content slot) to provide a notification indicating that the selection was incorrect. The content item can remain in the content slot for the user to reselect a second interactive element after an incorrect selection. In some cases, after notifying the user of an incorrect selection, the DPS can replace the content item with another content item.

[0119] In some implementations, the DPS can reward the user's account even if the user does not select the correct response. For example, the DPS can determine that the user is actively engaging with the content item (e.g., attempting to select the correct response for the content item, hovering the cursor over / moving the cursor over the interactive element, selecting an incorrect response, attempting to select the correct response for a second content item, etc.). After a period of time (e.g., 30 seconds, 1 minute, etc.), the DPS can determine to reward the user's effort. In some implementations, the reward may be different if the user does not select the correct response (e.g., fewer coins or lower item rarity).

[0120] In the third instance 530, the client device may display a reward interface in response to the user selecting the correct response. Concurrently with or in response to displaying the reward interface, the DPS may send an instruction to the first application to retrieve a reward corresponding to the reward interface (e.g., an item or object similar to the image) and provide the reward to the user account. In some implementations, the DPS may retrieve the corresponding reward stored in resources, allowing the DPS to provide the reward to the user account in response to the user selecting the correct response or displaying an image with a reward.

[0121] Throughout the second instance 520 or the third instance 530, the DPS may maintain an exit icon 524 and an actionable object 526 for display in a content slot. For example, at any time the content slot is visible or enabled on the client device's display, the user can interact with the exit icon 524 to terminate the content slot or content item. In some implementations, the DPS may insert the exit icon 524 into the content slot or content item after a period of time (such as 15 seconds after the content slot becomes visible on the client device). In some implementations, the DPS may insert the exit icon 524 after the user's first attempt to select an interactive element. The actionable object 526 may be included anywhere within the content slot (or content item), such as at the bottom of the content item. In some cases, the DPS may include the actionable object 526 as a second content item in the same content slot, such that the link to the second application is separate from the content item associated with the second application's metadata. By displaying the actionable object 526 throughout the presentation of the content item or rewards interface, the DPS may, for example, provide the user with the opportunity to be redirected to the installation page of the second application in response to interaction with the actionable object 526. For example, actionable object 526 may include a script that, when executed, can cause the client device to redirect to a page associated with or linked to actionable object 526.

[0122] In some implementations, the DPS may terminate the content item and / or content slot after the duration of the reward presentation to the user (e.g., if the user selects the correct response). For example, after 10 seconds of presenting the reward interface, the DPS may terminate the reward interface and content slot to allow the user to continue using the first application. In some implementations, the DPS may terminate the content item and / or content slot in response to the number of times the user fails to select the correct response or the number of times the user selects an incorrect response. For example, after a predetermined number of incorrect responses (e.g., 3 attempts, 5 attempts, and other numbers configured by the DPS), the DPS may terminate the content item and content slot after notifying the user of an incorrect selection (e.g., 5 seconds after the prompt). In some implementations, the appearance of the content item may be based on the metadata of the second application. For example, the background of the content item may include an image of the second application or include colors that match the image of the second application.

[0123] refer to Figure 6 The diagram illustrates a flowchart of an example method for generating queries and responses based on application metadata, according to an implementation. The functionality of method 600 described herein can be derived from, for example... Figure 1 One or more components of the computer system 100 shown, such as Figure 1 and Figure 2 The DPS112 shown, as well as other computing systems or any combination thereof, are used to perform or otherwise operate. In some implementations, at least in combination with... Figure 1 and Figure 2 The functionality of method 600 can be split among one or more components of computer system 100. Method 600 may include: in step 605, the DPS receives a request for content. In step 610, the DPS can access metadata for one or more applications. In step 615, the DPS can identify various field-value pairs. In step 620, the DPS can determine if the metadata is up-to-date. In step 625, the DPS can update the field-value pairs. In step 630, the DPS can identify one or more entries associated with one or more applications. In step 635, the DPS can select a content item. In step 640, the DPS can send the content item for display on a client device.

[0124] For more detailed information, please refer to [link / reference]. Figure 6In step 605, the DPS can receive a request for content from the client device. In some cases, the DPS can receive the request when the client device initiates the content publisher's application. In other cases, the DPS can receive the request when the application renders content slots, which allows the client device to send a request for content to the DPS. The application's content slots can be rendered during startup or after a time period configured by the content publisher. For example, the content publisher can set a timer for providing certain types of content slots (e.g., banners, interstitials, etc.). After receiving the request for content, the DPS can proceed to step 610.

[0125] In step 610, the DPS can access metadata for one or more applications that can be installed. By accessing this metadata, the DPS can provide at least one content item for display in a content slot, which can incentivize users of client devices to install the application associated with the content item (e.g., a query, response, or actionable object associated with the application). The metadata for each of the one or more applications can include multiple field-value pairs, each containing values ​​received from a device corresponding to the publisher of that application (e.g., a content publisher). For example, a content publisher can include one or more values ​​in at least one field for publishing content items that include queries and responses based on field-value pairs in the content slot. In this case, for example, the content publisher can help provide or configure at least interactive elements or queries against the content item.

[0126] In some cases, the publisher's application (e.g., a content publisher providing content slots for displaying content items) may be referred to as the first application. For example, a client device may launch the first application and request content items from content slots within the first application. In some implementations, a content request from the client device may include at least an identifier of a second application (e.g., the content provider's application). The content request may include an identifier of the content slot in which the content items are presented. For example, the DPS may receive a content request from the client device. From this request, the DPS may identify from which application (or application metadata) the entries were generated, including entries within content items, or identify from which application (or application metadata) the content items with queries or responses associated with the application's metadata were selected. After accessing the application's metadata, the DPS may proceed to step 615.

[0127] In step 615, the DPS can identify various field-value pairs. These field-value pairs can be stored as part of the metadata for each application. Field-value pairs can be retrieved directly from the content provider providing the metadata or from a data storage device located remotely from the content provider. Field-value pairs, including field names and values ​​associated with each field, can be presented in information resources associated with the content provider (such as the application's webpage, installation page, or app store page). Using the field-value pairs, the DPS can generate one or more entries. Each entry can include a query and a corresponding response to that query. Entries can be stored in a database. In some implementations, entries can be temporarily stored in a database in response to receiving a request for content and generating an entry for that content. In this case, the entry can be removed or deleted after it has been used to generate one or more content items or after one or more content items have been presented on a client device (e.g., after the content item ceases to be displayed on the client device).

[0128] Content providers can update field-value pairs. For example, a content provider can edit a store page or webpage associated with the application. The content, data, or information in at least one page can be metadata for the application. By updating the page, the content provider can update the application's metadata. The DPS can retrieve the most up-to-date metadata for generating content items, where outdated content items may not be stored for subsequent requests for content. In this case, the DPS can proceed to step 620 to determine the state of the metadata, for example, if the metadata is not reflected in one of the data storage devices or resources after the content provider provides updated metadata. In some implementations, if the DPS retrieves metadata from the storage device associated with the content provider, where the metadata is up-to-date and the DPS does not perform this check, the DPS can proceed to step 630.

[0129] In step 620, the DPS can determine whether the metadata is up-to-date. For example, metadata for one or more applications may be stored in a data storage device located away from the content provider's device. The DPS or other processing systems can utilize the metadata from the data storage device instead of communicating directly with the content provider's device. Therefore, the DPS can determine whether the metadata is up-to-date to retrieve the latest information. The DPS can determine whether the content provider has updated metadata that is not reflected in the metadata stored in the data storage device. For example, if the DPS relies on metadata from the data storage device, the DPS can determine whether the metadata is outdated (e.g., last updated 30 hours ago, 1 week ago, etc.) and synchronize the metadata based on the latest updated metadata. In some implementations, the DPS can retrieve metadata directly from the content provider's application installation page, thus having the latest up-to-date metadata. In these implementations, the DPS can skip checking whether the metadata is up-to-date and proceed to step 630. However, in the presence of a device using metadata from the data storage device, if the metadata is not up-to-date, the DPS can proceed to step 625.

[0130] In step 625, the DPS may update field-value pairs. For example, the DPS or other processing system may rely on metadata from a data storage device (e.g., a content provider device) located remotely from the content provider. The DPS may communicate with the content provider to synchronize metadata from the content provider to the metadata stored in the data storage device. When the metadata is updated, the field-value pairs of the metadata can be updated to generate queries, corresponding responses, and / or content items. After updating the metadata, the DPS may proceed to step 630.

[0131] In step 630, the DPS may determine one or more entries associated with one or more applications. The DPS may determine one or more entries from the metadata of one or more applications. One or more entries may include one or more queries and corresponding one or more responses. In some cases, determining one or more entries may refer to the DPS generating one or more entries from metadata in response to a request for content, within a predetermined time period (e.g., 1 day, 2 days, 3 days, etc.), or in response to an update of metadata. In some implementations, if the entries are stored in a data storage device, the DPS may refresh, update, or otherwise replace currently stored entries with updated entries based on the metadata of one or more applications. By determining the entries, the DPS may identify at least one entry to include in a content item. In some implementations, determining the entries may refer to determining the context of a content item. For example, an entry may be included as part of a content item. The DPS may determine the entries of a content item for selecting which content item to display on a client device. After determining the entries, the DPS may proceed to step 635.

[0132] In step 635, the DPS can select a subset of entries and content items comprising actionable objects. The subset of entries may include at least one entry containing a query and a corresponding response. The number of responses may vary, such as based on the query (e.g., fields(s) used to generate the query), the size of the content slot, or the preferences of the content provider or publisher (e.g., configurable by the content provider or adjustable by the content publisher publishing the content item). When the client device selects an actionable object, the actionable object (or a script included in the actionable object) can enable the client device to access information resources from which one or more applications can be installed. For example, an actionable object may include a hyperlink associated with a content provider's application (such as the content provider's or application's installation page, store page, or webpage). When selected, the client device may be redirected to the corresponding information resource.

[0133] In some implementations, the DPS can select content items based on the identifier of a second application. For example, the DPS can receive a request for content with the identifier of a second application (e.g., an application of a content provider). Based on which application is identified, the DPS can select content items generated from the metadata of the corresponding application identified by the identifier of the second application. In some implementations, the DPS can select content items based on the type of content slot used to display the content item. For example, the content slot may vary in size, shape, location, or the time at which the content slot appears on the client device. Based on the content slot, the DPS can determine which content item to select, such as how much response should be included, the context of the content item (e.g., to match the context of the first application at the time, which may change based on events in the first application), the type of content item that will be relevant to the user, and other criteria for selecting the content item.

[0134] In some implementations, instead of selecting content items, the DPS can select a subset of one or more items to include in a content item (e.g., thereby generating a content item). The DPS can select each item in the subset by identifying the priority of each field from the field-value pairs of the application's metadata. For example, based on the priority of each field, the DPS can select the highest priority item in the priority list or at least one highest priority item. By selecting at least one of these items, the DPS can generate a content item. Priorities can be assigned at least based on the number of values ​​associated with the field or the number of incorrect responses previously received from client devices for a query that includes a content item targeting that field. For example, for a larger number of values ​​associated with a field, the DPS can generate more responses for each query based on that field (e.g., category field, description field, rule field, keyword field, etc.). For a smaller number of values ​​associated with a field, the DPS may not generate many responses to include in a content item (e.g., version field, download count field, application size field, etc.). However, this may not be the case, and even if the number of values ​​is small, for example, if the category field has only one value, the DPS can still prioritize that field because it can include other responses as part of the interactive elements, or if the DPS can generate responses that can be noticed by the user.

[0135] In another example, the DPS can adjust field priority based on the number of incorrect responses. The number of responses can refer to a ratio, count, or other metrics used to monitor user choices. If a field used for a content item entry receives a large number of incorrect responses (e.g., 8 / 10 of responses or more than 1000 incorrect responses over a day or week), the DPS can assign low priority to that field, such as when generating or selecting other entries or content items. In some implementations, the DPS can adjust field priority based on the number of correct responses. For example, the DPS can determine that for a content item using a certain field(s) as an entry, the percentage of users selecting correct responses exceeds 95%, and other thresholds that can be configured by the DPS or the content provider. For example, instead of setting high priority for fields with the highest correct response rate, the DPS can assign medium priority to these fields, making the content item incentivize understanding of a second application rather than providing a free reward. In some cases, the DPS can automatically lower the priority of certain fields with the highest number of correct responses, making other fields available for content items. In some cases, the DPS may not select one of the highest-priority entries, but may select lower-priority entries. For example, to test whether the priority of a field or entry should be moved up, DPS can use lower-priority fields to generate or select content items. DPS can perform this selection, for example, once a week, once a month, or once within other time ranges. In some cases, DPS can disable this feature, allowing DPS to select content items with fields within a specific priority range (e.g., the first 10 or 20 fields).

[0136] By generating queries and responses from metadata accessible to DPS and using the metadata to generate content items, DPS can reduce resource consumption (e.g., reducing the amount of data stored in the database used to generate content items), reduce network traffic or congestion (e.g., the amount of data sent to and received from content providers), and reduce time consumption for content providers (e.g., content providers do not need to generate such queries and responses, arrange the content of content items, or update their lists of queries and responses).

[0137] In step 640, the DPS may send content items to the client device for display on the client device. For example, the DPS may send data of content items, which at least have a query, a response, and an actionable object, to a content slot. The content slot may display the content items for display on the client device. The DPS may receive input from the client device to select at least one interactive element (e.g., a corresponding response) from the content items. The DPS may determine that the input corresponds to a correct response associated with the content item. In some cases, the DPS may terminate the display of the content items on the client device after input corresponding to a correct response. In other cases, the DPS may disable the visibility of the content items displayed on the client device.

[0138] In some implementations, the DPS can use a selection model to select a subset of one or more items for inclusion in content items. The selection model can be trained using historical interaction data from client devices with content items previously generated and presented to the client devices. Using the selection model, the DPS can determine which subset of one or more items is of interest to the corresponding user and is likely to lead to user interaction (e.g., incentivizing or increasing user engagement). For example, the DPS can receive interaction data with content items presented on client devices. The interaction data can identify responses selected at the client device to indicate whether the response corresponds to a correct or incorrect response associated with the content item. The DPS can update the selection model used to select items for various client devices based on the interaction data from the client devices. For example, if the DPS receives interaction data from a client device indicating an incorrect response, and in some cases, interaction data from other client devices tends to (e.g., 8 / 10) indicate incorrect responses, the DPS may not select items where client devices tend to select incorrect responses. In some implementations, the DPS can determine from the interaction data that client devices have selected the same potentially incorrect responses. In this case, the DPS can notify the content provider to confirm the accuracy of the metadata. Accordingly, DPS can maintain or increase the accuracy of the metadata of the content provider's application.

[0139] In some implementations, content items may include scripts. Scripts may execute on the client device in response to at least one event occurring on the client device or in response to a content item (such as enabling a content slot on the client device for displaying the content item, entering a content item in the content slot, or interacting with the content item). Scripts may cause the client device to perform one or more features and functions described herein. For example, a script may cause the client device to present a subset of one or more items within a content slot (e.g., presenting a query and response within a content slot, or presenting at least one content item with one or more items). The client device may detect interaction data from a user's selection of one or more interactive elements associated with a subset of one or more items. Interactive elements may be or include one or more responses corresponding to an item. The client device may provide the DPS with the interaction data detected from the selection of one or more interactive elements within the content slot. The interaction data may indicate whether the selected interactive element is a correct or incorrect response.

[0140] In some implementations, a content item may include an image and script corresponding to a reward. The image may refer to a reward interface that displays the reward in response to a user selecting the correct response. For example, a client device may present a subset of one or more items (e.g., at least one query and its corresponding response) within a content slot. The client device may detect first interaction data from the selection of one or more interactive elements associated with the subset of one or more items. The client device may determine that the selection indicates an incorrect response. Accordingly, the client device may provide a notification to the client device's display device indicating an incorrect selection. In some cases, the client device may terminate or disable the visibility of the content item after notifying the user of an incorrect selection. In this case, no reward may be provided to the user or the user account. In some implementations, a client device may detect second interaction data from the selection of one or more other interactive elements associated with the subset of one or more items. The client device may determine that the selection indicates a correct response. Accordingly, the client device may present an image corresponding to a reward to the client device's display device in response to determining that the second interaction data corresponds to a correct response. The first and second interaction data may include instructions for interaction or selection of at least one interactive element within the content item. In this scenario, when a reward is presented to the client device, or also in response to determining that the second interaction data corresponds to a correct response, the DPS can notify the content publisher (e.g., the content publisher's device) to award a reward to the user account that provided the correct response. The reward can be the same as the one shown in the image.

[0141] In some implementations, the DPS can determine that an interaction time has exceeded a threshold after a content item has been presented on the client device. For example, the DPS can monitor the client device's activity or interaction data. The DPS can determine that the user on the client device is actively attempting to provide the correct response (e.g., moving the cursor within the content item, the user reading instructions for queries and responses, selecting an incorrect response after consideration, etc.). In response to the user's effort, the DPS can trigger a script for the content item to present a reward corresponding to the content item in response to the interaction time exceeding the threshold. For example, the interaction time can be predetermined or based on a counter activated during cursor movement or other user activities. When the predetermined time or counter reaches its time limit can be configured by the content publisher, content provider, or the DPS (e.g., 30 seconds, 1 minute, etc.). In some implementations, the DPS may not provide a reward to the user (e.g., the client device or user account within a first application) if no interaction data indicating a selection of a correct response is received.

[0142] In some implementations, after executing a script and determining that the user has selected the correct response, the client device may, in response to determining that the correct response has been selected, send an instruction to an entity associated with the content provider to update the value corresponding to the content provider. This value may correspond to a performance metric for the content item, such as a subset of one or more entries associated with the application and actionable objects. For example, the DPS may send an instruction to increase a ratio of the performance metric, which indicates the likelihood that the client device will select the correct response for the field-value pairs used to generate the content item. The performance metric may indicate the performance of each field-value pair when used to generate the content item.

[0143] In some implementations, if interaction data indicates a selection of an incorrect response, the DPS may degrade the performance metric associated with the item the user interacted with. In some cases, the performance metric may indicate the conversion rate of a user interacting with at least one response or actionable object to download the application. In other words, the performance metric may indicate user engagement performance such that receiving a selection of a response or actionable object can increase the performance metric. Otherwise, if the client device receives interaction data indicating a selection of an exit icon, the performance metric may be degraded to indicate that the user has not engaged with the content item or does not want to interact with it. Performance metrics may be updated for or sent to the content provider to determine the performance of content item activities registered by the content provider. In some cases, the DPS may perform prioritization or selection of items or content items based on performance metrics. For example, the DPS may prioritize content items or entries with higher performance metrics (e.g., those the user is likely to interact with) for display on the client device.

[0144] In some implementations, after constructing and updating performance metrics for a period of time (e.g., 10 days, 20 days, etc.), the DPS can determine which entries within the performance metric range (e.g., the top 30% of entries) will be used for displaying content items. Therefore, some field-value pairs may not be used to generate or select content items after a period of time. In some implementations, the DPS can reset the performance metrics after a period of time (e.g., 1 month, 2 months, or quarterly). Therefore, entries (e.g., fields) with low performance metric values ​​can be used at a later time. For example, in some cases, the performance of these fields may be better after resetting the performance metrics.

[0145] Some illustrative implementations and methods have now been described. It is obvious that the foregoing is illustrative and not limiting, and is presented by way of example. Specifically, although many of the examples presented herein involve specific combinations of method actions or system elements, those actions and elements can be combined in other ways to accomplish the same objective. Actions, elements, and features discussed in connection with only one implementation are not intended to exclude similar roles in other implementations or methods.

[0146] The wording and terminology used herein are for descriptive purposes and should not be considered restrictive. The terms “comprising,” “including,” “having,” “containing,” “involving,” “characterized as,” “featured as,” and variations thereof, as used herein, are intended to cover the items listed thereafter, their equivalents, and additional items, and to cover alternative implementations comprised of the items specifically listed thereafter. In one implementation, the systems and methods described herein include one, more than one, each combination of, or all of the described elements, actions, or components.

[0147] Any reference in this document to an embodiment, element, or action of a system or method mentioned in the singular may also include embodiments that include multiple such elements, and any reference in this document to any embodiment, element, or action mentioned in the plural may also include embodiments that include only a single element. The singular or plural references are not intended to limit the currently disclosed systems or methods, their components, actions, or elements to a single or multiple configuration. A reference to any action or element based on any information, action, or element may include an embodiment in which the action or element is at least partially based on any information, action, or element.

[0148] Any implementation disclosed herein may be combined with any other implementation, and references to “implementation,” “some implementations,” “alternative implementations,” “various implementations,” “one implementation,” etc., are not necessarily mutually exclusive, but are intended to indicate that a particular feature, structure, or characteristic described in connection with that implementation may be included in at least one implementation. These terms used herein do not necessarily refer to the same implementation. Any implementation may be combined inclusively or exclusively with any other implementation in any manner consistent with the aspects and implementations disclosed herein.

[0149] A reference to "or" can be interpreted as inclusive, such that any term described using "or" can refer to a single term, more than one term, or any of all terms in the terminology being described.

[0150] Where reference numerals follow technical features in the drawings, detailed descriptions, or any claims, the sole purpose of including the reference numerals is to increase the comprehensibility of the drawings, detailed descriptions, and claims. Accordingly, reference numerals, or their omission, do not limit the scope of any claim element.

[0151] The systems and methods described herein may be embodied in other specific forms without departing from their characteristics. While the examples provided herein involve maintaining session identifiers across multiple web pages for content selection and deploying countermeasures, the systems and methods described herein can be applied to other environments. The foregoing embodiments are illustrative and not limiting of the systems and methods described. Therefore, the scope of the systems and methods described herein is indicated by the appended claims rather than the foregoing description, and variations in the meaning and scope of equivalents of the claims are included therein.

Claims

1. A method for providing content, comprising: The data processing system receives content requests from the client device; The data processing system accesses metadata for one or more applications that can be installed, each of the one or more applications including multiple field-value pairs, the field-value pairs including values ​​received from a device corresponding to the publisher of the application; The data processing system determines one or more entries associated with the one or more applications from the metadata, the one or more entries including one or more queries and corresponding one or more responses; The data processing system selects a subset of the one or more entries and a content item that can be acted upon. When the content item is selected, the client device accesses information resources from which applications can be installed in the one or more applications. as well as The data processing system sends the content items to the client device for display on the client device.

2. The method according to claim 1, further comprising: The data processing system receives input from the client device corresponding to a correct response associated with the content item; as well as The data processing system terminates the content item on the client device; or The data processing system disables the visibility of the content item displayed on the client device.

3. The method according to claim 1 or 2, wherein, The application is a first application, and the request for content includes an identifier of a second application, which includes a content slot in which the content item is presented.

4. The method according to claim 3, wherein, The selection of the content item includes the data processing system selecting the content item based on the identifier of the second application and the type of the content slot.

5. The method of claim 1, further comprising selecting a subset of the one or more entries for inclusion in the content item by the data processing system, the data processing system selecting each entry of the subset by identifying the priority of each field from a plurality of field-value pairs of the application's metadata, the priority assignment being based on i) the number of values ​​associated with the field, or ii) the number of incorrect responses previously received from the client device for a content item that includes a query against the field.

6. The method according to claim 1, wherein, Using a selection model to select a subset of the one or more entries for inclusion in the content item, and wherein the method further includes: The data processing system receives interactive data from the client device and presents content items on the client device, the interactive data identifying the response selected at the client device; and The data processing system updates the selection model based on interaction data from the client devices to select multiple entries for multiple client devices.

7. The method according to claim 1, wherein, The content item includes a script that, when executed on the client device, causes the client device to: Present a subset of the one or more items within the content slot; Detect interactive data from the selection of one or more interactive elements associated with a subset of the one or more entries; as well as The data processing system is provided with interactive data detected from the selection of one or more interactive elements within the content slot.

8. The method according to claim 1, wherein, The content item includes an image and script corresponding to the reward, which, when executed on the client device, causes the client device to: Present a subset of the one or more items within the content slot; Detect first interactive data from the selection of one or more interactive elements associated with a subset of the one or more entries; The selection instruction was determined to be an incorrect response; Provide a notification to the display device of the client device indicating that the selection is incorrect; Detect second interactive data from the selection of one or more other interactive elements associated with a subset of the one or more entries; Confirm that the selection instruction responded correctly; as well as In response to determining that the second interaction data corresponds to the correct response, an image corresponding to the reward is presented to the display device of the client device.

9. The method according to claim 1, further comprising: The data processing system determines that the interaction time exceeds a threshold after the content item is presented on the client device; as well as The data processing system triggers the script of the content item so that the client device presents a reward corresponding to the content item in response to the interaction time exceeding the threshold.

10. The method according to claim 1, wherein, The content item includes a script that, when executed on the client device, causes the client device to: Present a subset of the one or more items within the content slot; Detect interactive data from the selection of one or more interactive elements associated with a subset of the one or more entries; Confirm that the selection instruction responded correctly; as well as In response to determining that the correct response has been selected, an instruction is sent to the entity associated with the content provider to update a value corresponding to the content provider, the value corresponding to a performance metric of a content item that includes a subset of the one or more entries and an actionable object associated with the application.

11. A system for providing content, comprising: A data processing system, including one or more processors and a memory, is configured to: Receive requests for content from the client device; Access metadata for one or more applications that can be installed, wherein the metadata for each of the one or more applications includes multiple field-value pairs, the field-value pairs including values ​​received from a device corresponding to the publisher of the application; From the metadata, determine one or more entries associated with the one or more applications, the one or more entries including one or more queries and corresponding one or more responses; Select a content item that includes a subset of the one or more entries and an actionable object, and when the content item is selected, the client device accesses information resources from which applications can be installed in the one or more applications; as well as The content item is sent to the client device for display on the client device.

12. The system according to claim 11, wherein, The data processing system is also configured to: Receive input from the client device corresponding to the correct response associated with the content item; as well as Terminate the content item on the client device; or Disable the visibility of the content item displayed on the client device.

13. The system according to claim 11 or 12, wherein, The application is a first application, and the request for content includes an identifier of a second application, which includes a content slot in which the content item is presented.

14. The system according to claim 13, wherein, In order to select the content item, the data processing system is configured to select the content item based on the identifier of the second application and the type of the content slot.

15. The system according to claim 11, wherein, The data processing system is also configured to select a subset of the one or more entries for inclusion in the content item. The data processing system selects each entry in the subset by identifying the priority of each field from multiple field-value pairs of the application's metadata. The priority allocation is based on i) the number of values ​​associated with the field, or ii) the number of incorrect responses previously received from the client device for a content item that includes a query targeting the field.

16. The system according to claim 11, wherein, A selection model is used to select a subset of the one or more entries for inclusion in the content item, and the data processing system is further configured to: Receives interaction data from the client device and presents content items on the client device, the interaction data identifying a response selected at the client device; and The selection model is updated based on interaction data from the client devices to select multiple entries for multiple client devices.

17. The system according to claim 11, wherein, The content item includes a script that, when executed on the client device, causes the client device to: Present a subset of the one or more items within the content slot; Detect interactive data from the selection of one or more interactive elements associated with a subset of the one or more entries; as well as The data processing system is provided with interactive data detected from the selection of one or more interactive elements within the content slot.

18. The system according to claim 11, wherein, The content item includes an image and script corresponding to the reward, which, when executed on the client device, causes the client device to: Present a subset of the one or more items within the content slot; Detect first interactive data from the selection of one or more interactive elements associated with a subset of the one or more entries; The selection instruction was determined to be an incorrect response; Provide a notification to the display device of the client device indicating that the selection is incorrect; Detect second interactive data from the selection of one or more other interactive elements associated with a subset of the one or more entries; Confirm that the selection instruction responded correctly; as well as In response to determining that the second interaction data corresponds to the correct response, an image corresponding to the reward is presented to the display device of the client device.

19. The system according to claim 11, wherein, The data processing system is also configured to: After the content item is presented on the client device, it is determined that the interaction time exceeds a threshold; and The script for the content item is triggered so that the client device presents a reward corresponding to the content item in response to the interaction time exceeding the threshold.

20. The system according to claim 11, wherein, The content item includes a script that, when executed on the client device, causes the client device to: Present a subset of the one or more items within the content slot; Detect interactive data from the selection of one or more interactive elements associated with a subset of the one or more entries; Confirm that the selection instruction responded correctly; as well as In response to determining that the correct response has been selected, an instruction is sent to the entity associated with the content provider to update a value corresponding to the content provider, the value corresponding to a performance metric of a content item that includes a subset of the one or more entries and an actionable object associated with the application.

Images