US20160134713A1

US20160134713A1 - System and method for tracking and illustrating user activity in a network environment

Info

Publication number: US20160134713A1
Application number: US14/538,983
Authority: US
Inventors: Michael George Maxim; David F. Koh
Original assignee: Match com LLC
Current assignee: Match Group LLC
Priority date: 2014-11-12
Filing date: 2014-11-12
Publication date: 2016-05-12
Also published as: US20230319153A1; US12107932B2; US20250016242A1

Abstract

A method is provided in one example embodiment and includes detecting actions taken by users in a computer-implemented matching system and, for each of the detected actions, storing data indicative of the detected action. The method further includes filtering the stored data in accordance with at least one filter selected by an administrator of the computer-implemented matching system and creating a user action log from the filtered stored data. The user action log includes all of the stored data that matches the selected at least one filter. The at least one filter may include log start time, log end time, type of action, user ID, target user ID, and/or site type. The detected action may include viewing another user's profile, changing the user's own profile, sending a message to another user via the computer-implemented matching system, and/or performing a matching search using the computer-implemented matching system.

Description

TECHNICAL FIELD

This disclosure relates in general to the field of communications and, more particularly, to a system and a method for tracking and illustrating user activity in a network environment.

BACKGROUND

Communications network architectures have experienced significant notoriety because they can offer the benefits of automation, convenience, and data management for their respective online communities. Certain network protocols may be used in order to allow an end user to be matched to other end users or to scenarios in which they stand to benefit (e.g., job searches, person-finding services, real estate searches, online dating, etc.).
In the case of an online dating service, for example, an end user will typically be prompted to specify a variety of preferences to be used in matching the end user with other end users in a particular online dating community. The information each end user provides about him or herself may be viewed by other end users in the online community in determining whether to interact with that end user. In certain cases, the actual dating platform can participate in matching activities. This interventionist involvement can often spur or provoke new relationships being formed.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:

FIG. 1 is a network diagram showing an operating environment of the present disclosure in accordance with one embodiment of the present disclosure;

FIGS. 2A-J are simplified screen shots of an example protocol for participating in an on-line dating service in accordance with one embodiment of the present disclosure;

FIG. 3 illustrates a block diagram of an embodiment of a system for implementing a user action log in connection with an online dating service in accordance with embodiments of the present disclosure;

FIG. 4 illustrates a user action log in accordance with certain aspects of embodiments described herein; and

FIGS. 5A-5D illustrate various graphs and charts that may be displayed on a match dashboard user interface in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

A method is provided in one example embodiment and includes detecting actions taken by users in a computer-implemented matching system and, for each of the detected actions, storing data indicative of the detected action. The method further includes filtering the stored data in accordance with at least one filter selected by an administrator of the computer-implemented matching system and creating a user action log from the filtered stored data. The user action log may include all of the stored data that matches the selected at least one filter. In certain embodiments, the storing may include accumulating the data in a disk array. Other embodiments may include transferring the accumulated data from the disk array to an analysis cluster. The method may further include presenting the accumulated data using a presentation type selected by the administrator of the computer-implemented matching system. In certain embodiments, the presentation type is one of a user action log, a pie chart, a list, and a graph. The at least one filter comprises at least one of log start time, log end time, type of action, user ID, target user ID, and site type. The detected action may include at least one of viewing another user's profile, changing the user's own profile, sending a message to another user via the computer-implemented matching system, and performing a matching search using the computer-implemented matching system.

Example Embodiments

