Stateless cookie operations server
First Claim
1. A stateless cookie operations server machine, comprising:
- at least one processor; and
at least one memory storing computer-executable instructions that, when executed by the processor, cause the server machine to;
receive name-value pairs as input parameters in a HTTP GET message;
receive a cookie data file in a header of the HTTP GET message;
parse the input parameters to identify the name of the name-value pairs;
parse the name to identify a cookie name;
parse the name to identify an operation;
compare the operation to a list of predefined operations involving the cookie data file to identify a selected operation;
perform the selected operation on data stored in the cookie data file corresponding to the cookie name;
update the cookie data file with an output of the selected operation;
transmit a HTTP request message; and
transmit the updated cookie data file.
10 Assignments
0 Petitions
Accused Products
Abstract
A 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 load an image element configured with parameters and a hyperlink (e.g., URL) that causes name-value pairs to be sent as parameters, along with a cookie data file, to a remote server. The remote server may process the parameters and perform operations based on both the value and the name of the name-value pairs. Mathematical and/or other operations may be performed on the parameters and the results saved into the appropriate cookie data file. The server sends the update cookie data file and any requested content (e.g., a transparent image pixel, or other information) back to the client-side device. As a result, the client-side application may use the information in the updated cookie data file to perform one or more web analytics and personalization functions on a real-time, user-specific, actionable basis.
-
Citations
20 Claims
-
1. A stateless cookie operations server machine, comprising:
-
at least one processor; and at least one memory storing computer-executable instructions that, when executed by the processor, cause the server machine to; receive name-value pairs as input parameters in a HTTP GET message; receive a cookie data file in a header of the HTTP GET message; parse the input parameters to identify the name of the name-value pairs; parse the name to identify a cookie name; parse the name to identify an operation; compare the operation to a list of predefined operations involving the cookie data file to identify a selected operation; perform the selected operation on data stored in the cookie data file corresponding to the cookie name; update the cookie data file with an output of the selected operation; transmit a HTTP request message; and transmit the updated cookie data file. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A non-transitory computer-readable medium of a stateless cookie operations server storing computer-executable instructions that, when executed by a processor of stateless cookie operations server, cause the stateless cookie operations server to:
-
receive name-value pairs as input parameters in an incoming message; receive a persistent data file in the incoming message; parse the input parameters to identify the name of the name-value pairs; parse the name to identify a persistent data file name; parse the name to identify an operation; compare the operation to a list of predefined operations involving the persistent data file to identify a selected operation; perform the selected operation on data stored in the persistent data file corresponding to the persistent data file name; update the persistent data file with an output of the selected operation; transmit an outgoing request message; and transmit the updated persistent data file. - View Dependent Claims (9, 10, 11, 12, 13)
-
-
14. A method comprising:
-
receiving name-value pairs as input parameters in an incoming message; receiving a persistent data file in the incoming message; parsing the input parameters to identify the name of the name-value pairs; parsing the name to identify a persistent data file name; parsing the name to identify an operation; comparing the operation to a list of predefined operations involving the persistent data file to identify a selected operation; performing the selected operation on data stored in the persistent data file corresponding to the persistent data file name; updating the persistent data file with an output of the selected operation; transmitting an outgoing request message; and transmitting the updated persistent data file. - View Dependent Claims (15, 16, 17, 18, 19, 20)
-
Specification