Processing apparatus, processing program, and processing method

Abstract

The present invention provides a processing unit that appropriately handles user access to web pages. [Solution] In the processing system 1, the management device 300, which is a processing device, obtains a first request for a user to access a web page via a user terminal device available to the user, assigns first contact information selected from a plurality of contact pieces of information for contacting a provider of services or goods to the access related to the first request in order to identify the access related to the first request, outputs display information of the web page including the assigned first contact information to the user terminal device, and selects whether or not to maintain the assignment of first contact information to the access related to the first request based on whether or not the user has left the web page or another web page in the same domain as the web page.

Description

Technical Field

[0001] The present disclosure relates to a processing apparatus, a processing program, and a processing method for processing contacts from a web page by a user.

Background Art

[0002] Conventionally, so-called tracking technologies for tracking and analyzing the route until a user accesses a predetermined web page and the user's browsing history on the web page have been known. For example, Patent Document 1 describes a management system that associates an access log and an incoming call history by collating a contact phone number and a destination phone number. However, there has been room for improvement in the method of utilizing the information obtained by such a method.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The present disclosure has been made from the above-described background, and provides a processing apparatus, a processing program, and a processing method capable of appropriately processing access to a web page by a user.

Means for Solving the Problems

[0005] According to one aspect of the present disclosure, a processing device is provided comprising at least one processor, wherein the at least one processor obtains a first request for a user to access a web page via a user terminal device available to the user, assigns first contact information selected from a plurality of contact pieces of information for contacting a provider of services or goods to the access relating to the first request in order to identify the access relating to the first request, outputs display information of the web page including the assigned first contact information to the user terminal device, and performs a process to select whether or not to maintain the assignment of the first contact information to the access relating to the first request based on whether or not the user has left the web page or another web page in the same domain as the web page.

[0006] According to one aspect of the present disclosure, a processing method is provided for a computer having at least one processor, the method being performed by the at least one processor, the method comprising: obtaining a first request for a user to access a web page via a user terminal device available to the user, and assigning first contact information selected from a plurality of contact pieces of information for contacting a provider of services or goods to an access relating to the first request in order to identify the access relating to the first request; outputting display information of the web page including the assigned first contact information to the user terminal device; and selecting whether or not to maintain the assignment of the first contact information to the access relating to the first request based on whether or not the user has left the web page or another web page in the same domain as the web page.

[0007] According to one aspect of the present disclosure, a processing program is provided which causes a computer having at least one processor to function to obtain a first request for a user to access a web page via a user terminal device available to the user, assign first contact information selected from a plurality of contact pieces of information for contacting a provider of services or goods to the access relating to the first request in order to identify the access relating to the first request, output display information of the web page including the assigned first contact information to the user terminal device, and execute a process to select whether or not to maintain the assignment of the first contact information to the access relating to the first request based on whether or not the user has left the web page or another web page in the same domain as the web page. [Effects of the Invention]

[0008] According to this disclosure, it is possible to provide a processing device, a processing program, and a processing method that can appropriately handle user access to web pages.

[0009] The effects described above are merely illustrative for the sake of explanation and are not limiting. In addition to, or in lieu of, any other effects described herein or that would be obvious to those skilled in the art may be achieved. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a schematic diagram showing an overview of the processing performed by the processing system 1 according to the embodiment of this disclosure. [Figure 2] Figure 2 is a conceptual diagram illustrating the configuration of the processing system 1 according to the embodiment of this disclosure. [Figure 3] Figure 3 is a block diagram showing an example of the configuration of a management device 300 according to an embodiment of this disclosure. [Figure 4A]Figure 4A is a conceptual diagram showing a tracking management table stored in the management device 300 according to an embodiment of this disclosure. [Figure 4B] Figure 4B is a conceptual diagram showing a user management table stored in the management device 300 according to the embodiment of this disclosure. [Figure 5A] Figure 5A is a diagram showing the processing sequence executed in the processing system 1 according to the embodiment of this disclosure. [Figure 5B] Figure 5B is a diagram showing the processing sequence executed in the processing system 1 according to the embodiment of this disclosure. [Figure 5C] Figure 5C is a diagram showing the processing sequence executed in the processing system 1 according to the embodiment of this disclosure. [Figure 6A] Figure 6A is a diagram showing the processing flow of the process performed in the management device 300 according to the embodiment of this disclosure. [Figure 6B] Figure 6B is a diagram showing the processing flow of the process performed in the management device 300 according to the embodiment of this disclosure. [Figure 6C] Figure 6C is a diagram showing the processing flow of the process performed in the management device 300 according to the embodiment of this disclosure. [Figure 6D] Figure 6D is a diagram showing the processing flow of the process performed in the management device 300 according to the embodiment of this disclosure. [Figure 6E] Figure 6E is a diagram showing the processing flow of the process performed in the management device 300 according to the embodiment of this disclosure. [Figure 7] Figure 7 shows the processing flow of the processes performed to generate a trained estimation model according to the embodiment of this disclosure. [Figure 8] Figure 8 is a conceptual diagram illustrating an example of behavioral information used in the processing according to the embodiments of this disclosure. [Figure 9A] Figure 9A shows an example of a web page displayed on the user terminal device 100-2 in an implementation of this disclosure. [Figure 9B]FIG. 9B is a diagram showing an example of a web page displayed on the user terminal device 100-2 in another embodiment of the present disclosure. [Figure 9C] FIG. 9C is a diagram showing an example of a web page displayed on the user terminal device 100-2 in another embodiment of the present disclosure. [Figure 9D] FIG. 9D is a diagram showing an example of a web page displayed on the user terminal device 100-2 in another embodiment of the present disclosure.

Embodiments for Carrying Out the Invention

[0011] Embodiments of the present disclosure will be described with reference to the accompanying drawings. In the drawings, common components are denoted by the same reference numerals.

[0012] 1. Overview of Processing System 1 related to this disclosure The processing system 1 according to the present disclosure is, for example, used to provide user attribute information and the like to the provider of a service or product introduced on the web page or the distributor of the web page when receiving a contact using, for example, a call from a user who has viewed the web page.

[0013] FIG. 1 is a diagram schematically showing an overview of the processing by the processing system 1 according to the embodiment of the present disclosure. The user terminal device included in the processing system 1 is a terminal device available to the user. The user terminal device, for example, receives a user's operation input, starts an application program (for example, a browser application), and executes a search process for a web page. When the user terminal device receives a selection of a desired access destination web page from the search web page on which the result is displayed, it transmits a distribution request for the selected web page to the distribution device. The distribution device transmits display information and the like for displaying the web page to the user terminal device.

[0014] The user terminal device outputs a web page to a display or similar device, making it viewable by the user. Subsequently, if the user terminal device, for example, shows interest in a service or product on the web page, it receives user input regarding contact information displayed on the web page, initiates contact (e.g., makes a phone call) with the provider of the service or product, and extracts behavioral information such as access history related to the web page.

[0015] When the management device receives a contact (e.g., a phone call) from a user terminal device, it forwards the contact (e.g., a phone call) to a provider terminal device available to the service or product provider. The management device provides the provider terminal device with the user's attribute information. The provider terminal device to which the contact (e.g., a phone call) is forwarded and the provider terminal device to which the attribute information is provided may be the same device or different devices.

[0016] Furthermore, the management device provides user attribute information to distributor terminal devices that can be used by distributors who distribute web pages introducing services or products.

[0017] Typically, unique contact information is assigned each time a user accesses a webpage to collect user behavior information and provide attribute information. However, such contact information, often using phone numbers, is limited in number and cannot always be used exclusively for that user's access. By estimating the usage status of this contact information based on user behavior information, the management system can efficiently manage this limited amount of contact information.

[0018] Furthermore, as mentioned above, there are qualitative differences in web page access and input regarding contact information. For example, the fees that providers pay to distributors and administrators may be determined by the frequency of input regarding contact information, but contact information may be manipulated fraudulently to increase this frequency. In other words, there are differences in the quality of input, such as differences in the degree of interest in the services or products introduced on the web page, or differences in the degree of actual purchase intent even if there is interest in the service or product. By estimating such quality based on behavioral information, the management device can make the attribute information provided more appropriate.

[0019] In this disclosure, "processing device" means a device that performs any of the processing related to this disclosure, and may be a management device, distribution device, user terminal device, provider terminal device, distributor terminal device, or any other device. In the following, the case in which a management device functions as a processing device will be described, but it is not limited to just the management device.

[0020] Furthermore, in this disclosure, "web page" refers to information output from the accessing device to each terminal device via a browser. Specific examples of web pages include a first web page accessed through a search using a browser application, or via a link in an displayed advertisement, and a second web page that displays advertisements and is accessed via a web page used when accessing the first web page.

[0021] A first webpage is a webpage created by a specific organization or individual to post information related to that organization or individual. While a webpage's destination is identified by its URL, a first webpage typically includes the domain (top-level domain, second-level domain, third-level domain, etc.) acquired by the organization or individual following the protocol. An example of a first webpage is a landing page. Such a first webpage (e.g., a landing page) includes introductory information introducing a specific service or product, an application page for the service or product or a link to access the application page, and contact information such as a telephone number. Preferably, the purpose of such a first webpage (e.g., a landing page) is to increase conversions such as purchase, inquiry, or request for information regarding the product or service viewed by the user. In this disclosure, "first webpage" is described as being accessible to an unspecified number of people via a browser application, etc., but it may also be a webpage prepared on a so-called intranet that is only accessible to specific individuals.

[0022] A second webpage is any other webpage accessed before reaching the first webpage. Typically, a second webpage includes a domain (top-level domain, second-level domain, and third-level domain, etc.) acquired by the search engine provider (e.g., the distributor) following the protocol. An example of a second webpage is a search webpage that displays the results of a search using specific keywords in the search engine. Such a second webpage (e.g., a search webpage) may include advertisements that include the first webpage to pique the user's interest, as well as link information (e.g., URLs) to the webpage hit by the search.

[0023] In this disclosure, the second webpage is any other webpage accessed via the path leading to the first webpage. Therefore, if access to webpage A is accessed via webpage B, webpage A becomes the first webpage and webpage B becomes the second webpage. Similarly, if access to webpage C is accessed via webpage A, webpage C becomes the first webpage and webpage A becomes the second webpage. In other words, the same webpage may sometimes be the first webpage and sometimes the second webpage.

[0024] Furthermore, in this disclosure, "contact" simply means making contact with another person (e.g., a provider) in order to transmit information. Therefore, the means of contact may be telephone, email, chat, or a combination thereof. Moreover, the recipient of such contact does not need to be a human being; it may be a chatbot, for example.

[0025] Furthermore, in this disclosure, "provider" means a person who provides a service or product. Therefore, a provider may be not only a specific individual, but also a group or organization (e.g., a company). Also, provider terminal equipment does not mean equipment that can be used by a specific individual, but broadly includes equipment that can be operated or used by a group or organization. In addition, provider terminal equipment is used to receive transfers of contacts (e.g., phone calls) and to receive attribute information, but the provider terminal equipment that receives transfers and the provider terminal equipment that receives attribute information do not always have to be the same device, and may be different devices.