FIG. 1 is a simplified block diagram of a system 10 for facilitating an online dating scenario in a network environment. In other embodiments in which communications or matching is valuable, system 10 can be leveraged to identify and to evaluate suitable candidates in other areas (e.g., hiring/employment, recruiting, real estate, general person searches, etc.). FIG. 1 includes multiple end users 12 and endpoints 13, a communications network 14, one or more servers, represented in FIG. 1 by a web server 16, each comprising memory 18 and a at least one processor 20, a website 22, and a data store 24. Data store 24 may be any type of mechanism(s) for storing data, including but not limited to one or more files, databases, memory devices, mass storage devices, data centers, disk arrays, etc. System 10, users 12 interact with web server 16 via endpoints 13, each of which comprises an appropriate user interface for interacting with web server 16 via website 22 for facilitating functions and features described herein. In certain example implementations, website 22 and web server 16 are consolidated into a single component, physical structure, equipment, etc.
FIG. 1 may be configured such that inter- and intra-communications are readily achieved by any of the components included therein. The present disclosure is capable of providing both an online component (as illustrated in FIG. 1) and an off-line component such that one or more end users can meet, gather information, resolve to meet, and then subsequently meet in person with the assistance of system 10. Ancillary components to such a comprehensive process may involve pre-date profiles, post-date follow-ups, and a myriad of other significant features, some of which are outlined in detail below.
End users 12 may include a variety of types of end users, such as clients, customers, prospective customers, or entities wishing to participate in an online dating scenario and/or to view information associated with other participants in the system. End users 12 may also seek to access or to initiate communications with other end users that may be delivered via communications network 14. End users 12 may review data (such as user profiles, for example) associated with other users in order to make matching decisions or selections. Data, as used herein in this document, refers to any type of numeric, voice, video, or script data, or any other suitable information in any appropriate format that may be communicated from one point to another.
End users 12 may access the aforementioned data via endpoints 13, which may be inclusive of devices used to initiate a communication. Note that the broad term “user” encompasses any type of node or user device, or any type of endpoint discussed herein. Additionally, the term “user” can further include any type of profile to be used in the system discussed herein. Hence, the term “user” can include (but is not limited to) elements such as a computer, a personal digital assistant (PDA), a laptop or electronic notebook, a cellular telephone, an IP telephone, an iPhone™, an iPad™, a Microsoft Surface™, an Android™ phone, a Google Nexus™, or any other device, component, element, or object capable of initiating voice, audio, or data exchanges within communication system 10. The endpoints may be inclusive of a suitable interface to the end user 12, such as a microphone, a display, or a keyboard or other terminal equipment. Endpoints 13 may also include any device that seeks to initiate a communication on behalf of another entity or element, such as a program, a database, or any other component, device, element, or object capable of initiating a voice or a data exchange within communication system 10. In addition, each of the endpoints 13 may be a unique element designed specifically for communications involving system 10. Such an element may be fabricated or produced specifically for matching applications involving end user 12 and endpoint 13.
A user may employ any device capable of operating as an endpoint 13 to connect to communications network 14 via wire, wireless, cellular, satellite link or other suitable interfaces. Web server 16, which as previously noted includes memory 18 and at least one processor 20, hosts website 22 and has access to transmit and receive user or presence data (e.g., user profile data, user and/or user endpoint data, user contact data) from database 24. Presence data may be collected, aggregated, and utilized as required to facilitate communications between endpoints 12 over communications network 10 or other outside communication systems. Presence data may also include information and/or instructions enabling the creation, duration, and termination of communication sessions between diverse endpoints 13 that utilize different communication and/or networking protocols.
Communications network 14 is a communicative platform operable to exchange data or information emanating from endpoints 13. Communications network 14 represents an Internet architecture in a particular embodiment of the present disclosure, which provides end users 12 with the ability to electronically execute or to initiate actions associated with finding a potential match candidate. Alternatively, communications network 14 could be a plain old telephone system (POTS), which end user 12 could use to perform the same operations or functions. Such transactions may be assisted by management associated with website 22 or manually keyed into a telephone or other suitable electronic equipment. In other embodiments, communications network 14 could be any packet data network (PDN) offering a communications interface or exchange between any two nodes in system 10. Communications network 14 may alternatively be any local area network (LAN), metropolitan area network (MAN), wide area network (WAN), wireless local area network (WLAN), virtual private network (VPN), intranet, or any other appropriate architecture or system that facilitates communications in a network or telephonic environment.
In one embodiment, web server 16 comprises a server that is operable to receive and to communicate information to one or more end users 12. In a generic sense, web server 16 can implement a computer-implemented matching system that provides a framework for suitable matching activities. Alternatively, web server 16 may be any switch, router, gateway, cache, server blade, software, processor, proprietary component, object, module, or element (or any combination of these) operable to facilitate communications involving end user 12. Web server 16 may be integrated with database 24 and/or website 22, where any one or more of these elements may share or otherwise coordinate the activities discussed herein.
In one particular embodiment, web server 16, via interaction with database 24 and/or in conjunction with website 22, is engaged in facilitating interaction(s) between parties interested in seeking a romantic partner (i.e., online dating). For example, website 22 can be online dating service provider www.Match.com, www.Chemistry.com, www.okcupid.com, or any other suitable provider. In certain example scenarios, a given end user may pay a fee for a subscription-based service (and potentially, only those users would qualify to be eligible to participate in events in certain example implementations, although other example embodiments involve non-members being eligible for participation). Additionally, certain end user fee structures may apply to different tiers of service: some of which may entitle an end user to enhanced features on website 22 (e.g., the ability to communicate more frequently with other users, additional matches being provided (potentially, more frequently) to an end user who paid the higher fee structure, the ability to store data, the ability to share data, the ability to upload additional information, the ability to target specific searches based on particular criteria, the ability to receive preferential positioning in the context of being matched to other users, the ability to perform video calls (e.g., Skype, etc.) with other users, the ability to perform audio calls with other users, etc.).
In certain embodiments, website 22 is a computer-implemented matching system, which may be any website or architecture provided for facilitating a connection involving two or more people, and which may make use of a given profile, photograph, resume, article description, etc. This could include services associated with job placements, escort services, auction services, social media, real estate listings, recruiting services (e.g., in athletics, academia, employment scenarios, instances involving the sales of goods and services), etc.
Considerable flexibility is provided by the structure of web server 16 and website 22 in the context of system 10. Thus, it can be easily appreciated that such functions could be provided external to web server 16 or website 22. In such cases, such a functionality could be readily embodied in a separate component, server, processor, device, or module. Note that these online dating features and capabilities may be provided in just one of these elements, in both, or distributed across both of them. Hence, in certain embodiments, the online dating operations may be consolidated in a single website, where no redirection is needed, nor performed for the user.
In operation of an example embodiment, consider a case where a given end user is interested in participating in an online dating scenario. End user 12 can access website 22 via the communications network 14 (which in the example presented comprises the Internet) using endpoint 13, register, and create a profile on the site. Moreover, end user 12 can access website 22 through any suitable banner, pop-up, partnership, e-mail solicitations, direct mailings, etc. It can be appreciated that online commerce can be generated by a plethora of marketing tools and any such tools can readily cooperate with the operations of the present disclosure.
At this point, matching of any form can commence amongst the members of the online community. For example, in the context of a romantic endeavor, a person may begin the dating process or engage in communications that would spawn such dating. Other applications could include job applicants who are being sought by employers. Any of the individuals who reside in the online community can begin using any of the tools or capabilities of the platform.
FIGS. 2A-2J illustrate example screen shots that may be provided in the online dating process to facilitate presentation of information to and gathering of information from member end users. FIGS. 2A-2J are presented herein for purposes of discussion. It is imperative to note that these illustrations are only being provided to further outline a particular implementation of the present disclosure. In no way should these diagrams be used to limit or to restrict the broad teachings of the present disclosure. Such illustrative information has been offered earnestly and, thus, should not be construed to confine the broad applications of the present disclosure.
FIG. 2A is an example screen shot of a home page from which an interested end user may begin his/her journey. In the illustrated example, the home page solicits location information, such as a city or zip code, as well as an indication of the end user's gender and an age range and gender preference of persons the end user is interested in “meeting” via system 10. Subsequent to the end user's completion of the requested information and clicking on a “How it Works” icon on the home page of FIG. 2A, a screen shot as shown in FIG. 2B is presented to the end user. The screen shot of FIG. 2B provides a generic outline of the online dating process. As outlined in the screen shot of FIG. 2B, as a first step, an end user may choose to browse the website to view pictures of members along with summaries of the members' profiles. After browsing the website, the end user may decide to create a free profile. Once the end user browses the website and creates a profile, the end user may opt to subscribe to the service and receive information from/about others who are part of the online community. For purposes of example and ease of explanation, it will be assumed for the remainder of the discussion of FIGS. 2A-2D that the potential new end user investigating and ultimately subscribing to the service is a male named “Tom” who is interested in finding a female match.
FIG. 2C is an example screen shot of a number of profiles that may be viewed by Tom during the browsing phase described above. In the context of this shot, Tom may be simply browsing. Assuming Tom has decided he would like to know more about one of the members whose profile is presented in FIG. 2C, he may click on the picture associated with the selected profile. For example, assuming Tom has decided he would like more information about “LadyDi520”, clicking on her picture results in his being directed to a web page as shown in FIG. 2D, where he is solicited to sign up for the online dating subscription such that he can effectively contact his candidate selection. It will be noted that the information solicited using the page shown in FIG. 2C may be used in selecting matches for Tom. The information may also be displayed on Tom's profile or summary thereof presented to other users to assist those users in determining whether they are interested in interacting with him.
FIGS. 2E-2G illustrate various screen shots comprising a user information collection process in accordance with one embodiment. Using the web pages illustrated in FIGS. 2E-2G, system 10 collects a variety of information from an end user, including, but not limited to, basic information about the end user (FIG. 2E), as well as information about the type person the end user would be interested in dating, including information about a potential date's physical appearance (FIG. 2F) and background and values (FIG. 2G). It will be recognized that the information collected using the web pages illustrated in FIGS. 2E-2G is illustrative only and that any type/amount of information may be solicited in the illustrated manner.
FIGS. 2H-2J are example screen shots of the full profile of LadyDi520, the picture Tom selected while browsing. In illustrated profile, LadyDi520's match criteria are displayed, as well as other information that may be pertinent to a potential mate. Any suitable items can be provided in such a profile (such as interests, favorite hot spots, favorite things, desire for children, background, etc.). Virtually any type or format of information (inclusive of video and audio data) may be provided in such a profile. In particular, the profile includes information that was solicited from LadyDi520 when she set up her online dating account. The profile may include a photo, biographical information (e.g., gender, age, location, relationship status, etc.), physical information (e.g., height, weight, hair and eye color, etc.), interests (e.g., hobbies, “favorites,” etc.), lifestyle information (e.g., exercise habits, employment, smoking/drinking habits, etc.), and background/values (e.g., ethnicity, faith, education, etc.). The profile may also include a section entitled “About My Date,” in which the end user specifies preferences about the type of person he/she would like to meet/date (e.g., appearance, interests, faith, education, relationship goals, etc.). In some embodiments, a full profile, including the profile information provided by the end user and stored in the system, is displayed to interested viewers; in other embodiments, only a summary or subset of the profile information is displayed.
In certain embodiments, it may be useful a provider of an online dating service, such as that illustrated in FIG. 1, to evaluate user actions, including, for example searches performed by each user, messaging conducted between users, and profile changes for each user, to determine what is leading to interaction via the service between users. For example, an interaction between first and second users may be initiated by the first user performing a match search and viewing the profile of and/or messaging the second user, who is presented in the results of the search. Alternatively, an interaction between first and second users may be initiated by the first user's selecting the second user from the first user's “daily matches.” Still further, an interaction between first and second users may result from the second user being presented to the first user as a “similar user” to other users in which the first user has expressed interest. It will be recognized that it would be useful for the provider of the online dating system to be able to track how each user pair “met” and aggregate this data for use in evaluating the effectiveness of different “introduction methods” employed by the online dating system.
Another aspect of determining the effectiveness of different introduction methods is to determine the effect of the introduction. For example, if the first user sends a message to the second user and the second user never responds, the introduction is likely not a quality introduction. In contrast, if the first user's message results in an ongoing exchange of messages between the first and second users (e.g., such as a two-way message or a four-way message), the introduction is more likely to be viewed as a quality introduction. As used herein, a quality introduction, or message thread, is a message thread that strengthens relationships between a pair of users, engages a pair of users, etc. In contrast, a “low value” introduction or message thread is one that does not strengthen relationships between a pair of users, engage each user of the pair of users, etc.
In some embodiments, all statistics among pairs of users are aggregated and may be reviewed and/or evaluated by an administrator of the system. Such evaluation may be useful in determining the effectiveness of various aspects and/or features of the system. The statistics may be displayed in graphical format or in text format, such as a list. In other embodiments, a streaming interface that displays the various statistics by user or by feature, for example, may be provided to enable real-time analysis by an administrator.
FIG. 3 illustrates a block diagram of an embodiment of a system for implementing a user action log in connection with an online dating service, for example. As shown in FIG. 3, a user 40 interacts with a website 42 comprising an interface of an online service, which in some embodiments may be an online dating service, to interact with other users of the service. In accordance with features described herein, all actions performed by user 40 in connection with the web site 42 are captured by a web server 44 that hosts the web site 42. As used herein, “actions” may include user 40 viewing another user's profile, changing his or her own profile, sending a message to another user via the website (e.g., via instant messaging, email, or other types of messaging services provided by the website), performing a match search that results in another user's profile being displayed, viewing another user's profile, etc. For each detected action, data documenting the action is streamed to a server 44, which in some embodiments may be an in-memory Remote Procedure Call (“RPC”) server. Server 44 streams in-memory data to a disk array 46 that may reside on server 44. After a certain period of time, the accumulated data may be committed to a long term analysis cluster 48, which may be implemented as a Hadoop cluster. From the cluster 48 aggregated data may be accessed, parsed, filtered, and analyzed in various ways to analyze various features of the online service.
FIG. 4 illustrates a user action log in accordance with certain aspects of embodiments described herein. User action log is populated with data from analysis cluster 48 (FIG. 3) filtered in accordance with various filters selected by an administrator, such as log start time, log end time, type of action (e.g., view page, view recommendation, send message, etc.), user ID (which identifies the user performing the actions), target user ID (which identifies the target of the actions), and site type (e.g., desktop, mobile site, mobile app). Once the filters are selected, the actions corresponding to the selected filter(s) are displayed, e.g., in chronological order (although it will be recognized that other ordering method may be selected and employed). The user log stream interface allows service administrators to determine which actions by a user may have led to the user's positive interaction with another user. For example, if two users leave the service, citing the fact that they are in a relationship with the other user as their reason for termination of the service, it may be beneficial to search recent actions of each of the users to determine what sequence of actions led to their relationship “success”. Conversely, if a user complains that he or she has had a less than favorable experience using the service, it would be helpful to be able to track his or her recent actions to attempt to determine why that was the case.
FIGS. 5A-5D illustrate various ways in which aggregated user action data may be displayed. FIG. 5A illustrates a matching dashboard display of a user interface in accordance with one embodiment on which a pie chart illustrating first contacts by recommendation type is displayed. A list along the left side of the matching dashboard lists totals for each of a variety of criteria over a period of time, which in one embodiment is the previous day. In certain embodiments, totals are listed for all users.
FIG. 5B illustrates a matching dashboard display of a user interface in accordance with one embodiment on which a pie chart illustrating successes by recommendation type is displayed. In certain embodiments, a “success” is defined as two users disabling their respective accounts and indicating that the other user is the reason they are disabling their account (i.e., the two users have presumably entered into a relationship with one another as a result of the system). FIG. 5C illustrates a matching dashboard display of a user interface in accordance with one embodiment on which a chart illustrating various statistics by recommendation type is displayed. For example, the chart shown in FIG. 5C indicates, for each recommendation type, impressions per recommendation, views per recommendation, first contacts per view, four-ways per contact, CI sends per four-way, and successes per contact information, or “CI,” send. In certain embodiments, a CI send indicates that two users have exchanged contact information (e.g., phone number, email address). FIG. 5D illustrates a matching dashboard display of a user interface in accordance with one embodiment showing an x-y graph of the number of first contacts over a selected time period.
All of the data provided by the user action log feature may be utilized as desired by the service administrator to improve aspects features of the service.
Although the present disclosure has been described in detail with reference to particular embodiments, it should be understood that various other changes, substitutions, and alterations may be made hereto without departing from the spirit and scope of the present disclosure. For example, although the present disclosure has been described with reference to a dating protocol, any service that deals with (or that leverages) profiles, photos, resumes, user information more generally, etc. could readily benefit from the present disclosure.
Moreover, although the present disclosure has been described with reference to a number of elements included within system 10, these elements may be rearranged or positioned in any appropriate manner to accommodate any suitable networking configurations. In addition, any of the elements of FIG. 1 may be provided as separate external components to system 10 or to each other where appropriate.
It should also be noted that any of the question portions of the platform can leverage any type of format. Thus, in any aspect of the online dating process described herein, such as establishing a personality profile, for example, any suitable question format can be employed. Example formats include a Yes/No format, a multiple choice question format, a short answer format, a true/false format, etc. Other formats can readily be used in order to achieve the desired responses and solicit the appropriate data.
Note that in certain example implementations, the matching functions outlined herein, such as those carried out by web server 16 and/or provided as an application for an endpoint being operated by an end user (e.g., a mobile application for an iPhone™), may be implemented by logic encoded in one or more non-transitory, tangible media (e.g., embedded logic provided in an application specific integrated circuit (“ASIC”), digital signal processor (“DSP”) instructions, software (potentially inclusive of object code and source code) to be executed by a processor, or other similar machine, etc.). In some of these instances, a memory, as shown in FIG. 1, can store data used for the operations described herein. This includes the memory being able to store software, logic, code, or processor instructions that are executed to carry out the activities described in this Specification.
A processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, the processor, as shown in FIG. 1, could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array (“FPGA”), an erasable programmable read only memory (“EPROM”), an electrically erasable programmable ROM (“EEPROM”)) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof.
These devices illustrated herein may maintain information in any suitable memory (random access memory (“RAM”), ROM, EPROM, EEPROM, ASIC, etc.), software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein should be construed as being encompassed within the broad term “memory.” Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term “processor.” Each of the network elements can also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment.
Note that with the example provided above, as well as numerous other examples provided herein, interaction may be described in terms of more than one network element. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that system 10 (and its teachings) are readily scalable and can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of system 10 as potentially applied to myriad other architectures.
It is also important to note that the steps in the preceding flow diagrams illustrate only some of the possible signaling scenarios and patterns that may be executed by, or within, system 10. Some of these steps may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the present disclosure. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by system 10 in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the present disclosure. Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure.
Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims.

