Processing device, processing program, and processing method

Abstract

To provide a processing device, a processing program, and a processing method that enable a user to appropriately process a contact.SOLUTION: Provided is a processing device comprising at least one processor. The at least one processor, in a web page including contact information for contacting a provider providing a service or a commodity, acquires attribute information indicating the attribute of a user in association with information for tracking that enables identification of access to the web page by the user in accordance with the user's operational input for the contact information. When the contact is received from a user terminal device that the user can use, the at least one processor provides the attribute information associated with the information for tracking to a provider terminal device that the provider can use and executes processing for transferring the contact to the provider terminal device.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] So-called tracking technology has been known for some time, which tracks and analyzes the path a user takes 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 comparing an inquiry telephone number with a destination telephone number. However, there is room for improvement in how the information acquired by this method is utilized. [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, and a processing method that are capable of appropriately processing contacts made by a user. [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, wherein the at least one processor is configured to, in a web page including contact information for contacting a provider that offers a service or product, acquire attribute information indicating the attributes of the user in association with tracking information capable of identifying the user's access to the web page in response to a user's operational input to the contact information, and, upon receiving the contact from a user terminal device available to the user, provide the attribute information associated with the tracking information to a provider terminal device available to the provider, and execute processing to transfer the contact to the provider terminal device."

[0006] 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: in a web page including contact information for contacting a provider that offers a service or product, in response to a user's operational input on the contact information, acquiring attribute information indicating the attributes of the user in association with tracking information capable of identifying the user's access to the web page; and, upon receiving the contact from a user terminal device available to the user, providing the attribute information associated with the tracking information to a provider terminal device available to the provider, and transferring the contact to the provider terminal device.

[0007] According to one aspect of the present disclosure, there is provided a program that causes a computer having at least one processor to function as follows: in a web page containing contact information for contacting a provider that provides a service or product, in response to a user's operational input on the contact information, acquire attribute information indicating the attributes of the user by associating it with tracking information that can identify the user's access to the web page; and, upon receiving the contact from a user terminal device available to the user, provide the attribute information associated with the tracking information to a provider terminal device available to the provider, and execute processing to transfer the contact to the provider terminal device. [Effects of the Invention]

[0008] According to the present disclosure, it is possible to provide a processing device, a processing program, and a processing method that are capable of appropriately processing contacts made by a user.

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

[0010] [Figure 1] FIG. 1 is a diagram schematically illustrating an overview of processing by a processing system 1 according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a conceptual diagram schematically illustrating the configuration of a processing system 1 according to an embodiment of the present disclosure. [Figure 3] FIG. 3 is a block diagram illustrating an example of the configuration of a management device 300 according to an embodiment of the present disclosure. [Figure 4A] FIG. 4A is a diagram conceptually illustrating a tracking management table stored in the management device 300 according to an embodiment of the present disclosure. [Figure 4B]FIG. 4B is a diagram conceptually illustrating a user management table stored in the management device 300 according to an embodiment of the present disclosure. [Figure 5] FIG. 5 is a diagram showing a processing sequence executed in the processing system 1 according to the embodiment of the present disclosure. [Figure 6A] FIG. 6A is a diagram showing a processing flow of processing executed in the management device 300 according to an embodiment of the present disclosure. [Figure 6B] FIG. 6B is a diagram showing a processing flow of processing executed in the management device 300 according to an embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram conceptually illustrating a communication process executed in an embodiment of the present disclosure. [Figure 8A] FIG. 8A 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 8B] FIG. 8B is a diagram showing an example of source code of a web page displayed on the user terminal device 100-2 in another embodiment of the present disclosure. [Figure 9] FIG. 9 is a diagram showing a processing sequence executed in the processing system 1000 according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] 1. Overview of Processing System 1 According to the Present Disclosure As an example, the processing system 1 of the present disclosure is used to receive contact, such as a phone call, from a user who has viewed a web page, and to appropriately forward the contact to a provider of a service or product introduced on the web page, as well as to provide attribute information about the user.

[0013] FIG. 1 is a diagram illustrating an outline of processing by a processing system 1 according to an embodiment of the present disclosure. A user terminal device included in the processing system 1 is a terminal device available to a user. The user terminal device, for example, accepts a user's operation input to launch an application program (e.g., a browser application) and executes a web page search process. When the user terminal device accepts the selection of a desired web page to be accessed from a search web page displaying the search results, the user terminal device transmits a distribution request for the selected web page to a 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 the web page to a display or the like, making it viewable by the user. Thereafter, when the user shows interest in a service or product or the like in the web page, the user terminal device accepts an operation input from the user in response to contact information displayed in the web page, initiates contact (e.g., a call) with the provider of the service or product, and extracts attribute information such as an access history related to the web page.

[0015] When the management device receives a contact (e.g., a call) from a user from the user terminal device, it transfers the contact (e.g., a call) to a provider terminal device that can be used by a provider of a service or product. The management device also provides the provider terminal device with attribute information of the user, including access history, etc. Note that the provider terminal device to which the contact (e.g., a call) is transferred and the provider terminal device to which the attribute information is provided may be the same device or different devices.

[0016] According to such a processing system 1, it is possible to appropriately transfer a contact (e.g., a call) received from a user to a provider terminal device, and the provider who uses the provider terminal device that received the contact (e.g., a call) can process the contact while referring to the attribute information of the user. Therefore, according to the processing system 1, it is possible to more appropriately process contacts from users.

[0017] In this disclosure, the term "processing device" refers to a device that executes any of the processes related to this disclosure, and may be any of a management device, a distribution device, a user terminal device, a provider terminal device, and other devices. In the following, a case where a management device functions as a processing device will be described, but it is not limited to only the management device.

[0018] In addition, in this disclosure, a "web page" refers to information output from an accessed device to each terminal device via a browser. Specific examples of web pages include a first web page accessed by a search using a browser application or via a link in a displayed advertisement, and a second web page via which an advertisement is posted when accessing the first web page.

