JP2022090213A - Contents contact history acquisition system and contents contact history acquisition method - Google Patents

Abstract

To manage a history of contacting, by the same terminal, contents of a plurality of sites, and to record the contact history and user information in associating with each other.SOLUTION: A contents contact history acquisition system comprises: a history collection server; and a user information management server which provides information on a user information checking page for associating terminal identification information of a user terminal with user identification information of a user. Upon browsing contents in the user terminal, the system transmits information which instructs to issue/record the terminal identification information from the user terminal to the history collection server identified in a DNS server based on a sub-domain. Upon accessing the user information checking page in the user terminal, the system transmits, to the history collection server identified based on the sub-domain in the DNS server, information which instructs to issue/record the terminal identification information of the user terminal, to check two pieces of terminal identification information, and to associate a history of contact to the contents, with the user identification information.SELECTED DRAWING: Figure 2

Description

The present invention relates to a content contact history acquisition system for investigating a contact situation with digital contents and digital advertisements, and a content contact history acquisition method.

In recent years, contact history with digital contents and digital advertisements has been collected and used for analysis of contact trends and measurement of advertising effectiveness.

For example, in Patent Document 1, when a website in which a tracking tag is embedded is displayed on a user terminal, a cookie ID is assigned to the user terminal, and the assigned cookie ID is used as an identifier to collect browsing history of the user terminal. Have been described.

Japanese Patent No. 6337332

However, in recent years, due to the growing interest in personal information protection, it is becoming difficult to acquire information that identifies a user's terminal and use it for investigation. In particular, with regard to third-party cookies, which are terminal identification information that can be used between multiple domains, it is possible to manage the contact history of the content of multiple sites by the same terminal, so it has been used for contact investigations of digital content in the past. It has been. In addition, if a third-party cookie issued by a research institution or the like is used, it is possible to link it with user information managed by the same research institution. However, it is expected that the use of third-party cookies will be restricted in the future.

Therefore, the present invention manages the contact history of the contents of a plurality of sites by the same terminal without imposing a burden on the user, and makes it possible to record the contact history and the user information in association with each other. With the goal.

The content contact history acquisition system according to the present invention manages a history collection server that acquires a contact history of the content to be investigated by the user terminal and a user's profile information, and manages the terminal identification information of the user terminal and the user. The user information management server that provides the information of the user information matching page for associating the user identification information of the above is provided, and the history collection server and the user information management server distribute the content to be investigated of the contact status. The content distribution server and the subdomain including the domain name of the content distribution server are connected to the DSN server, which defines the subdomain of the history collection server as an alias of the subdomain, via a communication line, and the content is connected to the subdomain. On the other hand, a first tag including information instructing to issue and / or record the terminal identification information of the user terminal that has come into contact with the content is set, and the URL of the user information matching page is the content. The user information matching page including the domain of the distribution server issues and / or records the terminal identification information to the user terminal for the subdomain, and links the user identification information to the terminal identification information. A second tag containing information instructing the user to record the tag is set, and when the first tag is activated by browsing the content on the user terminal, the DNS server is based on the subdomain. In response to the identification of the history collection server and transmission of the instruction information set in the first tag from the user terminal to the history collection server, the history collection server causes the user. When the second tag is activated by issuing and / or recording the terminal identification information of the user terminal to the terminal and accessing the user information matching page on the user terminal, the subdomain is activated on the DSN server. The history collection server is specified based on the above, and in response to transmission of the instruction information set in the second tag from the user terminal to the history collection server, the history collection server. Issuing and / or recording the terminal identification information of the user terminal to the user terminal, the terminal identification information recorded based on the first tag and the terminal recorded based on the second tag. By collating the identification information, the contact history with the content and the user identification information are linked. It is a thing.

