Processing device, processing program, processing method, and processing system

Abstract

To enable appropriate identification of an access to a webpage by users.SOLUTION: A processing device is provided, comprising at least one processor configured to perform processing for allowing a user to initiate a call on a webpage, outputting call information that enables identification of an access to the webpage by the user, and, upon receipt of input to the call information by the user, outputting at least a portion of consent information for requesting consent for the identification from the user in preference to the webpage.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a processing device, a processing program, and a processing method for identifying a user's access to a web page. [Background technology]

[0002] Conventionally, so-called tracking technology has been known that tracks and analyzes the route taken by a user to access a specific web page and the user's browsing history on the web page. For example, Patent Document 1 describes a management system that matches an access log with an incoming call history by checking an inquiry telephone number and a called telephone number. However, such a system is not desirable for a user who wants to refuse the matching of the access log with the incoming call history. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2017-037421 Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure has been made in light of the above-mentioned background, and provides a processing device, a processing program, a processing method, and a processing system that are capable of accurately identifying accesses to web pages by users. [Means for solving the problem]

[0005] According to one aspect of the present disclosure, there is provided a "processing device having at least one processor, the at least one processor being configured to execute a process to output call information on a web page capable of initiating a call by a user and identifying an access by the user to the web page, and upon receiving input by the user on the call information, output at least a portion of consent information requesting the user's consent to the identification in priority to the web page."

[0006] According to one aspect of the present disclosure, there is provided a "processing program for causing a computer having at least one processor to function as follows: to output call information capable of initiating a call by a user on a web page and identifying an access by the user to the web page; and, upon receiving input from the user on the call information, to output at least a portion of consent information requesting the user's consent to the identification in priority to the web page."

[0007] According to one aspect of the present disclosure, there is provided a "processing method executed by at least one processor in a computer having the at least one processor, the processing method including: outputting, on a web page, call information capable of initiating a call by a user and identifying an access by the user to the web page; and, upon receiving input by the user regarding the call information, outputting at least a portion of consent information for requesting the user's consent to the identification in priority to the web page."

[0008] According to one aspect of the present disclosure, there is provided "a processing system having at least one processor, the at least one processor being configured to execute a process to output, on a web page, call information capable of initiating a call by a user and identifying an access by the user to the web page, and upon receiving input by the user regarding the call information, output at least a portion of consent information requesting the user's consent to the identification in priority to the web page." Effect of the Invention

[0009] According to the present disclosure, it is possible to provide a processing device, a processing program, a processing method, and a processing system that are capable of accurately identifying accesses to web pages by users.

[0010] It should be noted that the above effects are merely illustrative for the convenience of explanation and are not limiting. In addition to or instead of the above effects, any effect described in this disclosure or any effect obvious to a person skilled in the art may be achieved. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an outline of tracking by a processing system 1 according to the first embodiment. [Diagram 2] FIG. 2 is a conceptual diagram illustrating a schematic configuration of a processing system 1 according to the first embodiment. [Diagram 3] FIG. 3 is a block diagram showing an example of the configuration of the terminal device 100 according to the first embodiment. [Figure 4] FIG. 4 is a block diagram showing an example of the configuration of the server device 200 according to the first embodiment. [Diagram 5] FIG. 5 is a block diagram showing an example of the configuration of the management device 300 according to the first embodiment. [Figure 6A]FIG. 6A is a diagram conceptually illustrating a tracking table stored in memory 313 of management device 300 according to the first embodiment. [Figure 6B] FIG. 6B is a diagram conceptually illustrating a tracking table stored in the memory 313 of the management device 300 according to the first embodiment. [Figure 7A] FIG. 7A is a diagram showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the server device 200, and the management device 300 according to the first embodiment. [Figure 7B] FIG. 7B is a diagram showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the server device 200, and the management device 300 according to the first embodiment. [Figure 7C] FIG. 7C is a diagram showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the server device 200, and the management device 300 according to the first embodiment. [Figure 8] FIG. 8 is a diagram showing a process flow executed in the user terminal device 100-2 according to the first embodiment. [Figure 9A] FIG. 9A is a diagram illustrating an outline of an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the first embodiment. [Figure 9B] FIG. 9B is a diagram showing an outline of an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the first embodiment. [Figure 9C] FIG. 9C is a diagram illustrating an outline of an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the first embodiment. [Figure 9D] FIG. 9D is a diagram showing an outline of an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the first embodiment. [Figure 10]FIG. 10 is a diagram showing a processing sequence of processing executed on a web page in the processing system 1 according to the second embodiment. [Figure 11] FIG. 11 is a diagram showing a process flow executed in the user terminal device 100-2 according to the second embodiment. [Figure 12] FIG. 12 is a diagram illustrating an outline of an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the second embodiment. [Figure 13] FIG. 13 is a diagram showing a processing sequence of processing executed on a web page in the processing system 1 according to the third embodiment. [Figure 14] FIG. 14 is a diagram showing an outline of an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the third embodiment. [Figure 15] FIG. 15 is a diagram showing a processing sequence of processing executed on a web page in the processing system 1 according to the fourth embodiment. [Figure 16A] FIG. 16A is a diagram showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the server device 200, and the management device 300 according to the fifth embodiment. [Figure 16B] FIG. 16B is a diagram showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the management device 300, and the call terminal device 500 according to the fifth embodiment. [Figure 17] FIG. 17 is a diagram showing an outline of an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the fifth embodiment. [Figure 18] FIG. 18 is a diagram showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the server device 200, and the management device 300 according to the sixth embodiment. [Figure 19]FIG. 19 is a diagram showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the management device 300, and the call terminal device 500 according to the sixth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] The embodiments of the present disclosure will be described with reference to the accompanying drawings, in which the same reference numerals are used to designate the same components.

[0013] 1. Overview of processing system 1 according to the first embodiment The processing system 1 according to the first embodiment is used, for example, to obtain consent from a user for call tracking or the like related to a call. Specifically, the processing system outputs consent information for requesting the consent to a terminal device of a user who makes a call based on call information including a monitoring telephone number or the like outputted on a web page. This processing system displays a restriction display that restricts the user from starting a call in priority over the web page.

[0014] 1 is a diagram illustrating an outline of processing by the processing system 1 according to the first embodiment. Specifically, when a user who has accessed a web page makes a call based on call information, consent information is output to a terminal device of the user for requesting consent to identifying the access.

[0015] The terminal device included in the processing system 1 is a terminal device owned by a user. The terminal device, for example, searches a web page by a so-called search engine through a user's operation. When the user shows an interest in an advertisement for a service or the like in a web page, the user calls an operator related to the advertisement using call information displayed in the web page. The operator can propose optimal services to the user by calling the user while referring to history information such as what kind of search the user performed to access the web page before calling and what information the user obtained before accessing the web page. Therefore, the processing system 1 allows the operator to obtain history information with the user's consent to at least identifying access to the web page. This allows the processing system 1 to provide appropriate guidance by the operator while giving the user a sense of security.

