US 11,657,430 B2
Client caching identification tracking
Omar Tawakol, Los Altos, CA (US); David Abraham Wiener, San Francisco, CA (US); Fang Fang, Cupertino, CA (US); Jason Leon Walsh, Seattle, WA (US); Raja Bishara Daoud, San Jose, CA (US); and Jeffrey Charles Frantz, Dublin, CA (US)
Assigned to Oracle International Corporation, Redwood Shores, CA (US)
Filed by Blue Kai, Inc., Seattle, WA (US)
Filed on Nov. 5, 2019, as Appl. No. 16/674,926.
Application 16/674,926 is a continuation of application No. 13/918,132, filed on Jun. 14, 2013, granted, now 10,482,506.
Prior Publication US 2020/0065862 A1, Feb. 27, 2020
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 30/02 (2012.01); G06F 7/00 (2006.01); G06Q 30/0251 (2023.01)
CPC G06Q 30/0267 (2013.01) [G06F 7/00 (2013.01); G06Q 30/0269 (2013.01)] 20 Claims
OG exemplary drawing
 
7. A system, comprising:
one or more data processors; and
a non-transitory computer-readable storage medium containing instructions which, when executed on the one or more data processors, cause the one or more data processors to perform operations including:
defining a first data structure associated with a mobile application domain of a mobile application, the first data structure defined to store (i) a first statistical identifier representing a first client device and (ii) one or more first activity categories associated with the first statistical identifier;
defining a second data structure associated with a web browser domain of a web browser, the second data structure defined to store (i) a second statistical identifier representing a second client device and (ii) one or more second activity categories associated with the second statistical identifier;
generating a profile enrichment store that stores the first statistical identifier and the second statistical identifier, the profile enrichment store comprising:
a first set of fields corresponding to the first statistical identifier and the second statistical identifier; and
a second set of fields corresponding to the one or more first activity categories associated with the first statistical identifier and the one or more second activity categories associated with the second statistical identifier, the first set of fields and the second set of fields arranged in the profile enrichment store so as to associate the first statistical identifier with the one or more first activity categories and the second statistical identifier with the one or more second activity categories;
identifying a third client device configured to execute a web browser and the mobile application, the third client device being characterized by one or more network activity attributes of the third client device, the one or more network activity attributes (i) commonly retrievable by each of the web browser and the mobile application, and (ii) including a unique device identifier;
generating a third statistical identifier to represent the third client device, the third statistical identifier being generated using the one or more network activity attributes of the client device;
receiving, from the third client device, a first communication requesting first content data, the first communication originating from the mobile application executing on the third client device, the first communication being associated with the third statistical identifier;
storing, in the profile enrichment store, the third statistical identifier in the first set of fields;
receiving a first plurality of data packets corresponding to mobile application activity performed by the third client device;
tracking, by unpacking the first plurality of data packets to generate first unpacked data, the mobile application activity performed by the third client device executing the mobile application, the mobile application activity being tracked using the first unpacked data and the unique device identifier associated with the third client device, the tracking comprising storing mobile application activity data including the third statistical identifier and one or more third activity categories in the first data structure;
receiving, from the third client device, a second communication requesting second content data, the second communication originating from the web browser executing on the third client device, the second communication including a client caching identifier stored at a cache of the third client device, the client caching identifier being stored independent of a browser persistent identification mechanism, the second communication being associated with the third statistical identifier;
receiving a second plurality of data packets corresponding to web activity performed by the third client device;
tracking, by unpacking the second plurality of data packets to generate second unpacked data, the web activity performed by the third client device executing the web browser, the web activity being tracked using a combination of the client caching identifier included in the second communication, the second unpacked data, and the third statistical identifier associated with the third client device, the tracking comprising storing web browser activity data including the third statistical identifier and one or more fourth activity categories in the second data structure;
storing the one or more third activity categories and the one or more fourth activity categories in the second set of fields of the profile enrichment store such that the third statistical identifier is associated with the one or more third activity categories and the one or more fourth activity categories;
determining a link between the mobile application activity performed by the third client device and the web activity performed by the third client device, the link being determined by (i) matching the first statistical identifier, the second statistical identifier, and the third statistical identifier, (ii) matching the one or more first activity categories and the one or more third activity categories, and (iii) matching the one or more second activity categories and the one or more fourth activity categories, wherein the third statistical identifier is used as a bridge between the mobile application activity performed by the third client device and the web activity performed by the third client device; and
sending, to the third client device via the web browser and based on the link between the mobile application activity and the web activity, a content object associated with a particular activity category, the particular activity category being included in the one or more first activity categories and not included in the one or more second activity categories.