[0026] Furthermore, in this disclosure, "contact information" refers to information that can identify a user's access to a webpage. Examples of such contact information include telephone numbers, email addresses, social networking service (SNS) accounts, management numbers used when responding to user inquiries in a chat format, links for online meetings, arbitrary identification information generated for tracking purposes, user ID information, terminal identification numbers of user terminal devices, telephone numbers of user terminal devices, or combinations thereof. Among these, telephone numbers, email addresses, SNS accounts, management numbers used when responding to user inquiries in a chat format, links for online meetings, arbitrary identification information generated for tracking purposes, or combinations thereof are preferred from the viewpoint of effectively processing attribute information such as the user's website access history. Typically, telephone numbers used for such tracking are assigned to a specific user's access when a user requests access to a webpage, and are set to be displayed in a predetermined location on the webpage. When the user's input to the telephone number is detected, a call application program different from the application program that displays the webpage is launched, and contact (e.g., making a call) is initiated.

[0027] Furthermore, in this disclosure, "attribute information" refers to information that indicates attributes related to a user. Examples of such attribute information include the user's age, gender, address, occupation, marital status, annual income, whether or not they have children, interests, life events, purchase history, accounts in browser applications, accounts in communication tools such as social networking services (SNS), telephone number of the user's terminal device, email address, terminal identification number, timing of device changes, IP address, display resolution, web page search history, browsing history, landing page access history, online game history via the internet, or behavioral information. Attribute information is not limited to text data; it may also be features based on the user's facial image and voice information. In addition, attribute information may include not only the specific information exemplified above, but also classification information that categorizes the user based on the specific information exemplified above (for example, if the user's age is "20 years old," the classification information that categorizes the user would be "20 to 24 years old").

[0028] Furthermore, in this disclosure, “behavioral information” refers to information indicating actions taken by a user in relation to a webpage containing contact information. Such behavioral information includes the time until a predetermined action is taken, the status of access to other webpages related to the webpage, other inputs made after an input to contact information has been made, or a combination thereof. Specifically, behavioral information includes the time until the user leaves the webpage (for example, “leaving” is detected by launching another application program in the foreground that is different from the browser application program that displays the webpage, accessing a webpage in a domain different from the domain of the webpage, terminating the application program that outputs the webpage, or inputting an “back” button), the time from leaving the webpage until returning to the webpage or another webpage in the same domain as the webpage (for example, “returning” is detected by launching the browser application that displays the webpage in the foreground, or accessing the webpage or another webpage in the same domain as the webpage), the history of accessing other webpages in the same domain as the webpage, or inputs indicating that the user consents to the provision of attribute information. The time until leaving the webpage can be any time related to the departure, such as the actual time until the user leaves the page, or the time until the user inputs an action to leave.

[0029] Furthermore, even if the disclosure includes terms such as "First" or "Second," it does not mean that it is limited to only those two elements. Naturally, it may also include "Third," "Fourth," and more elements.

[0030] 2. Configuration of Processing System 1 Figure 2 is a conceptual diagram schematically showing the configuration of the processing system 1 according to the embodiment of this disclosure. As shown in Figure 2, the processing system 1 includes a user terminal device 100-2 that can be used by the user, a distribution device 200 that distributes information related to web pages, and a management device 300 that manages attribute information, which will be described later.

[0031] Normally, a distribution device is provided for each domain name and hostname in the URL that identifies the destination of a web page. However, in Figure 2, for the sake of explanation, multiple distribution devices are grouped together and referred to as distribution device 200. In other words, distribution device 200 only needs to include at least one of the different distribution devices provided for each domain name and hostname.

[0032] Furthermore, the processing system 1 may include a provider terminal device 100-1 that can be used by the provider of a service or product. This allows the processing system 1 to receive contacts from the user terminal device 100-2 via the provider terminal device 100-1. In addition, although not specifically shown, it may also include a distributor terminal device that can be used by the distributor.

[0033] The provider terminal device 100-1, user terminal device 100-2, and distributor terminal device are typically wireless communication terminal devices such as smartphones, but are not limited to such devices. For example, any device capable of executing the program related to this disclosure can be suitably applied as a terminal device, such as a feature phone, personal digital assistant, PDA, laptop computer, or desktop computer. Furthermore, in processing system 1, the provider terminal device 100-1, user terminal device 100-2, and distributor do not need to be the same type of terminal device; they may be different types of terminal devices. Also, although Figure 2 shows a single device each for provider terminal device 100-1 and user terminal device 100-2, it is natural that multiple devices may be included depending on the number of users, providers, and distributors.

[0034] Each of the devices described above in processing system 1 is connected to communicate via network 400. Network 400 consists of a public network such as LTE or ISDN, an internet network, or a combination thereof. Therefore, the provider terminal device 100-1, the user terminal device 100-2, the distribution device 200, the management device 300, and the distributor terminal device are connected to each other via a public network or internet connection, and transmit and receive various types of information. Network 400 may be a network different from the internet, or it may be an intranet.

[0035] Furthermore, although the distribution device 200 and the management device 300 are described as single units, it is also possible to distribute each component and processing of the distribution device 200 and the management device 300 to multiple server devices or cloud server devices.

[0036] Furthermore, although a management device 300 is described as an example of a processing device, the processing device may be other than the management device 300. For example, the processing device may be at least one of the provider terminal device 100-1, the user terminal device 100-2, and the distribution device 200, and each of these devices can perform some of the processing that the management device 300 performs.

[0037] 3. Configuration of each device <Management device 300> Figure 3 is a block diagram showing an example configuration of a management device 300 according to an embodiment of this disclosure. The management device 300 does not need to include all of the components shown in Figure 3; it is possible to omit some components or add other components. Furthermore, while the management device 300 is typically configured as a server device, it is not necessary to house everything shown in Figure 3 in a single enclosure; the components and processing of the management device 300 can be distributed to multiple server devices or cloud server devices. In this embodiment, a database 315 for storing various information may be connected via a communication interface 314. In this disclosure, unless otherwise specified, the memory included in the server device may refer to a device including only memory 313, a device including only database 315, or a device including both memory 313 and database 315.

[0038] According to Figure 3, the management device 300 includes a processor 312 consisting of a CPU, RAM, ROM, and memory 313 including non-volatile memory and HDD, and a communication interface 314. These components are electrically connected to each other via control lines and data lines.

[0039] The processor 312 functions as a control unit for controlling other connected components based on various programs stored in the memory 313. Specifically, the processor 312 reads and executes programs from the memory 313 for running the application according to this disclosure and programs for running the OS. The processor 312 performs, in particular, the following: "a process of assigning first contact information, selected from a plurality of contact pieces of information for contacting a provider of services or goods by obtaining a first request for accessing a web page via a user terminal device available to the user, in order to identify the access related to the first request"; "a process of outputting display information of the web page including the assigned first contact information to the user terminal device"; and "a process of selecting whether or not to maintain the assignment of the first contact information to the access related to the first request, based on whether or not the user has left the web page or another web page in the same domain as the web page." The processor 312 is mainly composed of one or more CPUs, but may be combined with a GPU, FPGA, etc. as appropriate.

[0040] Memory 313 includes RAM, ROM, non-volatile memory, and HDD, and functions as a storage unit. ROM stores instruction programs for executing the applications and operating system related to this disclosure. Such programs are loaded and executed by processor 312. RAM is used to write and read data while the programs stored in ROM are being processed by processor 312. Non-volatile memory is memory on which data is written and read by the execution of the program, and data written thereto is retained even after the execution of the program has finished. Memory 313 stores programs that cause processor 312 to execute, in particular, "a process to assign a first contact information selected from multiple contact information for contacting a provider of services or goods by obtaining a first request for access to a web page via a user terminal device available to the user, in order to identify the access related to the first request," "a process to output display information of the web page including the assigned first contact information to the user terminal device," and "a process to select whether or not to maintain the assignment of the first contact information to the access related to the first request based on whether or not the user has left the web page or another web page in the same domain as the web page." Memory 313 also stores various information stored in the tracking management table and user management table together with database 315 as needed.

[0041] The communication interface 314 functions as a communication unit that transmits and receives information between the remotely installed provider terminal device 100-1, user terminal device 100-2, distribution device 200, and other devices via a communication processing circuit and antenna. The communication processing circuit processes the programs and various information used in the processing system 1 to transmit and receive information from the provider terminal device 100-1, user terminal device 100-2, distribution device 200, distributor terminal device, and other devices as processing progresses. The communication processing circuit processes based on a wideband wireless communication method such as the 5G method, but it can also process based on a narrowband wireless communication method such as wireless LAN such as IEEE802.11 or Bluetooth®, or a contactless wireless communication method. In addition, it is possible to use wired communication instead of or in addition to wireless communication.

[0042] Preferably, the communication interface 314 may perform communication with the provider terminal device 100-1 via at least an Internet network, which is a computer network using the Internet Protocol (IP), and communication with the user terminal device 100-2 via at least the above-mentioned Internet network or a public telephone network using a so-called telephone number.

[0043] <Distribution device 200> Although the configuration of the distribution device 200 is not specifically shown in the diagram, it consists of a processor, memory, and communication interface, similar to the management device 300 shown in Figure 3. Such a distribution device 200 is typically configured as a server device, but it does not need to be housed in a single enclosure; the components and processing of the distribution device 200 can be distributed to multiple server devices or cloud server devices. The distribution device 200 executes the processing shown in Figures 5A and 5B, for example, by having the processor process the program stored in memory.

[0044] <Provider terminal device 100-1, user terminal device 100-2, and broadcaster terminal device> Although not specifically illustrated, the configurations of the provider terminal device 100-1, user terminal device 100-2, and broadcaster terminal device consist of a processor, memory, and communication interface, as well as input interfaces such as a touch panel and mouse, and output interfaces such as a display. The provider terminal device 100-1, user terminal device 100-2, and broadcaster terminal device execute the processes shown in Figures 5A and 5B, for example, by having the processor process programs stored in memory.

[0045] 4. Information stored in the memory 313 of the management device 300 Figure 4A is a conceptual diagram showing a tracking management table stored in the management device 300 according to the embodiment of this disclosure. The information stored in the table is updated as the processing progresses.

[0046] According to Figure 4A, the tracking management table stores contact information, web page information, user ID information, attribute information, behavior information, exit judgment information, selection information, and judgment result information, all associated with the contact ID information. "Contact ID information" is assigned to each tracking process and is information used to identify each tracking process. Contact ID information is generated each time a new session occurs, for example, when a browsing request to access a new web page is sent from the user terminal device 100-2 to the distribution device 200, and a certain period of time (for example, until 30 minutes have passed since the last access, or until the browser application is closed) is defined as one unit. For example, when a new session is started, processes such as the management device 300 acquiring attribute information such as the access history of the user terminal device 100-2, the administrator using said attribute information, or the administrator providing said attribute information to a third party (for example, the distribution device 200) are performed to obtain the user's consent, and such information is also managed in association with the contact ID information.

[0047] "Contact information" is information used to identify a user's access to a webpage. Examples of such contact information include telephone numbers, email addresses, social media accounts, management numbers used when responding to user inquiries in a chat format, links for online meetings, arbitrary identification information generated for tracking purposes, user ID information, terminal identification numbers of user terminal devices, telephone numbers of user terminal devices, or combinations thereof. Among these, telephone numbers, email addresses, social media accounts, management numbers used when responding to user inquiries in a chat format, links for online meetings, arbitrary identification information generated for tracking purposes, or combinations thereof are preferred from the perspective of effectively processing attribute information such as the user's website access history. For example, when a user terminal device 100-2 sends a request to view a specific webpage and a session to view that webpage begins, different information is assigned to each session, and this assignment is released depending on whether or not the user has left the webpage. Then, for example, this contact information is displayed as contact information in a predetermined location on the webpage.