[0016] In this disclosure, the term "processing device" simply means a device that performs at least one of the processes related to the present disclosure. In particular, in this disclosure, the "processing device" is described as a terminal device owned by a user, but may be a device other than the terminal device.

[0017] In addition, in this disclosure, the term "user" simply means a person who uses or allows others to use a service provided by the processes of the present disclosure. In other words, a "user" may be any person involved in at least one of the processes of the present disclosure.

[0018] In addition, in this disclosure, the term "web page" simply means information output from a device accessed through communication. In particular, in this disclosure, the term "web page" is described as a web page accessed by searching with a search engine, but it may also be a so-called intranet that is made available for viewing only to specific individuals in advance. Specific examples of web pages include so-called landing pages that are accessed by searching with a search engine or via links in displayed advertisements. Such landing pages typically include introduction information for introducing a specific service or product, an application page for the service or product or a link for accessing the application page, call information, etc. It is preferable that the purpose of the landing page is to increase conversions such as purchases, inquiries, and requests for information on products and services by users who have viewed the page.

[0019] In addition, in this disclosure, "call information" simply means information for enabling a call between users. In particular, in this disclosure, "call information" includes "contact information" used to identify a device to be connected so as to be able to transmit information in order to make a call. In addition, a telephone number is given as an example of "contact information", but it may also be information for identifying a device to be connected in order to make a call using a data communication network. In addition, specific examples of call information include telephone numbers, accounts such as SNS, and links for so-called online conferences. In addition, the call information may be operated by a user to start a call application different from a browser application program for displaying a web page (hereinafter simply referred to as an "application") to start a call.

[0020] Furthermore, in this disclosure, the names given to each device are merely used to distinguish each device from others, and each device may be given a different name depending on its function.

[0021] In addition, even if the disclosure includes descriptions such as "first" and "second," this does not mean that the description is limited to only the two elements to which the description is attached. Naturally, the disclosure may include a "third," a "fourth," and more elements.

[0022] 2. Configuration of Processing System 1 Fig. 2 is a conceptual diagram showing a schematic configuration of a processing system 1 according to the first embodiment. As shown in Fig. 2, the processing system 1 includes a user terminal device 100-2 owned by a user, and a server device 200 that operates a web page. As a result, the user terminal device 100-2 outputs a web page and consent information based on information received from the server device 200, and allows the user to view them.

[0023] Preferably, the processing system 1 includes an operator terminal device 100-1 owned by an operator, and a management device 300 that identifies access to a web page by a user. This allows the processing system 1 to receive a call from a user terminal device 100-2 via the operator terminal device 100-1. Also, the management device 300 can manage consent information output to the user terminal device 100-2.

[0024] The above-mentioned devices in the processing system 1 are connected to each other so as to be able to communicate in both directions via a network 400. The network 400 is, for example, the Internet. That is, the terminal device 100 and the server device 200 are connected to an Internet line by wire or wirelessly, and are capable of transmitting and receiving various information and the like. Note that the network 400 may be a network different from the Internet, or may be an intranet.

[0025] In the example of FIG. 2, only one operator terminal device 100-1 and one user terminal device 100-2 are shown, but multiple operator terminal devices 100-1 and user terminal devices 100-2 that can access a web page may be connected to each other so as to be able to communicate with each other via the network 400.

[0026] Furthermore, although the server device 200 and the management device 300 are described as being single devices, the components and processes of the server device 200 and the management device 300 may be distributed across multiple server devices or cloud server devices.

[0027] Also, although the user terminal device 100-2 is described as an example of a processing device, the processing device may be other than the user terminal device 100-2. For example, the processing device may be the operator terminal device 100-1, the server device 200, or the management device 300, or may be a server device equipped with a machine learning function. In other words, the server device equipped with a machine learning function may access a web page in a machine learning manner and the user may consent to identifying the access to the web page.

[0028] 3. Configuration of the Terminal Device 100 3 is a block diagram showing an example of the configuration of the terminal device 100 according to the first embodiment. The terminal device 100 is a collective term for the operator terminal device 100-1 and the user terminal device 100-2. The terminal device 100 does not need to have all of the components shown in FIG. 3, and may have a configuration in which some components are omitted, or may have other components added. The operator terminal device 100-1 and the user terminal device 100-2 may have different configurations, and may not have the same configuration as the terminal device 100.

[0029] The terminal device 100 is typically a terminal device capable of wireless communication, such as a smartphone, but is not limited to such a device. For example, the terminal device may be a feature phone, a personal digital assistant, a PDA, a laptop computer, a desktop computer, a portable game machine, a stationary game machine, or any other device capable of executing the program according to the present disclosure. In addition, the terminal device 100 in the processing system 1 may include multiple terminal devices, but the terminal devices do not need to be the same type and may be different types of terminal devices.

[0030] 3, the terminal device 100 includes an output interface 111, a processor 112, a memory 113 including a RAM, a ROM, or a non-volatile memory (in some cases, an SSD), a communication interface 114 including a communication processing circuit and an antenna, and an input interface 115 including a touch sensor and a hard key. These components are electrically connected to each other via control lines and data lines.

[0031] The output interface 111 functions as an output unit that outputs images captured by a camera included in the input interface 115 and various displays output by executing a program according to the present disclosure to a device such as a display or a printer in response to an instruction from the processor 112. In addition, the output interface 111 outputs sounds based on acquired information and various sounds output by executing a program according to the present disclosure to a device such as a speaker in response to an instruction from the processor 112. Note that such a display is, for example, a liquid crystal display, an organic electroluminescence display, or electronic paper. In addition, the output interface 111 includes a speaker and is capable of emitting sounds in response to an instruction from the processor 112.

[0032] The processor 112 is composed of a CPU (microcomputer) and functions as a control unit that controls other components connected thereto based on various programs stored in the memory 113. Specifically, the processor 112 reads out from the memory 113 a program for executing an application according to the present disclosure and a program for executing an OS (Operating System) and executes the program. The processor 112 may be composed of a single CPU, or may be composed of a combination of a plurality of CPUs and GPUs. In the present disclosure, the processor 112 particularly executes "a process of outputting, on a web page, call information capable of starting a call by a user and identifying an access by the user to the web page" and "a process of outputting, upon receiving an input by the user for the call information, at least a part of consent information for requesting the user to consent to the identification in preference to the web page", etc.