The content contact history acquisition method according to the present invention is a content contact history acquisition method for acquiring a contact history of a content to be investigated by a user terminal by a history collection server, and the history collection server is a user profile. A user information management server that manages information and provides information on a user information matching page for associating the terminal identification information of the user terminal with the user identification information of the user, and distributes the content to be investigated for the contact status. The content distribution server and the DSN server that defines the subdomain including the domain name of the content distribution server as another name of the subdomain of the history collection server are connected via a communication line, and the content is connected to the subdomain. On the other hand, a first tag including information instructing to issue and / or record the terminal identification information of the user terminal that has come into contact with the content is set, and the URL of the user information matching page is the content. The user information matching page including the domain of the distribution server issues and / or records the terminal identification information to the user terminal for the subdomain, and links the user identification information to the terminal identification information. A second tag containing information instructing the user to record the tag is set, and when the first tag is activated by browsing the content on the user terminal, the DNS server is based on the subdomain. In response to the identification of the history collection server and transmission of the instruction information set in the first tag from the user terminal to the history collection server, the history collection server causes the user. When the second tag is activated by issuing and / or recording the terminal identification information of the user terminal to the terminal and accessing the user information matching page on the user terminal, the subdomain is activated on the DSN server. The history collection server is specified based on the above, and in response to transmission of the instruction information set in the second tag from the user terminal to the history collection server, the history collection server. Issuing and / or recording the terminal identification information of the user terminal to the user terminal, the terminal identification information recorded based on the first tag and the terminal recorded based on the second tag. By collating the identification information, the contact history with the content and the user identification information can be linked. It is something to do.

According to the present invention, it is possible to manage the contact history of the contents of a plurality of sites by the same terminal without imposing a burden on the user, and to record the contact history and the user information in association with each other.

The block diagram which shows the outline of the content contact history acquisition system 1 by embodiment of this invention. The flowchart of the content contact history acquisition processing by embodiment of this invention. The schematic diagram explaining the content contact history acquisition process by embodiment of this invention. A flowchart of a process of associating contact history data with contents and user profile information according to an embodiment of the present invention. The figure explaining the structure of the user information matching page by embodiment of this invention.

Next, a mode for carrying out the present invention will be described in detail with reference to the drawings.
Embodiment FIG. 1 is a block diagram showing an outline of a content contact history acquisition system 1 according to an embodiment of the present invention. As shown in FIG. 1, the content contact history acquisition system 1 includes a content distribution server 10, a history collection server 20, a first DNS (Domain Name System) server 30, a second DNS (Domain Name System) server 40, and a user. It includes an information management server 50 and a user terminal 60. The content distribution server 10, the history collection server 20, the first DSN server 30, the second DSN server 40, the user information management server 50, and the user terminal 60 are connected via a communication network. Communication networks are wired or wireless networks, such as the Internet, LAN, dedicated lines, telephone lines, corporate networks, mobile communication networks, Bluetooth®, WiFi (Wireless Fidelity), other communication lines, and combinations thereof. Etc. are included.

The content contact history acquisition system 1 acquires the contact history from the user terminal 60 to the digital content whose contact status is to be measured, analyzes the content contacted by the same user terminal 60, and analyzes the content contacted by the same user terminal 60. Analyze the composition (gender ratio, age group, etc.).

The content distribution server 10 is a server such as a video distribution site that distributes the content to be measured. The content distribution server 10 is configured by a general-purpose computer, and realizes a server function by operating a predetermined server program on the computer. The content distribution server 10 includes a control device 11 and a storage device 12. The control device 11 includes, as hardware, a CPU, a memory such as a ROM or a RAM, an input interface, an output interface, a communication interface, and the like. The control device 11 realizes various functions by the CPU executing a program stored in a ROM or the like. The storage device 12 is a hard disk drive or the like, and content data or the like is recorded.

The history collection server 20 is a server that records a content contact history including cookie information (terminal identification information) received from a user terminal 60 that has viewed the target content as contact history data for the content to be measured. The history collection server 20 is configured by a general-purpose computer, and realizes a server function by operating a predetermined server program on the computer. The history collection server 20 includes a control device 21 and a storage device 22.

The control device 21 includes, as hardware, a CPU, a memory such as a ROM or a RAM, an input interface, an output interface, a communication interface, and the like. The control device 21 realizes various functions by the CPU executing a program stored in a ROM or the like.

The storage device 22 is a hard disk drive or the like, and records the content contact history including the cookie information (terminal identification information) issued to the user terminal 60 that has contacted the content as the content contact history data. Further, the cookie information (terminal identification information) and the user ID (user identification information) issued to the user terminal 60 that has accessed the user information matching page are recorded.

The first DSN server 30 and the second DSN server 40 are servers having a name resolution function on a communication network, and convert a designated domain name into an IP address. The first DSN server 30 is a DSN server that manages the domain of the content distribution server 10, and the second DSN server 40 is a DSN server that manages the domain of the history collection server 10.