[0048] The arbitrary identification information used as contact information in the above context is, for example, information generated based on attribute information obtained from tag information provided to the user terminal device 100-2 along with the web page. By managing this identification information, it is possible to identify whether the user is accessing the web page for the first time or is accessing it again.

[0049] "Web page information" is information used to identify the web page to be tracked. In other words, web page information identifies the web page accessed by the user terminal device 100-2 during the session in which the contact ID information was generated. Typically, web page information stores information such as the URL.

[0050] "User ID information" is information used to identify a user. Examples of such user ID information include social networking service (SNS) accounts, email addresses, arbitrary strings specified by the user or service provider, names, or combinations thereof.

[0051] "Attribute information" refers to information that indicates attributes about a user. Examples of such attribute information include classification information generated based on the user's personal information (e.g., age range 20-24), and the user's browsing history on web pages. Browse history includes the user's web page search history, access history including the user's actions leading up to accessing a specific web page and their actions within the accessed domain, information stored in shopping carts on e-commerce sites, input information entered on web pages, user account information used on web pages, or combinations thereof. Such browse history can be collected as first-party data, such as cookies issued from the domain of a site the user accessed, or as third-party data, such as cookies issued from domains other than the site the user accessed.

[0052] "Behavioral information" refers to information that indicates actions taken by a user in relation to a webpage containing contact information. Examples of such behavioral information include the time elapsed until a specific action is performed, the status of access to other webpages related to the webpage in question, other inputs made after inputting information about contacts, or a combination of these. Specifically, behavioral information includes the time elapsed until the user leaves the webpage, the time elapsed from leaving the webpage until returning to the webpage or another webpage in the same domain (for example, "return" is detected by launching the browser application that displays the webpage in the foreground, or by accessing the webpage or another webpage in the same domain), the history of access to other webpages in the same domain as the webpage in question, or inputs indicating the user's consent to provide attribute information.

[0053] "Exit detection information" is information indicating the result of determining whether or not a user has left a webpage or another webpage within the same domain as that webpage. In other words, exit detection information includes, for example, information indicating that a user has left a webpage or another webpage within the same domain as that webpage, and the time of the departure. Such exit detection is determined based on, for example, the reception of access information from a web beacon contained in the webpage or another webpage within the same domain, the launch of a different application program in the foreground than the browser application program that displays the webpage, access to a webpage in a different domain than the domain of the webpage, termination of the application program that outputs the webpage, or input of an operation to the "back" button. Exit detection information is mainly used to decide whether or not to retain the contact information assigned to the access to the webpage.

[0054] "Selection information" is information that indicates the result of choosing whether or not to retain the contact information assigned to access the webpage in question. Such selections are made, for example, based on the determination of whether or not the user left the webpage in question or another webpage on the same domain as the webpage in question. More specifically, the selection is made to retain the information if a predetermined amount of time has not elapsed since it was determined that the user left the webpage in question or another webpage on the same domain as the webpage in question, and to release the assignment if the time has elapsed.

[0055] "Judgment result information" is information that shows the result of a judgment based on user behavior information. Examples of such judgment information include information that shows the estimated result of the quality of the user's input regarding contact information. Specifically, judgment information may include the result of estimating the degree of interest in the service or product introduced on the web page, the result of estimating the degree of intent to actually purchase the service or product, the result of determining whether the input regarding contact information is fraudulent, or a combination of these.

[0056] Figure 4B is a conceptual diagram showing a user management table stored in the management device 300 according to the embodiment of this disclosure. The information stored in this table is updated as processing progresses.

[0057] According to Figure 4B, the user management table stores personal information and attribute information associated with user ID information. In this disclosure, attribute information refers to information indicating attributes of the user, but such attribute information may include not only the information exemplified below and other attribute information, but also the behavioral information and judgment result information shown in Figure 4A.

[0058] As explained in Figure 4A, "User ID information" is information used to identify a user. Examples of such User ID information include SNS accounts, email addresses, arbitrary strings specified by the user or service provider, names, or combinations thereof.

[0059] "Personal information" includes the user's age, gender, address, occupation, marital status, annual income, whether they have children, interests, life events, purchase history, accounts in browser applications, accounts in communication tools such as social networking services (SNS), telephone number of user terminal device 100-2, email address, terminal identification number, timing of model changes, IP address, display resolution, or a combination thereof. This personal information may be updated and stored each time it is obtained in the course of processing by processing system 1, or it may be entered and stored in advance when the user is newly registered for a service provided by processing system 1.

[0060] "Attribute information" refers to information that indicates user attributes other than those exemplified above, and its details are explained in Figure 4A.

[0061] 5. Processing sequence executed by processing system 1 Figures 5A to 5C show processing sequences executed in the processing system 1 according to the embodiment of this disclosure. Specifically, Figure 5A shows a processing sequence mainly executed between the user terminal device 100-2, the distribution device 200, and the management device 300. Of these, S11 to S12 show setting processes for executing tracking processes on the web page, and S21 to S32 show tracking processes for providing attribute information to the provider terminal device and the distributor terminal device through tracking. Also, S26 to S52 in Figure 5B show a processing sequence related to the determination of abandonment. Furthermore, S61 to S71 in Figure 5B and Figure 5C show a processing sequence when the web page is accessed again.

[0062] <Configuration process for executing tracking> According to Figure 5A, the processor 312 of the management device 300 configures the web page to perform the tracking process (S11). Specifically, the processor 312 of the management device 300 collects attribute information such as operation history and configures tags (e.g., measurement tags) to acquire contact information when a session is started by accessing the website. These configurations are written in programming languages ​​such as JavaScript® or HTML. Once these configurations are made, the processor 312 of the management device 300 sends a registration request (T11) for these configurations to the web page stored in the distribution device 200 via the communication interface 314. This registration request includes information that identifies the website where the tags are configured.

[0063] When the processor of the distribution device 200 receives a registration request via the communication interface, it registers settings such as tags for the web page based on information that identifies the web page (S12). With this, the setting process for executing tracking processing is completed.

[0064] <Tracking process for providing attribute information> According to Figure 5A, the processor of the user terminal device 100-2 receives user input via the input interface and launches a browser application. The processor of the user terminal device 100-2 then receives user input via the input interface and sends an access request to a website that provides a search engine for searching web pages. This starts a new session and the collection of attribute information and other data. When the processor of the distribution device 200 receives this access request via the communication interface, it sends information about the website that provides the search engine to the user terminal device 100-2.

[0065] The processor of the user terminal device 100-2 receives website information via the communication interface and outputs the website received by the browser application via the output interface. Subsequently, the processor of the user terminal device 100-2 accepts user input via the input interface and inputs search terms into the search engine. Once the search terms are entered, the processor of the user terminal device 100-2 transmits the entered search terms to the distribution device 200 via the communication interface. The processor of the distribution device 200 generates a second web page (search web page) containing the search results based on the received search terms and transmits it to the user terminal device 100-2 via the communication interface.

[0066] Typically, such a second webpage (search webpage) includes, in addition to search results, advertisements that the distribution device 200 has decided to display. In other words, the processor of the distribution device 200 assigns advertisements to be displayed in the search results output to the browser application based on user ID information, search words, attribute information, etc.

[0067] The processor of the user terminal device 100-2 outputs search results and advertisements via an output interface using a browser application, based on the information from the received second web page. The processor of the user terminal device 100-2 also stores the search history, including the search words and search results entered by the user, as attribute information in memory.

[0068] The processor of the user terminal device 100-2 receives user input via an input interface and selects an advertisement or webpage (e.g., an advertisement) desired by the user from the display screen of the second webpage (S21). When a predetermined advertisement webpage is selected in the browser application, the processor of the user terminal device 100-2 sends a first request (T21) for viewing the selected webpage to the distribution device 200 via the communication interface. This first request includes a request for the provision of webpage information for displaying the webpage and terminal type information that identifies the type of user terminal device 100-2. One example of terminal type information is information that identifies whether the user terminal device is a terminal capable of communication over a public telephone network, that is, whether it is capable of using an application program for making calls using a telephone number. Furthermore, if the processor of the user terminal device 100-2 has identification information such as attribute management information and contact ID information assigned by the measurement tag stored in the local memory area prepared for the browser application program, it will also transmit this identification information along with the first request (Figure 5A will explain the case where no identification information is stored for the sake of clarity).

[0069] When the processor of the distribution device 200 receives the first request, it generates a contact information request to request contact information for the first request according to the settings in S11 to S12 (S22). The processor of the distribution device 200 transmits the generated contact information request (T22) along with terminal type information to the management device 300 via the communication interface. When the processor 312 of the management device 300 receives the contact information request via the communication interface 314, it assigns the first contact information for the first request (S23).

[0070] Here, Figure 6A is a diagram showing the processing flow of the process executed in the management device 300 according to the embodiment of this disclosure. Specifically, Figure 6A is a diagram showing the processing flow related to the contact information generation process executed by the processor 312 of the management device 300 in S23 of Figure 5A. This processing flow is mainly performed by the processor 312 of the management device 300 reading and executing a program stored in the memory 313. Note that if the processor of the distribution device 200 receives identification information such as attribute management information and contact ID information assigned by the measurement tag along with the first request, it also transmits the identification information along with the contact information request (in Figure 5A, for the sake of explanation, the case where identification information has not been received is described).

[0071] Here, as shown in Figure 6A, the processor 312 receives a contact information request from the distribution device 200 via the communication interface 314, along with terminal type information, to generate first contact information for the first request (S111). If the processor 312 receives identification information such as contact ID information at this time, it determines whether the contact information associated with the contact ID information is maintained, and proceeds to the following process only if it is not maintained.

[0072] When the processor 312 receives a contact information request for the first request, it generates first contact ID information unique to the series of sessions browsing the web page and stores it in the tracking management table of memory 313 (S112).

[0073] Here, the terminal type information received in S111 is information indicating the type of user terminal device, or information indicating whether or not the user terminal device is a terminal capable of communication over a public telephone network. In other words, terminal type information is typically used to determine whether or not an application program for making calls using a telephone number is available. Based on the terminal type information, the processor 312 determines whether or not the user terminal device 100-2 is a terminal device capable of communication over a public telephone network (S113). If the determination shows that communication over a public telephone network is possible, i.e., an application program for making calls is available, then a first contact information is generated from among multiple contact information, using one telephone number assigned to the session (S114).

[0074] For example, the management device 300's memory 313 may have several different telephone numbers pre-configured for tracking (e.g., 03-XXXX-XXX1, 03-XXXX-XXX2, 03-XXXX-XXX3, 03-XXXX-XXX4, etc.). When the processor 312 receives the contact information request, it selects one telephone number (e.g., 03-XXX-XXX1) from among the multiple telephone numbers. The processor 312 uses the selected telephone number (e.g., 03-XXX-XXX1) as contact information specific to that session. That is, for example, if a call (contact) is made from the selected telephone number (e.g., 03-XXX-XXX1) from the user terminal device 100-2, it can be identified as the telephone number assigned to that session, and it becomes possible to refer to the behavioral information etc. associated with that telephone number (contact information) in Figure 4A.

