JP2019509546A - Latency reduction - Google Patents

Abstract

Disclosed are methods, systems, and apparatus that include a computer program encoded on a computer storage medium for reducing latency in network communication and data presentation. In one aspect, a user session is initiated in which data related to the account is presented to the user. A user group to which a given user is assigned is identified. A first data set associated with the account is selected based on the user group. A second data set associated with the account is selected based on the type of data previously requested by other users in the user group. The user interface for the account is updated to present at least a portion of the first data set. By presenting the second data set to the client device prior to receiving the request for the second data set, the user interface can be used when presenting the first data set or additional portions of the second data set. Latency when updating is reduced.

Description

  The present invention relates to latency reduction.

  The Internet facilitates the exchange and trading of information between users around the world. This exchange of information allows data providers to provide data to various users. The data may be provided in response to multiple requests received from the client device. However, each request requires the use of computational resources (eg, servers and memory storage devices) and network resources (eg, routers, switches, and network bandwidth) to respond with the requested data. In addition, each request takes some time for the data provider to identify the appropriate data and send the data over the network to the client device.

  This document describes technologies related to reducing latency in network communications and data presentation.

  In general, one innovative aspect of the subject matter described herein is that a given user is an authorized user of a given online account based on data submitted through the given user's client device. Authenticating action and, for a given user, the action of initiating a user session in which data related to the account is presented to the user in response to authentication, with which the account has access to the account A given user interaction and user interface element with an action accessible by multiple users having information and (i) a user interface element presented within the user interface of the account during a previous user session Other user interactions Or (ii) the similarity between at least one data type requested by a given user during a previous user session and at least one data type requested by another user An action to identify a user group to which a given user is assigned based on gender and an action to select a first data set associated with the account based on the user group to which the given user is assigned, comprising: The first data set contains at least (i) the type of data requested by the given user during the previous user session, and (ii) the user interface element that the given user interacted with during the previous user session. Selected by the action and at least one user in a user group other than the user To present an action to select a second dataset associated with the account based on the type of data previously requested and at least a portion of the first dataset in the initial account view for the account An action that updates the user interface for an account, wherein the initial account view presents multiple different types of data combined into a single presentation that provides an overview of the account Presenting the first data set or an additional portion of the second data set at the client device by providing the second data set to the client device prior to receiving a request for the second data set from the device When updating the user interface for an account A action to reduce the latency, the second data set, is cached in the client device, not presented in the initial account view, we can be embodied in a method comprising the actions. Other embodiments of this aspect include corresponding systems, apparatus, and computer programs configured to perform the method actions encoded on the computer storage device.

  These and other embodiments can each optionally include one or more of the following features. In some aspects, a given user and other users can be assigned to user groups using a machine learning process that creates multiple user groups and assigns users to multiple user groups. In some aspects, a given user may: (i) a time range of data requested by a given user in a previous user session, (ii) data modified by the user, or (iii) a given Can be assigned to a user group based further on at least one of the frequency of access to data associated with the account.

  In some aspects, at least a portion of the second data set is (i) the type of data requested by a given user in a previous user session, (ii) by a given user in a previous user session. It may be selected based on at least one of the requested time range of data, or (iii) the geographic region from which a given user requested data from previous user sessions. In some aspects, each of the plurality of users is provided with a different initial account view based on the type of data requested by each of the plurality of different users.

  Some aspects may relate to a given user session initiated for a given user, a user interface element that the given user interacted with during the given user session, and the given user to the user session. Updating the user profile for the given user with data specifying the type of data requested therein, and modifying the initial account view for the given user based on the updating. it can.

  Some aspects may determine to update the second data cache at the user device based on the data cost for updating the cache being less than a threshold cost, and to update the cache. Providing a correspondingly updated data set to the user device. Some aspects identify two or more campaigns in an account having at least one same characteristic and at least one characteristic that is different for each of the two or more campaigns; and each of the two or more campaigns Providing data presenting data for each of the two or more campaigns in a manner that highlights at least one feature.

  Another aspect is filed through a memory device storing processor readable instructions, one or more processors configured to read and execute instructions stored in the memory, and a client device of a given user. Based on the data, authenticating a given user as an authorized user of a given online account, and for a given user, depending on the authentication, data associated with the account is presented to the user A first front-end server that initiates a user session, wherein the account is accessible by multiple users having credentials to access the account; and (i) before The user interface presented in the account user interface during the user session Similarity between the given user's interaction with the source element and the other user's other interaction with the user interface element, or (ii) at least requested by the given user during the previous user session Identify a user group to which a given user is assigned based on the similarity between one data type and at least one data type requested by another user, and the given user is assigned Selecting a first data set associated with an account based on a user group, wherein the first data set is at least (i) of data requested by a given user during a previous user session. Type, and (ii) the user interface that the given user interacted with during the previous user session Select based on the source element, and select a second data set associated with the account based on the type of data previously requested by various other users in the user group A data selector that performs and a user interface generator that updates the user interface for the account to present at least a portion of the first data set in the initial account view for the account, the initial account view comprising: Provide an overview of the account, present a plurality of different types of data combined into a single presentation, a user interface generator and a second before receiving a request for a second data set from the client device Providing datasets to client devices A second front-end server that reduces latency in updating a user interface for an account when presenting an additional portion of a first data set or a second data set at a client device, The second data set can be embodied in a system that includes a second front-end server that is cached at the second front-end server or client device and is not presented in the initial account view. The features described in the context of the first aspect can be implemented in combination with the system.

  Particular embodiments of the subject matter described in this specification can be implemented to realize one or more of the following advantages. The latency in presenting data to the user can be reduced by pre-caching at the user's device data that the user is likely to request but has not yet requested. By pre-caching data, the number of requests submitted over the network and thus the amount of requests imposed on the network and the computational resources used to respond to the requests can be reduced. It is. This reduction in the demands placed on network and computing resources increases the speed at which resources respond to requests and minimizes errors and performance degradation caused by overloading resources. The performance can be improved. Also, the demands placed on computing resources are reduced by retrieving the requested data and additional data to pre-cache at the same time rather than querying the data source multiple times. Thus, embodiments address the issues related to how appropriate data to be pre-cached at a device should be provided, eg cached data thanks to improved selection of cached data A set of data that provides benefits similar to the benefits of a larger set of can be cached at the device.

  Pre-caching data that is likely to be requested by the user also allows the client device to pass the request across the network, the server identifies the requested data, and the requested data travels towards the client device. This eliminates the need to wait and allows the client device to present the requested data more quickly. In addition, user frustration is reduced by presenting data without network connectivity in response to requests submitted by the user. The demands placed on the network and computing resources can also be reduced by selectively determining when to update the data stored in the cache.

  The details of one or more embodiments of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the present subject matter will be apparent from the description, drawings, and claims.