[0033] The memory 113 includes a main storage device such as a ROM, a RAM, a nonvolatile memory, and an auxiliary storage device such as a HDD or an SSD, and functions as a storage unit. The ROM stores instructions for executing the application and the OS according to the present disclosure as a program. The RAM is used to write and read data while the program stored in the ROM is being processed by the processor 112. The nonvolatile memory is a memory into which data is written and read by the execution of the program, and the data written therein is stored even after the execution of the program is terminated.

[0034] In the present disclosure, memory 113 stores programs for "processing for initiating a user call on a web page and outputting call information capable of identifying an access by the user to the web page" and "processing for, when receiving an input by the user regarding the call information, outputting at least a portion of consent information for requesting the user's consent to the identification in priority to the web page," etc.

[0035] The communication interface 114 functions as a communication unit that transmits and receives information to and from the remotely installed operator server device 200, or other terminal devices or server devices, via a communication processing circuit and an antenna. The communication processing circuit processes the programs and various information used in the processing system 1 to transmit and receive information from other terminal devices or other server devices according to the progress of processing.

[0036] The communication processing circuit processes based on a wideband wireless communication system such as the 5G system, but can also process based on a system related to narrowband wireless communication such as wireless LAN such as IEEE802.11 or Bluetooth (registered trademark) or a system related to non-contact wireless communication. Also, wired communication can be used instead of or in addition to wireless communication.

[0037] The input interface 115 is composed of a touch panel, hard keys, a camera, a microphone, etc., and functions as an input unit that accepts instruction inputs related to the execution of the program according to the present disclosure and inputs for registering various information. The touch panel is arranged to cover the output interface 111, and transmits position coordinate information corresponding to image data output from the output interface 111 to the display to the processor 112. As the touch panel method, known methods such as a resistive film method, a capacitive coupling method, and an ultrasonic surface acoustic wave method can be used. In the present disclosure, the touch panel detects a swipe operation or a tap operation on each icon displayed on the output interface 111 by an indicator. In the present disclosure, the input interface 115 provided in the terminal device 100 is used, but it is also possible to use an input interface 115 connected wirelessly or by wire to a main body provided with the processor 112, etc., such as a mouse. The camera and microphone included in the input interface 115 are devices capable of detecting external images and sounds. The camera and microphone may be built into the terminal device 100, or may be an external device connected wirelessly or by wire so as to be able to communicate with the terminal device 100.

[0038] 4. Configuration of Server Device 200 Fig. 4 is a block diagram showing an example of the configuration of the server device 200 according to the first embodiment. The server device 200 does not need to have all of the components shown in Fig. 4, and it is possible to adopt a configuration in which some components are omitted, or other components can be added. In addition, the server device 200 does not need to have the components shown in Fig. 4 in a single housing, and it is also possible to distribute the components and processes of the server device 200 to multiple server devices or cloud server devices.

[0039] 4, the server device 200 includes a processor 212 configured with a CPU or the like, a memory 213 including a RAM, a ROM, a non-volatile memory, an HDD, and the like, and a communication interface 214. These components are electrically connected to each other via control lines and data lines.

[0040] The processor 212 is composed of a CPU (microcomputer) and functions as a control unit for controlling other connected components based on various programs stored in the memory 213. Specifically, the processor 212 reads out from the memory 213 a program for executing an application according to the present disclosure and a program for executing an OS, and executes them. The processor 212 may be composed of a single CPU, or may be composed of multiple CPUs. In the present disclosure, the processor 212 particularly executes "a process of transmitting display information of a web page for outputting consent information to the management device 300 via the communication interface 214," "a process of transmitting history information such as a search history in the user terminal device 100-2 to the management device 300 via the communication interface 214," "a process of accepting a call," "a process of identifying access to a web page by a user," and the like.

[0041] The memory 213 includes a RAM, a ROM, a non-volatile memory, and a HDD, and functions as a storage unit. The ROM stores instructions for executing the application and the OS according to the present disclosure as a program. Such a program is loaded and executed by the processor 212. The RAM is used to write and read data while the program stored in the ROM is being processed by the processor 212. The non-volatile memory is a memory into which data is written and read by the execution of the program, and the data written therein is stored even after the execution of the program is terminated.

[0042] In the present disclosure, the memory 213 stores programs for "processing of transmitting display information of a web page for outputting consent information to the management device 300 via the communication interface 214," "processing of transmitting history information such as a search history in the user terminal device 100-2 to the management device 300 via the communication interface 214," "processing of accepting a call," "processing of identifying access to a web page by a user," and the like.

[0043] The communication interface 214 functions as a communication unit that transmits and receives information to and from the terminal device 100 and other server devices installed remotely via a communication processing circuit and an antenna. The communication processing circuit processes the programs and various information used in the processing system 1 to transmit and receive information from the terminal device 100 and other server devices according to the progress of processing. The communication processing circuit processes based on a wideband wireless communication method such as the 5G method, but can also process based on a method related to narrowband wireless communication such as wireless LAN and Bluetooth (registered trademark) such as IEEE802.11, or a method related to non-contact wireless communication. In addition, wired communication can be used instead of or in addition to wireless communication.

[0044] 5. Configuration of management device 300 Fig. 5 is a block diagram showing an example of the configuration of a management device 300 according to the first embodiment. The management device 300 does not need to include all of the components shown in Fig. 5, and may have a configuration in which some components are omitted, or other components may be added. In addition, the management device 300 does not need to include the components shown in Fig. 5 in a single housing, and each component and process of the management device 300 may be distributed to multiple server devices or cloud server devices.

[0045] 5, the management device 300 includes a processor 312 configured with a CPU or the like, a memory 313 including a RAM, a ROM, a non-volatile memory, an HDD, and the like, and a communication interface 314. These components are electrically connected to each other via control lines and data lines.

[0046] Processor 312 is configured with a CPU (microcomputer) and functions as a control unit for controlling other connected components based on various programs stored in memory 313. Specifically, processor 312 reads out and executes a program for executing an application according to the present disclosure and a program for executing an OS from memory 313. Processor 312 may be configured with a single CPU or multiple CPUs.

[0047] The memory 313 includes a RAM, a ROM, a non-volatile memory, and a HDD, and functions as a storage unit. The ROM stores instructions for executing the application and the OS according to the present disclosure as a program. Such a program is loaded and executed by the processor 312. The RAM is used to write and read data while the program stored in the ROM is being processed by the processor 312. The non-volatile memory is a memory into which data is written and read by the execution of the program, and the data written therein is stored even after the execution of the program is terminated.

[0048] The communication interface 314 functions as a communication unit that transmits and receives information to and from the terminal device 100 and other server devices installed remotely via a communication processing circuit and an antenna. The communication processing circuit processes the programs and various information used in the processing system 1 to transmit and receive information from the terminal device 100 and other server devices according to the progress of processing. The communication processing circuit processes based on a wideband wireless communication method such as the 5G method, but can also process based on a method related to narrowband wireless communication such as wireless LAN and Bluetooth (registered trademark) such as IEEE802.11, or a method related to non-contact wireless communication. In addition, wired communication can be used instead of or in addition to wireless communication.

