IP Library Granted Patent US 12,205,142
Granted Patent B2
US 12,205,142 · App. 17/814,580 · Granted Jan 21, 2025

Systems and methods for cross-browser advertising id synchronization

Inventor: Seth Mitchell Demsey (Dulles, VA)
Assignee: Yahoo Ad Tech LLC
G06Q30/0255G06Q30/0269G06Q30/0277
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,205,142
App. No.
17/814,580
Granted
Jan 21, 2025
Kind
B2
Abstract

Systems and methods are for identifying online advertisements to display to a user based on historical user data collected across the user's use of a plurality of Internet devices. One method includes receiving, over a network, a request for an advertisement to display at a first device of the user, the request including a unique identifier stored on the user's first device; accessing, in a database, a demographic or browsing history information generated from the user's use of a second device, the demographic or browsing history information being stored in the database in relation to the unique identifier; and identifying, based on the demographic or browsing history information, an advertisement to display at the user's first device. The demographic or browsing history information is synchronized based on the unique identifier being stored on the user's first device and the user's second device.

Claims (79)

1. A method of providing electronic content based on activity data associated with electronic devices, comprising:

creating a first data store on a first electronic device of a user, the first data store including activity data of the first electronic device and a unique user identifier associated with the user;

creating a second data store on a second electronic device of the user, the second data store including activity data of the second electronic device and the unique user identifier;

creating a remote data store configured to store activity data of the user using the unique user identifier;

synchronizing, using the unique user identifier, the first data store, the second data store, and the remote data store;

receiving a request from the second electronic device of the user for electronic content;

based on the synchronized second data store, providing the electronic content to the second electronic device of the user; and

updating the first data store based on a user-generated event on the second electronic device of the user.

2. The method of claim 1 , further comprising:

receiving a request for a graphical element from the first electronic device;

determining, based on the activity data in the first data store and/or the unique user identifier, the graphical element from a plurality of graphical elements; and

providing the graphical element to the first electronic device.

3. The method of claim 2 , wherein the graphical element comprises a digital advertisement.

4. The method of claim 1 , further comprising:

determining a user-generated event;

updating the first data store based on the user-generated event; and

synchronizing the first data store of the first electronic device and the second data store of the second electronic device by modifying activity data in the second data store on the second electronic device.

5. The method of claim 1 , wherein the first data store is a sandboxed storage system associated with a browser application.

6. The method of claim 1 , further comprising:

generating a first instance identifier associated with the first electronic device; and

associating the first instance identifier with the unique user identifier,

wherein the first instance identifier is associated with a sandboxed storage system, and the sandboxed storage system is associated with a browser application.

7. The method of claim 1 , further comprising:

generating a first instance identifier associated with the first electronic device; and

associating the first instance identifier with the unique user identifier,

wherein the first instance identifier is associated with a domain cookie storage system of a browser application.

8. A system for providing electronic content based on activity data associated with electronic devices, comprising:

at least one data storage device storing instructions; and

at least one processor configured to execute the instructions to perform operations comprising:

creating a first data store on a first electronic device of a user, the first data store including activity data of the first electronic device and a unique user identifier associated with the user;

creating a second data store on a second electronic device of the user, the second data store including activity data of the second electronic device and the unique user identifier;

creating a remote data store configured to store activity data of the user using the unique user identifier;

synchronizing, using the unique user identifier, the first data store, the second data store, and the remote data store;

receiving a request from the second electronic device of the user for electronic content;

based on the synchronized second data store, providing the electronic content to the second electronic device of the user; and

updating the first data store based on a user-generated event on the second electronic device of the user.

9. The system of claim 8 , wherein the operations further comprise:

receiving a request for a graphical element from the first electronic device;

determining, based on the activity data in the first data store and/or the unique user identifier, the graphical element from a plurality of graphical elements; and

providing the graphical element to the first electronic device.

10. The system of claim 9 , wherein the graphical element comprises a digital advertisement.

11. The system of claim 8 , wherein the operations further comprise:

determining a user-generated event;

updating the first data store based on the user-generated event; and

synchronizing the first data store of the first electronic device and the second data store of the second electronic device by modifying activity data in the second data store on the second electronic device.

12. The system of claim 8 , wherein the first data store is a sandboxed storage system associated with a browser application.

13. The system of claim 8 , wherein the operations further comprise:

generating a first instance identifier associated with the first electronic device; and

associating the first instance identifier with the unique user identifier, and

wherein the first instance identifier is associated with a sandboxed storage system, and the sandboxed storage system is associated with a browser application.