[0075] On the other hand, if the determination indicates that communication via the public telephone network is not possible, that is, that the application program for making calls cannot be used, then, for example, a first contact information is generated using arbitrary identification information generated for tracking purposes, which is different from the telephone number mentioned above (S115).

[0076] The arbitrary identification information generated for tracking, for example, is an identification information consisting of an arbitrary string generated by the processor 312 when the session is newly started. In this case, when the user terminal device 100-2 contacts the provider to obtain additional information or apply for a service or product, it will do so using an internet network using the Internet Protocol (IP). Such contact may be made by email, voice or text chat using SNS, online meeting, or a combination thereof. Therefore, by sending the arbitrary identification information generated at the start of these contacts to the management device 300, the user terminal device 100-2 can refer to the behavioral information etc. associated with the identification information (contact information) in Figure 4A.

[0077] Furthermore, if communication via the public network is not possible, it is possible to use other identification information in place of arbitrary identification information. For example, it is possible to generate new information specific to the online meeting link and use it as contact information. By accessing this link, the online meeting will start, making it possible to refer to the behavioral information associated with that link (contact information).

[0078] Furthermore, instead of arbitrary identification information, email addresses and social media accounts generated as session-specific information can also be used. By contacting the email address or social media account assigned as contact information, it becomes possible to access associated behavioral information and other data.

[0079] As described above, once contact information is generated by the processing in S114 or S115, the generated contact information is stored in the tracking management table in association with the contact ID information, and is transmitted to the distribution device 200 via the communication interface 314 (S116). This completes the processing flow.

[0080] Returning to Figure 5A, once the first contact information is assigned for the access requested by the first request, the processor 312 of the management device 300 transmits the first contact ID information generated in S112 of Figure 6A and the first contact information (T23) generated in S114 or S115 to the distribution device 200 via the communication interface.

[0081] The processor of the distribution device 200 generates webpage information (S24) that includes the first contact information received for the webpage (e.g., advertisement A) requested in the first request (T21). This webpage information includes the various contents that make up the webpage of advertisement A, which is the first webpage, as well as the first contact information received in T23 and the URL to be accessed. The processor of the distribution device 200 transmits the webpage information (T24) and the first contact ID information to the user terminal device 100-2 via the communication interface as a viewing response to the first request.

[0082] The processor of the user terminal device 100-2 outputs the web page generated by the browser application to the display based on the web page information contained in the received browsing response (S25).

[0083] Here, Figures 9A and 9B show examples of web pages displayed on the user terminal device 100-2 in the embodiment of this disclosure. Specifically, Figures 9A and 9B show examples of web page 10 displayed on the user terminal device 100-2 at S25 in Figure 5A. According to Figure 9A, web page 10 contains information related to advertisement A as content, and an icon 11 labeled "Start Contact" is displayed at the bottom as first contact information.

[0084] Note that Figure 9A assumes that the user terminal device 100-2 is capable of communication via a public telephone network. Therefore, the icon 11 displayed as the first contact information shows a telephone number. However, the display method of the first contact information differs depending on the terminal type information of the user terminal device. For example, if a telephone number assigned to a session accessing the web page is used as the first contact information, an icon directly displaying that telephone number may be displayed as the first contact information (see, for example, Figure 9). Also, as shown in Figure 9B, if arbitrary identification information generated for tracking is used as the first contact information, instead of directly displaying the identification number, an icon 12 for launching a contact application program may be displayed as the first contact information, as in web page 10 (in this case, contact is made, for example, by email, voice or text chat using SNS, online meeting, or a combination thereof). Furthermore, if a link for an online meeting assigned to a session accessing the web page is used as the first contact information, an icon for accessing that link may be displayed as the first contact information.

[0085] Returning to Figure 5A, when the processor of the user terminal device 100-2 receives user input for the first contact information via the input interface (S26), it outputs a consent screen via the output interface. Then, when the user terminal device 100-2 receives user input for the consent button included in the consent screen via the input interface (S27), it extracts attribute information such as the operation history contained in the user terminal device 100-2 (S28). The operation input on the consent screen will be explained in detail in Figures 5B and 9C.

[0086] Here, the attribute information typically includes search history, which includes search terms and search results entered by the user. However, it can also include access history, which includes the user's actions leading up to accessing a specific webpage and their actions within the domain they accessed, information stored in the shopping cart on e-commerce sites, input information entered on a webpage, user account information used on a webpage, or a combination of these. In other words, although not specifically illustrated, if a user accesses another webpage within the domain that includes a website, that access history is stored as attribute information. Also, if a user clicks on a specific icon or watches a video on an accessed webpage, the access history indicating these actions is stored as attribute information. Furthermore, if a user adds a service or product to their cart or favorites on an accessed webpage, information such as the service name or product name is stored as attribute information. Additionally, personal information entered by the user on an accessed webpage is stored as attribute information. Finally, user account information used on an accessed webpage (for example, user ID information used as an account provided on the webpage, or user ID information used as an account with a browser application provider) is stored as attribute information. Therefore, the processor of the user terminal device 100-2 extracts various types of information as attribute information, as exemplified above.

[0087] Furthermore, attribute information includes, as described above, first-party data collected by measurement tags issued by the domain of the site accessed by the user and identifiers assigned by said measurement tags (e.g., cookies), and third-party data collected by measurement tags issued by third parties (i.e., domains other than the site accessed by the user) and identifiers assigned by said measurement tags (e.g., cookies). However, particularly regarding measurement tags issued by third parties used to collect third-party data and identifiers assigned by said measurement tags, from a security and personal information perspective, storage in the browser or local memory of the user terminal device 100-2 may be restricted, thereby regulating the collection of third-party data.

[0088] For example, in the case of the source code of a web page as shown in Figures 9A and 9B, the HTML source code contains " <script>···ファーストパーティ計測タグ···< / script> As indicated, the measurement tags and attribute management information (e.g., identifiers) are written in JavaScript or VBScript. Therefore, when the HTML file shown in (a) is loaded, JavaScript etc. is executed within the HTML file, and attribute information is collected by linking it to the attribute management information via the measurement tags. In this way, measurement tags etc. written directly in the HTML source code are identified as being issued by a first party, and the collected attribute information is also treated as first-party data.

[0089] On the other hand, within the HTML source code: <script src=""https: / / サードパーティ計測タグ.js”">< / script>As described above, the tracking tags are written as link information to JavaScript. Therefore, when the HTML file is loaded, the JavaScript at the specified link destination, which is a domain other than the web page's domain, is accessed, and attribute information is collected by linking it to attribute management information via the tracking tag at the linked destination. In this way, tracking tags written at the link destination that specifies an external domain are identified as being issued by a third party, and the attribute information collected by them is also treated as third-party data. For this reason, as stated above, access to the link destination where such tracking tags and identifiers issued by third parties are written may be restricted, and the collection of attribute information may be regulated.

[0090] Therefore, in Figure 5A, the web page generated by S24 will not execute any measurement tags issued by third parties by accessing links on external domains, but will instead have them directly written into the HTML source code and executed within that HTML file. Specifically, within the HTML source code, <script>···サードパーティ計測タグ···< / script> This means that even if the measurement tag is issued by a third party, it will still be possible to collect attribute information using the measurement tag, even if access to links on external domains is restricted.

[0091] The processor of the user terminal device 100-2 reads the web page information represented by HTML as described above in a browser application, which executes the measurement tag and issues attribute management information (e.g., an identifier), and a series of attribute information is collected in association with said attribute management information. The processor of the user terminal device 100-2 then transmits the extracted attribute information (T25: including attribute management information (e.g., an identifier)) along with the contact ID information to the management device 300 via the communication interface (S28). When the management device 300 receives the attribute information, it associates it with the contact ID information received together and stores the received attribute information in the tracking management table (S29).

[0092] When the user terminal device 100-2 receives an operation input for the first contact information in S26, it starts the application program associated with the first contact information and initiates contact (T26) with the management device 300. This contact ultimately transfers the information to a provider terminal device available to the service or product provider, where processing such as providing detailed information to the user or processing applications is carried out.

[0093] For example, in webpage 10 shown in Figure 9A, if a telephone number assigned to the session is included as the first contact information, and an icon for launching a calling application program is displayed as contact information along with the telephone number, the calling application program is launched to initiate contact (making a call) using the public telephone network. Also, in webpage 10 shown in Figure 9B, if arbitrary identification information assigned to the session is set as the first contact information, and an icon 12 labeled "Send Email" is displayed as the first contact information, an application program such as email is launched to initiate contact using the internet network (the arbitrary identification information is also sent along with the contact). Another example is if, on a webpage, a link for an online meeting assigned to the session is set as the first contact information, and an icon labeled "Start Contact" is displayed as the first contact information, then an application program for online meetings is launched to initiate contact (online meeting) using the internet network. Furthermore, if a webpage has a single SNS account assigned to a session set as the primary contact information, and an icon labeled "Start Contact" is displayed as the primary contact information, the application program for voice or text chat using SNS will be launched to initiate contact (voice or text chat) over the internet network.

[0094] As described above, once a contact is initiated, the contact is received by the management device 300. When the processor 312 of the management device 300 receives the contact via the communication interface 314, it refers to the tracking management table based on the first contact information and identifies the contact ID information (S30). At this time, if a telephone number is used as the first contact information, the management device 300 identifies which contact ID information it is by matching the incoming telephone number with the first contact information in the tracking management table. Similarly, if arbitrary identification information is used as the first contact information, the management device 300 identifies which contact ID information it is by matching the arbitrary identification information received along with the contact with the first contact information in the tracking management table. Furthermore, if an online meeting link, SNS account, or email address is used as the first contact information, the management device 300 identifies which contact ID information it is by matching the online meeting link, SNS account, or email address received with the contact information in the tracking management table.

[0095] Once contact ID information is identified, the processor 312 of the management device 300 extracts attribute information associated with the contact ID information from the tracking management table (S31). At this time, the attribute information includes the user account information used on the accessed web page (for example, user ID information used as an account provided on the web page, or user ID information used as an account for a provider that provides a browser application). Therefore, the processor 312 of the management device 300 refers to the user management table to identify user ID information that matches the above account information, and stores the identified user ID information in the tracking management table. The processor 312 of the management device 300 also extracts personal information and other attribute information associated with the identified user ID information in the user management table, and prepares attribute information that can be provided to the provider terminal device 100-1. Once attribute information including personal information has been extracted, the processor 312 transmits the attribute information to the provider terminal device 100-1 via the communication interface 314.

[0096] Here, Figure 6B is a diagram showing the processing flow of the process performed in the management device 300 according to the embodiment of this disclosure. Specifically, Figure 6B is a diagram showing the processing flow related to the storage of behavioral information extracted by the processor 312 of the management device 300 in S29 of Figure 5A. This processing flow is mainly performed by the processor 312 of the management device 300 reading and executing a program stored in the memory 313.

