System and method for improved opt-out recognition for a mobile device
A technique for identifying an opt-out status for a user's mobile or other computing device without relying exclusively on client-side storage or primarily on the use of non-determinative mechanisms is discussed. Embodiments provide server-based or otherwise hosted techniques of accurately identifying devices of users that wish to opt-out of having their device activity tracked. These techniques enable accurate identification of a device's opt-out status even in the absence of a client-side opt-out indicator.
1. A computing-device implemented method for associating opt-out status to a unified identifier (“Unified ID”) for a mobile device, comprising:
receiving a request from the mobile device at a host server for an opt-out status for tracking of the mobile device;
identifying a unique first verification identifier for the mobile device;
determining that the unique first verification identifier is associated with a plurality of Unified IDs for the mobile device in a storage location;
linking the plurality of Unified IDs based on the determining; and
assigning an opt-out status for the mobile device to the linked plurality of Unified IDs, the opt-out status stored in the storage location and associated with each of the plurality of Unified IDs.
2. The method of claim 1 , further comprising:
receiving a subsequent request for a resource at the host server from the mobile device accompanied by one of the linked plurality of Unified IDs;
verifying the one of the linked plurality of Unified IDs that accompanied the request using the associated unique first verification identifier;
identifying, at the host server, based on the verifying, the opt-out status for the mobile device; and
processing the received subsequent request at the host server based on the opt-out status.
3. The method of claim 1 , further comprising:
receiving a subsequent request for a resource at the host server from the mobile device not accompanied by one of the linked plurality of Unified IDs;
identifying one of the linked plurality of Unified IDs for the mobile device using the associated unique first verification identifier in the storage location;
determining, at the host server, the opt-out status for the mobile device based on an opt-out status assigned to the identified one of the linked plurality of Unified IDS; and
processing the received subsequent request at the host server based on the opt-out status.
4. The method of claim 1 , wherein each of the plurality of Unified IDs were created in response to a request from one of a plurality of separate browsers on the mobile device.
5. The method of claim 4 wherein at least one of the plurality of separate browsers is an in-app browser.
6. The method of claim 1 wherein the unique first verification identifier is one of a carrier ID, device ID, SIM card address, cookie, Ethernet card address or advertising identifier.
7. The method of claim 1 wherein a plurality of different types of unique verification identifiers for the mobile device are associated with at least one of the plurality of Unified IDs.
8. The method of claim 7 wherein the plurality of different types of unique verification identifiers for the mobile device that are associated with at least one of the plurality of Unified IDs are also linked with each other in the storage location.
9. The method of claim 1 , further comprising:
deleting stored data previously associated with one or more of the plurality of Unified IDs upon assigning the opt-out status for the mobile device to the linked plurality of Unified IDs.
10. The method of claim 1 , further comprising:
linking the plurality of Unified IDs by replacing them with a same consolidated Unified ID; and
associating the opt-out status to the consolidated Unified ID in the storage location; and
transmitting a copy of the consolidated Unified ID to the mobile device.
11. A non-transitory computer-readable medium holding computing device-executable instructions for associating opt-out status to a unified identifier (“Unified ID”) for a mobile device, the instructions when executed causing at least one computing device to:
receive a request from the mobile device at a host server for an opt-out status for tracking of the mobile device;
identify a unique first verification identifier for the mobile device;
determine that the unique first verification identifier is associated with a plurality of Unified IDs for the mobile device in a storage location;
link the plurality of Unified IDs based on the determining; and
assign an opt-out status for the mobile device to the linked plurality of Unified IDs, the opt-out status stored in the storage location and associated with each of the plurality of Unified IDs.
12. The medium of claim 11 , wherein the instructions when executed further cause the at least one computing device to:
receive a subsequent request for a resource at the host server from the mobile device accompanied by one of the linked plurality of Unified IDs;
verify the one of the linked plurality of Unified IDs that accompanied the request using the associated unique first verification identifier;
identify, at the host server, based on the verifying, the opt-out status for the mobile device; and
process the received subsequent request at the host server based on the opt-out status.
13. The medium of claim 11 , wherein the instructions when executed further cause the at least one computing device to:
receive a subsequent request for a resource at the host server from the mobile device not accompanied by one of the linked plurality of Unified IDs;
identify one of the linked plurality of Unified IDs for the mobile device using the associated unique first verification identifier in the storage location;
determine, at the host server, the opt-out status for the mobile device based on an opt-out status assigned to the identified one of the linked plurality of Unified IDS and
process the received subsequent request at the host server based on the opt-out status.
14. The medium of claim 11 , wherein each of the plurality of Unified IDs were created in response to a request from one of a plurality of separate browsers on the mobile device.
15. The method of claim 14 wherein at least one of the plurality of separate browsers is an in-app browser.
16. The medium of claim 11 wherein the unique first verification identifier is one of a carrier ID, device ID, SIM card address, cookie, Ethernet card address or advertising identifier.
17. The medium of claim 11 wherein a plurality of different types of unique verification identifiers for the mobile device are associated with at least one of the plurality of Unified IDs.
18. The medium of claim 17 wherein the plurality of different types of unique verification identifiers for the mobile device that are associated with at least one of the plurality of Unified IDs are also linked with each other in the storage location.
19. The medium of claim 11 , wherein the instructions when executed further cause the at least one computing device to:
delete stored data previously associated with one or more of the plurality of Unified IDs upon assigning the opt-out status for the mobile device to the linked plurality of Unified IDs.
20. The medium of claim 11 , wherein the instructions when executed further cause the at least one computing device to:
link the plurality of Unified IDs by replacing them with a same consolidated Unified ID; and
associate the opt-out status to the consolidated Unified ID in the storage location; and
transmit a copy of the consolidated Unified ID to the mobile device.