US 12,423,716 B2
Method, apparatus, and computer program product for consumer tracking
Jiaqi Guo, Chicago, IL (US); Michael Elizarov, Sammamish, WA (US); Jim Breen, Chicago, IL (US); and Selvam Velmurugan, Issaquah, WA (US)
Assigned to Bytedance Inc., Wilmington, DE (US)
Filed by Bytedance Inc., Wilmington, DE (US)
Filed on Aug. 31, 2022, as Appl. No. 17/900,148.
Application 17/900,148 is a continuation of application No. 16/875,138, filed on May 15, 2020, granted, now 11,468,454.
Application 16/875,138 is a continuation of application No. 16/051,955, filed on Aug. 1, 2018, granted, now 10,706,430, issued on Jul. 7, 2020.
Application 16/051,955 is a continuation of application No. 15/389,749, filed on Dec. 23, 2016, granted, now 10,068,240, issued on Sep. 4, 2018.
Application 15/389,749 is a continuation of application No. 14/039,473, filed on Sep. 27, 2013, granted, now 9,563,900, issued on Feb. 7, 2017.
Prior Publication US 2023/0118419 A1, Apr. 20, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 30/0601 (2023.01); G06F 16/23 (2019.01); G06Q 30/0201 (2023.01); H04L 43/106 (2022.01); H04L 67/146 (2022.01); H04L 67/303 (2022.01); H04L 67/50 (2022.01)
CPC G06Q 30/0201 (2013.01) [G06F 16/2322 (2019.01); G06Q 30/0601 (2013.01); H04L 43/106 (2013.01); H04L 67/146 (2013.01); H04L 67/303 (2013.01); H04L 67/535 (2022.05)] 20 Claims
OG exemplary drawing
 
1. An apparatus comprising at least one processor and at least one memory storing instructions that, with the at least one processor, cause the apparatus to:
receive, from a client device, a request comprising one or more tokens associated with the client device, wherein the request is based at least in part on electronic interactions performed by the client device with a user interface;
generate, based at least in part on the one or more tokens, a client device ID;
compare the client device ID to a plurality of known client device versions;
responsive to determining that the client device ID is not associated with any of the plurality of known client device versions, generate a new known client device version associated with the client device ID and client device profile data associated with the client device ID;
compare the client device ID to a plurality of known client device sessions;
responsive to determining that the client device ID is not associated with any of the plurality of known client device sessions, generate a new known client device session associated with the client device ID and the client device profile data associated with the client device ID;
assign the new known client device version as a latest known client device version for the client device ID; and
assign the new known client device session as a latest known client device session for the client device ID.