[0097] As explained in S11 and S28 of Figure 5A, the website is equipped with tags (e.g., measurement tags) for collecting attribute information such as access history. Therefore, when the user terminal device 100-2 first accesses the website due to the setting of these tags, the attribute information stored in memory up to that point is extracted. This attribute information includes, as described above, search history including search words and search results entered by the user, access history including the user's actions leading up to accessing a specific web page and the user's actions within the domain accessed by the user, information held in the shopping cart on e-commerce sites, input information entered on the web page, user account information used on the web page, or a combination of these. Once this attribute information is extracted, the processor of the user terminal device 100-2 transmits the attribute information to the management device 300 via the communication interface due to the setting of the tags.

[0098] According to Figure 6B, the processor 312 of the management device 300 receives the attribute information and attribute management information (e.g., identifier) ​​from the user terminal device 100-2 via the communication interface 314 (S211). Upon receiving this information, the processor 312 refers to the attribute information in the tracking management table to determine whether or not the attribute management information (e.g., identifier) ​​is stored (S212). This attribute management information is unique identification information for a browser application that outputs a website with tags set, and is used to centrally manage attribute information when accessing the website from the same browser application program. This attribute management information may include, for example, an identifier temporarily stored in the local memory area of ​​the browser application program, or an identifier such as the local IP address of the user terminal device 100-2.

[0099] As described above, when the user terminal device 100-2 is accessing the website for the first time, the attribute information in the tracking management table shown in Figure 4A does not contain any attribute management information. Therefore, in S212, the result is "No", and the user terminal device 100-2 newly stores the attribute management information (e.g., identifier) ​​issued by the measurement tag in the attribute information of the tracking management table (S213). Then, the processor 312 of the management device 300 transmits the generated attribute management information to the user terminal device 100-2 via the communication interface 314 (S214).

[0100] Although not specifically illustrated, the processor of the user terminal device 100-2 that receives the attribute management information stores the received attribute management information in the memory for its browser application.

[0101] Next, the processor 312 of the management device 300 identifies user ID information based on attribute information and associates the attribute information and attribute management information (e.g., identifiers) with the user ID information (attribute management information is not shown in Figure 4B). Specifically, as described above, the attribute information includes user account information used on the accessed web page (e.g., user ID information used as an account provided on the web page, or user ID information used as an account of a provider that provides a browser application). Therefore, the processor 312 refers to the user management table and identifies user ID information that has information matching the account information included in the attribute information (S215). Then, once the user ID information is identified, the processor 312 associates the attribute information and attribute management information with that user ID information. In addition to user account information, information such as access history, IP address, access time, or the type of browser application or OS used by the user can also be used to identify user ID information.

[0102] On the other hand, when the user terminal device 100-2 accesses the website for the second time or later, the attribute information stored in memory up to that point is extracted in the same manner as described above. However, as described above, the user terminal device 100-2's memory stores the attribute management information received in S214. Therefore, when the user terminal device 100-2 accesses the website for the second time or later, the processor of the user terminal device 100-2 transmits the attribute information along with the attribute management information to the management device 300.

[0103] When the processor 312 of the management device 300 receives attribute management information along with attribute information in S211, it proceeds to the "Yes" branch in S212 because the attribute management information is already stored, and proceeds to the process in S215. Specifically, the processor 312 refers to the user management table based on the attribute management information received along with the attribute information and identifies the user ID information associated with the attribute management information (S215). Then, the processor 312 stores the attribute information in the user management table in association with the identified user ID information (S216). With this, the processing flow is completed.

[0104] In other words, according to the history management process shown in Figure 6B, it is possible to accumulate not only attribute information from the first access to a web page, but also attribute information from subsequent accesses to the same web page. Therefore, for example, it is possible to check changes such as whether the user's behavior on the web page changed on the second access as a result of contact between the user and the provider during the first access.

[0105] Returning to Figure 5A, when the processor 312 of the management device 300 receives a contact from the user terminal device 100-2 as described above, it forwards the contact via the communication interface 314 to the provider terminal device 100-1, which is available to the provider that provides the web page related to the session (S32). Once forwarded to the provider terminal device 100-1, contact is initiated between the provider terminal device 100-1 and the user terminal device 100-2 (S33). Specifically, if a contact by telephone is received, the processor 312 of the management device 300 forwards the telephone call as is, and telephone contact is initiated between the provider terminal device 100-1 and the user terminal device 100-2. If a contact by online meeting is received, the processor 312 of the management device 300 sends an online meeting participation notification to the provider terminal device 100-1, and online meeting contact is initiated between the provider terminal device 100-1 and the user terminal device 100-2. When a voice or text contact is received using an SNS account, the processor 312 of the management device 300 forwards the voice or text chat, initiating a voice or text chat contact between the provider terminal device 100-1 and the user terminal device 100-2. When an email contact is received, the processor 312 of the management device 300 forwards the email, initiating an email contact between the provider terminal device 100-1 and the user terminal device 100-2.

[0106] At this time, the provider terminal device 100-1 receives the attribute information extracted in S31 from the management device 300. Therefore, providers using the provider terminal device 100-1 can contact users while referring to the received attribute information, enabling them to conduct business negotiations and other activities more efficiently.

[0107] This concludes the tracking process for providing attribute information.

[0108] <Determination process for withdrawal and selection process for assigning first contact information> As shown in Figure 5A, when an operation input is made to the first contact information, a contact with the provider terminal device 100-1 is initiated. However, this contact may result in the user leaving the webpage or other website. Therefore, in order to decide whether or not to retain the first contact information, the departure determination process shown in Figure 5B is executed to determine whether or not the user has left the webpage or other website. Note that there are differences in quality between such contacts and operation inputs, and the departure determination process in Figure 5B is also used to estimate the quality of the contact or operation input.

[0109] As shown in Figure 5B, as explained in Figure 5A, when the processor of the user terminal device 100-2 receives an operation input from the user to the first contact information via the input interface (S26), a timer provided in the user terminal device 100-2 measures the time the operation input was received and stores this time as the time the operation input to the first contact information was received (S51). Next, the processor of the user terminal device 100-2 outputs a consent screen via the output interface. The user terminal device 100-2 then receives user operation input, such as the consent button included in the consent screen, via the input interface (S27).

[0110] Here, Figure 9C shows an example of a web page displayed on the user terminal device 100-2 in an implementation of this disclosure. Specifically, Figure 9C shows an example of a consent screen 20 displayed on the user terminal device 100-2 at S27 in Figure 5A. According to Figure 9C, the consent screen 20 includes an explanatory text display area 23 requesting consent to provide the user's attribute information to a so-called first party or third party, such as a distributor terminal device or provider terminal device 100-1, a consent button 21 to start a call after consenting, and a disagreement button 22 to start a call without consenting. That is, when the processor of the user terminal device 100-2 receives user input to the consent button 21 at the input interface, it notifies the management device 300 of this. The management device 300 extracts the user's attribute information at timings such as S31 in Figure 5A and transmits the attribute information to the provider terminal device 100-1. On the other hand, when the processor of the user terminal device 100-2 receives user input to the disagree button 22 via the input interface, it notifies the management device 300 of this fact. However, in this case, the management device 300 does not extract the user's attribute information at timings such as S31 in Figure 5A and transmit the attribute information to the provider terminal device 100-1.

[0111] Note that inputting an action to the agree button 21 or the disagree button 22 is an example of other inputs made in relation to the first contact information (for example, icon 11 in Figure 9A or icon 12 in Figure 9B) before or after inputting an action to the first contact information. Such other inputs include: • An operation input indicating permission to initiate contact, resulting from an operation input related to the first contact information. • When contacting the contact person identified in the first contact information, the user must perform an input related to prior user authentication. • Inputting operations to display the first contact information in a visible format for the user. • Inputting information to answer questionnaires related to the services and products featured on the webpage where the first contact information is displayed. • Input to consent to or refuse to save attribute information in cookies on the webpage where the first contact information is displayed. • Inputting operations related to the display of upsell offer screens and other screens related to the services and products introduced on the webpage where the first contact information is displayed. This includes, among others.

[0112] Here, Figure 9D shows an example of a web page displayed on the user terminal device 100-2 in an embodiment of this disclosure. Specifically, Figure 9D shows an example of "other operation inputs" displayed on the user terminal device 100-2 at S27 in Figure 5A. According to Figure 9D, a mask image 14 is displayed on the web page 10 so as to cover the icon 11. Therefore, when the processor of the user terminal device 100-2 detects a user operation input to the mask image 14 via the input interface, it displays the icon 11 in a visible manner. In other words, the user operation input to the mask image 14 falls under "an operation input for displaying contact information to the user in a visible manner" among the "other operation inputs".

[0113] Returning to Figure 5B, when the processor of the user terminal device 100-2 receives "other operational inputs made in relation to contact information before or after operational inputs to contact information" as illustrated in Figure 9C or Figure 9D via the input interface, it launches a contact application program (for example, an application program for making calls) in the foreground instead of the browser application program that displays the web page 10 or consent screen 20. It then initiates contact (T26) with the provider terminal device 100-1 via the management device 300.

[0114] When the management device 300 receives a contact from the user terminal device 100-2, it performs a determination process to determine whether or not the user has left web page 10 or another web page in the same domain as web page 10 (S52).

[0115] Here, Figure 6C is a diagram showing the processing flow of the process executed in the management device 300 according to the embodiment of this disclosure. Specifically, Figure 6C is a diagram showing the processing flow related to the departure determination executed by the processor 312 of the management device 300 in S52 of Figure 5B. This processing flow is mainly performed by the processor 312 of the management device 300 reading and executing a program stored in the memory 313.

[0116] According to Figure 6C, the management device 300 determines whether or not the user has left by measuring the time elapsed since receiving access information from the user terminal device 100-2.

[0117] Access information is information transmitted from the user terminal device 100-2 at any time when access is being made to web page 10 or other web pages on the same domain as web page 10. One example of such access information is the use of a web beacon. Specifically, when JavaScriot®, which is written as a web beacon in the HTML used to display the above web page, is executed, the processor of the user terminal device 100-2 transmits access information to the management device 300 via the communication interface, for example, once every 30 seconds. Alternatively, a small image file can be included as a web beacon in the HTML used to display the above web page, and the processor of the user terminal device 100-2 transmits a request to the management device 300 via the communication interface each time the web page is accessed, as access information, to load the image file.

[0118] When the processor 312 of the management device 300 receives any access information via the communication interface 314, it stores the access information and the time when the access information was received, in association with the identification information such as attribute management information and contact ID information that was received along with it.

[0119] Therefore, the processor 312 refers to a table that stores access information and the time the access information was received in association with identification information at predetermined intervals, and calculates the elapsed time since the last time the access information was received for each piece of identification information (S311). The processor 312 then determines whether the elapsed time calculated for each piece of identification information is shorter than a predetermined time T1 (for example, 30 seconds) (S312). If the processor 312 determines that the elapsed time is shorter than time T1, it determines that the user has not yet left the webpage and terminates the processing flow. On the other hand, if the processor 312 determines that the elapsed time is equal to or greater than time T1, it determines that the user has left the webpage 10 or another webpage in the same domain as the webpage 10 (S313).

[0120] When the processor 312 determines that a user has left the system, as described above, it associates this with the contact ID information identified from the identification information and stores the result of the departure and the time at which the departure was determined in the departure determination information. With this, the processing flow is terminated.