[0049] 6. Information stored in memory 313 of management device 300 6A is a diagram conceptually illustrating a tracking table stored in memory 313 of management device 300 according to the first embodiment. In the tracking table, an administrator ID, a web ID, a contact ID, and a user ID are stored in association with a tracking ID. Note that the information stored in the tracking table is merely an example, and it is not necessary to satisfy all of the information, and information other than the information may be stored in the tracking table.

[0050] The "tracking ID" is an identification number given to each tracking process. The "tracking ID" is a number given when the user agrees to the management device 300 acquiring history information such as search history in the user terminal device 100-2, the administrator using the history information, and the administrator providing the history information to a third party (hereinafter also referred to as tracking). The tracking process is a process that starts when the user agrees to tracking. The "administrator ID" is an identification number given to each company or the like that is the administrator of the web page. The "web ID" is an identification number given to each web page. Therefore, when one administrator manages one web page, one "web ID" is assigned to the "administrator ID". On the other hand, when one administrator manages multiple web pages, multiple "web IDs" are assigned to the "administrator ID". Also, when multiple administrators jointly manage web pages, multiple "administrator IDs" are assigned to one "web ID".

[0051] The "contact ID" is an identification number given to each piece of contact information (e.g., a telephone number) for monitoring calls made by a user. The contact information is, for example, a telephone number used for tracking. This telephone number is a telephone number owned by the management device 300. When the user terminal device 100-2 calls the telephone number, the operator terminal device 100-1 makes a call via the management device 300. A single or multiple "contact IDs" are assigned to one "web ID". Specifically, when multiple user terminal devices 100-2 access a web page corresponding to the "web ID", the "contact ID" assigns different contact information to each user terminal device 100-2. That is, the "contact ID" as call information is assigned so as to be linked to the access to the web page of the user terminal device 100-2. The "user ID" is an identification number given to each user. Specifically, the "user ID" is an identification number assigned to a user inferred from the individual number of the user terminal device 100-2 that accessed the web page. By accumulating information in this manner in the tracking table, unique information for each user is accumulated.

[0052] 6B is a diagram conceptually illustrating a user information table stored in the memory 313 of the management device 300 according to the first embodiment. The user information table is an information table formed by accumulating information stored in the tracking table. In the user information table, user information and external data IDs are stored in association with user IDs. Note that the information stored in these user information tables is merely an example, and it is not necessary to satisfy all of this information, and information other than this information may be stored in the user information table.

[0053] "User information" is information including a history of actions by a user. The user information is generated based on information stored in the tracking table and a table corresponding to the information. Specifically, the user information includes a history of access to web pages accessed by the user using the user terminal device 100-2, a call history including the date and time of a call, contact information used for a call, the contents of responses given to an operator when making a call, and a response history to a questionnaire, etc. The "external data ID" is identification information given to external information acquired from a database, etc. different from the tracking table. The external information includes user attribute information such as the user's age and sex. The external information also includes information that overlaps with the above-mentioned user information. By forming a user information table in this way, user-specific information can be collectively managed.

[0054] The memory 313 may store a management table combining the above-mentioned tracking table and user information table, instead of storing the tracking table and user information table separately. In this case, the processor 312 of the management device 300 may appropriately generate a table composed of necessary information from the one table. In addition, although the above description has been given with the user information and the external information separated, the user information may be stored in the external information, or the external information may be stored in the user information.

[0055] 7. Processing sequence performed by processing system 1 7A to 7C are diagrams showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the server device 200, and the management device 300 according to the first embodiment. The processing flow and information provided to the user will be described below with reference to each drawing.

[0056] (A. Setting Registration) First, FIG. 7A is a diagram showing a processing sequence of a process of registering a setting for executing a tracking process in a web page in the processing system 1 according to the first embodiment. As shown in FIG. 7A, the management device 300 sets a setting for executing the tracking process in the web page (S11). Specifically, the processor 312 of the management device 300 sets a setting for displaying contact information and a setting for displaying a consent screen, which will be described later, and the like. These settings are configured in a programming language such as JavaScript (registered trademark). After setting (S11), the management device 300 transmits a request for registering the setting to a web page stored in the server device 200 via the communication interface 314 (T11). The server device 200 receives the request via the communication interface 214 and registers the setting. Specifically, the management device 300 assigns a web ID to the web page stored in the server device 200 and stores it in a web table (not shown). In addition, the management device 300 assigns an administrator ID to an administrator who manages the web page, and stores it in an administrator table (not shown).

[0057] (B. Tracking Processing) Next, Fig. 7B and Fig. 7C are diagrams showing a processing sequence of the processing executed on the above-mentioned web page in the processing system 1 according to the first embodiment. As shown in Fig. 7B, the user terminal device 100-2 executes a web search process in response to a user's operation (T21). Specifically, in the web search process, a search engine searches for web pages related to keywords arbitrarily set by the user. The user terminal device 100-2 repeats the web search process in response to a user's operation, and when the user selects a link to the above-mentioned web page, the user terminal device 100-2 requests the server device 200 to browse the web page (T22). The browsing request (T22) includes terminal information such as the identification number, model, and OS identification information of the user terminal device 100-2.

[0058] When the server device 200 receives the browsing request (T22), it requests the management device 300 for a phone number for tracking as contact information (T23). The management device 300 stores a plurality of phone numbers for tracking in a contact table (not shown) associated with a contact ID, and responds to the server device 200 by assigning at least one of the plurality of phone numbers to the browsing request (T22) (T24). The management device 300 also requests the user to consent to the tracking process (T25) at substantially the same time as the number response (T24). When the server device 200 receives the consent request (T25), it generates display information to be displayed as a web page and acceptance information for accepting an operation by the user (S21). Specifically, the server device 200 generates the display information and acceptance information by specifying the angle of view of the web page, the size and position of the icon to be displayed, and the programming language for the process executed by the user's operation, based on the terminal information received in the browsing request (T22). Furthermore, the server device 200 transmits (T26) the display information, the acceptance information (S21), and response information including the telephone number to the user terminal device 100-2 that made the viewing request (T22).

[0059] The user terminal device 100-2 outputs the web page on the display in accordance with the viewing response (T26) received from the server device 200 (S22). An icon displaying the above-mentioned telephone number is arranged on the web page, which will be described in detail later. The user operates to make a call to the telephone number by, for example, tapping the icon. That is, the user terminal device 100-2 accepts a call operation from the user when the icon arranged on the web page is tapped (S23). When the user terminal device 100-2 accepts the call operation (S23), it requests the user to consent to the tracking process. Specifically, the user terminal device 100-2 requests the user to consent to a process of transmitting, for example, the search history of a web search (T21) performed by the tracking process and history information such as the date and time of access to the web page to the management device 300. More specifically, the user terminal device 100-2 displays a so-called pop-up screen (consent information) that requests the user to give consent on the display (that is, displays it superimposed on the web page) in priority to the web page (S24).