FIG. 2 is an exemplary environment in which a pre-cache system provides data for caching at a client device. FIG. 2 is an exemplary environment in which an account management system manages account data and provides a user interface for presenting account data. 4 is a screen shot of an exemplary user interface in which account data is presented. 6 is a flow diagram of an exemplary process for reducing latency in presenting account data. 2 is a flowchart of an exemplary process for updating a cache. 4 is a flow diagram of an example process for assigning a given user to a user group and identifying data to provide to the given user based on the user group. 4 is a flow diagram of an example process for generating a visualization that presents account data for multiple campaigns.

  Like reference symbols and symbols in the various drawings indicate like elements.

  The system can reduce latency in presenting data by sending data to the client device before the client device sends a request for data and caching the data at the client device. However, in general, the amount of data that can be cached is less than the amount of data available. Thus, the system can determine which of the different users can benefit from the benefits afforded by caching data (e.g., faster user interface updates and / or real-time interaction with the user interface). Decide if data should be cached. The system can select data to provide to the client device based on the user's previous interaction with the user interface presenting the data. For example, if a user requests specific data multiple times in a specific time period (eg, data in the previous week), the system will provide specific data for that time period before the user actually sends a request for data May be. If the user sends a request for data later, the data is cached at the user device and is retrieved and presented more quickly than if the client device had to request data from a remote system, eg, over a network Can be done. Additional data can also be cached by remote systems for faster delivery to client devices.

  The system can transmit data for presentation to the user and data for caching at the user's device when the user accesses an account managed by the system. For example, when a user logs in to their account, the system can provide a user interface that includes an initial account view in the dashboard and additional data to cache on the user's device. The dashboard can include an account summary that includes a summary of data selected for the user based on the user's previous interaction with the user interface provided by the system. The manner in which the data is presented can also be selected based on the user's previous interaction with the user interface provided by the system. These user interactions are, for example, specific user interface elements that the user has viewed, selected, or interacted with (e.g., controls, display cards, etc.), requested or modified by the user. Data types and / or dimensions of the data (eg, data within a specific time period or associated with a specific geographic location). The user can then interact with the dashboard user interface elements to view different data or to view different types of presentation of data. In response, appropriate data can be obtained from the cached data or requested from the system that maintains the data.

  The data presented in the initial account view and / or the data provided for caching at the client device can be selected based on the user group to which the user is assigned. For example, a particular group of users may request similar types of data and / or interact with similar types of user interface elements. In certain examples, users in similar organizations but in different organizations may request and view similar types of data and data in similar dimensions. In some implementations, the data cached for a given user is based on those actions performed by other users in the group, even when the given user did not perform the action. Can be selected.

  FIG. 1 is an exemplary environment 100 in which the pre-cache system 110 provides data for caching at the client device 130. The pre-cache system 110 can provide data from the data storage device 115 in response to a data request 140 received from the client device 130. Client device 130 provides data request 140 over data communication network 120, eg, a local area network (LAN), a wide area network (WAN), the Internet, or a combination thereof. Each data request 140 may specify particular data that the user has requested using the client device 130.

  In response to each data request 140, the pre-cache system 110 can obtain the requested data from the data storage device 115 and provide the requested data 142 to the client device 130. For example, the pre-cache system 110 may send the requested data 142 to the client device 130 in one or more transmissions of one or more data packets. The pre-cache system 110 can also select and provide additional data 144 that was not requested by the data request 140. For example, the user of client device 130 may not request additional data 144. Additional data 144 can be cached at client device 130 so that when a user requests additional data 144, it can be provided quickly without sending another data request over network 120. It is. For example, the additional data 144 can be stored in the high speed cache 135 of the client device 130. The fast cache 135 may include a fast memory device that is installed on the client device 130 and stores additional data 144.

  In some implementations, pre-cache system 110 selects additional data 144 based on the user of client device 130. For example, the pre-cache system 110 may be based on a user's previous interaction with one or more user interfaces that present data to the user, eg, one or more user interfaces provided by the pre-cache system 110. Additional data 144 may be selected. User interactions used by the pre-cache system 110 to select additional data 144 include, for example, user interface elements that the user interacted with (e.g., controls, display cards, graph types, etc.), the type of data requested by the user ( (E.g., keywords, performance measures, bids), actual data requested by the user (e.g., specific campaigns, specific keywords, specific content items, etc.), dimensions of the data requested by the user (e.g. For example, a specific time period, a specific geographical location, a specific range of values, etc.), how often the user accesses the account, and / or preferences selected by the user. For example, if a user requests previous week's impression data for a particular content delivery campaign during a previous user session, the pre-cache system 110 may currently request previous week's impression data for a particular campaign before requesting this data. May be provided as additional data for other user sessions.

  In some implementations, some data requests 140 may be generic or implicit requests rather than specific requests for specific data. For example, the pre-cache system 110 generates and provides a user interface, such as a dashboard, with an initial account view that provides an overview of the account in response to a user logging into or otherwise accessing the account. Also good. This summary of data can be selected in response to a user logging into an account rather than a specific request for data contained in the summary. The pre-cache system 110 can also select and provide additional data that the user may request after viewing the dashboard.

  In some implementations, the pre-cache system 110 may also cache additional data in the pre-cache system 110. In this way, the pre-cache system can provide data more quickly in response to a data request specifying additional data. This additional data can be selected in the same manner as the additional data 144 transmitted to the client device 130. For example, the pre-cache system 110 may select a set of additional data to pre-cache. The pre-cache system 110 may send a subset of the additional data to the client device 130 for caching at the client device. Pre-cache system 110 may also cache a subset of the additional data at pre-cache system 110. For example, the pre-cache system 110 may identify data from the set of additional data that is most likely to be selected by the user and provide that data to the client device 130. The remaining data in the set of additional data may be cached in the pre-cache system 110. This cache in the pre-cache system 110 can take some time to retrieve data from the data storage device 115 in response to a request for data, and can increase the demand for computing resources used to retrieve the data. At some point, latency in providing data to the client device 130 can be reduced.

  FIG. 2 is an exemplary environment 200 in which the account management system 210 manages online account data and provides a user interface for presenting account data. Account management system 210 may include one or more servers located in one or more data centers. One or more servers may receive a request for online account data over a data communication network 250, such as a LAN, WAN, the Internet, or a combination thereof. For example, account management system 210 may include one or more front-end servers 240 that receive requests for online data and provide the requested data to client devices 262 and 272 via network 250. Account management system 210 also includes one or more back-end servers that receive requests from front-end servers, obtain appropriate account data based on the requests, and provide the obtained data to front-end server 240 be able to.

  Account management system 210 can manage online account data for a plurality of different accounts of a plurality of different account holders. For example, account management system 210 can manage account data for a number of different organizations, such as account holders 260 and 270. Although two account holders 260 and 270 are shown in FIG. 2, the account management system 210 can manage account data for other numbers of account holders. The systems and techniques described below can be applied to various other types of data.

  Account data managed by the account management system 210 can be attributed to the account, such as performance data about content items (eg, impressions, click rate, conversion rate, etc.), budget information about account holders, and / or content item delivery criteria. Any relevant data can be included. Account data for each account holder is stored in an account data storage device 227 that may include multiple data storage devices located in one or more data centers. Account data for each account holder may be stored separately and securely so that account data for one account holder is not provided to users of different account holders.

  Each account holder 260 and 270 may have one or more authorized users who are authorized to view data associated with the account holder's account. For example, an organization may have multiple users who are authorized to manage campaigns for which account management system 210 maintains account data. Each user authorized to access account holder 260 account data can access account data using client devices 262-1 through 262-n. Similarly, each user authorized to access account holder 270 account data can access account data using client devices 272-1 through 272-n. The user may be prompted to enter credential information (eg, username and password) before being allowed to access account data.

  A client device is an electronic device that can request and receive electronic resources and other data over network 250. Exemplary client devices include personal computers, mobile communication devices (eg, smartphones, tablet computing devices, and / or smart watches), and other devices that can send and receive data over the network 250. In general, the client device includes a user application, such as a web browser, to facilitate sending and receiving data over the network 250. A web browser can allow a user to interact with text, images, videos, music, and other information that is typically placed on a web page of the website. A client device can include a particular type of device or other application developed for a particular platform, such as a native application.

  Each client device 262 and 272 can include a high speed cache 264 and an account viewer 266. The account viewer 266 is an application that presents account data to the user of the client device. Account viewer 266 is a web browser or native application that requests account data from account management system 210 and presents the account data using one or more user interfaces, as described in more detail below. There may be.

  The high speed cache 264 includes a high speed memory device that stores account data that may be presented by the account viewer 266. For example, high speed cache 264 may include static random access memory (SRAM) and / or solid state memory devices. The fast cache 264 may store account data that has not yet been requested by the user of the client device. When a user requests account data stored in the high speed cache 264, the account viewer 266 can quickly obtain account data from the high speed cache 264 without sending a request for account data over the network 250. This pre-caching of data reduces the latency in presenting account data and reduces the demands placed on the computational resources of the network 250 and account management system 210.

  In some implementations, the account viewer 266 can be configured to examine the high speed cache 264 in response to a request for account data. If the requested account data is found in the high speed cache 264, the account viewer 266 can retrieve the account data from the high speed cache 264 and present the account data to the user. If the requested account data is not in the high speed cache, the account viewer 266 can request account data from the account management system 210 by sending a request over the network 250, for example.

  The account management system 210 includes a data transmission subsystem 220, an interaction logger 230, and a user group engine 235. The data transmission subsystem 220 receives and responds to requests for account data. The data request may include a specific request for specific account data. An example of a specific request is a request for performance data for a specific campaign during a specific time period. Account management system 210 may also provide account data in response to a comprehensive or implicit request. An example of a comprehensive or implicit request is that the user logs into an account that the user is authorized to access. In this example, data transmission subsystem 220 may select a data summary to provide an initial account view for the user.

  The data transmission subsystem 220 includes a data selector 221 and a user interface generator 229. Data selector 221 identifies account data to provide in response to a data request (eg, a specific, generic or implicit request) received from a client device. For example, the data selector 221 may access the account data storage device 227 to obtain specific data specified by a specific data request. For generic or implicit data requests, the data selector 221 can select a subset of account data based on the particular user for whom the request was made. This subset of account data is a subset of the account data of the account that the user is authorized to access. For example, as described in more detail below, the data selector 221 may select a subset of account data to provide based on the user's previous interaction with the user interface provided by the account management system 210. .

  The user interface generator 229 can generate various user interfaces that present account data. The user interface includes user interface elements (e.g., controls, display cards, menus, etc.) that allow the user to request and view various data in various formats (e.g., graphs, charts, tables, etc.). Dashboards can be included. The dashboard may present an initial account view each time the user first accesses the account, for example in response to the user logging into the account. The initial account view can, for example, provide a summary of the account and include a subset of account data adapted to the user accessing the account. As described in more detail below, the summary of account data may include data selected based on the user's previous interaction with the user interface provided by account management system 210.

  The user interface can include one or more display card user interface elements. Each display card can present a particular type of data in a particular way. For example, a first display card may present impression data for a content item in a table, while a second display card uses a bar graph to show click rates for multiple keywords for delivering a content item. May be presented. In some implementations, the user interface generator 229 selects a display card to provide in the initial account view based on the user's previous interaction with the display card or other user interface element. For example, if the user chooses to view a particular display card at least a threshold number of times, the user interface generator 229 may provide the particular display card in the initial account view. In another example, the user interface generator 229 may include one or more display cards in the initial account view that the user chooses to view most frequently. As described in more detail below, the user interface generator 229 may also select a display card for inclusion in the initial account view based on the user group to which the user is assigned. An exemplary user interface is shown in FIG. 3 and described below.

  The interaction logger 230 logs data describing the user's interaction with the user interface provided by the account management system 210 and / or presented by the account viewer 266. As will be described in more detail below, this interaction data is used to select account data provided to the user. For example, each user may view account data and / or log into their account to make changes to an account that the user is authorized to view and make changes to. While the user is logged in and with the user's permission, the interaction logger 230 can receive data describing the user's interaction with the user interface and store the data in the secure interaction log 232. . For example, the account viewer 266 may include an embedded script that obtains data about each interaction and provides the data to the interaction logger 230. Data describing the user's interaction stored in the interaction log 232 includes, for example, user interface elements that the user interacted with (eg, control, display card, graph type, etc.), the type of data requested by the user (eg, keyword , Performance measures, bids, etc.), the actual data requested by the user (e.g., specific campaigns, specific keywords, specific content items, etc.), dimensions of the data requested by the user (e.g., specific time period) , Specific geographic location, specific value range, etc.), how often the user accesses the account, preferences selected by the user, and / or other suitable interaction data.

  In some implementations, the interaction logger 230 generates a user profile for each user that includes logged data. In the user profile for the user, the interaction logger 230 may include data identifying each user interface element that the user interacted with, the number of times the user interacted with the user interface element, and / or the frequency with which the user interacted with the user interface element. . The user profile for the user may also include data identifying each type of data requested by the user, the number of times the user requested each type of data, and the frequency with which the user requests each type of data. The same identifying and frequency data can be stored for each particular portion of actual data requested by the user. For each type of data and / or for each particular portion of data requested by the user, the user profile can include dimensions for the data. For example, if a user requests the outcome of a particular content item during a particular period of time, the user profile will have a specific time for that type of data (achievement data) and for the actual data (a particular content item's outcome). Contains data that specifies a period. After each user session in which the user accesses the online account, the user interaction logger 230 can update the user's profile to account for the user's interaction with the data and user interface elements during the user session.

  The user group engine 235 can assign users to user groups based on the user's interaction with the user interface provided by the account management system 210. For example, the user group engine 235 may assign users to user groups based on the similarity between the user's user profiles. The user group can include users having at least a threshold similarity as members of the user group with each other user in the group based on the user profile of the user. For example, a similarity score can be determined for each pair of users based on the similarity between data stored in the profiles of two users. If the similarity score meets the threshold (eg, by meeting or exceeding the threshold), the two users may be included in the user group together. The similarity score can be based on the number of matching features between the two users. For example, if two users requested the same type of data and / or selected the same user interface element, the two users did not request the same type of data or the same user interface It may have a higher similarity score than if no element was selected. User groups can be used to identify account data and user interface elements to provide to members of the group, as described in more detail below.

  In some implementations, user groups are based on specific roles within the organization. For example, the user group engine 235 may create and populate the user group for the product manager and another user group for the accountant. A user group for a particular role can include users with user profiles that match or are similar to the profile for the particular role. For example, a user in a particular role may access similar types of data in similar data dimensions and / or view the same or similar user interface elements.

  A user group can include users for multiple different account holders. For example, a user group for product managers may include product managers from different organizations. In this way, to identify data types in which patterns of user interaction from multiple different organizations are more likely to be required by users with the same role or otherwise similar Can be used. An exemplary process for assigning users to user groups is shown in FIG. 6 and described below.

  As described above, the data selector 221 can select data to provide to the user based on the user's previous interaction with the user interface provided by the account management system 210. In particular, the data selector 221 may select data to provide in the initial account view for the user based on the user's previous interaction with the user interface provided by the account management system 210. For example, when a user accesses an account in the account management system 210, the data selector 221 includes a first data set of account data that is provided in an initial account view for the user in response to the user accessing the account and , Potentially selecting data to be cached by the client device even if that data may not be used for the initial account view.

  The data selector 221 includes the frequency at which specific data is requested or viewed by the user, the frequency at which specific types of data are requested or viewed by the user, and the frequency at which the user interacts with specific user interface elements. And / or data for inclusion in the first data set may be selected based on other data included in the user's profile. For example, the initial account view may include a certain number of cards selected by the user interface generator 229, for example. The data selector 221 can select a first data set for inputting data to the display card. This first data set may include the most frequently requested data for inclusion in the display card and / or the most frequently selected type of data.

  The data selector 221 may select the first data set based on the dimension of the data requested by the user. For example, the first data set may include data regarding a particular time period for which the user previously requested data. In certain instances, the user may only be interested in recent data, for example, data regarding events that occurred last week. In this example, the user often requests data for the previous week without requesting older data. The data selector 221 may provide the user with a first data set that includes data relating to events that occurred in the week before the user logs in in the initial account view. The data selector 221 may decide not to provide older data to the user until the user requests the data, resulting in less data being provided over the network and stored on the client device.

  The dimension of data used in selecting the first data set may also be selected based on frequency. For example, a user may request data regarding different time periods or different geographic locations. The data selector 221 may select the first data set based on the most frequently requested time period or geographic location.

  The data selector 221 may select a first data set for the initial account view based on the type of data presented in the initial account view for the user. For example, a particular display card may present a particular type of data. If a particular card is selected for the initial account view, the data selector 221 may select the appropriate data to include in the first data set to populate the particular display card.

  In some implementations, the data selector 221 can also select the first data set based on the user group or role to which the user is assigned. For example, other users within a group or having the same role may request a particular type of data or interact with a particular user interface element (eg, a particular display card). Data selector 221 may allow a user to be interested in the types of data requested by other users in the group (or assigned the same role), or know that these types of data are useful. At some point, these types of data may be included in the first data set. Of course, actual data from other accounts is not included in the first data set. Instead, the data selector 221 may specify in an account that the user is authorized to access the same type of account data requested by other users in the group.

  The data selector 221 selects the type of data requested by other users in the user group for inclusion in the first data set based on the frequency with which other users in the group request or view the data. Data can be selected. For example, if a group generally requests or views a particular type of data as a whole, that particular type of data may be included in the first data set. The data selector 221 also requests that type of data for inclusion in the first data set based on the number of other users that request or view the type of data requested by other users in the user group. It is possible to select. For example, a particular type of data that is requested or viewed by the most users (or at least a threshold number of users) may be included in the first data set.

  Similarly, the user interface generator 229 can select user interface elements to include in the initial account view, such as a display card, based on user interface elements selected or viewed by other users in the user group. For example, the user interface generator 229 may determine the initial account view based on the number of times users in a user group have selected or viewed user interface elements and / or the number of users in the group that have selected or viewed user interface elements. User interface elements for may be selected.

  Users to include in the initial account view for a user based on the user's previous interaction with the user interface provided by the account management system 210 and / or based on the user's interaction with other users included in the group By selecting interface elements and data, the account management system 210 can provide a summary of data that is likely to be most useful to the user, thereby increasing the usefulness of the data summary. This can result in higher user satisfaction and a reduction in the number of requests for additional data submitted by the user. Thus, this selection process can reduce the demands placed on the network and the latency caused by the network.

  The data selector 221 includes a pre-cache engine 223 and a campaign grouper 225. The pre-cache engine 223 can select one or more second data sets to provide to the client device in response to a request for account data. The pre-cache engine 223 selects a second data set in response to a specific request for specific data and / or a comprehensive or implicit request for data (e.g., a user logging into an account). Can do. The pre-cache engine 223 can select and provide the second data set prior to receiving a request for data contained in the second data set. For example, the second data set may be data that was not specified in a particular request or selected for inclusion in the first data set provided for the initial account view.

  The pre-cache engine 223 can send the second data set to the client device along with the account data obtained in response to the specific request or with the first data set. Alternatively, the pre-cache engine 223 can provide the second data set after other data is sent to the client device. The client device can store the second data set in the high speed cache 264. In this way, the account data of the second data set can be quickly presented by the user when the user requests such data.

  The pre-cache engine 223 is included in the second data set for the user based on the user's previous interaction with the user interface provided by the account management system 210 and / or the user group or role to which the user is assigned. Can be selected. Similar criteria used to select the first data set can be used to select the second data set. For example, the pre-cache engine 223 may determine how often specific data is requested or viewed by the user, how often a particular type of data is requested or viewed by the user, Frequency of interaction, dimension of data requested by the user, frequency of other users in the user group requesting or viewing certain data, others in the user group requesting or viewing certain data Select data for inclusion in the second data set based on the number of users and / or other appropriate data regarding user interaction with the user interface and data regarding other user interaction with the user interface Door can be.

  In some implementations, the first data set may be selected based on the user's previous interaction with the user interface, while the second data set may be a user group or role miscellaneous to which the user is assigned. Selected based on user interaction. In some implementations, the first data set and the second data set are both of the user's previous interaction with the user interface provided by the account management system 210 and the user group or role to which the user is assigned. It is selected based on a combination with other user interactions. In this example, the user interaction may be given more weight than the other user interaction of the user group or role to which the user is assigned.

  In some implementations, the pre-cache engine 223 may store the second data set, a portion of the second data set, or a different third data set in the fast cache 245 of the front-end server 240. For example, the front-end server 240 may include or be coupled to a high speed cache 245 that includes high speed memory such as SRAM and / or solid state memory devices. In some implementations, the second data set may be stored in the high speed cache 245 of the account management system 210 rather than the high speed cache of the client device. In some implementations, a portion of the second data set is stored in the fast cache 245 of the account management system 210 and a portion of the second data set is cached at the client device.

  In some implementations, the second data set may be stored in the high speed cache of the client device, and the third data set may be stored in the high speed cache 245 of the account management system 210. The third data set may be selected in the same manner as the second data set. By storing additional data on the front-end server, it eliminates the time required to identify and retrieve data from the account data storage device 227, so that additional data can be stored in response to a request for additional data. Latency when presenting can be reduced.

  The campaign grouper 225 can identify groups of campaigns (or other groups of information) that have specific characteristics that are similar but all of the campaigns are different. For example, an account holder may have multiple different campaigns for the same product or service that use the same keywords and content items. However, each campaign may target a different state. In this example, the content item delivery criteria may be the same for each campaign except for the states where content items for each campaign can be delivered. The campaign grouper 225 can identify these campaigns and add them to the campaign group.

  The user interface generator 229 can generate a visualization for each campaign group that highlights the differences between campaigns and any differences in campaign performance based on the differences. Continuing the previous example, the user interface generator 229 may generate a visualization that includes a map of 50 states. On the map, visualizations may highlight the outcome of campaigns in each state, for example using outcome numbers, outcome colors, or other visual effects that highlight differences between campaigns in different states .

  In another example, the user interface generator 229 may generate a visualization that highlights the same or similar campaign performance differences that differ based on the day of the week on which the content item is offered for the campaign. For example, a heat map may be used to show the relative performance of campaigns on different days of the week. In yet another example, multiple campaigns may differ based only on the type of keyword matching (eg, exact match, broad match, etc.). In this example, the user interface may present campaign results for each type of keyword matching.

  FIG. 3 is a screenshot 300 of an exemplary user interface 310 where account data is presented. The example user interface 310 includes an initial account view of the account that is displayed in the dashboard for the account. An initial account view can be generated for a given user based on the user's interaction with the user interface during a previous user session in which the user accessed the account, for example.

  The user interface 310 includes a menu 320 and a display card set 330. Menu 310 may provide a list of other display cards that the user can select to view. Menu 310 may also provide a list of data that the user can select for viewing. In response to the selection of an item in menu 320, user interface 310 may cause a client device presenting user interface 310 to request the selected display card or selected data. For example, the client device first accesses the client device's cache to determine whether the selected data (or data that will be presented in the selected display card) is stored in the cache. Also good. If stored, the client device can retrieve the data from the cache and present the data in the user interface 310. If the data is not stored in the cache, the client device can request data from a remote system, eg, account management system 210 of FIG.

  Each display card can present a particular type of data in a particular way. For example, the display card 331 presents performance data (eg, conversions, clicks, and impressions) and cost data regarding the campaign. Display card 331 also presents this data in a numerical format and includes a line graph that presents at least a portion of the results and / or cost data.

  Display card 333 presents results and cost data for several campaigns in a table format. Similarly, the display card 337 presents achievement and cost data in a table format for a number of keywords used to deliver the content item. Another display card 335 presents a bar graph showing performance and cost data for different types of devices on which content items for the campaign were presented. Yet another display card 339 presents a heat map over time showing campaign metrics (eg, outcome measures, cost measures, etc.). For example, the darkness of each square in the heat map may change based on a metric value for the corresponding time. The time range of the heat map can be adjusted by selecting “Day”, “Day and Time”, or “Time” at the top of the display card 339.

  As discussed above, the display card and / or data included in the initial account view can be selected based on the user's previous interaction with the user interface and / or the user group to which the user is assigned. It is. For example, display card 331-339 and data presented by display card 331-339 may be selected based on the user selecting display card 331-339 during a previous user session with an account. In addition, the campaigns included on the display card 333 may be selected based on a user's previous request for data related to these campaigns. Similarly, keywords included in display card 337 may be selected based on a user requesting data associated with these keywords. In another example, the time range presented in the display card 339 is selected based on the user's previous interaction with the display card 339 (or another display card) to view data during that time period. May be.

  Additional cards with additional data can be provided to the client device and cached at the client device before the user requests the additional card. For example, the user interface 310 includes five display cards 331-339. However, users often browse nine different display cards. Five display cards presented in the user interface and the other four display cards can be provided to the client device (along with the data presented in the display card) when the user logs into the account It is. In this way, when the user selects one of the four display cards, the selected display card can be presented to the user quickly without sending another request over the network. It is.

  Another exemplary display card can indicate how a particular content item was displayed on the user's device. For example, the content item may be the type of client device on which the content item is presented (eg, the content item may be presented differently than a desktop computer on a smartphone), the location on the resource where the content item is presented (eg, , The content item may be presented at the top of the web page differently from one side of the web page), or the type of resource on which the content item was presented (for example, the content item will appear on the blog on the search results page) May be presented differently based on). For this display card, the user interface generator 229 makes a probabilistic determination as to how the content item was displayed for each impression of the content item and displays a representation of how the content item was presented. be able to. For example, the user interface generator 229 may affect the type of device on which the content item was presented, the location of the resource on which the content item was presented, the type of resource on which the content item was presented, and / or the presentation of the content item Probabilistic determinations may be made for a particular impression based on other suitable data that is possible.

  The display card can present a subset of the methods in which it was determined that the content item was presented. For example, the user interface generator 229 may make a probabilistic determination as to how the content item was displayed for each impression of the content item. User interface generator 229 may count the number of impressions for each method in which a content item may be presented based on a probabilistic determination. The user interface generator 229 may then generate a display card that shows a representation of the content item for the method with the most impressions. For example, the top four representations based on impressions may be presented in the display card. In this way, the user can quickly see how the content item is likely to be presented to the user.

  FIG. 4 is a flow diagram of an example process 400 for reducing latency in presenting account data. The operations of process 400 may be implemented, for example, by a data processing device such as account management system 210 of FIG. Process 400 may also be implemented by instructions stored on a computer storage medium, where execution of instructions by the data processing device causes the data processing device to perform the operations of process 400.

  A given user is authenticated (402) for an online account. The online account may be an account that the user can access. For example, the user may be an employee of an organization whose account management system manages the account data of the organization. Multiple different users may be able to access the account. For example, an organization may have different employees with different roles (e.g., product manager, brand manager, campaign manager, etc.) that each have access to an online account to view and / or modify data related to the employee You may have.

  A given user may be authenticated based on data submitted through the given user's client device. For example, a user may provide a unique username and password for accessing an online account. A user may be authenticated for an online account if the username and password provided by the given user matches the username and password stored for the given user.

  In response to authenticating the user, a user session is initiated for the given user (404). A user session allows a user to view account data regarding an online account. Account data can be presented to the user using one or more user interfaces. For example, a dashboard may be presented to the user. This dashboard can include an initial account view with an account summary. In addition, the dashboard may include links or other user interface controls that allow the user to request additional data or select other display cards that a given user may be interested in. .

  A user group to which a given user is assigned is identified (406). For example, a given user may interact between a given user's interaction with a user interface element presented within the user interface of the account during a previous user session and other user's other interactions with the user interface element. May be assigned to one or more user groups based on their similarity. A given user is a user based on the similarity between at least one data type requested by a given user during a previous user session and at least one data type requested by another user. It may be assigned to a group. An exemplary process for assigning users to user groups is shown in FIG. 6 and described below.

  A first data set associated with the online account is selected (408). The first data set includes account data for an online account that the user is authorized to access. For example, the first data set may include account data for presentation in an initial account view that provides an overview of an online account to a given user. The initial account view is customized for a given user and the user's previous request for user interface elements (e.g., specific display cards, controls, graphs, etc.) and / or user interface elements (e.g., specific display cards) , Controls, graphs, etc.), a given user's request or modification to data or data type, a given user's request or view of a particular dimension of data (e.g., time duration, geographical location, etc.) , Based on how often a given user accesses an online account, the preferences selected by the given user, the user group to which the given user is assigned, and / or other appropriate data Also good. The initial account view can be combined into a single presentation to present multiple different types of data that provide an overview of the online account to a given user.

  In some implementations, the first data set for presentation in the initial account view is the user's previous interaction with the user interface presented in the given user's previous user session and / or the given The user may be selected from a data store of account data related to the online account based on the user group to which the user is assigned. For example, the first data set may be a type of data requested by a given user during a previous user session and / or a user interface element that a given user interacted with during a given user's previous user session. May be selected based on The first data set may also be selected based on the type of data requested by other users in the user group to which a given user is assigned and / or user interface elements that other users interact with. Good.

  A second data set associated with the online account is selected (410). The second data set may include data that is not presented in the initial account view. Alternatively, the second data set may be sent to a given user's client device for caching at the client device. In this way, if a given user requests to view additional data that is not shown in the initial account view but is included in the second data set, the additional data will receive additional data from the remote device. It can be presented to a given user without request. Therefore, latency when presenting additional data can be reduced.

  In general, the second data set may include data that is likely to be associated with a given user, but may not be as relevant as the data in the first data set. Also, the second data set is selected based on the user's previous interaction with the user interface presented in the given user's previous user session and / or the user group to which the given user is assigned. It is possible. For example, the second data set was requested by at least a threshold number of other users in the user group to which a given user was assigned or requested at least a threshold number of times by other users in the user group It may be data.

  The user interface for the account is updated (412) to present at least a portion of the first data set. For example, the user interface on which a given user submitted authorization data can be updated to present an initial account view of an account for the given user. The initial account view that provides an overview of the online account for a given user can include at least a portion of the first data set.

  The latency in updating the user interface when presenting the first data set or an additional portion of the second data set at the client device before the client device receives a request for the second data set from the client device. Reduced by providing the device with a second data set (414). For example, the second data set can be transmitted to the client device along with the first data set. In another example, the second data set may be sent to the client device after the first data set is sent to the client device but before the request for the second data set is received. Is possible. The second data set (and the first data set) can be stored in the client device cache to reduce latency in presenting the cached data when requested at the client device. is there.

  After each user session, a given user's profile can be updated based on the data during the user session and the user's interaction with user interface elements. Based on updates to the profile, the initial account view for the user may be updated. For example, the initial account view may be updated to present the display card requested by the user during the user session and / or data requested or modified by the user during the user session. What is included in the first data set and / or the second data set may be similarly updated based on updates to a given user's profile.

  The client device cache may be refreshed with updated data, for example, if the data has changed or if the data has been stored in the cache for at least a threshold amount of time. However, there are costs associated with updating the cache. For example, a large amount of data may need to be acquired and transmitted over a network. Accordingly, a pre-cache engine, such as pre-cache engine 223 of FIG. 1, can determine whether to update the cache based on these costs and benefits associated with updating the cache.

  FIG. 5 is a flow diagram of an example process 500 for updating a cache. The operations of process 500 may be implemented, for example, by a data processing device such as account management system 210 of FIG. Process 500 can also be implemented by instructions stored on a computer storage medium, where execution of instructions by the data processing apparatus causes the data processing apparatus to perform the operations of process 500.

  A trigger for updating the cache of the client device is identified (502). In some implementations, the trigger may be based on the amount of time that has elapsed since the data was sent to the client device for storage in the cache. The trigger can also be based on whether the data stored in the cache has changed from the value stored in the cache. For example, the number of conversions for a content item may have increased due to a new conversion event that occurred after the cache was populated with data containing the number of conversions for the content item. The trigger can be based on the number of data items that have changed since the data was sent to the client device for storage in the cache. For example, a cache update may be triggered if at least a threshold number of data items change. Triggers can also be based on user modifications to account data.

  In response to identifying the trigger, a determination is made whether the cache should be updated (504). The determination can be based on the costs associated with updating the cache and the benefits associated with updating the cache. For example, updates to the cache require the use of computational and network resources to obtain updated data and send the updated data to the client device. Another cost is the amount of time it takes to update the cache with updated data.

  Profit includes presenting the latest data rather than the old data. Benefits may also include reduced latency in presenting updated data when, for example, a client device requests updated data in response to a user request to view the data. However, the benefit of the latest data to the user may depend on the type of data. For example, the impression data for the previous year is unlikely to change, and any changes are likely to be minimal. Thus, the benefits of updating the cache with data regarding past time periods may be of little benefit. However, the benefit of updating the current day's performance data can be very beneficial to the user.

  In some implementations, the determination of whether to update the cache is based on the type of data and / or the amount of data stored in the cache. For example, some types of data may take more time to acquire and provide over the network and / or include more data that must be transmitted. In some implementations, the determination of whether to update the cache is based on historical data related to the type of data and / or the amount of data stored in the cache. For example, the determination may be based on an analysis of the number of previous latencies with respect to previous query patterns.

  If it is determined not to update the cache, the cache is not updated. Instead, the process 500 may wait until another trigger is identified, at which time another determination can be made whether to update the cache. If a determination is made to update the cache, updated data is obtained for at least a portion of the data stored in the cache (506). For example, all of the cached data may be updated. In another example, only data that has changed since the data was cached at the client device may be updated.

  The updated data is sent to the client device (508). For example, the updated data may be sent over the network to the client device using one or more data transmissions of one or more data packets. When received, the client device can replace the previous cached data with the updated data.

  FIG. 6 is a flow diagram of an example process 600 for assigning a given user to a user group and identifying data to provide to the given user based on the user group. The operations of process 600 may be implemented, for example, by a data processing device such as account management system 210 of FIG. Process 600 can also be implemented by instructions stored on a computer storage medium, where execution of instructions by the data processing apparatus causes the data processing apparatus to perform the operations of process 600.

  A user profile for a given user is obtained (602). The user profile for a given user can include data describing previous user interaction with the user interface presenting account data. For example, as described above, a user profile for a given user may include data identifying each user interface element that a given user interacts with, the number of times a given user interacts with the user interface element, and / or a given Frequency of user interaction with user interface elements. The user profile for a given user is the data that identifies each type of data requested or modified by a given user, the number of times a given user requested or modified each type of data, and the given The frequency with which a given user requests or modifies each type of data may also be included. The same identifying and frequency data can be stored for each particular portion of actual data requested or modified by a given user. For each type of data and / or for each specific part of the data requested by a given user, the user profile includes dimensions related to the data (e.g. time period or geographical location for the data) Can do.

  A given user is assigned to a user group based on a user profile for the given user (604). In some implementations, a given user is assigned to a user group based on the similarity between a given user's profile and other users' user profiles. For example, a given user may be assigned a user group having other users with similar user profiles. In particular, a given user is presented in a given user interaction and user interface with a user interface element (e.g., control) presented in the user interface for the user's account during a previous user session. May be assigned to user groups based on similarities between other user interface elements and other user interactions. In addition, a given user may have a similarity between the type of data requested by a given user and the type of data requested by other users, and / or the data requested by a given user. User groups may be assigned based on the similarity between the dimensions and the dimensions of the data requested by other users.

  In some implementations, a machine learning process is used to generate user groups and populate data based on the similarity between the user's user profiles. For example, the machine learning process may be based on decision trees, neural networks, deep learning, and / or clustering techniques.

  Types of data and user interface elements are identified for a given user based on the user group to which the given user is assigned. For example, a given user may be provided with the type of data requested by other users in the group and / or user interface elements selected or viewed by other users in the group. In certain examples, a given user may be provided with the type of data requested by at least a threshold number of users in the user group or the type of data most frequently requested by users in the user group. . Similarly, a given user may be a user interface element that is selected or viewed by at least a threshold number of users in the group and / or a user interface that is most frequently selected or viewed by users in the user group. Elements may be provided.

  FIG. 7 is a flow diagram of an example process 700 for generating a visualization that presents account data for multiple campaigns. The operations of process 700 can be implemented, for example, by a data processing device such as account management system 210 of FIG. Process 700 can also be implemented by instructions stored on a computer storage medium, where execution of instructions by the data processing apparatus causes the data processing apparatus to perform the operations of process 700.

  Multiple campaigns of account holders are identified (702). For example, an account holder may have multiple different content distribution campaigns. In certain examples, an account holder may have multiple different campaigns for products or services. Account holders may also have campaigns for other products or services.

  A set of similar campaigns for account holders is identified (704). A set of similar campaigns can include campaigns with specific characteristics that are similar but all of the campaigns are different. For example, an account holder may have multiple different campaigns for a particular product that use the same delivery criteria but have different content items delivered for each campaign. These different campaigns can be included in a set of campaigns for a particular product.

  A visualization for the set of campaigns is generated (706). For example, visualization may highlight data differences for campaigns within a set of campaigns. Continuing with the above example, the visualization may highlight the outcome of each content item for each campaign in the set of campaigns. The visualization can be automatically generated and presented in a display card for presentation on the account holder user's client device. For example, the visualization may be generated automatically in such a way that in response to identifying a similar set of campaigns, the visualization highlights one different feature.

  Although the subject matter is generally described above with reference to a content delivery management system, the subject matter is applicable in alternative systems where data is provided to the user and is not limited to managing content delivery. Will be understood.

  In addition to the above description, the user may be responsible for user information (e.g., the user's social network, social action or activity, occupation, user's preferences, or user's preferences). Allows the user to make a choice as to whether and when to activate the set of (current location information) and whether the user is to send content or communications from the server Controls may be provided. Further, specific data may be processed in one or more ways before being stored or used such that personally identifiable information is deleted. For example, if the user's identification information is such that personally identifiable information cannot be determined for the user, or the location information is obtained, the user's geographic location (city, zip code, or Can be generalized (such as to a state level) and thus processed such that a particular location of the user cannot be determined. Thus, the user may be able to control what information is collected about the user, how that information is used, and what information is provided to the user.

  Embodiments and operations of the subject matter described herein include digital electronic circuits, or computer software, firmware, or hardware, or any of these, including the structures disclosed herein and their structural equivalents. Can be implemented in one or more combinations. Embodiments of the subject matter described in this specification are encoded on a computer storage medium for execution by one or more computer programs, i.e., a data processing device, or for controlling the operation of a data processing device. Can be implemented as one or more modules of computer program instructions. Alternatively or additionally, the program instructions may be artificially generated propagation signals generated to encode information for transmission to a suitable receiver device for execution by a data processing device, such as a machine Can be encoded on an electrical signal, an optical signal, or an electromagnetic signal. The computer storage medium may be or be included in a computer readable storage device, a computer readable storage substrate, a random or serial access memory array or device, or a combination of one or more thereof. Further, a computer storage medium can be a source or destination of computer program instructions that are not propagation signals but are encoded in artificially generated propagation signals. A computer storage medium may be or be included in one or more separate physical components or media (eg, multiple CDs, disks, or other storage devices).

  The operations described herein can be implemented as operations performed by a data processing device on data stored on one or more computer-readable storage devices or received from other sources. It is.

  The term “data processing device” refers to all types of devices for processing data, including, by way of example, one programmable processor, one computer, one system on chip, or multiple or combinations thereof, Includes devices and machines. The device can include dedicated logic circuitry, such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). In addition to hardware, the device can also generate code that generates an execution environment for the computer program in question, such as processor firmware, protocol stack, database management system, operating system, cross-platform runtime environment, virtual machine, or Codes that make up one or more of these may be included. The device and execution environment can implement a variety of different computing model infrastructures, such as a web services infrastructure, a distributed computing infrastructure, and a grid computing infrastructure.

  A computer program (also known as a program, software, software application, script, or code) may be written in any form of programming language, including a compiled or interpreted language, a declarative or procedural language And can be arranged in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment . A computer program may correspond to a file in a file system, but this is not always the case. A program is part of a file that holds other programs or data (for example, one or more scripts stored in a markup language document), a single file dedicated to the program in question, or multiple It can be stored in a linked file (eg, a file that stores one or more modules, subprograms, or portions of code). A computer program may be placed on one computer, or in one location, or distributed across multiple locations and executed on multiple computers interconnected by a communication network Is possible.

  The process and logic flow described herein includes one or more programmable programs for one or more programmable programs to perform operations by performing operations on input data and generating output. It can be executed by executing. Processes and logic flows can also be performed by dedicated logic circuits, such as FPGAs (Field Programmable Gate Arrays) or ASICs (Application Specific Integrated Circuits), and the device can also perform their dedicated logic. It can be implemented as a circuit.

  Suitable processors for the execution of computer programs include, by way of example, both general and special purpose microprocessors and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for performing actions according to instructions and one or more memory devices for storing instructions and data. Also, in general, a computer includes or receives data from one or more mass storage devices for storing data, such as a magnetic disk, a magneto-optical disk, or an optical disk, Alternatively, they are operatively coupled to transfer data to those mass storage devices, or both. However, the computer may not include such a device. In addition, a computer can be another device, such as a mobile phone, personal digital assistant (PDA), mobile audio or video player, game console, global positioning system (GPS) receiver, or portable device, to name just a few. It can be incorporated into a storage device (eg, a universal serial bus (USB) flash drive). Devices suitable for storing computer program instructions and data include, by way of example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices, magnetic disks such as internal hard disks or removable disks, magneto-optical disks, and CD-ROMs Includes all forms of non-volatile memory, media, and memory devices, including disks and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, dedicated logic circuitry.

  In order to provide user interaction, embodiments of the subject matter described herein include display devices for displaying information to the user, such as CRT (CRT) or LCD (Liquid Crystal Display) monitors, and users Can be implemented on a computer with a keyboard and pointing device, such as a mouse or trackball, that can provide input to the computer. Other types of devices can also be used to provide interaction with the user, for example, the feedback provided to the user can be any form of sensory feedback, eg visual feedback, audio feedback , Or tactile feedback, and input from the user can be received in any form including acoustic, utterance, or tactile input. In addition, the computer sends a document to a device used by the user and receives the document from the device, for example, in response to a request received from the web browser, to the web browser on the user's client device. You can interact with the user by sending a page.

  Embodiments of the subject matter described herein include a back-end component, eg, as a data server, or a middleware component, eg, an application server, or a front-end component, eg, a user, herein. Includes a client computer with a graphical user interface or web browser capable of interacting with the implementation of the described subject matter, or any of one or more such back-end components, middleware components, or front-end components Can be implemented in a computing system including a combination of: The components of the system can be interconnected by any form or medium of digital data communication, eg, a communication network. Examples of communication networks include local area networks (“LAN”) and wide area networks (“WAN”), internetworks (eg, the Internet), and peer-to-peer networks (eg, ad hoc peer-to-peer networks).

  The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship between the client and the server is generated by a computer program that is executed on each computer and has a client-server relationship with each other. In some embodiments, the server provides data (e.g., HTML pages) to the client device (e.g., for the purpose of displaying data to a user interacting with the client device and receiving user input from such user). Send. Data generated at the client device (eg, the result of user interaction) can be received from the client device at the server.

  This specification includes many specific implementation details, but these should not be construed as limitations on the scope of any invention or what may be claimed, but rather specific to a particular embodiment of a particular invention. Should be regarded as an explanation of the characteristics of Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. In addition, a feature may be described above as operating in a particular combination, and may even be so claimed initially, but one or more features of the claimed combination may be In some cases, it may be deleted from the combination, and the claimed combination may be targeted to a partial combination or a variation of a partial combination.

  Similarly, operations are shown in a particular order in the figures, but this may be performed in the particular order shown or in sequential order, or to achieve the desired result. Therefore, it should not be understood that all operations shown for this need to be performed. In certain situations, multitasking and parallel processing may be advantageous. Further, the division of various system components in the above-described embodiments should not be understood as requiring such division in all embodiments, and the described program components and systems are generally simply It should be understood that they can be integrated together in one software product or packaged into multiple software products.

  Thus, specific embodiments of the present subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes shown in the accompanying drawings do not necessarily have to be in the specific order or sequential order shown in order to achieve the desired result. In certain implementations, multitasking and parallel processing may be advantageous.

100 environment
110 Pre-cache system
115 Data storage devices
120 Data communication network
130 client devices
135 Fast cache
140 Data request
142 Requested data
144 Additional data
200 environment
210 Account management system
220 Data transmission subsystem
221 Data selector
223 pre-cache engine
225 Campaign Grouper
227 Account data storage device
229 User Interface Generator
230 Interaction Logger
232 Interaction Log
235 User Group Engine
240 front-end server
245 fast cache
250 Data communication network
260 Account holder
262 client devices
264 fast cache
266 Account Viewer
270 account holder
272 client devices
300 screenshots
310 User interface
320 Menu
331 display card
333 display card
335 display card
337 Display card
339 display card
400 processes
500 processes
600 processes
700 processes

Claims (10)

A method performed by a data processing device, comprising:
Authenticating the given user as an authorized user of a given online account based on data submitted through the given user's client device;
Initiating a user session in which data related to an account is presented to the user for the given user and in response to the authentication, wherein the account has credentials to access the account Accessible by a plurality of users having information; and
(i) the similarity between the given user's interaction with the user interface element presented in the user interface of the account during a previous user session and the other user's other interaction with the user interface element Or (ii) similarity between at least one data type requested by the given user during the previous user session and at least one data type requested by other users Identifying a user group to which the given user is assigned;
Selecting a first data set associated with the account based on the user group to which the given user is assigned, the first data set comprising at least (i) the previous user session Selected based on the type of data requested by the given user during, and (ii) user interface elements that the given user interacted with during the previous user session;
Selecting a second data set associated with the account based on the type of data previously requested by at least one user in the user group other than the given user;
Updating a user interface for the account to present at least a portion of the first data set in an initial account view for the account, the initial account view comprising an overview of the account Presenting a plurality of different types of data combined into a single presentation providing
Providing the second data set to the client device prior to receiving a request for the second data set from the client device, so that the first data set or the second data at the client device; Reducing latency in updating the user interface for the account when presenting an additional portion of the set, wherein the second data set is cached at the client device and the initial A method that includes steps that are not presented in the account view.   The method of claim 1, wherein the given user and the other users are assigned to the user group using a machine learning process that creates a plurality of user groups and assigns users to the plurality of user groups. .   The given user is (i) a time range of data requested by the given user in a previous user session, (ii) data modified by the user, or (iii) the given user The method according to claim 1 or 2, wherein is assigned to the user group further based on at least one of the frequency of accessing data associated with the account.   At least a portion of the second data set is (i) the type of data requested by the given user in the previous user session, and (ii) requested by the given user in the previous user session. The time range of the data, or (iii) selected based on at least one of the geographical regions from which the given user requested data in the previous user session. The method according to claim 1.   5. The method of any one of claims 1-4, wherein each of the plurality of users is provided with a different initial account view based on the type of data requested by each of a plurality of different users. For each given user session initiated for the given user, the user interface element with which the given user interacted during the given user session and the given user during the user session Updating a user profile for the given user with data specifying the type of data requested in
6. The method of any one of claims 1 to 5, further comprising: modifying the initial account view for the given user based on the updating step. Determining to update the cache of second data at the user device based on a data cost for updating the cache being less than a threshold cost;
7. The method of any one of claims 1 to 6, further comprising: providing the user device with an updated data set in response to determining to update the cache. Identifying the two or more campaigns of the account having at least one same feature and at least one feature that is different for each of the two or more campaigns;
Providing data presenting data for each of the two or more campaigns in a manner that highlights the at least one feature of each of the two or more campaigns. The method as described in any one of. A system,
Memory for storing processor readable instructions;
One or more processors configured to read and execute instructions stored in said memory; and
Wherein the processor readable instructions comprise instructions configured to control the system to perform a method according to any one of claims 1 to 8,
system.   9. A non-transitory computer storage medium encoded with a computer program, wherein when the computer program is executed by one or more data processing devices, the data processing device is any one of claims 1 to 8. A non-transitory computer storage medium comprising instructions for performing an operation comprising the method of claim 1.

Images