[0121] It should be noted that this method for determining departure is merely an example, and other methods may certainly be used. For example, this method of determining departure may be based on whether the management device 300 has received information from the user terminal device 100-2 indicating that an application program other than the browser application program that displays web page 10 has been launched in the foreground, that a web page 10 in a domain different from the domain of web page 10 has been accessed, that the application program that outputs web page 10 has been terminated, or that an operation input to the "back" button has been made on the user terminal device 100-2.

[0122] Figure 6D is a diagram showing the processing flow of the process performed in the management device 300 according to the embodiment of this disclosure. Specifically, Figure 6D is a diagram showing the processing flow related to the selection of whether or not to maintain the assignment of contact information, which is performed in relation to the departure determination performed by the processor 312 of the management device 300 in S52 of Figure 5B. This processing flow is mainly performed by the processor 312 of the management device 300 reading and executing a program stored in the memory 313.

[0123] According to Figure 6D, the processor 312 of the management device 300 executes the processing flow at predetermined intervals. Specifically, the processor 312 refers to the departure determination information in the tracking management table every predetermined time. The processor 312 then reads the departure time information for each contact ID information that stores information indicating that the user left web page 10 or another web page within the same domain as web page 10. The processor 312 calculates the elapsed time since departure based on the read departure time and the current time (S411).

[0124] The processor 312 determines whether each calculated elapsed time is shorter than a predetermined time T2 (for example, 60 minutes) (S412). If the processor 312 determines that the elapsed time is shorter than time T2, it chooses to maintain the assignment of the first contact information for the access related to the first request to web page 10 (T21 in Figure 5A) and terminates the processing flow (if "Yes" is selected in S412 in Figure 6D). On the other hand, if the processor 312 determines that the elapsed time is equal to or greater than time T2, it chooses to release the assignment of the first contact information for the access related to the first request to web page 10 (T21 in Figure 5A) (S413). The processor 312 stores the result of the selection, that is, information indicating that maintenance was selected or information indicating that release was selected, in the selection information of the tracking management table. Furthermore, if the processor 312 selects to release the assignment, it deletes the first contact information from the contact information stored in association with the contact ID information for which the assignment was selected to be released, and also deletes the attribute information stored in association with the said contact ID information. This completes the processing flow.

[0125] Thus, the processor 312 of the management device 300 does not immediately release the contact information assignment after it is determined that the user has left the web page, but only releases it after a certain period of time (time T2) has elapsed. Therefore, if the user accesses the web page 10 again before the certain period of time (time T2) has elapsed, it is possible to use the already assigned first contact information and store new attribute information along with the attribute information collected during the previous access. On the other hand, once the certain period of time (time T2) has elapsed, the assignment of the first contact information is released, making it possible to newly assign the first contact information to other accesses. Although multiple such contact information sets are available, there is a limit to the number, which allows for efficient operation.

[0126] Returning to Figure 5B, for example, the user terminal device 100-2 stops sending the access information shown in Figure 6C when the contact application program is launched in the foreground. Therefore, a determination of whether or not the user has left, and a choice of whether or not to maintain the assignment of the first contact information, can be made using the method described as an example in Figure 6C. With this, the departure determination process is completed.

[0127] <Processing when a second request, which is a second access, is received>

[0128] As shown in S52 of Figure 5B, after it is determined that the user has left the webpage, the contact between the user terminal device 100-2 and the provider terminal device 100-1 ends, which may cause the user terminal device 100-2 to access the webpage 10 again. S61 to S71 of Figure 5B and S81 to S85 of Figure 5C describe the processing that occurs when the webpage 10 is accessed again in this manner. More specifically, S61 to S71 of Figure 5B show the processing when the webpage is accessed again before the assignment of the first contact information is released, and Figure 5C shows the processing when the webpage is accessed again after the assignment of the first contact information has already been released.

[0129] According to Figure 5B, the processor of the user terminal device 100-2 receives user input via an input interface and selects an advertisement or webpage (e.g., an advertisement) desired by the user from the display screen of the second webpage (S61). When a predetermined advertisement webpage is selected in the browser application, the processor of the user terminal device 100-2 sends a second request (T61) for viewing the selected webpage to the distribution device 200 via the communication interface. This second request includes a request for the provision of webpage information for displaying the webpage and terminal type information that identifies the type of user terminal device 100-2. If identification information such as attribute management information or contact ID information assigned by a measurement tag is stored in the local memory area prepared in the browser application program, the processor of the user terminal device 100-2 also sends this identification information along with the second request.

[0130] When the processor of the distribution device 200 receives the second request, it generates a contact information request to request contact information for the second request according to the settings in S11 to S12 of Figure 5A (S62). The processor of the distribution device 200 transmits the generated contact information request (T62) to the management device 300 via the communication interface, along with identification information such as terminal type information and attribute management information. When the processor 312 of the management device 300 receives the contact information request via the communication interface 314, it determines whether the identification information such as attribute management information is stored in the attribute information according to S28 and S29 of Figure 5A. Since the processor 312 of the management device 300 determines that the identification information such as attribute management information is stored in the attribute information, it extracts the first contact information from the tracking management table based on the contact ID information associated with the attribute information (S63). In other words, the processor 312 of the management device 300 can determine whether the second request is a second access by the user or user terminal device 100-2 that requested access in the first request, by checking whether identification information such as attribute management information is stored in the attribute information.

[0131] As described above, the second request is sent before the assignment of the first contact information can be released. Therefore, the tracking management table maintains the assignment of the first contact information, associated with the contact ID information. Consequently, the processor 312 of the management device 300 reuses the first contact information assigned for the access by the first request without assigning new contact information.

[0132] When the first contact information is extracted in response to the access by the second request, the processor 312 of the management device 300 transmits the first contact ID information and the first contact information (T63) associated with the first contact information to the distribution device 200 via the communication interface 314.

[0133] The processor of the distribution device 200 generates webpage information (S64) that includes the received first contact information for the webpage (e.g., advertisement A) requested in the second request (T61). Then, the processor of the distribution device 200 transmits the webpage information (T64) and the first contact ID information to the user terminal device 100-2 via the communication interface as a viewing response to the second request.

[0134] The processor of the user terminal device 100-2 outputs the web page generated by the browser application to the display based on the web page information contained in the received browsing response (S65). As a result, the processor of the user terminal device 100-2 detects the return to the web page 10 (S66), measures the time of return using a timer provided in the user terminal device 100-2, and stores this time as the return time (S67).

[0135] Next, the processor of the user terminal device 100-2 detects a move to a web page having the same domain as web page 10 (S68). The processor of the user terminal device 100-2 then stores the history of the move as an access history (S69). Examples of web pages having the same domain as web page 10 include web pages that describe detailed information about the service or product introduced on web page 10, web pages that show payment methods for purchasing the service or product, web pages that display surveys related to the service or product, web pages that display provider attribute information, or web pages that introduce other services or products related to the service or product.

[0136] Next, the processor of the user terminal device 100-2 transmits behavioral information (T65) to the management device 300 via the communication interface, along with the contact ID information. This information includes the time when an operation input to the contact information stored in memory was received (S26 in Figure 5B), whether or not other operation inputs were received (S27 in Figure 5B), the time when the user left the web page 10 (S52), the time when the user returned to the web page 10 (S57), and the access history within the same domain as the web page 10 (S59).

[0137] When the processor 312 of the management device 300 receives behavioral information via the communication interface 314, it stores it in the tracking management table in association with the contact ID information. Then, the processor 312 uses the stored behavioral information to perform estimation processing to estimate the quality of the operation input or the quality of the contact for the contact information (S71).

[0138] Here, Figure 6E is a diagram showing the processing flow of the process performed in the management device 300 according to the embodiment of this disclosure. Specifically, Figure 6E is a diagram showing the processing flow related to the estimation of contact quality, which is performed by the processor 312 of the management device 300 at S71 in Figure 5B. This processing flow is mainly performed by the processor 312 of the management device 300 reading and executing a program stored in the memory 313.

[0139] According to Figure 6E, the processor 312 reads the behavioral information stored in the tracking management table based on the tracking ID information (S511).

[0140] Here, Figure 8 is a conceptual diagram illustrating an example of behavioral information used in the processing according to the embodiment of this disclosure. Specifically, it is a diagram showing an example of behavioral information transmitted in T65 in Figure 5B. According to Figure 8, one of the behavioral pieces of information is whether or not an operation input has been made to the consent button or the disagree button on the consent screen. Whether or not an operation input has been made on this consent screen is used as an example of other operation inputs made before or after the operation input to the first contact information in relation to said contact information. Such other operation inputs are additionally required in addition to the operation inputs made by the user to contact the first contact information. Therefore, these operation inputs may be an additional burden for the user. However, the fact that the user is making such an additional operation input in order to contact the first contact information indicates a stronger intention to contact the first contact information. Therefore, by using the presence or absence of such other operation inputs as behavioral information, it is possible to estimate the quality of the operation input to the first contact information or the quality of the contact.

[0141] Furthermore, as shown in Figure 8, the departure time is indicated as one of the behavioral information items. This departure time is, for example, the time from when the operation input for the first contact information, measured in S26 of Figure 5B, is received, until the user leaves the web page 10, measured in S52 of Figure 5B. Normally, it takes a considerable amount of time from when a user makes an operation input for the first contact information until the contact is actually initiated by the contact application program, as it requires various operations inputs such as other operations on the consent screen or pressing the contact button, as well as the time the user spends thinking. However, if someone is attempting to make a fraudulent contact using a system or processing device, for example, these processes are carried out automatically, so it is expected that the time required will be short. Therefore, by determining whether the departure time is shorter than a predetermined time as behavioral information, it is possible to estimate the quality of the operation input for the first contact information or the quality of the contact.

[0142] Furthermore, as shown in Figure 8, the return time is indicated as one of the behavioral information items. This return time is, for example, the time from when the user leaves webpage 10, as measured in S52 of Figure 5B, until they return to webpage 10. Normally, when a user leaves webpage 10 to contact provider terminal device 100-1, a considerable amount of time should elapse because contact (for example, a conversation between the provider and the user) takes place between provider terminal device 100-1 and user terminal device 100-2. However, if someone is attempting to make an unauthorized contact using, for example, a system or processing device, it is expected that the attempt will be terminated immediately upon contact with provider terminal device 100-1. In such a case, the user will immediately return to webpage 10. Therefore, by determining whether the return time is shorter than a predetermined time as behavioral information, it is possible to estimate the quality of the operation input or the quality of the contact regarding the contact information.

[0143] Furthermore, as shown in Figure 8, access history within the same domain as webpage 10 is presented as one piece of behavioral information. After contact between the provider terminal device 100-1 and the user terminal device 100-2 is completed, users often access other webpages within the same domain to gather information on related services or products. In other words, such users are expected to have a higher level of interest in the services or products on the webpage containing the first contact information. Therefore, by utilizing the access history within the domain as behavioral information, it is possible to estimate the quality of the user input or the quality of the contact regarding the first contact information.

[0144] Returning to Figure 6E, the processor 312 uses the behavioral information illustrated in Figure 8 to estimate the quality of the operation input or the quality of the contact for the first contact information (S512).