Claims

What is claimed is:

1. A method comprising:

detecting actions taken by users in a computer-implemented matching system;

for each of the detected actions, storing data indicative of the detected action;

filtering the stored data in accordance with at least one filter selected by an administrator of the computer-implemented matching system; and

creating a user action log from the filtered stored data, the user action log comprising a log of all of the stored data that matches the selected at least one filter.

2. The method of claim 1, wherein the storing comprises accumulating the data in a disk array.

3. The method of claim 2 further comprising transferring the accumulated data from the disk array to an analysis cluster.

4. The method of claim 2 further comprising presenting the accumulated data using a presentation type selected by the administrator of the computer-implemented matching system.

5. The method of claim 4, wherein the presentation type comprises one of a user action log, a pie chart, a list, and a graph.

6. The method of claim 1, wherein the at least one filter comprises at least one of log start time, log end time, type of action, user ID, target user ID, and site type.

7. The method of claim 1, wherein the detected action comprises at least one of viewing another user's profile, changing the user's own profile, sending a message to another user via the computer-implemented matching system, and performing a matching search using the computer-implemented matching system.

8. One or more non-transitory tangible media that includes code for execution and when executed by a processor is operable to perform operations comprising:

detecting actions taken by users in a computer-implemented matching system;

9. The media of claim 8, wherein the storing comprises accumulating the data in a disk array.

