System and method for preserving consumer choice

1. A computer-implemented method for preserving computer user attribute data, said method for use in a computer network including a plurality of servers, and a plurality of clients having a network browser, said method comprising the steps of:

storing the user attribute data in two or more data locations, said user attribute data being associated with a client;

receiving, at a client from a server, instruction code which is code executable by the client or code self-executing in the client, and which is configured to cause the user attribute data to be preserved;

determining synchronization of the user attribute data stored in said two or more data locations responsive to receipt of the instruction code;

synchronizing the user attribute data stored in said two or more data locations to preserve the user attribute data if said stored user attribute data is not already synchronized to preserve the user attribute data;

determining a lack of synchronization of the user attribute data stored in a first of said two or more data locations with the user attribute data stored in a second of said two or more data locations; and

responsive to determining the lack of synchronization of the user attribute data stored in the first and second of said two or more data locations, restoring the user attribute data in the first of said two or more data locations so that the user attribute data in the first and second of said two or more data locations is synchronized.

2. The computer-implemented method of claim 1 , wherein the stored user attribute data includes information pertaining to client-side opt out choices.

3. The computer-implemented method of claim 1 , wherein the user attribute data includes information pertaining to the identity of the client.

4. The computer-implemented method of claim 1 , wherein the user attribute data is stored as a browser cookie.

5. The computer-implemented method of claim 1 , wherein the user attribute data is stored as a Java Applet.

6. The computer-implemented method of claim 1 , wherein the user attribute data is stored as a Flash Shared Objects.

7. The computer-implemented method of claim 1 , wherein the user attribute data is stored in browser cache.

8. The computer-implemented method of claim 1 , wherein the user attribute data is stored in random-access-memory.

9. The computer-implemented method of claim 1 , further comprising the step of:

updating stored user attribute data in said two or more data locations associated with said client if said user attribute data is outdated.

10. The computer-implemented method of claim 1 , wherein said determination of synchronization further comprises the steps of:

comparing the user attribute data stored in said two or more data locations to each other; and

selecting one of said two or more data locations to be the first of said two or more data locations based on recency data.

11. A system for preserving computer user attribute data, said system for use in a computer network including a plurality of servers, and a plurality of clients having a network browser, said system comprises a processor and a memory that:

stores the user attribute data in two or more data locations, said user attribute data being associated with a client;

receives, at a client from a server, instruction code which is code executable by the client or code self-executing in the client, and which is configured to cause the user attribute data to be preserved;

determines synchronization of the user attribute data stored in said two or more data locations responsive to receipt of the instruction code;

synchronizes the user attribute data stored in said two or more data locations to preserve the user attribute data if said stored user attribute data is not already synchronized to preserve the user attribute data;

determines a lack of synchronization of the user attribute data stored in a first of said two or more data locations with the user attribute data stored in a second of said two or more data locations; and

responsive to determining the lack of synchronization of the user attribute data stored in the first and second of said two or more data locations, restores the user attribute data in the first of said two or more data locations so that the user attribute data in the first and second of said two or more data locations is synchronized.

12. The system of claim 11 , wherein the stored user attribute data includes information pertaining to client-side opt out choices with respect to communications with a network site.

13. The system of claim 11 , wherein the user attribute data includes information pertaining to the identity of the client.

14. The system of claim 11 wherein the user attribute data is stored as a browser cookie.

15. The system of claim 11 wherein the user attribute data is stored as a Java Applet.

16. The system of claim 11 wherein the user attribute data is stored as a Flash Shared Objects.

17. The system of claim 11 wherein the user attribute data is stored in browser cache.

18. The system of claim 11 wherein the user attribute data is stored in random-access-memory.

19. The system of claim 11 further comprises:

updates stored user attribute data in said two or more data locations associated with said client if said user attribute data is outdated.

20. The system of claim 11 , wherein said determination of synchronization further comprises:

compares the user attribute data stored in said two or more data locations to each other; and

selects one of said two or more data locations to be the first of said two or more data locations based on recency data.