[0145] <Estimation by logic processing> For example, the processor 312 estimates quality by calculating a score based on behavioral information such as the presence or absence of other user inputs, the time spent away from the user, the time spent returning to the user, and the access history within the same domain as the webpage 10. For example, the score is calculated based on the following conditions: • 10 points if other inputs are made, 0 points if none are made. • If the withdrawal time is shorter than the specified time, 0 points are awarded; if it is longer, 5 points are awarded. • If the recovery time is shorter than the specified time, you will receive 0 points; if it is longer, you will receive 20 points. • If there is no access history, you will receive 0 points. If there is an access history to the web page of a related service or product, you will receive 5 points. If there is an access history to the payment page, you will receive 15 points.

[0146] The above method for calculating the score is merely an example, and other methods are certainly acceptable. Furthermore, while four behavioral information points are given as an example, other behavioral information points may be used, as may five or more, or even three or fewer.

[0147] <Estimation using a pre-trained estimation model> As another example, the processor 312 estimates by inputting behavioral information such as the presence or absence of other inputs, exit time, return time, and access history within the same domain as the web page 10 into a trained estimation model and outputting a quality score.

[0148] Figure 7 is a diagram showing the processing flow for the process performed to generate a trained estimation model according to the embodiment of this disclosure. Specifically, Figure 7 is a diagram showing the processing flow for generating a trained estimation model used in the estimation process of S512 in Figure 6C. This processing flow may be executed by the processor 312 of the management device 300, or by the processor of another device such as a model generation device.

[0149] As shown in Figure 7, the processor 312 performs a step of acquiring information about actions taken by a user in relation to any web page in which a service or product is introduced as learning behavior information (S611). Next, the processor 312 estimates the quality of the operation input and the quality of the contact for the contact information of the said web page, for example, by logic processing, and performs a processing step of assigning the estimated quality as the correct label to each learning behavior information acquired in S411 (S612). Note that although the correct label was assigned by logic processing, for example, the results of evaluations by the provider or distributor may also be assigned as the correct label.

[0150] Then, the processor 311 performs the step of associating each assigned correct label information with each learning action information and storing it as learning estimation result information (S613). Once the learning action information and the corresponding correct label information are obtained, the processor 311 performs the step of using these to perform machine learning to estimate the quality of the operation input for contact information and the quality of the contact (S614). This machine learning is performed, for example, by providing these sets of information to a neural network made up of neurons and repeatedly learning while adjusting the parameters of each neuron so that the output from the neural network is the same as the correct label information. Then, the step of obtaining a trained estimation model is performed (S615). The obtained trained estimation model may be stored in the memory 313 of the management device 300 or in another device connected to the management device 100 via a wired or wireless network.

[0151] In addition to the methods mentioned above, pre-trained estimation models can also be generated using other methods such as deep neural networks (DNN), neural networks, convolutional neural networks, multilayer herceptons (MLP), LSTM (Long Short-Term Memory), GRU (Gated Recurrent Unit), GNN (Graph Neural Network), and Transformers; gradient boosting decision trees (GBDT) such as LightGBM (Light Gradient Boosting Machine), XGBoost, and CatBoost; and machine learning methods such as ridge regression, logistic regression, support vector regression (SVR), nearest neighbor, decision trees, regression trees, and random forests. It is also possible to use pre-trained models known as generative AI, which utilize these learning methods.

[0152] Returning again to FIG. 6E, when the processor 312 estimates a score indicating the quality of the contact by means of logic processing or processing by a learned estimation model, the processor 312 determines whether the quality meets a predetermined threshold (S513). As an example, the processor 312 makes the determination as follows and stores the result, as determination result information, in association with the contact ID information in the tracking management table. · If the score < S1, then "Suspicious of fraud" · If S1 ≤ score < S2, then "Low interest" · If S2 ≤ score < S3, then "Average interest" · If S3 ≤ score, then "High interest"

[0153] The processor 312 transmits attribute information including action information and determination result information to the provider terminal device or the distributor terminal device according to the determination result information (S514). As an example, when the determination result information is "Suspicious of fraud", the processor 312 transmits only the determination result information and does not transmit other attribute information. Also, when the determination result information is "Low interest", the processor 312 transmits only the determination result information and some of the attribute information. Also, when the determination result information is "Average interest", the processor 312 transmits only the determination result information and some other attribute information. Also, when the determination result information is "High interest", the processor 312 transmits only the determination result information and all of the attribute information.

[0154] In this way, by changing the attribute information transmitted according to the determination result information, it is possible to avoid providing unnecessary information and enable more efficient operation.

[0155] Returning again to FIG. 5B, as described in FIG. 6E, the processor 312 transmits attribute information including action information to the provider terminal device or the distributor terminal device according to the determination result information via the communication interface 314.

[0156] For example, when the distributor terminal device receives attribute information, including behavioral information and judgment result information, from the management device 300, it performs processing according to that information. For example, if the judgment result information is "suspected fraud" or "low interest," the likelihood of the user purchasing a service or product on the webpage again is low. If contact information, which is limited in number, is kept assigned to such users, the operation of contact information is inefficient. Therefore, if the received judgment result information is "suspected fraud" or "low interest," the processor of the distributor terminal device releases the assignment of the first contact information for access by the first request. Also, for example, if the judgment result information is "suspected fraud," it is suspected that fraud is attempting to artificially inflate advertising fees by falsely increasing the frequency of operation inputs to contact information. Therefore, if the received judgment result information is "suspected fraud," the processor of the distributor terminal device calculates advertising fees without counting such operation inputs. Also, for example, if the judgment result information is "high interest," the user is an important customer who is likely to purchase a service or product on the webpage again. Therefore, if the received judgment result information indicates "high interest," the processor of the broadcaster terminal device adds information indicating that the customer is an important customer to the associated user ID information and proactively sends promotional information to that customer.

[0157] In this way, the management device can efficiently manage the limited number of contact information by estimating the usage status of the first contact information based on user behavior information. The management device can also make the attribute information it provides more appropriate by estimating its quality based on behavior information.

[0158] Next, based on Figure 5C, the processing that occurs when the first contact information is accessed again after the assignment has already been resolved will be explained. According to Figure 5C, the processor of the user terminal device 100-2 receives user input via the input interface and selects the advertisement or web page (e.g., an advertisement) desired by the user from the display screen of the second web page (S81). When a predetermined advertisement web page is selected in the browser application, the processor of the user terminal device 100-2 sends a second request (T81) for viewing the selected web page to the distribution device 200 via the communication interface. This second request includes a request for the provision of web page information for displaying the web page and terminal type information that identifies the type of user terminal device 100-2. If identification information such as attribute management information and contact ID information assigned by the measurement tag is stored in the local memory area prepared in the browser application program, the processor of the user terminal device 100-2 also sends this identification information along with the second request.

[0159] When the processor of the distribution device 200 receives the second request, it generates a contact information request to request contact information for the second request according to the settings in S11 to S12 of Figure 5A (S82). The processor of the distribution device 200 transmits the generated contact information request (T82) to the management device 300 via the communication interface, along with identification information such as terminal type information and attribute management information. When the processor 312 of the management device 300 receives the contact information request etc. via the communication interface 314, it determines whether the identification information such as attribute management information is stored in the attribute information according to S28 and S29 of Figure 5A. Here, as described above, the second request in Figure 5C is transmitted after the release of the assignment of the first contact information has been selected and the attribute information etc. has been deleted. Therefore, in the tracking management table, no identification information such as attribute management information is stored in any of the attribute information. In this case, the processor 312 of the management device 300 newly assigns second contact information different from the first contact information to the access by the second request (S83). Furthermore, the processing related to this assignment can be carried out using the same process as shown in Figure 6A, which describes the assignment of the first contact information.

[0160] When new second contact information is assigned in response to access by the second request, the processor 312 of the management device 300 transmits to the distribution device 200 via the communication interface the second contact ID information generated by the same process as in S112 in Figure 6A, and the second contact information (T83) generated by the same process as in S114 or S115.

[0161] The processor of the distribution device 200 generates webpage information (S84) that includes the second contact information received for the webpage requested in the second request (T81) (for example, advertisement A). This webpage information includes the various contents that make up the webpage of advertisement A, which is the first webpage, as well as the second contact information received in T83 and the URL to be accessed. The processor of the distribution device 200 transmits the webpage information (T84) and the second contact ID information to the user terminal device 100-2 via the communication interface as a viewing response to the second request.

[0162] The processor of the user terminal device 100-2 outputs the web page generated by the browser application to the display based on the web page information contained in the received browsing response (S25). Thereafter, the same processing as from S26 onwards in Figure 5A is performed for the second contact information as well. With this, the processing for receiving a second request, which is a second access, is terminated.

[0163] In this way, depending on whether the access via the second request resulted in a departure from web page 10 or a predetermined amount of time had elapsed since that departure, the system selects whether to continue using the first contact information or to assign new second contact information. Therefore, it becomes possible to efficiently manage the limited number of contact information.

[0164] As described above, according to this embodiment, it is possible to provide a processing device, a processing program, and a processing method that can appropriately handle user access to web pages.

[0165] 6. Variations In the above embodiment, a case was described in which, when a second request is received, second contact information is assigned only if a predetermined amount of time has elapsed since the user left the web page 10 or the like. However, the invention is not limited to this, and second contact information may be assigned uniformly whenever a user leaves the web page 10 or the like.

[0166] In the above embodiment, time T2 was used as a comparison target for the elapsed time since departure in order to select whether or not to maintain the assignment of the first contact information (S412 in Figure 6D). With respect to time T2, for example, if a contact is actually made to the provider terminal device 100-1 based on the first contact information, a longer time than time T2 may be set as the comparison target. That is, when the processor 312 of the management device 300 receives information indicating that a contact was made from the provider terminal device 100-1 or the user terminal device 100-2 after leaving the web page 10, the processor 312 of the management device 300 sets a time T3 that is longer than time T2 in the selection process corresponding to the contact ID information of the first contact information. Then, in the determination in S412 in Figure 6D, the processor 312 of the management device 300 determines whether or not the elapsed time calculated by subtracting the contact ID information is shorter than time T3 (for example, 120 minutes). The subsequent processing is the same as in Figure 6D. Thus, when a contact is made, the processor 312 of the management device 300 maintains the assignment of the first contact information for a longer period of time. It is presumed that users who actually make a contact are users who have a higher level of interest in the service or product, and by maintaining the assignment of the first contact information for such users for a longer period of time, it is possible to collect attribute information and perform other tasks more efficiently.

[0167] Conversely, if, for example, a contact is actually made to the provider terminal device 100-1 based on the first contact information, a shorter time than time T2 may be set as the comparison target. In other words, when the processor 312 of the management device 300 receives information indicating that a contact has been made from the provider terminal device 100-1 or the user terminal device 100-2 after leaving the web page 10, the processor 312 of the management device 300 sets a time T4 that is longer than time T2 in the selection process corresponding to the contact ID information of the first contact information. Then, in the determination at S412 in Figure 6D, the processor 312 of the management device 300 determines whether the elapsed time calculated for the contact ID information is shorter than time T4 (for example, 5 minutes). The subsequent processing is the same as in Figure 6D. In this way, when a contact is made, the processor 312 of the management device 300 maintains the assignment of the first contact information for a shorter period. For example, there may be cases where the process on webpage 10 is completed through a contact and there is no need to access webpage 10 any further. For such users, shortening the retention period for the assignment of the first contact information makes it possible to make more effective use of the contact information resources.