[0019] A first web page is a web page created by a specific organization or individual to post information related to that organization or individual. The destination of a web page is identified by a URL, and a first web page typically includes a domain (such as a top-level domain, second-level domain, or third-level domain) acquired by each organization or individual following a protocol. An example of a first web page is a landing page. Such a first web page (e.g., a landing page) includes introductory information for 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 phone number. It is preferable that the first web page (e.g., a landing page) is intended to increase conversions, such as encouraging users who view the first web page to purchase, inquire, or request information about a product or service. In this disclosure, a "first web page" is described as one that can be accessed by anyone via a browser application or the like, but it may also be a web page prepared on a so-called intranet that can be viewed only by specific individuals.

[0020] The second web page is another web page that is accessed before the first web page is accessed. The second web page typically includes a domain (such as a top-level domain, a second-level domain, or a third-level domain) acquired by a search engine provider following the protocol. An example of a second web page is a search web page that displays the results of a search using specific keywords in a search engine. Such a second web page (e.g., a search web page) includes an advertisement including the first web page to arouse the interest of the accessing user, and link information (e.g., a URL) of the web page hit by the search.

[0021] In the present disclosure, a second web page is another web page that is accessed before accessing a first web page. Therefore, if web page B is accessed via web page A, web page A becomes the first web page and web page B becomes the second web page. Also, if web page A is accessed via web page C, web page C becomes the first web page and web page A becomes the second web page. In other words, the same web page may be either the first web page or the second web page.

[0022] Furthermore, in this disclosure, "contact" simply means contacting another company (e.g., a provider) to convey information. Therefore, the means of contact may be a phone call, email, chat, or a combination of these. Furthermore, such contact does not necessarily require the contact person to be a human being; it may be, for example, a chatbot.

[0023] Furthermore, in this disclosure, a "provider" refers to a person who provides a service or product. Therefore, a provider is not limited to a specific individual, but also includes an organization or group (e.g., a company). Furthermore, a provider terminal device does not refer to a device that can be used by a specific individual, but broadly includes devices that can be operated or used by an organization or group. Note that a provider terminal device is used to accept transfers of contacts (e.g., calls) and receive attribute information, but the provider terminal device that accepts transfers and the provider terminal device that receives attribute information do not necessarily have to be the same device and may be different devices.

[0024] In the present disclosure, "tracking information" refers to information that can identify a user. Examples of such tracking information include a telephone number, an email address, a social networking service account, an administrative number used to respond to user inquiries in chat format, a link for an online conference, arbitrary identification information generated for tracking, user ID information, a terminal identification number of a user terminal device, a telephone number of a user terminal device, or a combination thereof. Among these, from the viewpoint of effectively processing attribute information such as a user's website access history, a telephone number, an email address, a social networking service account, an administrative number used to respond to user inquiries in chat format, a link for an online conference, arbitrary identification information generated for tracking, or a combination thereof is preferred. Such telephone numbers, etc. used for tracking are typically configured such that, upon receiving a request to access a webpage from a user, a specific telephone number is assigned to the user's access and displayed at a predetermined position on the webpage. When a user's input to the telephone number, etc. is detected, a calling application program, which is different from the application program displaying the webpage, is launched to initiate contact (e.g., a call).