[0060] In addition, the "consent to the tracking process" is not limited to the above example, and may include a request for consent from the user for the management device 300 to specify the access to the web page of the user terminal device 100-2 by the user's operation. In addition, the "consent to the tracking process" may include a request for consent from the user for specifying and acquiring information such as the access history and search history leading up to the access. In addition, the "consent to the tracking process" may include a request for consent from the user for the management device 300, which has acquired the information on the access, to provide the information to a third party other than the administrator of the management device 300. In addition, the "consent to the tracking process" may include a request for consent from the user for using the information acquired by the tracking process, such as optimizing advertisements displayed on a web page, based on the information acquired by the tracking process. In addition, the "consent to the tracking process" may include a request for consent for a combination of these, or may include a request for consent for other things.

[0061] The user decides whether or not to consent to the tracking process based on the pop-up screen. That is, when the user operates to consent to the tracking process (S25), the user terminal device 100-2 transmits history information to the management device 300 (T27). Here, the history information includes link information of the web page, a telephone number as contact information assigned when responding to the browsing request (T22) (T24), terminal information of the user terminal device 100-2, and the like. When the management device 300 receives the history information (T27), it stores the history information in a tracking table and a user information table (S26). Specifically, the management device 300 generates a tracking ID and stores it in the tracking table, stores each ID associated with the tracking ID in the tracking table (FIG. 6A), and stores the history information (particularly the search history of the web search (T21) and the access date and time of the web page) in the user information of the user information table.

[0062] More specifically, the management device 300 identifies a web ID from a web table based on link information of the web page included in the history information, for example. The management device 300 also identifies an administrator ID from an administrator table based on a web ID, for example. The management device 300 also identifies a contact ID from a contact table based on a telephone number as contact information included in the history information, for example. The management device 300 also generates a contact ID based on terminal information of the user terminal device 100-2 included in the history information, for example. The management device 300 then stores these IDs in a tracking table. In addition to generating a contact ID, the management device 300 may also identify a user ID from a user information table based on terminal information of the user terminal device 100-2. In addition, it has been described that the user terminal device 100-2 transmits history information to the management device 300, but the history information may be stored in the server device 200, and the server device 200 may transmit the history information to the management device 300.

[0063] After that, as shown in FIG. 7C, the user terminal device 100-2 calls the above-mentioned telephone number by the user's operation (T30). When the management device 300 receives a call from the user terminal device 100-2 to the telephone number, it identifies the user based on the calling number (i.e., the telephone number as contact information assigned when responding (T24) to the browsing request (T22)) (S31). Specifically, the management device 300 identifies a contact ID from a contact table based on the calling number, and identifies a tracking ID from a tracking table (FIG. 6A). In addition, the management device 300 identifies a user ID corresponding to the tracking ID. Note that, although it has been described above that the user is identified based on the calling number (S31), the user may be identified based on the called number (i.e., the telephone number of the user terminal device 100-2). In this case, the management device 300 may identify user information including the called number from a user information table, and identify the corresponding user ID.

[0064] The management device 300 identifies user information corresponding to the identified user ID from the user information table, and extracts history information (particularly the search history of the web search (T21) and the access date and time of the web page) (S32). After that, the management device 300 transfers the call from the user terminal device 100-2 to the operator terminal device 100-1 (T31). Also, if an operation to consent to the tracking process is performed in S25, the management device 300 transmits the history information to the operator terminal device 100-1 (T32). Then, the operator terminal device 100-1 executes a call process with the user terminal device 100-2 while allowing the operator to view the history information (S33). That is, the operator can make a call with the user while viewing the history information. Note that, although it has been described above that the history information is transmitted to the operator terminal device 100-1 (T32), all of the information contained in the user information may be transmitted to the operator terminal device 100-1, or a part of the user information may be transmitted to the operator terminal device 100-1.

[0065] 8. Processing flow executed in the user terminal device 100-2 The process flow executed in the user terminal device 100-2 will now be described in detail. Fig. 8 is a diagram showing a processing flow executed in the user terminal device 100-2 according to the embodiment of the first embodiment. The processing flow is mainly performed by the processor 112 of the user terminal device 100-2 reading and executing a program stored in the memory 113. Figs. 9A to 9D are diagrams showing an outline of an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the embodiment of the first embodiment.

[0066] 8, in step S101, when a user selects a link to a webpage in an application for displaying a webpage, processor 112 of user terminal device 100-2 requests server device 200 to view the webpage. Next, in step S102, processor 112 repeatedly executes step S102 until a view response to the view request is received from server device 200 (No), and transitions to step S102 when a view response is received (Yes). Next, in step S103, processor 112 displays the webpage on the display based on the view response.

[0067] According to FIG. 9A, a web page of ABC Co., Ltd., which is the administrator of the web page, is displayed on the display of the user terminal device 100-2. On this web page, call information 401 is arranged. The call information 401 is an icon with a tracking phone number displayed in the approximate center. The user terminal device 100-2 accepts a call operation when the user taps on the call information 401.

[0068] Returning to Fig. 8, in step S104, processor 112 determines whether the user has left the web page due to an operation by the user. Specifically, although not shown, the processor 112 determines that the user has left the web page when the state of user terminal device 100-2 transitions to a state in which the user cannot view the web page due to an operation for returning to a screen before browsing the web page, an operation for stopping a search engine, an operation for stopping the operation of user terminal device 100-2, etc. Note that processor 112 may determine that the user has left the web page when a preset time has elapsed since the web page was displayed on the display, or may determine that the user has left the web page when it is estimated that the user is not browsing the web page.

[0069] In step S104, when the processor 112 determines that the user has left the web page due to the user's operation, the process flow ends. On the other hand, when the processor 112 determines that the user has not left the web page, the process proceeds to step S105. In step S105, the processor 112 determines whether or not a call operation has been performed. Specifically, according to FIG. 9A, when the user taps the call information 401 arranged on the web page, the processor 112 determines that a call operation has been performed. When the processor 112 determines that a call operation has not been performed, the process returns to step S104. That is, the processor 112 repeatedly executes steps S104 and 105 until the processor 112 determines that a call operation has been performed in step 105. When the processor 112 determines that a call operation has been performed, the process proceeds to step S106.

[0070] In step 106, the processor 112 displays consent information 403 for requesting consent from the user for the tracking process. As shown in Fig. 9B, the consent information 403 is a so-called pop-up screen that is displayed with priority over a web page. The consent information 403 displays an explanatory text 404 that explains the tracking process to the user, an consent icon 405 that the user taps (i.e., accepts input from the user) when consenting to the tracking process, and a disagreement icon 407 that the user taps when not consenting.