[0168] In the above embodiment, we described a case where, based on behavioral information, the assignment of the first contact information to the access by the first request is removed if the contact to the first contact information is deemed "suspicious" or "of low interest." However, such removal of contact information assignments based on behavioral information may be performed according to the number of contact information items. For example, the processor 312 of the management device 300 calculates the number of contact information items that are currently maintained as assigned to any access at any given time based on the information in the tracking management table. Then, the processor 312 calculates the percentage of contact information items that are currently maintained as assigned, based on the total number of contact information items that have been prepared in advance as candidates for assignment. If the calculated percentage exceeds a predetermined percentage (for example, 80%), the processor 312 selects whether or not to continue maintaining the assignment of the currently assigned contact information, depending on the judgment result based on behavioral information (for example, if the judgment result is "suspicious" or "of low interest"). In this way, under normal circumstances, control based on behavioral information is not performed to prioritize processing efficiency, while when the resources for contact information are strained, the assignment of contact information is actively removed to enable efficient operation.

[0169] In the above embodiment, a case was described in which multiple telephone numbers such as 03-XXXX-XXX1, 03-XXXX-XXX2, 03-XXXX-XXX3, and 03-XXXX-XXX4 are prepared as candidates for assigning the first contact information, and the first contact information is selected from among these candidates. In other words, as described above, since the contact information is selected from multiple contact information sets that have been prepared in advance, there is a limit to the number of candidates when viewed from the perspective of the provider alone. Therefore, the number of contact information sets that can become candidates for assignment may be increased according to the number of contact information sets that are currently maintained with an assignment. For example, the processor 312 of the management device 300 calculates the number of contact information sets that are currently maintained with an assignment for access to the web page provided by provider A at any time based on the information in the tracking management table. Then, the processor 312 calculates the percentage of contact information sets that are currently maintained with an assignment based on the total number of contact information sets that have been prepared in advance as candidates for assignment for provider A. If the calculated percentage exceeds a predetermined percentage (e.g., 80%), the processor 312 temporarily adds contact information prepared as an allocation candidate for other providers whose percentage is lower than the predetermined percentage (e.g., 30%) as an allocation candidate for provider A. In this way, it becomes possible to smoothly manage the limited number of contact information among providers.

[0170] The above embodiment describes the process when first contact information is assigned in response to access by the first request. Each process described in the above embodiment can be similarly applied to other requests and other contact information, such as the second request, third request, or fourth request, or the second contact information, third contact information, or fourth contact information.

[0171] In the above embodiment, the presence or absence of other operation inputs, departure time, return time, and access history within the same domain as the web page 10 were used as behavioral information, and the case in which quality is estimated based on this behavioral information was described. However, in addition to these, for example, the presence or absence of contact (e.g., a call) made between the user terminal device 100-2 and the provider terminal device 100-1, i.e., between the user and the provider, as shown in S33 of Figure 5A, can also be used as evaluation information to estimate quality. Specifically, as shown in Figure 5A, when a contact (T26) is made from the user terminal device 100-2, the processor 312 of the management device 300 transfers the contact to the provider terminal device 100-1. Therefore, the processor 312 of the management device 300 can manage the presence or absence of contact.

[0172] When the processor 312 of the management device 300 receives evaluation information indicating whether or not contact has occurred, as described above, it weights a score indicating quality based on that evaluation information. Furthermore, when the processor 312 estimates quality using a trained estimation model, it inputs the evaluation information together with the behavioral information and obtains the estimation result from the trained estimation model. The trained estimation model is generated by acquiring training evaluation information indicating whether or not contact has occurred between the provider of a service or product introduced on an arbitrary web page and the user who has entered contact information on that web page, and then assigning correct labels based on that training evaluation information and training behavioral information to generate training estimation result information.

[0173] Please note that the above forwarding process may not be performed if the contact information is not provided by telephone number. In such cases, it is possible to obtain contact information from a CRM (Customer Relationship Management) system or similar.

[0174] Furthermore, in the above embodiment, as shown in Figure 6B, for example, a case was described in which attribute information is stored in association with the same user ID information even on subsequent accesses, based on attribute management information (e.g., an identifier) ​​assigned by a tag for storing attribute information. However, it is also possible to store attribute information in association with the same user ID information even on subsequent accesses by other methods without relying on attribute management information. For example, the processor 312 of the management device 300 compares the attribute information stored when the website is accessed for the second time or later with the attribute information stored in the user management table in association with each user ID information.

[0175] Specifically, the processor 312 reads user identification information from the attribute information stored during the second and subsequent accesses, such as access history, IP address, access time, or the type of browser application or OS the user is using, which can be used to identify the user. The processor 312 then matches this user identification information with the attribute information stored in the user management table, which is associated with each user ID information. As a result of the matching, the processor 312 associates the attribute information stored during the second and subsequent accesses with the user ID information that has a high degree of similarity to the user identification information and stores it in storage.

[0176] The matching process may also be performed by the processor 312 comparing the user identification information with information already stored in the user management table, such as access history, IP address, access time, or the type of browser application or OS used by the user. Alternatively, the processor 312 may pre-label the similarity of training information, which includes combinations of training user identification information and training attribute information, as the correct answer, and then input the user identification information into a trained comparison model generated by machine learning or deep learning using this training information.

[0177] In this way, by matching attribute information that has been pre-stored in association with user ID information with newly acquired attribute information, it becomes possible to store newly acquired attribute information in association with the same user ID information without using attribute management information. In particular, attribute management information assigned by tags may only be stored for a certain period (for example, 7 days), but even if attribute management information is not stored, it is still possible to store newly acquired attribute information in association with the same user ID information.

[0178] In the above embodiment, behavioral information was described in which, as an example, the presence or absence of other operation inputs, departure time, return time, and access history within the same domain as the web page 10 were used, and quality was estimated based on this behavioral information. However, in addition to these, for example, the time of contact (e.g., a phone call) made between the user terminal device 100-2 and the provider terminal device 100-1, i.e., between the user and the provider, as shown in S33 of Figure 5A, can also be used as evaluation information to estimate quality. The longer the time required for contact, the higher the estimated interest in the service or product introduced on the web page. Therefore, by using the time required for contact as evaluation information, it is possible to estimate quality more accurately.

[0179] In addition, other evaluation information that can be used is the content of a conversation between the user terminal device 100-2 and the provider terminal device 100-1. For example, the processor 312 can analyze the content of the conversation using language analysis processing with a trained model, and estimate the degree of interest in the service or product based on the analysis results.

[0180] Specifically, when the processor 312 of the management device 300 receives evaluation information indicating the time required for contact from the user terminal device 100-2 or the provider terminal device 100-1, it weights a score indicating quality based on the evaluation information. Furthermore, when the processor 312 estimates quality using a trained estimation model, it inputs the evaluation information together with the behavioral information and obtains the estimation result from the trained estimation model. The trained estimation model is generated by acquiring training evaluation information indicating the time required for contact between a provider of a service or product introduced on an arbitrary web page and a user who has entered contact information on that web page, and then assigning correct labels based on the training evaluation information and training behavioral information to generate training estimation result information.

[0181] The processes and procedures described herein can be implemented not only by means of expressly described herein, but also by software, hardware, or a combination thereof. Specifically, the processes and procedures described herein can be implemented by implementing logic corresponding to the process on media such as integrated circuits, volatile memory, non-volatile memory, magnetic disks, and optical storage. Furthermore, the processes and procedures described herein can be implemented as computer programs and executed by various computers, including terminal devices and server devices.

[0182] Even if it is stated that the processes and procedures described herein are performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, multiple software programs, multiple components, and / or multiple modules. Similarly, even if it is stated that the various types of information described herein are stored in a single memory or storage unit, such information may be distributed and stored in multiple memories within a single device or in multiple memories distributed across multiple devices. Furthermore, the software and hardware elements described herein may be implemented by integrating them into fewer components or by decomposing them into more components. [Explanation of Symbols]

[0183] 100-1 Provider terminal device 100-2 User terminal device 200 distribution devices 300 Management device

Claims

1. A processing unit comprising at least one processor, The at least one processor, By obtaining a first request for a user to access a web page via a user terminal device available to the user, the system assigns a first contact information selected from among multiple contact information for contacting a provider of services or goods to the access related to the first request in order to identify the access related to the first request. The display information of the web page, including the assigned first contact information, is output to the user terminal device. Based on whether the user has left the aforementioned webpage or another webpage within the same domain as the aforementioned webpage, the system selects whether or not to maintain the assignment of the first contact information to the access related to the first request. A processing unit configured to perform a process for that purpose.

2. The processing apparatus according to claim 1, wherein when a second request for accessing the web page again is received from the user or the user terminal device, a second contact information different from the first contact information is assigned to the access relating to the second request, in accordance with the selection.

3. The apparatus according to claim 1, wherein the departure is determined using a web beacon contained in the web page or the other web page.

4. The processing apparatus according to claim 1, wherein the departure is determined by using at least one of the following: the launch of another application program in the foreground that is different from the browser application program that displays the web page; access to a web page in a domain different from the domain of the web page; termination of the application program for outputting the web page; and detection of an operation input to the operation buttons of the user terminal device.

5. The apparatus according to claim 1, wherein the selection is made based on whether or not a predetermined time has elapsed since the time of departure.

6. The processing apparatus according to claim 1, wherein if a predetermined time has elapsed since the time of the aforementioned withdrawal, it is selected not to maintain the assignment of the first contact information.

7. The processing apparatus according to claim 5 or 6, which changes the predetermined time depending on whether or not contact has been made with the provider via the first contact information.

8. The processing device according to claim 1, which, when a second request to access the web page again is received from the user or the user terminal device before a predetermined time has elapsed since the aforementioned departure, causes the web page containing the first contact information to be output again.

9. The processing apparatus according to claim 8, wherein whether the second request is a second access from the user or the user terminal device is determined based on the identification information assigned in response to the first request.

10. The processing apparatus according to claim 1, wherein, among the plurality of contact information, new contact information that is a candidate for assignment is added in accordance with the number of contact information for which the assignment is currently maintained.

11. The processing device according to claim 1, which, based on the number of contact information items among the plurality of contact information items for which the assignment is currently maintained, selects whether or not to maintain the assignment of the first contact information to the access relating to the first request, based on a determination result based on behavioral information indicating actions taken in relation to the web page.

12. A computer comprising at least one processor, wherein a processing method is performed by the at least one processor, The process involves obtaining a first request for a user to access a web page via a user terminal device available to the user, and assigning a first contact information selected from among multiple contact information for contacting a provider of services or goods to the access related to the first request in order to identify the access related to the first request. The steps include outputting the display information of the web page, including the assigned first contact information, to the user terminal device, A step of selecting whether or not to maintain the assignment of the first contact information to the access relating to the first request, based on whether or not the user has left the aforementioned webpage or another webpage within the same domain as the aforementioned webpage, A processing method that includes this.

13. In a computer comprising at least one processor, the at least one processor is: By obtaining a first request for a user to access a web page via a user terminal device available to the user, the system assigns a first contact information selected from among multiple contact information for contacting a provider of services or goods to the access related to the first request in order to identify the access related to the first request. The display information of the web page, including the assigned first contact information, is output to the user terminal device. Based on whether the user has left the aforementioned webpage or another webpage within the same domain as the aforementioned webpage, the system selects whether or not to maintain the assignment of the first contact information to the access related to the first request. A processing program that is designed to perform a specific action.

Images