Systems and methods for leveraging social queuing to identify and prevent ticket purchaser simulation

1. A method for filtering and sorting ticket purchasing opportunities for an event, the method comprising:

querying a social media account associated with a user to obtain social media account information or a third-party data source to obtain user information;

receiving social media account information from the social media account or receiving user information from the third-party data source;

querying the social media account to obtain social media identification information;

compiling either or both of the social media account information from the social media account or the user information from the third-party data source to form a user account history;

calculating an index value based on the user information, said index value being based, at least in part, on the account history;

determining whether the index value is more than a first threshold value;

in response to determination that index value is more than the threshold value, associating the social media identification information as a priority identification information;

receiving a plurality of ticket purchasing requests associated with an event, wherein each of the plurality of ticket purchase requests are associated with the user;

for ticket purchasing requests associated with the priority identification information, placing ticket purchasing requests in a priority ticket purchase queue;

for logins not associated with the priority identification information, placing ticket purchasing requests in a non-priority ticket purchase queue;

determining if the index value is more than a second threshold value; and

in response to determining that the index value is more than the second threshold value, tagging the social media identification information as a non-priority identification information.

2. The method, as recited in claim 1 , further comprising categorizing a first portion of the plurality of ticket purchasing requests as human-based logins, a second portion of the plurality of ticket purchasing requests as non-human-based logins and a third portion of the plurality of ticket purchasing requests as human-based priority logins.

3. The method, as recited in claim 1 , further comprising determining whether the user account history includes one or more parameters that indicate whether the user account history is related to an automated entity or a human entity.

4. The method, as recited in claim 3 , wherein the one or more parameters include a determination of less than a threshold number of friends associated with the account.

5. The method, as recited in claim 3 , wherein the one or more parameters include at a determination more than a threshold frequency of historic ticket purchases per unit time.

6. The method, as recited in claim 3 , wherein the user account history comprises streaming audio time from the third-party data source.

7. The method, as recited in claim 1 , further comprising updating social media identification information; and

updating the index value based on update in social media identification information.

8. A system for filtering and sorting ticket purchasing opportunities for an event, comprising:

one or more data processors; and

a non-transitory computer-readable storage medium containing instructions which, when executed on the one or more data processors, cause the one or more data processors to perform operations including:

querying a social media account associated with a user to obtain social media account information or a third-party data source to obtain user information;

receiving social media account information from the social media account or receiving user information from the third-party data source;

querying the social media account to obtain social media identification information;

compiling either or both of the social media account information from the social media account or the user information from the third-party data source to form a user account history;

calculating an index value based on the user information, said index value being based, at least in part, on the account history;

determining whether the index value is more than a first threshold value;

in response to determination that index value is more than the threshold value, associating the social media identification information as a priority identification information;

receiving a plurality of ticket purchasing requests associated with an event, wherein each of the plurality of ticket purchase requests are associated with the user;

for ticket purchasing requests associated with the priority identification information, placing ticket purchasing requests in a priority ticket purchase queue;

for logins not associated with the priority identification information, placing ticket purchasing requests in a non-priority ticket purchase queue;

determining if the index value is more than a second threshold value; and

in response to determining that the index value is more than the second threshold value, tagging the social media identification information as a non-priority identification information.

9. The system, as recited in claim 8 , further comprising categorizing a first portion of the plurality of ticket purchasing requests as human-based logins, a second portion of the plurality of ticket purchasing requests as non-human-based logins and a third portion of the plurality of ticket purchasing requests as human-based priority logins.

10. The system, as recited in claim 8 , further comprising determining whether the user account history includes one or more parameters that indicate whether the user account history is related to an automated entity or a human entity.

11. The system, as recited in claim 10 , wherein the one or more parameters include a determination of less than a threshold number of friends associated with the account.

12. The system, as recited in claim 10 , wherein the one or more parameters include at a determination more than a threshold frequency of historic ticket purchases per unit time.

13. The system, as recited in claim 10 , wherein the user account history comprises streaming audio time from the third-party data source.

14. The system, as recited in claim 1 , further comprising updating social media identification information; and

updating the index value based on update in social media identification information.

15. A computer-program product tangibly embodied in a non-transitory machine-readable storage medium, including instructions configured to cause a data processing apparatus to perform operations including:

querying a social media account associated with a user to obtain social media account information or a third-party data source to obtain user information;

receiving social media account information from the social media account or receiving user information from the third-party data source;

querying the social media account to obtain social media identification information;

compiling either or both of the social media account information from the social media account or the user information from the third-party data source to form a user account history;

calculating an index value based on the user information, said index value being based, at least in part, on the account history;

determining whether the index value is more than a first threshold value;

in response to determination that index value is more than the threshold value, associating the social media identification information as a priority identification information;

receiving a plurality of ticket purchasing requests associated with an event, wherein each of the plurality of ticket purchase requests are associated with the user;

for ticket purchasing requests associated with the priority identification information, placing ticket purchasing requests in a priority ticket purchase queue;

for logins not associated with the priority identification information, placing ticket purchasing requests in a non-priority ticket purchase queue;

determining if the index value is more than a second threshold value; and

in response to determining that the index value is more than the second threshold value, tagging the social media identification information as a non-priority identification information.

16. The computer-program product, as recited in claim 15 , further comprising categorizing a first portion of the plurality of ticket purchasing requests as human-based logins, a second portion of the plurality of ticket purchasing requests as non-human-based logins and a third portion of the plurality of ticket purchasing requests as human-based priority logins.

17. The computer-program product, as recited in claim 15 , further comprising determining whether the user account history includes one or more parameters that indicate whether the user account history is related to an automated entity or a human entity.

18. The computer-program product, as recited in claim 17 , wherein the one or more parameters include a determination of less than a threshold number of friends associated with the account.

19. The computer-program product, as recited in claim 17 , wherein the one or more parameters include at a determination more than a threshold frequency of historic ticket purchases per unit time.

20. The computer-program product, as recited in claim 17 , wherein the user account history comprises streaming audio time from the third-party data source.