[0071] According to FIG. 8, in step S107, when the consent icon 405 is tapped, the processor 112 determines that the user consents to the tracking process, and proceeds to step S108. In step S108, the processor 112 transmits the history information to the management device 300 via the communication interface 114, and proceeds to step S109. In step S109, the processor 112, as shown in FIG. 9C, for example, starts an application for calling, displays it on the display, and outputs a phone number for tracking as call information 401 in a phone number input field 408 in the application for calling. Thereafter, for example, the user taps the call start icon 409 to start the call process. That is, the processor 112 makes a call to the phone number for tracking by the user's operation.

[0072] On the other hand, if the disagreement icon 407 is tapped in step 107, the processor 112 determines that the user does not agree to the tracking process, and proceeds to step S110. In step S110, the processor 112 transmits information indicating that the disagreement icon 407 is tapped to the management device 300 via the communication interface 114, and proceeds to step S109. In step S109, the processor 112 outputs a telephone number as the call information 401 to the telephone number input field 408 in the call application. Note that the telephone number in this case may or may not be for tracking. In addition, if the disagreement icon 407 is tapped, the processor 112 may return to step S103 without proceeding to step S109. That is, the processor 112 may restrict the call until the agreement icon 405 is tapped, for example, by repeating steps S103 to S107 until the agreement icon 405 is tapped in step 107.

[0073] 9D shows a modified example of the consent information described above. The consent information 413 includes an explanatory text 404, an consent icon 415, and a disagreement icon 417. The consent icon 415 is an icon that the user taps when agreeing to the tracking process, similar to the consent icon 405 described above. The disagreement icon 417 is an icon that the user taps when not agreeing to the tracking process, similar to the disagreement icon 407 described above.

[0074] Below the consent information 413 in the drawing, a call display 418 by a calling application is displayed. The call display 418 is an icon with a tracking phone number displayed in the approximate center. When the consent information 413 is not output, the call display 418 accepts a call operation by tapping it by the user, and executes a call process to the phone number. In other words, the consent information 413 restricts the call operation.

[0075] Here, as described above, the processor 112 displays a web page on the display based on the viewing response (step S103). The viewing response includes display information and acceptance information generated based on the terminal information. The terminal information includes identification information of the OS of the user terminal device 100-2. Therefore, for example, when the OS of the user terminal device 100-2 displays the call display 418 on the lower side of the display in terms of the drawing view, the agreement information 413 is displayed above the call display 418. This allows the user to view the agreement information 413 while viewing the call display 418, which gives the user a sense of security and allows the user to tap the agreement icon 415 or the disagreement icon 417.

[0076] With the above-described configuration, the user terminal device 100-2 according to the first embodiment has a processor 112 that outputs call information 401 that enables a user to initiate a call on a web page and to identify the user's access to the web page (a specific example is tracking processing), and upon receiving user input on the call information 401, executes processing to output at least a portion of consent information 403 for requesting the user's consent to tracking in priority to the web page.

[0077] As a result, when the user makes a call, the user terminal device 100-2 according to the first embodiment can execute the tracking process after obtaining the user's consent for the tracking process, for example. In particular, since the user terminal device 100-2 outputs the call information 401, for example, on a display, it can urge the user to make a call. Note that the consent information 403 may be, for example, information requesting consent for the tracking process, but may be information requesting consent for any process, such as a process of recording the contents of the call, a process of making a call while sharing an image, and a process of remote operation by an operator.

[0078] In addition, since the call information 401 includes contact information for monitoring calls made by the user, the user can make a call with the operator after obtaining consent for the monitoring of the user's calls. In addition, since the contact information is assigned when the user terminal device 100-2 accesses a web page, the number of contact information assigned to the web page can be optimized according to the increase or decrease in the number of accesses to the web page.

[0079] 9. Overview of Processing System 1 According to Second Embodiment Next, a processing system 1 according to a second embodiment will be described. Note that a description of configurations common to the first embodiment will be omitted, and configurations different from the first embodiment will be mainly described.

[0080] FIG. 10 is a diagram showing a processing sequence of processing executed on a web page in the processing system 1 according to the second embodiment. As shown in FIG. 10, in the processing system 1 according to the second embodiment, the user terminal device 100-2 outputs the web page according to the second embodiment to the display in accordance with the viewing response (T26) received from the server device 200 (S22). Although details will be described later, the web page has a restriction display 423 arranged so as to cover an icon displaying a phone number for tracking. When the user taps the restriction display 423 (S42), the user terminal device 100-2 displays the consent information 403 on the display in priority to the web page (i.e., superimposed on the web page) (S24). After that, when the user operates to consent to the tracking process (S25), the user terminal device 100-2 hides the restriction display 423 (S43). Thereafter, the user terminal device 100-2 transmits the history information to the management device 300 (T27), and accepts a call operation from the user by tapping the icon arranged on the web page (S23). In the second embodiment, the process before the viewing response (T26) is similar to that of the first embodiment, and therefore the description thereof will be omitted here. In the second embodiment, the process after the call operation (S23) is similar to that of the first embodiment, and therefore the description thereof will be omitted here.

[0081] Fig. 11 is a diagram showing a process flow executed in the user terminal device 100-2 according to the second embodiment. Fig. 12 is a diagram showing an outline of an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the second embodiment.

[0082] In step S103, the processor 112 displays a web page on the display based on the browsing response. According to FIG. 12, in the second embodiment, the display displays a restriction display 423 at a position where the call information 401 in the first embodiment is located. Specifically, the call information 401 includes a call icon 421 and a restriction display 423. The call icon 421 is an icon with a tracking phone number displayed in the approximate center. This call icon 421 can accept a call operation when tapped by a user. The restriction display 423 is a pop-up that is displayed with priority over the web page so as to cover the call icon 421. That is, the restriction display 423 is displayed to restrict the call information 401 from being operated by the user to make a call.

[0083] Returning to FIG. 11, in step S111, step S104 is repeated until the user taps the restriction display 423 (No). When the user taps the restriction display 423 (Yes), the process proceeds to step S106 to display the consent information 403 (S106). When the consent icon 405 or the disagreement icon 407 in the consent information 403 is operated (S107), the restriction display 423 is hidden in step S112 (S112). That is, the restriction display 423, which is displayed in priority over the web page so as to cover the call icon 421, is hidden, and the call icon 421 is displayed. This allows the user to make a call by operating the call icon 421 (S109). In the second embodiment, the process before step S103 is the same as in the first embodiment, so that the description here is omitted.