The user information management server 50 manages the user ID and profile information (gender, age, residential area, e-mail address, etc.) of the user registered as a monitor, and causes the user terminal 60 to access the user information matching page. , A server that links contact history data to content with user profile information. The user information management server 50 is managed by, for example, a trader who manages the history collection server 20. The user information management server 50 is configured by a general-purpose computer, and realizes a server function by operating a predetermined server program on the computer. The user information management server 50 includes a control device 51 and a storage device 52. The control device 51 includes, as hardware, a CPU, a memory such as a ROM or a RAM, an input interface, an output interface, a communication interface, and the like. The storage device 52 is a hard disk drive or the like, and stores a user ID, profile information, and the like.

The user terminal 60 is a terminal such as a smartphone, a mobile phone, a tablet terminal, a personal computer (PC), a notebook PC, a wearable device, or a personal digital assistant (PDA) owned by the user. The user terminal 60 includes a processor, a keyboard and a mouse, an input device such as an operation button and a touch panel, a display device such as a liquid crystal display, a communication interface, and a storage device such as a disk drive or a semiconductor memory (ROM, RAM, etc.). The storage device stores a computer program executed by the processor.

Next, the flow of content contact history acquisition by the content contact history acquisition system 1 will be described with reference to the flowchart of FIG. 2 and the schematic diagram of FIG. Here, a history acquisition when the user terminal 60 accesses the video distribution site ABC provided by the content distribution server 10 and comes into contact with the video content C will be described as an example. The domain name of the content distribution server 10 is "abc.com".

A measurement tag T (first tag) is embedded in the content C. The measurement tag T describes a process of instructing the subdomain "sub.abc.com" of the domain "abc.com" to issue and record the cookie information to the user terminal 60. ..

First, when the user operates the user terminal 60 to access the video distribution site ABC and browse the content C (step S101), the measurement tag T embedded in the content C is activated (step S102).

When the measurement tag T is activated, access to the subdomain "sub.abc.com" is started from the user terminal 60, and the name resolution of the subdomain "sub.abc.com" (IP address) is performed on the first DSN server 30. Acquisition) is executed (step S103). The first DSN server 30 stores the CNAME setting of "sub.abc.com", and specifically, for example, a record having the content of "sub.abc.com IN CNAME tag.xyz.com". It is remembered. This record shows that "sub.abc.com" is a nickname for "tag.xyz.com", and the IP address of "sub.abc.com" is actually the subdomain "tag.xyz". It indicates that it is an IP address of ".com". "Tag.xyz.com" is the host name of the history collection server 20.

Name resolution (acquisition of IP address) of the subdomain "tag.xyz.com" is executed on the second DSN server 40. When the name resolution of the subdomain "tag.xyz.com" is executed, the history collection server 20 is specified in the second DSN server 40 based on the subdomain "tag.xyz.com", and the history collection server 20 is specified from the user terminal 60. The instruction information set in the measurement tag T is transmitted to the history collection server 20, and in response, the history collection server 20 issues terminal identification information to the user terminal 60 and / or contacts the content C. The terminal identification information is recorded as historical data. Further, the history collection server 20 transmits the content contact history data including the cookie information to the user terminal 60 (step S104). Specifically, when the user terminal 60 contacts the content C for the first time, the history collection server 20 issues terminal identification information (actually, browser identification information) for identifying the user terminal 60. Then, the terminal identification information (cookie information) and the content contact information (date and time, content identification information, etc.) are transmitted to the user terminal 60. Further, in the case of the second and subsequent contacts, the user terminal 60 provides the history collection server 20 with the terminal identification information stored in the user terminal 60, and the history collection server 20 provides the terminal identification information and the content contact information. The content contact history including and is transmitted to the user terminal 60.

The user terminal 60 saves the content contact history including the received cookie information, and sends a copy of the saved information to the history collection server 20 (step S105).

The history collection server 20 stores the content contact history including the cookie information received from the user terminal 60 in the storage device 22 (step S106).

Here, if the cookie information transmitted to the user terminal 60 is managed as if it was issued from the history collection server 20, it is a cookie from a domain different from the content distribution server 10 being accessed to display the content C. Therefore, it is recognized as a third-party cookie. However, in this embodiment, the cookie is recognized as a first-party cookie because it is managed as a cookie issued from the subdomain "sub.abc.com" of "abc.com". That is, since the third-party cookie actually issued by the history collection server 20 by using the CNAME setting is a cookie issued by accessing "sub.abc.com", the content distribution server 10 It is treated as a first party cookie issued from the domain of.