14. The system of claim 8 , wherein the operations further comprise:

generating a first instance identifier associated with the first electronic device; and

associating the first instance identifier with the unique user identifier, and

wherein the first instance identifier is associated with a domain cookie storage system of a browser application.

15. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations for providing electronic content based on activity data associated with electronic devices, the operations comprising:

creating a first data store on a first electronic device of a user, the first data store including activity data of the first electronic device, profile information of the user, and a unique user identifier associated with the user;

creating a second data store on a second electronic device of the user, the second data store including activity data of the second electronic device and the unique user identifier;

creating a remote data store configured to store activity data of the user using the unique user identifier;

synchronizing, using the unique user identifier, the first data store, the second data store, and the remote data store;

receiving a request from the second electronic device of the user for electronic content;

based on the synchronized second data store, providing the electronic content to the second electronic device of the user; and

updating the first data store based on a user-generated event on the second electronic device of the user.

16. The non-transitory computer-readable medium of claim 15 , wherein the operations further comprise:

receiving a request for a graphical element from the first electronic device;

determining, based on the activity data in the first data store and/or the unique user identifier, the graphical element from a plurality of graphical elements; and

providing the graphical element to the first electronic device.

17. The non-transitory computer-readable medium of claim 16 , wherein the graphical element comprises a digital advertisement.

18. The non-transitory computer-readable medium of claim 15 , the operations further comprising:

determining a user-generated event;

updating the first data store based on the user-generated event; and

synchronizing the first data store of the first electronic device and the second data store of the second electronic device by modifying activity data in the second data store on the second electronic device.

19. The non-transitory computer-readable medium of claim 15 , wherein the operations further comprise:

generating a first instance identifier associated with the first electronic device; and

associating the first instance identifier with the unique user identifier, and

wherein the first instance identifier is associated with a sandboxed storage system, and the sandboxed storage system is associated with a browser application.

20. The non-transitory computer-readable medium of claim 15 , wherein the operations further comprise:

generating a first instance identifier associated with the first electronic device; and

associating the first instance identifier with the unique user identifier, and

wherein the first instance identifier is associated with a domain cookie storage system of a browser application.

