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 method for improved identification of a mobile device, comprising:
identifying a unique first verification identifier for a mobile device at a host server;
creating a unified identifier (“Unified ID”) for the mobile device at the host server;
storing the identified first verification identifier and the Unified ID in a storage location, the stored first verification identifier associated with the stored Unified ID in the storage location;
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 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 Unified ID and an association of one of the one or more associated sets of data received from the second entity with the 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 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 Unified ID;
verifying the 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 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 stored 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, and 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 Unified ID;
verifying the 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 Unified ID; and
associating, at the host server, a data payload with the 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 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 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 Unified ID; and
associating the first set of data with the Unified ID after the creation of the 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:
identify a unique first verification identifier for a mobile device at a host server;
create a unified identifier (“Unified ID”) for the mobile device at the host server;
store the identified first verification identifier and the Unified ID in a storage location, the stored first verification identifier associated with the stored Unified ID in the storage location;
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 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 Unified ID and an association of one of the one or more associated sets of data received from the second entity with the 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 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 Unified ID;
verify the 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 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 stored 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, and 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 Unified ID;
verify the 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 Unified ID; and
associate, at the host server, a data payload with the 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 associate each of the plurality of different unique verification identifiers for the mobile device with the stored 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 Unified ID.
18. A computing device configured for improved identification of a mobile device, comprising:
a communication interface configured to receive over a network requests originating from a mobile device; and
a processor configured to execute instructions for a verification module, the verification module when executing causing the computing device to:
identify a unique first verification identifier for a mobile device at a host server;
create a unified identifier (“Unified ID”) for the mobile device at the host server;
store the identified first verification identifier and the Unified ID in a storage location, the stored first verification identifier associated with the stored Unified ID in the storage location;
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 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 Unified ID and an association of one of the one or more associated sets of data received from the second entity with the Unified ID.
19. The computing device of claim 18 , wherein the verification module when executed further causes the 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 stored Unified ID in the storage location.
20. The computing device of claim 18 , 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, and advertising identifier.