That is, every time the user contacts the content C from the user terminal 60, the measurement tag embedded in the content C is activated, and the contact history data in which the user terminal 60 (browser) is identified by the first-party cookie is the history collection server 20. Accumulate in.

Next, a mechanism for associating the contact history data with the content with the profile information of the user will be described using the flowchart of FIG.

The user information management server 50 periodically sends an e-mail urging access to the user information matching page to the user terminal 60 of the user whose user ID is registered (step S201). The e-mail contains a URL for the user to access and a sentence for urging the user to access the URL. The URL corresponds to a subdomain containing the domain name of the site that distributes the content (for example, the subdomain "sub.abc.com" including the domain name "abc.com" of the distribution site ABC). The user ID of the user is added to the URL as a URL parameter (for example, information described after "?" At the end of the URL). Specifically, for example, if the user ID is "U123", the URL of the user information matching page can be "sub.abc.com? Id = U123".

When the user accesses the URL described in the mail from the user terminal 60 (step S202), the access to the URL "sub.abc.com? Id = U123" is started from the user terminal 60, and the first DSN server At 30, name resolution (acquisition of IP address) of "sub.abc.com" is executed. As described above, the first DNS server 30 stores the CNAME setting of "sub.abc.com" ("sub.abc.com IN CNAME tag.xyz.com"), and "sub.abc. The IP address of "com" indicates that it is actually the IP address of the subdomain "tag.xyz.com". Further, the name resolution of "tag.xyz.com" is executed in the second DSN server 40, and the history collection server 20 is specified. As a result, the user information matching page constructed in the history collection server 20 is displayed on the user terminal 60 (step S203).

The user information matching page is built in the history collection server 20, but when viewed from the user who accessed the described URL (here, "sub.abc.com? Id = U123"), the content is delivered. The domain of the site. A second tag is embedded in the user information matching page. The second tag describes a process of instructing the subdomain "sub.abc.com" to issue and record the cookie information to the user terminal 60. As described above, the first DSN server 30 stores a CNAME setting of "sub.abc.com", that is, a record having the content of "sub.abc.com IN CNAME tag.xyz.com". That is, "sub.abc.com" is a nickname for "tag.xyz.com", and the IP address of "sub.abc.com" is actually the subdomain "tag.xyz.com". It indicates that it is an IP address of. "Tag.xyz.com" is the domain name of the history collection server 20.

The configuration of the user information matching page will be described in detail with reference to the flowchart of FIG. 4 and FIG. As shown in FIG. 5, when the URL described in the mail is accessed from the user terminal 60, the user information matching page P1 of the first distribution site ABC is first displayed. When the user information matching page P1 is displayed, the second tag (tag T1) embedded in the user information matching page P1 is activated, and the same mechanism as when browsing the survey target content C of the distribution site ABC is used. A cookie issued corresponding to the domain of the distribution site ABC (a cookie issued by the history collection server 20) is transmitted to the user terminal 60 (step S204). That is, the history collection server 20 is specified based on the subdomain "sub.abc.com", and the user terminal 60 responds to the transmission of the instruction information set in the second tag to the history collection server 20. Then, the history collection server 20 issues the cookie information to the user terminal 60. Further, when the content is browsed, the content contact information (date and time, content identification information, etc.) is issued together with the terminal identification information (cookie information) as the content contact history, but the content contact information is displayed on the user information matching page. Instead of, the user ID of the user set as the URL parameter is issued together with the terminal identification information. The terminal identification information issued based on the second tag and the terminal identification information issued based on the first tag are both subdomains of the same domain (for example, "abc.com") (for example, Since the issuance is instructed to "sub.abc.com"), the same terminal identification information is issued. In the present embodiment, the first tag and the second tag instruct the same subdomain to issue a cookie, but these are different subdomains belonging to the same domain (for example, "sub1." It may be "abc.com" and "sub2.abc.com"). Also in this case, since both subdomains are subdomains of the same domain, the same terminal identification information is issued.

The user terminal 60 stores the received cookie information and transmits the history including the cookie information and the user ID to the history collection server 20 (step S205). The history collection server 20 stores the cookie information received from the user terminal 60 in the storage device 22 (step S206).