Assignments (5)
CHANGE OF NAME Recorded Feb 24, 2023
From: AOL ADVERTISING INC.
To: OATH (AMERICAS) INC.
Reel/Frame 062864/0449 →
CHANGE OF NAME Recorded Jan 23, 2023
From: AOL ADVERTISING INC.
To: OATH (AMERICAS) INC.
Reel/Frame 063753/0815 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 29, 2022
From: DEMSEY, SETH MITCHELL
To: AOL ADVERTISING INC.
Reel/Frame 060924/0519 →
CHANGE OF NAME Recorded Aug 29, 2022
From: OATH (AMERICAS) INC.
To: VERIZON MEDIA INC.
Reel/Frame 061354/0688 →
CHANGE OF NAME Recorded Aug 29, 2022
From: VERIZON MEDIA INC.
To: YAHOO AD TECH LLC
Reel/Frame 061354/0704 →
Continuity (4)
Continuation 15684604 · Aug 23, 2017
Continuation 14662755 · Mar 19, 2015
Continuation 13922379 · Jun 20, 2013
Related Publication 20220358541A1 · Nov 10, 2022
References Cited (58)
US 5924094A · Sutter · 1999 [cited by examiner]
US 6247135B1 · Feague · 2001 [cited by examiner]
US 6519571B1 · Guheen · 2003 [cited by examiner]
US 6643635B2 · Nwabueze · 2003 [cited by examiner]
US 6671705B1 · Duprey · 2003 [cited by examiner]
US 7266702B2 · Hotti · 2007 [cited by examiner]
US 7318133B2 · Yagawa · 2008 [cited by examiner]
US 7437601B1 · Manley · 2008 [cited by examiner]
US 7523148B2 · Suzuki · 2009 [cited by examiner]
US 7979463B2 · Durbin · 2011 [cited by examiner]
US 8001414B2 · Bensinger · 2011 [cited by examiner]
US 8176358B2 · Bensinger · 2012 [cited by examiner]
US 8296537B2 · Inoue · 2012 [cited by examiner]
US 8429128B2 · Muratov · 2013 [cited by examiner]
US 8504425B2 · Peterson · 2013 [cited by examiner]
US 8639966B2 · Bensinger · 2014 [cited by examiner]
US 9176823B2 · Bensinger · 2015 [cited by examiner]
US 10621203B2 · Hunt · 2020 [cited by examiner]
US 20030170012A1 · Cochran · 2003 [cited by examiner]
US 20030191916A1 · McBrearty · 2003 [cited by examiner]
US 20040064351A1 · Mikurak · 2004 [cited by examiner]
US 20040073831A1 · Yanai · 2004 [cited by examiner]
US 20040078569A1 · Hotti · 2004 [cited by examiner]
US 20040181539A1 · Munson · 2004 [cited by examiner]
US 20050050057A1 · Mital · 2005 [cited by examiner]
US 20050050199A1 · Mital · 2005 [cited by examiner]
US 20070067334A1 · Durbin · 2007 [cited by examiner]
US 20070077921A1 · Hayashi et al. · 2007 [cited by applicant]
US 20070101361A1 · Spielman · 2007 [cited by examiner]
US 20070220575A1 · Cooper et al. · 2007 [cited by applicant]
US 20070234108A1 · Cox · 2007 [cited by examiner]
US 20080189440A1 · Goyal · 2008 [cited by examiner]
US 20080235040A1 · Ratliff · 2008 [cited by examiner]
US 20080300980A1 · Benjamin · 2008 [cited by examiner]
US 20090006156A1 · Hunt · 2009 [cited by examiner]
US 20090018996A1 · Hunt · 2009 [cited by examiner]
US 20090182619A1 · Menditto et al. · 2009 [cited by applicant]
US 20110276396A1 · Rathod · 2011 [cited by examiner]
US 20120072731A1 · Winograd · 2012 [cited by examiner]
US 20120259710A1 · Peterson · 2012 [cited by examiner]
US 20130007208A1 · Tsui · 2013 [cited by examiner]
US 20130185750A1 · Ayoub · 2013 [cited by examiner]
US 20130219456A1 · Sharma · 2013 [cited by examiner]
US 20130238745A1 · Ramachandran · 2013 [cited by examiner]
US 20140032265A1 · Paprocki · 2014 [cited by examiner]
US 20140379482A1 · Demsey · 2014 [cited by examiner]
KR 20090113456A · 2009 [cited by examiner]
WO WO2005036472A1 · 2005 [cited by examiner]
WO WO2010093033A1 · 2010 [cited by examiner]
S. Agarwal et al. On the Scalability of Data Synchronization Protocols for PDAs and Mobile Devices (Jul. 15, 2001). Retrieved online Nov. 19, 2020. http://people.bu.edu/staro/pda_review.pdf (Year: 2001). [cited by examiner]
Oracle. Oracle Database Lite: Synchronizing Data Between a Device and an Oracle Database. (Aug. 2007). Retrieved online Oct. 20, 2021. https://www.oracle.com/technetwork/database/database-lite/olsync-131762.pdf (Year: 2… [cited by examiner]
Oracle. “Database Mobile Server Administration and Deployment Guide.” (Jan. 2, 2012). Retrieved online Feb. 11, 2022. https://docs.oracle.com/cd/E22663_01/doc.11100/e22678/admsync.htm#OLDEP006 (Year: 2012). [cited by examiner]
CISCO. Network Management System: Best Practices White Paper. (Jul. 11, 2007). Retrieved online Jun. 1, 2017. http://www.cisco.com/c/en/us/support/docs/availability/high-availability/15114-NMS-bestpractice.html. [cited by applicant]
International Preliminary Report on Patentability issued in corresponding International Application No. PCT/US2014/43252, dated Apr. 5, 2016 (5 pages). [cited by applicant]
International Search Report and Written Opinion issued in corresponding International Application No. PCT/US2014/43252, dated Mar. 3, 2016 (14 pages). [cited by applicant]
Oracle. “Database Mobile Server Administration and Deployment Guide.” (Jan. 2, 2012). Retrieved online Feb. 11, 2022. https://docs.oracle.com/cd/E22663_01/doc.11100/e22678/admsync.htm#OLDEP006. [cited by applicant]
Oracle. Oracle Database Lite: Synchronizing Data Between a Device and an Oracle Database. (Aug. 2007). Retrieved online Oct. 20, 2021. https://www.oracle.com/technetwork/database/database-lite/olsync-131762.pdf. [cited by applicant]
S. Agarwal et al. “On the Scalability of Data Synchronization Protocols for PDAs and Mobile Devices” (Jul. 15, 2001), 14 pgs. Retrieved online Nov. 19, 2020. http://people.bu.edu/staro/pda_review.pdf. [cited by applicant]