IP Library Granted Patent US 9,553,918
Granted Patent B1
US 9,553,918 · App. 14/976,859 · Granted Jan 24, 2017

Stateful and stateless cookie operations servers

Inventors: Joshua R. Manion (Los Altos, CA); Joshua C. Goodwin (Mountain View, CA); Sam Jackson (San Francisco, CA); Chris Zakharoff (San Jose, CA)
Assignee: Ensighten, Inc.
H04L67/06G06F17/30G06F17/30017G06F17/30861H04L29/06476H04L29/06482H04L29/08756H04L67/02H04L67/2823
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 9,553,918
App. No.
14/976,859
Granted
Jan 24, 2017
Kind
B1
Abstract

A stateful or stateless cookie operations server machine can provide real-time, actionable, user-specific tracking abilities in the collection of impressions and user interactions with a company's digital properties. The client-side code (e.g., in a web browser) may request an element configured with parameters and a hyperlink (e.g., URL) that causes parameters to be sent to a remote server. The remote server may process the parameters and perform various operations based on the parameters. Mathematical and/or other operations may be performed using the parameters. The remote server may retrieve a configuration corresponding to the request. The remote server may generate or transform content, based on the configuration. The remote server may transmit the transformed content.

Claims (39)

1. A cookie operations server machine, comprising:

at least one processor; and

at least one memory storing computer-executable instructions that, when executed by the at least one processor, cause the cookie operations server machine to:

receive a request for web content;

parse the request for the web content to identify, based on a Uniform Resource Identifier (URI) in the request, a configuration corresponding to the web content;

retrieve the configuration;

retrieve the web content;

transform, based on the configuration, the web content; and

transmit the web content.

2. The cookie operations server machine of claim 1 , wherein the web content comprises an image, video, audio, text, Hyper Text Markup Language (HTML), or JavaScript.

3. The cookie operations server machine of claim 1 , wherein the configuration comprises instructions to perform one or more transformations on the web content.

4. The cookie operations server machine of claim 1 , wherein the configuration comprises a reference to a second configuration.

5. The cookie operations server machine of claim 1 , wherein the instructions that cause the cookie operations server machine to parse the request for the web content comprise instructions that cause the cookie operations server machine to resolve a token.

6. The cookie operations server machine of claim 1 , wherein the instructions that cause the cookie operations server machine to parse the request for the web content comprise instructions that cause the cookie operations server machine to:

identify a token in the request for the web content;

determine a replacement value for the token; and

replace the token with the replacement value.

7. The cookie operations server machine of claim 6 , wherein the instructions further cause the cookie operations server machine to record the request for the web content, in a log, after the token has been replaced with the replacement value.

8. A cookie operations server machine, comprising:

at least one processor; and

at least one memory storing computer-executable instructions that, when executed by the at least one processor, cause the cookie operations server machine to:

receive, from a client device, an HTTP GET message corresponding to first JavaScript, wherein the HTTP GET message comprises a parameter indicating at least one transformation;

retrieve the first JavaScript;

perform the at least one transformation on the first JavaScript, thereby generating second JavaScript; and

transmit, to the client device, the second JavaScript.

9. The cookie operations server machine of claim 8 , wherein the instructions that cause the cookie operations server machine to perform the at least one transformation on the first JavaScript comprise instructions that cause the cookie operations server machine to minify the first JavaScript.

10. The cookie operations server machine of claim 8 , wherein the instructions that cause the cookie operations server machine to perform the at least one transformation on the first JavaScript comprise instructions that cause the cookie operations server machine to obfuscate the first JavaScript.

11. The cookie operations server machine of claim 8 , wherein the instructions that cause the cookie operations server machine to perform the at least one transformation on the first JavaScript comprise instructions that cause the cookie operations server machine to replace document.write in the first JavaScript.

12. The cookie operations server machine of claim 8 , wherein the instructions that cause the cookie operations server machine to perform the at least one transformation on the first JavaScript comprise instructions that cause the cookie operations server machine to replace one or more dynamic content Universal Resource Locators (URLs) in the first JavaScript.

13. A method comprising:

receiving, at a first device, from a client device, an HTTP GET message corresponding to JavaScript;

determining that the JavaScript is not stored at the first device;

parsing, by the first device, the HTTP GET message to identify a second device corresponding to the JavaScript;

retrieving the JavaScript from the second device;

storing the JavaScript in a cache at the first device; and

transmitting, from the first device to the client device, and responsive to the HTTP GET message, the JavaScript.

14. The method of claim 13 , wherein the HTTP GET message comprises an indication of an amount of time to cache the JavaScript.

15. The method of claim 13 , wherein the HTTP GET message comprises an indication of a transformation to perform on the JavaScript.

16. The method of claim 13 , further comprising performing one or more transformations on the JavaScript prior to transmitting the JavaScript from the first device.

Assignments (10)
SECURITY INTEREST Recorded Feb 3, 2024
From: CHEQ AI TECHNOLOGIES (2018) LTD
To: KREOS CAPITAL VII AGGREGATOR SCSP
Reel/Frame 066335/0842 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 26, 2023
From: ENSIGHTEN HOLDINGS, INC.
To: CHEQ TECHNOLOGIES INC.
Reel/Frame 065953/0121 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 26, 2023
From: CHEQ TECHNOLOGIES INC.
To: CHEQ AI TECHNOLOGIES (2018) LTD.
Reel/Frame 065953/0130 →
RELEASE OF SECURITY INTEREST Recorded Dec 26, 2023
From: KREOS CAPITAL VII AGGREGATOR SCSP
To: ENSIGHTEN INC.
Reel/Frame 066128/0373 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 26, 2023
From: ENSIGHTEN, INC.
To: ENSIGHTEN HOLDINGS, INC.
Reel/Frame 065953/0085 →
SECURITY INTEREST Recorded Oct 20, 2022
From: ENSIGHTEN INC
To: KREOS CAPITAL VII AGGREGATOR SCSP
Reel/Frame 061476/0495 →
RELEASE OF SECURITY INTEREST Recorded Jun 17, 2022
From: SILICON VALLEY BANK
To: ENSIGHTEN, INC.
Reel/Frame 060238/0768 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY NUMBER 9236580 PREVIOUSLY RECORDED AT REEL: 044652 FRAME: 0062. ASSIGNOR(S) HEREBY CONFIRMS THE . Recorded Dec 7, 2018
From: ENSIGHTEN, INC.
To: SILICON VALLEY BANK
Reel/Frame 047739/0116 →
SECURITY INTEREST Recorded Jan 18, 2018
From: ENSIGHTEN, INC.
To: SILICON VALLEY BANK
Reel/Frame 044652/0062 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 29, 2016
From: MANION, JOSHUA R.; GOODWIN, JOSHUA C.; JACKSON, SAM; ZAKHAROFF, CHRIS
To: ENSIGHTEN, INC.
Reel/Frame 040454/0495 →
Continuity (1)
Continuation In Part 14555550 · Nov 26, 2014