10. The method of claim 9, wherein the operations further comprise transferring the accumulated data from the disk array to an analysis cluster.

11. The media of claim 9, wherein the operations further comprise presenting the accumulated data using a presentation type selected by the administrator of the computer-implemented matching system.

12. The media of claim 11, wherein the presentation type comprises one of a user action log, a pie chart, a list, and a graph.

13. The media of claim 8, wherein the at least one filter comprises at least one of log start time, log end time, type of action, user ID, target user ID, and site type.

14. The media of claim 8, wherein the detected action comprises at least one of viewing another user's profile, changing the user's own profile, sending a message to another user via the computer-implemented matching system, and performing a matching search using the computer-implemented matching system.

15. An apparatus, comprising a processor and a memory, wherein the apparatus is configured to:

detect actions taken by users in a computer-implemented matching system;

for each of the detected actions, store data indicative of the detected action;

filter the stored data in accordance with at least one filter selected by an administrator of the computer-implemented matching system; and

create a user action log from the filtered stored data, the user action log comprising a log of all of the stored data that matches the selected at least one filter.

16. The apparatus of claim 15, wherein the storing comprises accumulating the data in a disk array.

17. The apparatus of claim 16 further comprising presenting the accumulated data using a presentation type selected by the administrator of the computer-implemented matching system.

18. The apparatus of claim 17, wherein the presentation type comprises one of a user action log, a pie chart, a list, and a graph.

19. The apparatus of claim 15, wherein the at least one filter comprises at least one of log start time, log end time, type of action, user ID, target user ID, and site type.

20. The apparatus of claim 15, wherein the detected action comprises at least one of viewing another user's profile, changing the user's own profile, sending a message to another user via the computer-implemented matching system, and performing a matching search using the computer-implemented matching system.