Setting a first-party user ID cookie on a web servers domain

• US 10,193,988 B2
• Filed: 11/06/2015
• Issued: 01/29/2019
• Est. Priority Date: 11/06/2015
• Status: Active Grant

• Current Assignee: Criteo Technology SAS (Criteo SA)
• Original Assignee: Criteo SA
• Inventors: Wyatt, Patrick, Roux, Cedric, Roggeri, Bruno
• Primary Examiner(s): Choudhury, Azizul
• Application Number:
  US14/934,637
• Publication Number:
  US 20170134512A1
• Time in Patent Office: 1,180 Days
• Field of Search: None
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display

Abstract

Methods and systems for setting first-party cookies are disclosed. A first request for a first webpage is sent by a user device to a first web server on a first domain. The first webpage includes first ad system call instructions. The first ad system call instructions are executed to send a second request to an ad system on a second domain to initiate determining a supply side platform (SSP) user ID. First SSP call instructions are received by the user device. The first SSP call instructions are executed to send a third request to an SSP server on a third domain. Second ad system call instructions including the SSP user ID are received by the user device. The second ad system call instructions are executed to send a fourth request comprising the SSP user ID to the ad system. First storing instructions for the SSP user ID are received.

Claims

1. A method performed by a user device, the method comprising:

sending, by the user device, to a first web server on a first domain, a first request for a first webpage;

receiving, by the user device, from the first web server, the first webpage comprising first ad system call instructions that include a target URL on a second domain;

determining, by the user device, whether a first browser cookie can be set on the first domain;

executing, by the user device, the first ad system call instructions to send a second request using the target URL on the second domain to an ad system on second domain, the second request comprising an indicator of whether the first browser cookie can be set on the first domain;

receiving, by the user device, from the ad system, first SSP call instructions that include a URL on a third domain, the target URL on the second domain, and the indicator of whether the first cookie can be set on the first domain;

executing, by the user device, the first SSP call instructions to send a third request using the URL on the third domain to an SSP server on the third domain, the third request comprising the target URL on the second domain, the SSP server determining an SSP user ID associated with the user device based upon the third request;

receiving, by the user device, from the SSP server, second ad system call instructions, the second ad system call instructions comprising the SSP user ID and the target URL on the second domain;

executing, by the user device, the second ad system call instructions using the target URL on the second domain to send a fourth request comprising the SSP user ID to the ad system;

receiving, by the user device, from the ad system, first storing instructions comprising the SSP user ID;

executing, by the user device, the first storing instructions to store the SSP user ID in the first browser cookie on the first domain.

2. The method of claim 1, wherein the third request comprises at least one of an SSP browser cookie comprising the SSP user ID and fingerprint data associated with the user device.

3. The method of claim 1, further comprising:

sending, by the user device, a first ad request for a first ad, the first ad request comprising the SSP user ID;

receiving, by the user device, a first ad comprising a target URL on the second domain;

in response to a user interaction with the first ad, sending, by the user device, a fifth request for a resource associated with the URL to the ad system on the second domain;

receiving, by the user device, from the ad system, second storing instructions comprising an ad system user ID associated with the SSP user ID;

executing, by the user device, the second storing instructions to store the ad system user ID in an ad system browser cookie associated with the second domain.

4. The method of claim 3, wherein the ad system browser cookie is a first-party browser cookie associated with the second domain.

5. The method of claim 3, further comprising:

sending, by the user device, to the first web server on the first domain, a sixth request for a second webpage;

receiving, by the user device, from the first web server, the second webpage comprising third ad system call instructions; and

executing, by the user device, the third ad system call instructions to send a seventh request to the ad system on the second domain, the seventh request comprising the ad system user ID.

6. The method of claim 1, further comprising:

sending, by the user device, to the first web server on the first domain, a fifth request for a second webpage;

receiving, by the user device, from the first web server, the second webpage comprising third ad system call instructions; and

executing, by the user device, the third ad system call instructions to send a sixth request to the ad system on the second domain, the sixth request comprising the SSP user ID.

7. A method performed by a computing system, the method comprising:

sending, by a user device, to a first web server on a first domain, a first request for a first webpage;

sending, by the first web server, to the user device, the first webpage comprising first ad system call instructions that include a target URL on a second domain;

determining, by the user device, whether a first browser cookie can be set on the first domain;

executing, by the user device, the first ad system call instructions to send a second request using the target URL on the second domain to an ad system on the second domain, the second request comprising an indicator of whether the first browser cookie can be set on the first domain;

determining, by the ad system, based on the second request, the user device does not store a pre-existing ad system user ID and does not store a pre-existing SSP user ID;

sending, by the ad system, to the user device, first SSP call instructions that include a URL on a third domain, the target URL on the second domain, and the indicator of whether the first browser cookie can be set on the first domain;

executing, by the user device, the first SSP call instructions to send a third request using the URL on the third domain to an SSP server on the third domain, the third request comprising the target URL on the second domain, the SSP server determining an SSP user ID associated with the user device based upon the third request;

sending, by the SSP server, to the user device, second ad system call instructions, the second ad system call instructions comprising the SSP user ID and the target URL on the second domain;

executing, by the user device, the second ad system call instructions using the target URL on the second domain to send a fourth request to the ad system, the fourth request comprising the SSP user ID;

determining, by the ad system, an ad system user ID associated with the SSP user ID;

sending, by the ad system, to the user device, storing instructions comprising the SSP user ID; and

executing, by the user device, the storing instructions to store the SSP user ID in the first browser cookie on the first domain.

8. The method of claim 7, wherein the third request comprises at least one of an SSP browser cookie comprising the SSP user ID and fingerprint data associated with the user device.

9. The method of claim 7, wherein determining, by the ad system, an ad system user ID comprises:

generating, by the ad system, an ad system user ID; and

associating, by the ad system, the ad system user ID with the SSP user ID.

10. The method of claim 7, wherein determining, by the ad system, an ad system user ID comprises:

retrieving, by the ad system, an associated ad system user ID associated with the SSP user ID.

11. The method of claim 7, wherein the fourth request further comprises one or more user behavior events, the method further comprising:

associating, by the ad system, the one or more user behavior events with the ad system user ID.

12. The method of claim 7, further comprising:

sending, by the user device, a first ad request for a first ad, the first ad request comprising the SSP user ID; and

receiving, by the user device, a first ad comprising a target URL on the second domain.

13. The method of claim 12, wherein the ad system selects the first ad based on a plurality of user behavior events associated with the ad system user ID.

14. The method of claim 12, further comprising:

in response to an interaction with the first ad, sending, by the user device, a fifth request for a resource associated with the URL to the ad system on the second domain;

receiving, by the user device, from the ad system, second storing instructions comprising an ad system user ID associated with the SSP user ID;

executing, by the user device, the second storing instructions to store the ad system user ID in an ad system browser cookie associated with the second domain.

15. The method of claim 14, wherein the ad system browser cookie is a first-party browser cookie associated with the second domain.

16. The method of claim 14, further comprising:

sending, by the user device, to the first web server on the first domain, a sixth request for a second webpage;

receiving, by the user device, from the first web server, the second webpage comprising third ad system call instructions;

executing, by the user device, the third ad system call instructions to send a seventh request to the ad system on the second domain, the seventh request comprising the ad system user ID; and

not sending, by the ad system, additional SSP call instructions in response to receiving the seventh request comprising the ad system user ID.

17. The method of claim 7, further comprising:

sending, by the user device, to the first web server on the first domain, a fifth request for a second webpage;

receiving, by the user device, from the first web server, the second webpage comprising third ad system call instructions;

executing, by the user device, the third ad system call instructions to send a sixth request to the ad system on the second domain, the sixth request comprising the SSP user ID; and

not sending, by the ad system, additional SSP call instructions in response to receiving the sixth request comprising the SSP user ID.

18. The method of claim 7, wherein determining, by the ad system, based on the second request, the user device does not store a pre-existing ad system user ID and does not store a pre-existing SSP user ID comprises:

determining the second request does not comprise a pre-existing ad system browser cookie; and

determining the second request does not comprise the pre-existing SSP user ID.