[0025] In the present disclosure, "attribute information" refers to information indicating attributes related to a user. Examples of such attribute information include the user's age, gender, address, occupation, marital status, annual income, presence or absence of children, interests, life events, buying and selling history, browser application accounts, accounts for communication tools such as social networking sites, the user's terminal device's telephone number, email address, terminal identification number, model change timing, IP address, display resolution, webpage search history, browsing history, landing page access history, and online game history via the Internet. "Attribute information" is not limited to text data, but may also be feature quantities based on photographic information of the user's face and voice information of the user. Furthermore, the attribute information may be not only the specific information exemplified above, but also classification information that classifies users based on the specific information exemplified above (for example, if the user's age is "20 years old," the classification information that classifies the user is "20 to 24 years old").

[0026] Furthermore, in this disclosure, even if a description such as "first" or "second" is used, it does not mean that the description is limited to only the two elements to which it is attached. Naturally, multiple elements such as "third," "fourth," and more may also be included.

[0027] 2. Configuration of Processing System 1 2 is a conceptual diagram illustrating a schematic configuration of a processing system 1 according to an embodiment of the present disclosure. As illustrated in FIG. 2, the processing system 1 includes a user terminal device 100-2 available to a 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.

[0028] Typically, a distribution device that distributes a web page for each domain name and host name in a URL that specifies the access destination of the web page is provided. However, for the sake of convenience, in Figure 2, multiple distribution devices are collectively referred to as distribution device 200. In other words, distribution device 200 may include at least one of the different distribution devices provided for each domain name and host name.

[0029] The processing system 1 may also include a provider terminal device 100-1 that can be used by a provider of a service or product. This allows the processing system 1 to receive contact from a user terminal device 100-2 via the provider terminal device 100-1.

[0030] The provider terminal device 100-1 and the user terminal device 100-2 are typically terminal devices capable of wireless communication, such as smartphones, but are not limited to such devices. For example, any device capable of executing the program according to the present disclosure, such as a feature phone, a personal digital assistant (PDA), a laptop computer, or a desktop computer, can be suitably applied as the terminal device. Furthermore, in the processing system 1, the provider terminal device 100-1 and the user terminal device 100-2 do not need to be the same type of terminal device, but may be different types of terminal devices. Furthermore, while FIG. 2 illustrates a single device for each of the provider terminal device 100-1 and the user terminal device 100-2, it goes without saying that multiple devices may be included depending on the number of users and providers.

[0031] The above-described devices in the processing system 1 are communicatively connected via a network 400. The network 400 is configured by a public line network such as LTE or ISDN, an Internet line network, or a combination of these. Therefore, the provider terminal device 100-1, the user terminal device 100-2, the distribution device 200, and the management device 300 are communicatively connected to each other via a public line network or an Internet line, and transmit and receive various information, etc. Note that the network 400 may be a network different from the Internet, or may be an intranet.

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

[0033] Furthermore, although the 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 may perform part of the processing performed by the management device 300.

[0034] 3. Configuration of each device <Management device 300> FIG. 3 is a block diagram illustrating an example of the configuration of a management device 300 according to an embodiment of the present disclosure. The management device 300 does not need to include all of the components illustrated in FIG. 3 ; some components may be omitted, or other components may be added. Furthermore, while the management device 300 is typically configured as a server device, the components illustrated in FIG. 3 do not need to be contained in a single housing; the components and processes of the management device 300 may be distributed across multiple server devices or cloud server devices. In this embodiment, a database 315 storing various information may be connected via a communication interface 314. Furthermore, in this disclosure, the memory included in the server device may refer to any of the following cases, unless otherwise specified: a memory 313 only; a database 315 only; or both the memory 313 and the database 315.

[0035] 3, the management device 300 includes a processor 312 configured with a CPU or the like, a memory 313 including RAM, ROM, 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.

[0036] 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 from the memory 313 a program for executing an application according to the present disclosure and a program for executing an OS. The processor 312 executes, among other things, "a process of acquiring attribute information indicating a user's attributes in association with tracking information capable of identifying a user's access to a web page in response to a user's operation input for the contact information on a web page including contact information for contacting a provider who provides a service or product" and "a process of providing the attribute information associated with the tracking information to a provider terminal device available to the provider and transferring the contact to the provider terminal device upon receiving a contact from a user terminal device available to the user." The processor 111 is primarily composed of one or more CPUs, but may also be combined with a GPU, FPGA, or the like as appropriate.

[0037] The memory 313 includes RAM, ROM, nonvolatile memory, and HDD and functions as a storage unit. The ROM stores instructions for executing the application and OS according to the present disclosure as a program. Such programs are 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 nonvolatile memory is memory into which data is written and read by the execution of the program, and data written therein is retained even after the execution of the program has ended. The memory 313 stores programs that cause the processor 312 to execute, in particular, "a process of acquiring attribute information indicating a user's attributes in association with tracking information capable of identifying a user's access to a web page in response to a user's operation input for the contact information on a web page including contact information for contacting a provider who provides a service or product" and "a process of providing attribute information associated with the tracking information to a provider terminal device available to the provider and transferring the contact to the provider terminal device upon receiving a contact from a user terminal device available to the user." Furthermore, the memory 313 stores various types of information to be stored in the tracking management table and the user management table, together with the database 315 as necessary.

[0038] The communication interface 314 functions as a communication unit that transmits and receives information to and from 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 an antenna. The communication processing circuit processes programs and various information used in the processing system 1 to transmit and receive information to and from the provider terminal device 100-1, user terminal device 100-2, distribution device 200, and other devices as the processing progresses. The communication processing circuit processes based on a wideband wireless communication method such as the 5G method, but can also process based on a narrowband wireless communication method or a contactless wireless communication method such as a wireless LAN or Bluetooth (registered trademark) such as IEEE802.11. Wired communication can also be used instead of or in addition to wireless communication.

[0039] In addition, the communication interface 314 preferably communicates with the provider terminal device 100-1 at least via the Internet network, which is a computer network using the Internet Protocol (IP), and communicates with the user terminal device 100-2 at least via the above-mentioned Internet network or a public line network using a so-called telephone number.

[0040] <Distribution device 200> Although the configuration of the distribution device 200 is not specifically illustrated, it is configured with a processor, memory, communication interface, etc., similar to the management device 300 shown in Fig. 3. Such a distribution device 200 is typically configured as a server device, but it does not need to be provided in a single housing, and each component and process of the distribution device 200 can be distributed to multiple server devices or cloud server devices. The distribution device 200 executes each process shown in Fig. 5, for example, by having the processor process a program stored in the memory.

[0041] <Provider Terminal Device 100-1 and User Terminal Device 100-2> Although the configuration of the provider terminal device 100-1 and the user terminal device 100-2 is not specifically shown in the drawings, they are composed of a processor, a memory, a communication interface, an input interface such as a touch panel or a mouse, an output interface such as a display, etc. Such provider terminal device 100-1 and user terminal device 100-2 execute, for example, each process shown in FIG. 5 by the processor processing a program stored in the memory.

[0042] 4. Information stored in the memory 313 of the management device 300 4A is a diagram conceptually illustrating a tracking management table stored in the management device 300 according to an embodiment of the present disclosure. The information stored in the table is updated and stored as the processing progresses.

[0043] 4A, the tracking management table stores tracking information, web page information, history information, user ID information, and the like, in association with tracking ID information. "Tracking ID information" is assigned to each tracking process and is information for identifying each tracking process. For example, tracking ID information is generated each time a new session occurs, with the session duration being a certain period (e.g., 30 minutes after no accesses have occurred or until the browser application is closed) since a browsing request for new access to a web page is sent to the distribution device 200 from the user terminal device 100-2. For example, when a new session is started, the management device 300 acquires attribute information, such as the access history of the user terminal device 100-2, and requests the user's consent for the administrator to use the attribute information or for the administrator to provide the attribute information to a third party (e.g., the distribution device 200). Such information is also managed in association with the tracking ID information.

[0044] "Tracking information" is information used to identify users who access a web page. Examples of such tracking information include telephone numbers, email addresses, social networking service accounts, administrative numbers used to respond to user inquiries in chat format, online conference links, arbitrary identification information generated for tracking, 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 networking service accounts, administrative numbers used to respond to user inquiries in chat format, online conference links, arbitrary identification information generated for tracking, or combinations thereof are preferred from the perspective of effectively processing attribute information such as a user's website access history. For example, when a request to view a specific web page is sent from user terminal device 100-2 and a session to view the web page is initiated, different tracking information is assigned to each session. For example, the tracking information is displayed as contact information in a predetermined position on the web page.

[0045] The arbitrary identification information used as tracking information in the above is, for example, information generated based on attribute information acquired from tag information provided to the user terminal device 100-2 along with a web page. By managing the identification information, it is possible to identify whether a user has accessed the web page for the first time or has accessed it again.

[0046] The "web page information" is information for identifying a web page to be tracked. That is, the web page information identifies the web page accessed by the user terminal device 100-2 in the session in which the tracking ID information was generated. The web page information typically stores information such as a URL.

[0047] "History information" refers to information related to the history acquired when accessing a web page. Examples of history information include a user's web page search history, 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 stored in a cart on an e-commerce site, input information entered within a web page, user account information used on a web page, or a combination of these. Such history information includes, for example, first-party data collected by cookies issued from the domain of the site accessed by the user, and third-party data collected by cookies issued from domains other than the site accessed by the user.

[0048] "User ID information" is information for identifying a user. Examples of user ID information include an SNS account, an email address, an arbitrary character string designated by the user or service provider, a name, or a combination of these.

[0049] 4A, tracking ID information is generated each time a new session occurs, and tracking information used for tracking is managed in association with the tracking ID information. Then, history information on the user's access history is collected based on the tracking information, and the user is identified based on the collected history information, and the user ID information is managed.

[0050] 4B is a diagram conceptually illustrating a user management table stored in the management device 300 according to an embodiment of the present disclosure. The information stored in the table is updated and stored as the processing progresses.

[0051] 4B, the user management table stores personal information, history information, attribute information 1, attribute information 2, attribute information 3, etc. in association with user ID information. In the present disclosure, attribute information means information indicating attributes related to a user, and the attribute information includes personal information, history information, attribute information 1, attribute information 2, attribute information 3, and other attribute information.

[0052] "User ID information" is information for identifying a user. Examples of the user ID information include an SNS account, an email address, an arbitrary character string designated by the user or the service provider, a name, or a combination thereof. "Personal information" includes the user's age, gender, address, occupation, marital status, annual income, parental status, interests, life events, buying and selling history, browser application accounts, accounts for communication tools such as SNS, the telephone number, email address, terminal identification number, time of model change, IP address, display resolution of the user terminal device 100-2, or a combination thereof. This personal information may be updated and stored each time it is obtained during processing by the processing system 1, or may be entered and stored in advance when the user newly registers for a service provided by the processing system 1.

[0053] The "history information" is the same as the history information in Fig. 4A. When user ID information is identified based on the history information acquired in Fig. 4A, the user ID information is associated with the user ID information and stored as history information in the user management table.

[0054] "Attribute information 1" to "Attribute information 3" are information indicating attributes of the user other than those exemplified above. For example, they may be any information such as classification information (such as 20-24 years old) generated based on the user's personal information.

[0055] 5. Processing sequence performed by processing system 1 Fig. 5 is a diagram showing a processing sequence executed in the processing system 1 according to an embodiment of the present disclosure. Specifically, Fig. 5 shows a processing sequence executed among the user terminal device 100-2, the distribution device 200, and the management device 300. Of these, S11 to S12 indicate a setting process for executing a tracking process on a web page, and S21 to S32 indicate a tracking process for providing attribute information to a provider terminal device by tracking.

[0056] <Settings for tracking> 5, the processor 312 of the management device 300 configures a web page to execute the tracking process (S11). Specifically, the processor 312 of the management device 300 collects history information such as access history and configures tags (e.g., measurement tags) for acquiring tracking information when a website is accessed and a session is started. These configurations are configured using programming languages ​​such as JavaScript (registered trademark) and HTML. Once the configurations are configured, the processor 312 of the management device 300 transmits a registration request (T11) for the configurations to the web page stored in the distribution device 200 via the communication interface 314. The registration request includes information identifying the website on which the tag is configured.

[0057] When the processor of distribution device 200 receives the registration request via the communication interface, it registers settings such as tags for the web page based on the information that identifies the web page. This completes the setting process for executing the tracking process.

[0058] <Tracking process to provide attribute information> 5, the processor of the user terminal device 100-2 accepts a user's operation input via the input interface and launches a browser application. The processor of the user terminal device 100-2 then accepts the user's operation input via the input interface and transmits an access request to a website that provides a search engine for searching web pages. This initiates a new session, and history information and the like are collected. Upon receiving the access request via the communication interface, the processor of the distribution device 200 transmits information about the website that provides the search engine to the user terminal device 100-2.

[0059] When the processor of the user terminal device 100-2 receives the website information via the communication interface, it outputs the received website via the browser application via the output interface. The processor of the user terminal device 100-2 then accepts a user's input via the input interface and inputs a search term into a search engine. When the search term is input, the processor of the user terminal device 100-2 transmits the input search term to the distribution device 200 via the communication interface. The processor 212 of the distribution device 200 generates a second web page (search web page) including search results based on the received search term and transmits the second web page to the user terminal device 100-2 via the communication interface 214.

[0060] Such a second web page (search web page) typically includes, in addition to the search results, advertisements that the distribution device 200 has decided to post. That is, the processor 212 of the distribution device 200 assigns advertisements to be posted in the search results output to the browser application based on the user ID information, search words, attribute information, and the like.

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

[0062] The processor of the user terminal device 100-2 accepts user input via the input interface and selects a desired advertisement or web page (e.g., an advertisement) from the display screen of the second web page (S21). When a web page of a specific advertisement is selected in the browser application, the processor of the user terminal device 100-2 transmits a view request (T21) for the selected web page to the distribution device 200 via the communication interface. The view request includes a request for web page information for displaying the web page and terminal type information that identifies the type of the user terminal device 100-2. The terminal type information is, for example, information that identifies whether the user terminal device is a terminal capable of communication via a public line network, i.e., whether an application program for calling using a telephone number is available.

[0063] When the processor of the distribution device 200 receives the viewing request, it generates a tracking information request in accordance with the settings of S11 to S12 (S22). The processor of the distribution device 200 transmits the generated tracking information request (T22) together with terminal type information to the management device 300 via the communication interface. When the processor 312 of the management device 300 receives the tracking information request via the communication interface 314, it generates tracking information (S23).

[0064] Here, Fig. 6A is a diagram showing a processing flow of processing executed in the management device 300 according to an embodiment of the present disclosure. Specifically, Fig. 6A is a diagram showing a processing flow related to the tracking information generation processing executed by the processor 312 of the management device 300 in S23 of Fig. 5. 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.

[0065] 6A, the processor 312 receives a tracking information request together with terminal type information from the distribution device 200 via the communication interface 314 (S111). Upon receiving the tracking information request, the processor 312 generates tracking ID information unique to a series of sessions browsing web pages and stores the generated tracking ID information in a tracking management table in the memory 313.

[0066] Here, the terminal type information received in S111 is information that specifies whether the user terminal device is a terminal capable of communication via a public line network, i.e., whether an application program for calling using a telephone number can be used. Therefore, based on the terminal type information, the processor 312 determines whether the user terminal device 100-2 is a terminal device capable of communication via a public line network (S112). If the result of the determination shows that communication via a public line network is possible, i.e., an application program for calling can be used, tracking information is generated using a telephone number assigned to the session (S114).

[0067] As an example, a number of different telephone numbers (e.g., 03-XXX-XXX1, 03-XXX-XXX2, 03-XXX-XXX3, 03-XXX-XXX4, etc.) are prepared in advance in memory 313 of management device 300 for tracking purposes. Then, upon receiving the tracking information request, processor 312 selects one telephone number (e.g., 03-XXX-XXX1) from the number of telephone numbers. Processor 312 uses the selected telephone number (e.g., 03-XXX-XXX1) as tracking information specific to the session. That is, for example, when a call (contact) is made from user terminal device 100-2 to the selected telephone number (e.g., 03-XXX-XXX1), it is possible to identify that the telephone number is assigned to the session, and it becomes possible to refer to history information, etc., associated with the telephone number (tracking information) in FIG. 4A.

[0068] On the other hand, if the result of the determination is that communication via the public line network is not possible, i.e., the application program for calls cannot be used, tracking information is generated using any identification information generated for tracking purposes that is different from the above telephone number (S115).

[0069] As an example, the arbitrary identification information generated for tracking purposes is identification information consisting of an arbitrary character string generated by the processor 312 when a new session is started. In this case, when the user terminal device 100-2 contacts a provider to obtain additional information about or apply for a service or product, the contact is made using an Internet network using the Internet Protocol (IP). The contact is made, for example, by email, voice or text chat using an SNS, online conference, or a combination of these. Therefore, by having the user terminal device 100-2 transmit the arbitrary identification information generated upon the start of such contact to the management device 300, it becomes possible to refer to the history information, etc. associated with the identification information (tracking information) in FIG. 4A.

[0070] If communication via a public line network is not possible, other identification information can be used instead of the arbitrary identification information. For example, link information for an online conference can be newly generated as information specific to the session and used as tracking information. Accessing the link starts the online conference, making it possible to refer to history information, etc. associated with the link (tracking information).

[0071] Instead of any identification information, it is also possible to use an email address or social media account generated as information specific to the session. By contacting the email address or social media account assigned as tracking information, it becomes possible to refer to the associated history information.

[0072] As described above, when tracking information is generated by the processing of S114 or S115, the generated tracking information is stored in the tracking management table in association with the tracking ID information, and is also transmitted to the distribution device 200 via the communication interface 314. This ends the processing flow.

[0073] Returning to Figure 5 again, once the tracking information is generated, the processor 312 of the management device 300 transmits the tracking ID information generated at S112 of Figure 6A and the tracking information (T23) generated at S114 or S115 to the distribution device 200 via the communication interface.

[0074] The processor of the distribution device 200 generates web page information (S24) including the tracking information received for the web page (e.g., Advertisement A) requested in the browse request (T21). This web page information includes the tracking information received in T23 and a URL to be accessed, in addition to various contents constituting the web page of Advertisement A, which is the first web page. The processor of the distribution device 200 transmits the web page information (T24) and tracking ID information to the user terminal device 100-2 via the communication interface 214 as a browse response to the browse request.

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

[0076] 8A 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. Specifically, it is a diagram showing an example of the web page 10 displayed on the user terminal device 100-2 at S25 in FIG. 5. According to FIG. 8A, the web page 10 includes information related to advertisement A as content, and an icon 11 saying "Start contact" is displayed at the bottom as contact information.

[0077] The content of the contact information displayed varies depending on the type of tracking information generated in S23 of Fig. 5. For example, if a telephone number assigned to a session accessing the web page is used as the tracking information, an icon directly displaying the telephone number may be displayed as the contact information. If any identification information generated for tracking is used as the tracking information, an icon 11 for launching a contact application program, as in web page 10, may be displayed as the contact information, rather than directly displaying the identification number (in this case, contact is made by, for example, email, voice or text chat using an SNS, online conference, or a combination thereof). If a link for an online conference assigned to a session accessing the web page is used as the tracking information, an icon for accessing the link may be displayed as the contact information.

[0078] Returning to FIG. 15, when the processor of user terminal device 100-2 receives an operation input to the contact information by the user via the input interface (S26), it extracts the history information included in user terminal device 100-2 (S27).

[0079] The historical information typically includes a search history including search words entered by the user and search results, as well as an 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 stored in a cart on an e-commerce site, input information entered within a web page, user account information used on the web page, or a combination of these. That is, although not specifically illustrated, when a user accesses another web page within a domain containing a website, the access history is stored as historical information. Furthermore, when a user clicks on a specific icon or watches a video on an accessed web page, the access history indicating these actions is stored as historical information. Furthermore, when a user adds a service or product to a cart or favorites on an accessed web page, information such as the service name and product name is stored as historical information. Furthermore, personal information of the user entered on an accessed web page is stored as historical information. Furthermore, user account information used on an accessed web page (e.g., user ID information used as an account provided on the web page, user ID information used as an account with a provider that provides a browser application, etc.) is stored as historical information. Therefore, the processor of the user terminal device 100-2 extracts the various types of information exemplified above as history information.

[0080] Here, as described above, the history information includes information called first-party data collected by measurement tags issued from the domain of the site accessed by the user and identifiers (e.g., cookies) assigned by the measurement tags, and third-party data collected by measurement tags issued from third parties (i.e., domains other than the site accessed by the user) and identifiers (e.g., cookies) assigned by the measurement tags. However, from the viewpoint of security and personal information, particularly with regard to measurement tags issued by third parties used to collect third-party data and identifiers assigned by the measurement tags, storage in the browser or local memory of the user terminal device 100-2 may be restricted, thereby restricting the collection of third-party data.

[0081] FIG. 8B is a diagram showing an example of source code of a web page displayed on the user terminal device 100-2 in another embodiment of the present disclosure. According to FIG. 8B, in the case of the source code of the web page as shown in (a), " <script>···ファーストパーティ計測タグ···< / script> As shown in the example below, the measurement tag and history management information (e.g., identifier) ​​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 the measurement tag links the history management information to collect history information. In this way, measurement tags, etc. written directly within the html source code are identified as having been issued by a first party, and the collected history information is also treated as first-party data.

[0082] On the other hand, in (a), the source code of html contains " <script src=""https: / / サードパーティ計測タグ.js”">< / script>", measurement tags and the like are written as link information to JavaScript. Therefore, when the html file shown in (a) is loaded, the JavaScript at the linked destination, which specifies a domain other than the domain of the web page, is accessed, and history information is collected by linking it to history management information using the measurement tag at the linked destination. In this way, measurement tags and the like written at linked destinations specifying external domains are identified as having been issued by a third party, and the history information collected thereby is also treated as third-party data. Therefore, as mentioned above, access to linked destinations containing such measurement tags and identifiers issued by third parties may be restricted, and the collection of history information may be regulated.

[0083] Therefore, as shown in (b) of FIG. 8B, the web page generated in S24 in FIG. 5 is not executed by accessing a link destination of an external domain, but is written directly into the html source code and executed within the html file, even for measurement tags issued by third parties. Specifically, as shown in (b), " <script>···サードパーティ計測タグ···< / script> This means that even if a measurement tag issued by a third party is restricted from accessing links on external domains, it will be possible to collect history information using the measurement tag without being subject to such restrictions.

[0084] The processor of the user terminal device 100-2 loads, for example, web page information exemplified in (b) of Figures 8A and 8B in a browser application, thereby executing the measurement tag, issuing history management information (e.g., an identifier), and collecting a series of history information in association with the history management information.The processor of the user terminal device 100-2 then transmits the extracted history information (including the history management information (e.g., the identifier)) together with tracking ID information to the management device 300 via the communication interface.When the management device 300 receives the history information, it associates the received history information with the tracking ID information received together and stores the received history information in the tracking management table (S28).

[0085] Here, Fig. 6B is a diagram showing a processing flow of processing executed in the management device 300 according to an embodiment of the present disclosure. Specifically, Fig. 6B is a diagram showing a processing flow related to storing history information extracted by the processor 312 of the management device 300 in S28 of Fig. 5. 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.

[0086] As described in S11 and S27 of FIG. 5 and FIG. 8B, a tag (e.g., a measurement tag) is set on a website to collect history information such as access history. Therefore, when the user accesses the website for the first time, the tag setting allows the user terminal device 100-2 to extract history information stored in memory up to that point. As described above, the history information may include a search history including the search terms entered by the user and search results, an access history including the user's actions before accessing a specific webpage and the user's actions within the domain accessed by the user, information stored in a cart on an e-commerce site, input information entered on a webpage, user account information used on a webpage, or a combination thereof. Once the history information is extracted, the processor of the user terminal device 100-2 transmits the history information to the management device 300 via a communication interface according to the tag setting.

[0087] 6B, the processor 312 of the management device 300 receives the history information and history management information (e.g., an identifier) ​​from the user terminal device 100-2 via the communication interface 314 (S211). Upon receiving this information, the processor 312 references the history information in the tracking management table and determines whether the history management information (e.g., an identifier) ​​is stored (S212). The history management information is identification information unique to the browser application that outputs the website to which the tag is set, and is used to centrally manage the history information when the website is accessed from the same browser application program. For example, an identifier such as the local IP address of the user terminal device 100-2 may be used as the history management information.

[0088] As described above, when the user terminal device 100-2 accesses the website for the first time, no history management information is stored in the history information of the tracking management table shown in Fig. 4A. Therefore, the result in S212 is "No," and the history management information (e.g., an identifier) ​​newly issued by the measurement tag in the user terminal device 100-2 is newly stored in the history information of the tracking management table (S213). Then, the processor 312 of the management device 300 transmits the generated history management information to the user terminal device 100-2 via the communication interface 314 (S214).

[0089] Although not shown, the processor of the user terminal device 100-2 that has received the history management information stores the received history management information in a memory for its own browser application.

[0090] Next, processor 312 of server device 300 identifies user ID information based on the history information and associates the history information and history management information (e.g., an identifier) ​​with the user ID information (the history management information is not shown in FIG. 4B). Specifically, as described above, the history information includes user account information used in the accessed web page (e.g., user ID information used as an account provided in the web page, user ID information used as an account with the provider that provides the browser application, etc.). Therefore, processor 312 refers to the user management table to identify user ID information that has information matching the account information included in the history information (S215). Then, when the user ID information is identified, processor 312 associates the history information and history management information with the user ID information.

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

[0092] Therefore, when processor 312 of management device 300 receives history management information together with history information in S211, it proceeds to the "Yes" branch at S212 because the history management information has already been stored, and proceeds to processing at S215. Specifically, processor 312 references the user management table based on the history management information received together with the history information, and identifies the user ID information associated with the history management information (S215). Then, processor 312 stores the history information in the user management table in association with the identified user ID information (S216). This ends the processing flow.

[0093] 6B, it is possible to accumulate not only the history information from the first access to a web page, but also the history information from successive accesses to the same web page. Therefore, it is possible to check, for example, whether the behavior on the web page has changed the second time the user accesses the page as a result of contact between the user and the provider at the first access.

[0094] 5, when the processor of the user terminal device 100-2 receives the operation input to the contact information in S26, it starts an application program associated with the contact information and starts contacting (T26) the management device 300. The contact ultimately transfers the service or product provider to an available provider terminal device, where detailed information is provided to the user, an application is made, and other processing is performed.

[0095] For example, in the web page 10 shown in FIG. 8A , if a phone number assigned to a session is included as tracking information and an icon for launching a calling application program is displayed together with the phone number as contact information, the calling application program is launched to initiate contact (call) using a public line network. Also, if any identification information assigned to a session is set as tracking information on the web page and an icon labeled "Start Contact" is displayed as contact information, an application program for email, voice or text chat using an SNS, or online conference is launched to initiate contact using an Internet line network (the any identification information is also transmitted along with the contact). Also, if a link for an online conference assigned to a session is set as tracking information on the web page and an icon labeled "Start Contact" is displayed as contact information, an application program for online conference is launched to initiate contact (online conference) using an Internet line network. Also, if a social networking service account assigned to a session is set as tracking information on the web page and an icon labeled "Start Contact" is displayed as contact information, an application program for voice or text chat using an SNS is launched to initiate contact (voice or text chat) using an Internet line network.

[0096] When a contact is initiated as described above, the contact is received once 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 tracking information and identifies the tracking ID information (S29). At this time, if a telephone number is used as the tracking information, the management device 300 identifies which tracking ID information it is by matching the incoming telephone number with the tracking information in the tracking management table. Similarly, if any identification information is used as the tracking information, the management device 300 identifies which tracking ID information it is by matching the any identification information received with the contact with the tracking information in the tracking management table. Furthermore, if a link to an online conference, a social media account, or an email address is used as the tracking information, the management device 300 identifies which tracking ID information it is by matching the online conference link, social media account, or email address received with the tracking information in the tracking management table.

[0097] When the tracking ID information is identified, the processor 312 of the management device 300 extracts history information associated with the tracking ID information from the tracking management table (S30). At this time, the history information includes the user's account information used in the accessed web page (e.g., user ID information used as an account provided in the web page, user ID information used as an account with the provider that provides the browser application, etc.). Therefore, the processor 312 of the management device 300 refers to the user management table to identify user ID information having information matching the account information and stores the identified user ID information in the tracking management table. In addition, the processor 312 of the management device 300 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. When the attribute information including the history information, personal information, etc. is extracted, the processor 312 transmits the attribute information to the provider terminal device 100-1 via the communication interface 314.

[0098] When the processor 312 of the management device 300 receives a contact from the user terminal device 100-2 as described above, it transfers the contact via the communication interface 314 to the provider terminal device 100-1, which is available to the provider who provides the web page related to the session (S31). When the contact is transferred to the provider terminal device 100-1, contact is initiated between the provider terminal device 100-1 and the user terminal device 100-2 (S32). Specifically, when a contact via a phone call is received, the processor 312 of the management device 300 transfers the call as is, and contact via a phone call is initiated between the provider terminal device 100-1 and the user terminal device 100-2. When a contact via an online conference is received, the processor 312 of the management device 300 transmits a participation notification for the online conference to the provider terminal device 100-1, and contact via an online conference is initiated between the provider terminal device 100-1 and the user terminal device 100-2. When contact by voice or text using an SNS account is accepted, the processor 312 of the management device 300 transfers the voice or text chat as is, and contact by voice or text chat is initiated between the provider terminal device 100-1 and the user terminal device 100-2. When contact by email is accepted, the processor 312 of the management device 300 transfers the email as is, and contact by email is initiated between the provider terminal device 100-1 and the user terminal device 100-2.

[0099] At this time, the provider terminal device 100-1 receives the attribute information extracted in S30 from the management device 300. Therefore, the provider using the provider terminal device 100-1 can contact the user while referring to the received attribute information, and can proceed with business negotiations, etc. more efficiently.

[0100] FIG. 7 is a diagram conceptually illustrating a communication process executed in an embodiment of the present disclosure. Specifically, FIG. 7 illustrates the communication process performed after S26 in FIG. 5 when a telephone number is used as tracking information among the contacts made between the user terminal device 100-2 and the provider terminal device 100-1. According to FIG. 7, a call application program is launched in the user terminal device 100-2, thereby initiating communication (contact) via a public line network with the telephone number as the destination. As an example, the communication utilizes a public line network such as LTE or 5G. Upon receiving the communication (contact), the management device 300 transfers the communication (contact) via the public line network to the provider terminal device 100-1 identified by the telephone number, as shown in FIG. 5.

[0101] At this time, the management device 300 first transfers the communication (contact) to a transfer server device installed between the management device 300 and the provider terminal device 100-1. The transfer server device stores a conversion table in which the telephone number of the provider terminal device 100-1 to be transferred is associated with the IP address of the provider terminal device 100-1. Therefore, when the transfer server device receives the transferred communication (contact), it refers to the conversion table based on one of the telephone numbers of the transfer destination and identifies the associated IP address. Based on the identified IP address, the transfer server device transfers the communication (contact) to the provider terminal device 100-1 using the Internet line network, which is a computer network using the Internet Protocol (IP).

[0102] One example of such transfer processing is a method called SIP trunking, but it can also be achieved by other methods.

[0103] Typically, a large number of provider terminal devices 100-1 are prepared because they are expected to process a large number of contacts. However, if all provider terminal devices 100-1 are allowed to communicate via a public line network, it may require high installation and maintenance costs, as well as complicated contract procedures. However, if each provider terminal device 100-1 communicates (contacts) via the Internet line network, the above costs and complicated procedures can be eliminated, and the system can be constructed more efficiently.

[0104] Returning to FIG. 5 again, the tracking process for providing attribute information is now complete.

[0105] As described above, in this embodiment, it is possible to provide a processing device, a processing program, and a processing method that are capable of appropriately processing contacts made by a user.

[0106] 6. Variations 1 to 8B, the management device 300 generates tracking information each time a new session is started and a tracking information request is received. However, instead of this, it is also possible to generate tracking information in advance.

[0107] Fig. 9 is a diagram showing a processing sequence executed in the processing system 1000 according to an embodiment of the present disclosure. Specifically, Fig. 9 shows a processing sequence executed between the user terminal device 100-2, the distribution device 200, and the management device 300. Of these, S11-1 to S12-2 indicate setting processing for executing tracking processing on a web page, and S21 to S32 indicate tracking processing for providing attribute information to a provider terminal device by tracking. Note that, except for points specifically mentioned in Fig. 9, the processing sequence is the same as that of the processing system 1 in Fig. 5.

[0108] <Settings for tracking> 9, the processor 312 of the management device 300 configures the web page to execute the tracking process (S11-1). Specifically, the processor 312 of the management device 300 collects history information such as access history, and configures tags (e.g., measurement tags) for acquiring tracking information when a website is accessed and a session is started. These configurations are configured using programming languages ​​such as JavaScript (registered trademark) and HTML.

[0109] Next, the processor 312 of the management device 300 generates tracking information (S11-2). Unlike the case of FIG. 5, at this point, the management device 300 has not received terminal type information. Therefore, here, tracking information corresponding to any one terminal type may be generated, or multiple types of tracking information may be generated for each terminal type. As in the case of FIG. 5, the generated tracking information may include, for example, a tracking phone number, arbitrary tracking identification information, a tracking online conference link, a tracking email address, a tracking SNS account, or a combination of these. The processor of the management device 300 generates a large amount of the above tracking information so as to be able to handle cases where multiple user terminal devices 100-2 access the management device 300 and multiple sessions occur.

[0110] Once the tracking information is generated, the processor 312 of the management device 300 transmits a registration request (T11-1) for the settings and the generated tracking information to a web page stored in the distribution device 200 via the communication interface 314. The registration request includes information that identifies the website on which the tag is set.

[0111] When the processor of the distribution device 200 receives the registration request via the communication interface, it registers settings such as tags for the web page based on information that identifies the web page (S11-1).

[0112] In addition, the processor of the distribution device 200 uses the multiple pieces of tracking information received together with the registration request to generate multiple web pages including the tracking information for each piece of tracking information (S11-2). For example, if multiple phone numbers (e.g., 03-XXXX-XXX1, 03-XXXX-XXX2, 03-XXXX-XXX3, and 03-XXXX-XXX4) are received as tracking information, the processor of the distribution device 200 generates a web page in which 03-XXXX-XXX1 is included in the contact information, a web page in which 03-XXXX-XXX2 is included in the contact information, a web page in which 03-XXXX-XXX3 is included in the contact information, and a web page in which 03-XXXX-XXX4 is included in the contact information, and stores these in memory. This completes the setting process for executing the tracking process.

[0113] The process for generating the web pages in S12-2 may be executed by the processor 312 of the management device 300 after S11-2, and the generated web pages may then be transmitted to the distribution device 200.

[0114] Furthermore, when generating a large number of web pages as described above, it is possible to obtain as output information displaying each web page in which each tracking information is included in the contact information, for example, by inputting information on a reference web page and a large amount of tracking information into a trained large-scale language model and inputting a prompt to generate a web page corresponding to each tracking information.

[0115] <Tracking process to provide attribute information> 9, the processor of the user terminal device 100-2 accepts a user's input via the input interface and selects a desired advertisement or web page (e.g., an advertisement) from the display screen of the second web page (S21). When a web page containing a specific advertisement is selected in the browser application, the processor of the user terminal device 100-2 transmits a browse request (T21) for the selected web page to the distribution device 200 via the communication interface. The browse request includes a request for web page information for displaying the web page and terminal type information that identifies the type of the user terminal device 100-2. The terminal type information, for example, is information that identifies whether the user terminal device is a terminal capable of communication via a public line network, i.e., whether an application program for making calls using a telephone number is available. The series of processes up to the process of S21 are the same as those described in FIG. 5.

[0116] When the processor of the distribution device 200 receives the browsing request, it reads from memory web pages including tracking information corresponding to the received terminal type information, and selects one of the web pages (S22-1). Then, the processor of the distribution device 200 transmits the tracking information (T22-1) included in the selected web page to the management device 300 via the communication interface as the tracking information for that web page. When the management device 300 receives the tracking information, it generates new tracking ID information and stores the received tracking information in association with the tracking ID information in the tracking management table (S23-1).

[0117] The processor of distribution device 200 also transmits web page information (T24) for displaying the web page selected in S22-1 to user terminal device 100-2 via the communication interface. The processor of user terminal device 100-2 outputs a web page generated by the browser application to the display based on the web page information included in the received browsing response (S25). The subsequent processing is the same as in FIG. 5, and therefore description thereof will be omitted.

[0118] According to FIG. 9, by generating a web page including a large amount of tracking information in advance, it is possible to quickly process a viewing request received from the user terminal device 100-2.

[0119] The processes and procedures described herein may be implemented not only by those explicitly described in this disclosure, but also by software, hardware, or a combination thereof. Specifically, the processes and procedures described herein may be implemented by implementing logic corresponding to the processes in media such as integrated circuits, volatile memory, nonvolatile memory, magnetic disks, and optical storage. Furthermore, the processes and procedures described herein may be implemented as computer programs and executed by various computers, including terminal devices and server devices.

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

[0121] 100-1 Provider terminal device 100-2 User terminal device 200 Distribution Device 300 Management device

Claims

1. A processing device comprising at least one processor, The at least one processor: In a web page including contact information for contacting a provider of a service or product, attribute information indicating an attribute of the user is acquired in response to a user's operation input on the contact information, in association with tracking information capable of identifying an access by the user to the web page; When the contact is received from a user terminal device available to the user, the attribute information associated with the tracking information is provided to a provider terminal device available to the provider, and the contact is transferred to the provider terminal device. a processing device configured to perform processing for:

2. The processing device according to claim 1 , wherein the attribute information includes a history of accesses to the web page by the user.

3. The processing device according to claim 2 , wherein the web page is a landing page that introduces the service or product.

4. the contact is accepted from the user terminal device via a public line network; The transfer is performed to the provider terminal device via an internet network. The processing device of claim 1 .

5. The processing device according to claim 1 , wherein the transfer to the provider terminal device is performed by SIP trunking.

6. The processing device according to claim 1 , wherein the tracking information is information of a different type depending on the type of the user terminal device that outputs the web page.

7. The tracking information is a telephone number available for a public line if the user terminal device is capable of communication via a public line network, The tracking information is any identification information different from the telephone number when the user terminal device cannot communicate via a public line network. The processing device of claim 1 .

8. The processing device according to claim 1 , wherein the attribute information includes history information indicating an access history of the user to the web page or to a web page different from the web page.

9. A processing method executed by at least one processor in a computer having the at least one processor, comprising: a step of acquiring attribute information indicating attributes of a user in association with tracking information capable of identifying an access by the user to the web page in response to an operation input by the user to the contact information in a web page including contact information for contacting a provider of a service or product; receiving the contact from a user terminal device available to the user, providing the attribute information associated with the tracking information to a provider terminal device available to the provider, and transferring the contact to the provider terminal device; A processing method comprising:

10. In a computer having at least one processor, the at least one processor: In a web page including contact information for contacting a provider of a service or product, attribute information indicating an attribute of the user is acquired in response to a user's operation input on the contact information, in association with tracking information capable of identifying an access by the user to the web page; When the contact is received from a user terminal device available to the user, the attribute information associated with the tracking information is provided to a provider terminal device available to the provider, and the contact is transferred to the provider terminal device. A program that functions to perform processing for a

Images