Further, if a certain time (for example, 10 seconds) has elapsed since the user information matching page P1 was accessed, the user information matching page (second user information matching page) of the next site is registered (if it is registered (second user information matching page). Step S207: YES), redirects to the user information matching page of the next site (in the example of FIG. 5, the user information matching page P2 of the distribution site DEF) based on the setting of the history collection server 20 (step S208). The URL corresponds to a subdomain containing the domain name of the distribution site DEF (for example, the subdomain "sub.def.com" (second subdomain) containing the domain name "def.com" of the distribution site DEF). There is. Further, as in the case of the first user information matching page, the user ID of the user is added to the URL as a URL parameter. For example, the URL of the second user information matching page is "sub.def.com? Id = U123". Also on the second user information matching page (user information matching page P2), a tag (third tag) instructing the subdomain "sub.def.com" to issue a cookie to the user terminal 60 is activated. Then, a history including the terminal identification information and the user ID is issued. In this way, the pages of the distribution sites included in the user information matching page are sequentially redirected, and when each page is accessed, the cookie corresponding to each distribution site is issued. When the redirect to the pages of all distribution sites is completed (step S207: NO), the completion page is displayed (step S209).

The history collection server 20 accesses the content contact history including the first party cookie (terminal identification information) and content contact information of each site recorded when the survey target content is browsed from the user terminal 60, and the user information matching page. The history including the first party cookie (terminal identification information) and the user ID recorded at the time of the operation is recorded. Since the terminal identification information that identifies the user terminal 60 is common to each site, it is possible to link the contact history with the content and the user ID by collating with the terminal identification information. As a result, the contact history with the content can be associated with the profile information of the user recorded in the user information management server 50.

Of the contact history data recorded in the history collection server 20, the data that can be associated with the user ID is analyzed for the gender ratio, age-specific composition ratio, etc. using the user profile, and the entire contact history data is obtained. The tendency of can be estimated.

Further, in the present embodiment, the terminal identification information corresponding to the same user (user terminal 60) differs depending on the site, but by using the user information matching page, the contact history by the same user can be summarized. Explaining using a specific example, the terminal identification information (cookie ID) issued to the user terminal 60 of the user U1 corresponding to the distribution site ABC is "111", and the terminal issued corresponding to the distribution site DEF. Assuming that the identification information is "222" and the terminal identification information issued corresponding to the distribution site GHI is "333", the history data including these cookie IDs is by the same user only in the contact history data to the contents. I don't know. On the other hand, when the user U1 accesses the user information matching page, each cookie ID is associated with the user ID of the user U1, so that it can be specified that any contact history is due to the user U1.

As described above, according to the present embodiment, the content to be investigated distributed by the content distribution server 10 includes the subdomain including the domain name of the content distribution server 10 to the user terminal 60 that has come into contact with the content. A first tag is set to instruct to issue the cookie information and record the content contact history including the issued cookie information (terminal identification information). Further, in the first DSN server 30, the history collection server 20 is defined as another name for the subdomain including the domain name of the content distribution server 10. When the history collection server 20 cooperates with the content distribution server 10 and the first DSN server 30, the first-party cookie issued from the history collection server 20 is actually issued from the domain of the content distribution server 10. Since it is treated as a party cookie, it is possible to manage the contact history using the conventional third party cookie even on a site where the use of the third party cookie is restricted. According to this embodiment, at each site that distributes the content to be surveyed, it is only necessary to set the measurement tag and register the CNAME setting of the domain in the site in the DSN server, so that it is very small. It only costs a burden.

In addition, by having the user terminal 60 access the user information matching page, it is possible to record the user information in association with the first-party cookie issued from the domain of each distribution site. This makes it possible to estimate the tendency of all contact history data (male / female ratio, age ratio, etc.) and specify the contact history of the same user to a plurality of sites. Also, even if the number of target sites increases, it can be easily dealt with by increasing the number of pages to be redirected. Since the user information matching page may be constructed by a research company or the like that manages the history collection server 20, the site that distributes the content to be surveyed is not burdened. In the present embodiment, the user ID is transmitted to the history collection server 20 by adding the user ID as a URL parameter to the URL of the user information matching page, but this is the method for acquiring the user ID. Not limited to. For example, the site of the user information matching page may be logged in using the user ID, and the second tag may be activated during the login to acquire the user ID.

The present invention is not limited to the above-described embodiment, and can be implemented in various other forms without departing from the gist of the present invention. For this reason, the above embodiments are merely examples in all respects and are not to be construed in a limited manner. For example, the above-mentioned processing steps can be arbitrarily changed in order or executed in parallel within a range that does not cause a contradiction in the processing contents. Further, another step may be added between each processing step. Further, the step described as one step may be executed by dividing it into a plurality of steps, or the step described by dividing it into a plurality of steps may be grasped as one step.