[0084] With the above-described configuration, in the user terminal device 100-2 according to the second embodiment, the call information 401 includes the restriction display 423 that restricts the user from starting a call, and when an input by the user is accepted for the restriction display 423, at least a part of the consent information 403 is output in preference to the web page, and when a response to the consent information 403 is accepted from the user, the restriction by the restriction display 423 is released. As a result, for example, when the tracking process of the processing system 1 according to the second embodiment is implemented on a web page on which a call icon 421 is arranged in advance, it is possible to restrict the user from starting a call by implementing the process related to the restriction display 423 and the consent information 403. Therefore, the processing system 1 according to the second embodiment can reduce the burden of the work and processing required for implementing the tracking process.

[0085] 10. Overview of Processing System 1 According to Third Embodiment Next, a processing system 1 according to a third embodiment will be described. Note that a description of configurations common to the first embodiment will be omitted, and configurations different from the first embodiment will be mainly described.

[0086] Fig. 13 is a diagram showing a processing sequence of processing executed on a web page in the processing system 1 according to the third embodiment. As shown in Fig. 13, in the processing system 1 according to the third embodiment, when a viewing request (T22) is received from the user terminal device 100-2, the server device 200 transfers the viewing request to the management device 300. Here, in the third embodiment, the response information (T26) that the server device 200 transmits to the user terminal device 100-2 does not include a phone number for tracking. When the user terminal device 100-2 receives the response information (T26), it displays the web page on the display (S22).

[0087] 14 is a diagram showing an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the third embodiment. In the third embodiment, the call information 401 does not display a phone number for tracking.

[0088] Returning to FIG. 13, when the user terminal device 100-2 accepts a call operation from the user (S23), it requests the server device 200 to provide a phone number for tracking as contact information (T23). The server device 200 transfers the number request (T23) received from the user terminal device 100-2 to the management device 300. The management device 300 transmits the tracking phone number assigned to the number request (T23) to the server device 200 (T24). The server device 200 transfers the number response (T24) received from the management device 300 to the user terminal device 100-2.

[0089] After receiving the number response (T24) from the management device 300 via the server device 200, the user terminal device 100-2 displays the consent information 403 on the display in preference to the web page, and accepts the consent operation (S25). After that, the user terminal device 100-2, for example, hides the consent information 403 and displays the call information 401 on the display (S51). Note that the call information 401 displayed here may be an icon displaying a telephone number as shown in FIG. 9A.

[0090] With the above-mentioned configuration, in the processing system 1 according to the third embodiment, contact information is not assigned until a call operation from the user is accepted (S23), and is assigned (T23-T24) after the call operation from the user is accepted (S23). As a result, in the processing system 1 according to the third embodiment, contact information is not assigned in cases where the user leaves the web page without making a call, so that the number of contact information to be assigned can be reduced.

[0091] 11. Overview of Processing System 1 According to Fourth Embodiment Next, a processing system 1 according to a fourth embodiment will be described. Note that a description of configurations common to the third embodiment will be omitted, and configurations different from the first embodiment will be mainly described.

[0092] FIG. 15 is a diagram showing a processing sequence of processing executed on a web page in the processing system 1 according to the fourth embodiment. According to FIG. 15, the user terminal device 100-2 transmits a number request (T23) after a calling operation (S23) in the third embodiment (see FIG. 13), whereas in the fourth embodiment, the user terminal device 100-2 transmits a number request (T23) after an agreement operation (S25). In addition, in the fourth embodiment, the number request (T23) includes information on whether or not the user has agreed to the tracking process. Furthermore, in the fourth embodiment, when allocating a phone number to the number request (T23), the management device 300 allocates a phone number for tracking if the user has agreed to the tracking process.

[0093] Specifically, when the user terminal device 100-2 accepts a call operation from the user (S23), it displays the consent information 403 on the display in preference to the web page, and accepts the consent operation (S25). After that, the user terminal device 100-2 requests a tracking phone number as contact information from the server device 200 (T23). The server device 200 transfers the number request (T23) received from the user terminal device 100-2 to the management device 300. The management device 300 transmits the tracking phone number assigned to the number request (T23) to the server device 200 (T24). The server device 200 transfers the number response (T24) received from the management device 300 to the user terminal device 100-2.

[0094] After receiving the number response (T24) from the management device 300 via the server device 200, the user terminal device 100-2 hides the consent information 403, for example, and displays the call information 401 on the display (S51). The call information 401 displayed here may be an icon displaying a telephone number as shown in Fig. 9A. In the fourth embodiment, the process before the call operation (S23) is the same as in the third embodiment, and therefore will not be described here.

[0095] With the above-described configuration, in the processing system 1 according to the fourth embodiment, the contact information is determined after accepting input of the consent information 403 from the user. As a result, for example, when a phone number is used as the contact information, a phone number for tracking can be assigned only when the user consents to the tracking process. Therefore, the assignment of phone numbers for tracking can be reduced.

[0096] 12. Overview of Processing System 1 According to Fifth Embodiment Next, a processing system 1 according to a fifth embodiment will be described. Note that a description of configurations common to the second embodiment will be omitted, and configurations different from the second embodiment will be mainly described.

[0097] FIG. 16A is a diagram showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the server device 200, and the management device 300 according to the fifth embodiment. FIG. 16B is a diagram showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the management device 300, and the call terminal device 500 according to the fifth embodiment. Note that FIG. 16A omits the call terminal device 500 described later. FIG. 16B omits the server device 200. The user terminal device 100-2 of the fifth embodiment is a terminal device that does not have a call function based on the call information according to the present disclosure. Specifically, the user terminal device 100-2 is a terminal device that does not have a call application or is limited in calls by a call application. More specifically, the user terminal device 100-2 is a terminal device that does not have a SIM card. A SIM (Subscriber Identity Module Card) card is a storage medium that includes identification information that identifies a subscriber of a mobile phone line. That is, the user terminal device 100-2 of the fifth embodiment is not assigned a telephone number (that is, contact information).

[0098] The call terminal device 500 is a device different from the user terminal device 100-2, and is a terminal device having a call function based on the call information according to the present disclosure. Specifically, the call terminal device 500 is a terminal device having a call application. More specifically, the call terminal device 500 is a terminal device having a SIM card. The call terminal device 500 may be a device having only a call function based on call information such as a landline phone, or may be a device similar to the user terminal device 100-2 described in the first to fourth embodiments.

[0099] According to FIG. 16A, the user terminal device 100-2 requests to view a web page (T22). As described above, the viewing request (T22) includes terminal information such as the identification number, model, and OS identification information of the user terminal device 100-2. That is, the server device 200 generates display information to be displayed as a web page and acceptance information for accepting an operation by a user based on the terminal information (S21). Specifically, first, a restriction display 423 similar to that of the second embodiment is displayed on the display (FIG. 12). As in the second embodiment, when the restriction display 423 is tapped by the user, the consent information 403 is displayed (S24), and when the consent icon 405 or the disagreement icon 407 in the consent information 403 is operated, the restriction display 423 is hidden (S43). After that, the user terminal device 100-2 transmits history information to the management device 300 (T27). When management device 300 receives the history information from user terminal device 100-2, management device 300 stores the history information in association with the tracking phone number (S26).

