Mobile device identification using second entity matching
An improved technique for identifying a user's mobile device is discussed. A persistent and unified identifier that bridges mobile app to mobile web and to other web browser-compatible mediums is utilized. Using a unique verification identifier, the unified identifier is consistently verified, revived and distributed across application and browser mediums.
1. A computing device-implemented method for improved identification of a mobile device, comprising:
creating at a host server a separate unified identifier (“Unified ID”) for each of a plurality of requesting browsers on a mobile device, the plurality of requesting browsers including at least one in-app browser;
linking at the host server the separate Unified IDs under a consolidated Unified ID that is associated with a unique first verification identifier for the mobile device;
storing an indication of the association of the first verification identifier and the consolidated Unified ID in a storage location accessible to the host server;
receiving one or more verification identifiers and one or more associated sets of data at the host server, the one or more verification identifiers identified by a second entity;
matching the unique first verification identifier or another verification identifier associated with the consolidated Unified ID with the one or more verification identifiers received from the second entity; and
performing, based on the matching, at least one of an action related to the consolidated Unified ID or an association of one of the one or more associated sets of data received from the second entity with the consolidated Unified ID.
2. The method of claim 1 , further comprising:
associating, at the host server, a data payload received from the mobile device with the consolidated Unified ID.
3. The method of claim 1 , further comprising:
receiving a subsequent request at the host server from the mobile device, the subsequent request not accompanied by the consolidated Unified ID or one of the separate Unified IDs;
verifying the consolidated Unified ID for the mobile device using the stored first verification identifier; and
associating, at the host server, based on the verifying, a data payload with the consolidated Unified ID, the data payload received from the mobile device.
4. The method of claim 1 , further comprising:
identifying a plurality of different types of unique verification identifiers for the mobile device; and
storing and associating each of the plurality of different types of unique verification identifiers for the mobile device with the consolidated Unified ID in the storage location.
5. The method of claim 4 wherein the plurality of different types of unique verification identifiers include at least two of a carrier ID, device ID, SIM card address, cookie, Ethernet card address, or advertising identifier.
6. The method of claim 4 , further comprising:
receiving a subsequent request at the host server from the mobile device, the subsequent request not accompanied by the consolidated Unified ID or one of the separate Unified IDs;
verifying the consolidated Unified ID for the mobile device using a second verification identifier from among the stored plurality of different types of unique verification identifiers associated with the stored consolidated Unified ID; and
associating, at the host server, a data payload with the consolidated Unified ID, the data payload received from the mobile device.
7. The method of claim 1 , further comprising:
identifying a plurality of different unique verification identifiers for the mobile device; and
storing and associating each of the plurality of different unique verification identifiers for the mobile device with the stored consolidated Unified ID in the storage location, wherein the plurality of unique verification identifiers include at least two different cookies.
8. The method of claim 1 , further comprising:
sending a targeted advertisement to the mobile device following an association of the one or associated sets of data with the consolidated Unified ID.
9. The method of claim 1 , further comprising:
storing a first set of data and an association of the first set of data with the first verification identifier prior to the creation of the consolidated Unified ID; and
associating the first set of data with the consolidated Unified ID after the creation of the consolidated Unified ID based on the first verification identifier.
10. A non-transitory medium holding computer-executable instructions for improved identification of a mobile device, the instructions when executed causing at least one computing device to:
create at a host server a separate unified identifier (“Unified ID”) for each of a plurality of requesting browsers on a mobile device, the plurality of requesting browsers including at least one in-app browser;
link at the host server the separate Unified IDs under a consolidated Unified ID that is associated with a unique first verification identifier for the mobile device;
store an indication of the association of the first verification identifier and the consolidated Unified ID in a storage location accessible to the host server;
receive one or more verification identifiers and one or more associated sets of data at the host server, the one or more verification identifiers identified by a second entity;
match the unique first verification identifier or another verification identifier associated with the consolidated Unified ID with the one or more verification identifiers received from the second entity; and
perform, based on the matching, at least one of an action related to the consolidated Unified ID or an association of one of the one or more associated sets of data received from the second entity with the consolidated Unified ID.
11. The medium of claim 10 , wherein the instructions when executed further cause the at least one computing device to:
associate, at the host server, a data payload received from the mobile device with the consolidated Unified ID.
12. The medium of claim 10 , wherein the instructions when executed further cause the at least one computing device to:
receive a subsequent request at the host server from the mobile device, the subsequent request not accompanied by the consolidated Unified ID or one of the separate Unified IDs;
verify the consolidated Unified ID for the mobile device using the stored first verification identifier; and
associate, at the host server, based on the verifying, a data payload with the consolidated Unified ID, the data payload received from the mobile device.
13. The medium of claim 10 , wherein the instructions when executed further cause the at least one computing device to:
identify a plurality of different types of unique verification identifiers for the mobile device; and
store and associate each of the plurality of different types of unique verification identifiers for the mobile device with the consolidated Unified ID in the storage location.
14. The medium of claim 13 wherein the plurality of different types of unique verification identifiers include at least two of a carrier ID, device ID, SIM card address, cookie, Ethernet card address, or advertising identifier.
15. The medium of claim 13 , wherein the instructions when executed further cause the at least one computing device to:
receive a subsequent request at the host server from the mobile device, the subsequent request not accompanied by the consolidated Unified ID or one of the separate Unified IDs;
verify the consolidated Unified ID for the mobile device using a second verification identifier from among the stored plurality of different types of unique verification identifiers associated with the stored consolidated Unified ID; and
associate, at the host server, a data payload with the consolidated Unified ID, the data payload received from the mobile device.
16. The medium of claim 10 , wherein the instructions when executed further cause the at least one computing device to:
identify a plurality of different unique verification identifiers for the mobile device; and
store and associating each of the plurality of different unique verification identifiers for the mobile device with the stored consolidated Unified ID in the storage location, wherein the plurality of unique verification identifiers include at least two different cookies.
17. The medium of claim 10 , wherein the instructions when executed further cause the at least one computing device to:
send a targeted advertisement to the mobile device following an association of the one or associated sets of data with the consolidated Unified ID.
18. The medium of claim 10 , wherein the instructions when executed further cause the at least one computing device to:
store a first set of data and an association of the first set of data with the first verification identifier prior to the creation of the consolidated Unified ID; and
associate the first set of data with the consolidated Unified ID after the creation of the consolidated Unified ID based on the first verification identifier.