1 ... Content contact history acquisition system 10 ... Content distribution server 11 ... Control device 12 ... Storage device 20 ... History collection server 21 ... Control device 22 ... Storage device 30 ... First DSN server 40 ... Second DSN server 50 ... User Information management server 51 ... Control device 52 ... Storage device 60 ... User terminal

Claims (5)

A history collection server that acquires the contact history of the content to be investigated by the user terminal, and
It is provided with a user information management server that manages user profile information and provides information on a user information matching page for associating the terminal identification information of the user terminal with the user identification information of the user.
The history collection server and the user information management server define a content distribution server that distributes content to be investigated for contact status and a subdomain including the domain name of the content distribution server as another name for the subdomain of the history collection server. Connected to the DNS server via a communication line,
The content is set with a first tag containing information instructing the subdomain to issue and / or record terminal identification information of a user terminal that has come into contact with the content.
The URL of the user information matching page includes the domain of the content distribution server, and the user information matching page issues and / or records terminal identification information to the user terminal for the subdomain. , A second tag including information instructing to record the user identification information in association with the terminal identification information is set.
When the first tag is activated by browsing the content on the user terminal, the history collection server is specified on the DNS server based on the subdomain, and the history collection server is notified from the user terminal to the history collection server. In response to the transmission of the instruction information set in the tag 1, the history collection server issues and / or records the terminal identification information of the user terminal to the user terminal.
When the second tag is activated by accessing the user information matching page in the user terminal, the history collection server is specified in the DNS server based on the subdomain, and the history collection server is specified from the user terminal. In response to the transmission of the instruction information set in the second tag, the history collection server issues and / or records the terminal identification information of the user terminal to the user terminal. Do,
By collating the terminal identification information recorded based on the first tag with the terminal identification information recorded based on the second tag, the contact history with the content and the user identification information are linked. I do,
Content contact history acquisition system. When a certain period of time has elapsed after accessing the user information matching page on the user terminal, the user is redirected to the second user information matching page.
The URL of the second user information matching page includes the domain of the second content distribution server that distributes the content to be investigated, and the second user information matching page includes the domain of the second content distribution server. A third tag containing information instructing the user terminal to issue and / or record the terminal identification information is set for the second subdomain including.
The first aspect of claim 1, wherein the history collection server and the user information management server are connected to a DSN server that defines the second subdomain as another name for the subdomain of the history collection server via a communication line. Content contact history acquisition system. The terminal identification information is
The content contact history acquisition system according to claim 1 or 2, which is a cookie corresponding to the domain of the site being accessed by the user terminal. The user information management server is
The content contact history acquisition system according to any one of claims 1 to 3, which periodically notifies the user terminal of the URL of the user information matching page. It is a content contact history acquisition method that acquires the contact history of the content to be investigated by the user terminal by the history collection server.
The history collection server is
A user information management server that manages user profile information and provides information on a user information matching page for associating the terminal identification information of the user terminal with the user identification information of the user, and content to be investigated for contact status. Is connected to the content distribution server that distributes the information and the DSN server that defines the subdomain including the domain name of the content distribution server as another name for the subdomain of the history collection server via a communication line.
The content is set with a first tag containing information instructing the subdomain to issue and / or record terminal identification information of a user terminal that has come into contact with the content.
The URL of the user information matching page includes the domain of the content distribution server, and the user information matching page issues and / or records terminal identification information to the user terminal for the subdomain. , A second tag including information instructing to record the user identification information in association with the terminal identification information is set.
When the first tag is activated by browsing the content on the user terminal, the history collection server is specified on the DNS server based on the subdomain, and the history collection server is notified from the user terminal to the history collection server. In response to the transmission of the instruction information set in the tag 1, the history collection server issues and / or records the terminal identification information of the user terminal to the user terminal.
When the second tag is activated by accessing the user information matching page in the user terminal, the history collection server is specified in the DNS server based on the subdomain, and the history collection server is specified from the user terminal. In response to the transmission of the instruction information set in the second tag, the history collection server issues and / or records the terminal identification information of the user terminal to the user terminal. Do,
By collating the terminal identification information recorded based on the first tag with the terminal identification information recorded based on the second tag, the contact history with the content and the user identification information are linked. I do,
Content contact history acquisition method.

Images