[0100] Fig. 17 is a diagram showing an outline of an example of a web page or the like displayed on the display of the user terminal device 100-2 according to the fifth embodiment. According to Fig. 17, the restriction display 423 is hidden (S24), and thus the call information 431 according to the fifth embodiment is displayed. The call information 431 according to the fifth embodiment displays a phone number for tracking. On the other hand, the call information 431 does not accept an input operation by the user.

[0101] Therefore, when the user terminal device 100-2 according to the fifth embodiment does not have a calling function, the user terminal device 100-2 displays a tracking phone number (i.e., contact information) as the call information 431. This allows the user to make a call using, for example, the call terminal device 500.

[0102] Returning to FIG. 16B, the user operates the call terminal device 500 to make a call to the tracking telephone number displayed in the call information 431. As described in the first embodiment, the management device 300 identifies the user based on the calling number (i.e., the telephone number as contact information assigned when responding (T24) to the viewing request (T22)) (S31). As a result, when an operation to consent to the tracking process is performed in the user terminal device 100-2, the management device 300 can identify the user and perform the tracking process even if the call is made by a call terminal device 500 different from the user terminal device 100-2.

[0103] 13. Overview of Processing System 1 According to Sixth Embodiment Next, a processing system 1 according to a sixth embodiment will be described. Note that a description of configurations common to the fifth embodiment will be omitted, and configurations different from the fifth embodiment will be mainly described.

[0104] 18 and 19 are diagrams showing a processing sequence executed among the operator terminal device 100-1, the user terminal device 100-2, the server device 200, the management device 300, and the call terminal device 500 according to the sixth embodiment. Note that the call terminal device 500 is omitted in FIG. 18, and the server device 200 is omitted in FIG. 19. According to FIG. 18, the server device 200 executes the processing up to the number response (T24) as in the fifth embodiment. Thereafter, the server device 200 generates display information and acceptance information (S21) without executing the consent request (T25), and transmits the response information to the user terminal device 100-2 (T26). As a result, a web page is output on the display of the user terminal device 100-2 (S22). Here, the call information 431 similar to that of the fifth embodiment is displayed on the web page displayed on the display (FIG. 17). In other words, the restriction display 423 in the fifth embodiment is not displayed.

[0105] According to FIG. 19, the user operates the call terminal device 500 to make a call to the tracking telephone number displayed in the call information 431. As in the fifth embodiment, the management device 300 identifies the user based on the calling number (S31). The management device 300 requests consent to the tracking process from the user terminal device 100-2 of the identified user (T25). After that, the user terminal device 100-2 displays consent information on the display in preference to the web page (S24), and when an operation to consent to the tracking process is performed (S25), the management device 300 transmits history information to the management device 300 (T27). Then, the management device 300 stores the history information in the tracking table and the user information table (S26), and thereafter executes the same process as in the fifth embodiment.

[0106] As a result, in the sixth embodiment, even if a call is made from a call terminal device 500 other than the user terminal device 100-2, the management device 300 can identify the user and display consent information for tracking processing on the user terminal device 100-2 owned by the user.

[0107] As described above, in the present embodiment, it is possible to provide a processing device, a processing program, a processing method, and a processing system that are capable of accurately identifying accesses to web pages by users.

[0108] 14. Variations

[0109] In the above-described embodiment, the process according to the present disclosure has been described using the first to fifth embodiments, but the process may be carried out in an embodiment in which each of the embodiments is appropriately combined.

[0110] The processes and procedures described in this specification can be realized not only by those explicitly described in this disclosure, but also by software, hardware, or a combination of these. Specifically, the processes and procedures described in this specification can be realized by implementing logic corresponding to the processes in a medium such as an integrated circuit, a volatile memory, a non-volatile memory, a magnetic disk, or an optical storage. In addition, the processes and procedures described in this specification can be implemented as computer programs and executed by various computers including terminal devices and server devices.

[0111] Although the processes and procedures described herein are described as being executed by a single device, software, component, or module, such processes or procedures may be executed by multiple devices, multiple software, multiple components, and / or multiple modules. Furthermore, although the various information described herein is described as being stored in a single memory or storage unit, such information may be stored in multiple memories provided in a single device or multiple memories distributed across multiple devices. Furthermore, the software and hardware elements described herein may be realized by integrating them into fewer components or breaking them down into more components. [Explanation of symbols]

[0112] 100 Terminal device (processing device) 200 Server device

Claims

1. A processing device comprising at least one processor, The at least one processor: outputting, on the web page, call information capable of initiating a call by a user and identifying an access by the user to the web page; when an input by the user is accepted for the call information, at least a part of consent information for requesting consent to the identification from the user is output in preference to the web page; 23. A processing device configured to perform processing for:

2. The processing device of claim 1 , wherein the call information includes contact information for monitoring calls made by the user.

3. The processing device of claim 2 , wherein the contact information is assigned when the processing device accesses the web page.

4. The processing device of claim 2 , wherein the contact information is determined after receiving an input by the user regarding the call information and before receiving an input regarding the consent information from the user.

5. The processing device of claim 2 , wherein the contact information is determined after receiving input of the consent information from the user.

6. the call information includes a restriction indicator that restricts the user from initiating the call; When an input by the user is accepted in response to the restriction display, at least a portion of the consent information is output in priority to the web page; The processing device according to claim 1 , wherein the restriction is lifted when a response to the consent information is received from the user.

7. The processing device according to claim 2 , wherein the processing device displays the contact information as the call information when the processing device does not have a call function.

8. In a computer having at least one processor, the at least one processor is outputting, on the web page, call information capable of initiating a call by a user and identifying an access by the user to the web page; when an input by the user is accepted for the call information, at least a part of consent information for requesting consent to the identification from the user is output in preference to the web page; A processing program that makes it function as follows.

9. A processing method executed by at least one processor in a computer having at least one processor, comprising: outputting, on the web page, call information capable of initiating a call by a user and identifying an access by the user to the web page; outputting at least a part of consent information for requesting consent to the identification from the user in priority to the web page when the user inputs the call information; A processing method comprising:

10. 1. A processing system comprising at least one processor, The at least one processor: outputting, on the web page, call information capable of initiating a call by a user and identifying an access by the user to the web page; when an input by the user is accepted for the call information, at least a part of consent information for requesting consent to the identification from the user is output in preference to the web page; 23. A processing system configured to perform processing for:

Images