Systems and methods for leveraging social queuing to identify and prevent ticket purchaser simulation
A method for identifying a simulated social media account history is provided. The method may include querying a social media account to obtain social media identification information. The querying may determine whether the account history includes one or more parameters that indicate whether the social media account is related to an automated entity or a human entity. The parameters may include at least one of less than a threshold number of friends on the account; more than a threshold frequency of historic ticket purchases per unit time; disparate location of historic ticket purchases per unit time and/or a historic record of less than a threshold reaction time to a plurality of ticket offers.
1. A computer-implemented method comprising:
receiving a request to log in to a system for assigning access rights to resources, the request being associated with identification information representing a user;
in response to receiving the request, querying a third party data source to determine whether the identification information is associated with a human user or a bot user, the querying including identifying one or more previous interactions between a third party platform associated with the third party data source and the user;
evaluating the one or more previous interactions to determine whether the one or more previous interactions is more similar to a user profile associated with an automated entity or a user profile associated with a human entity, wherein evaluating includes data mining the one or more previous interactions to identify an affinity for one or more performers;
in response to determining that the one or more previous interactions is more similar to the user profile associated with an automated entity, inhibiting the user from accessing the system for assigning access rights; and
in response to determining that the one or more previous interactions is more similar to the user profile associated with a human user, enabling the user to access the system to request assignment of at least one access right for an event associated with the one or more performers.
2. The computer-implemented method of claim 1 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes a determination of less than a threshold number of friends associated with an account represented by the identification information.
3. The computer-implemented method of claim 1 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes a determination of more than a threshold frequency of historic ticket purchases per unit time.
4. The computer-implemented method of claim 1 , wherein the third party platform enables users to purchase and/or sell one or more items.
5. The computer-implemented method of claim 1 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes a historic record of less than a threshold average reaction time to ticket offers.
6. The computer-implemented method of claim 1 , further comprising monitoring one or more parameters identifiable from the third party platform, wherein the monitoring is performed over a pre-determined period of time.
7. The computer-implemented method of claim 1 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes ticket purchasing history over a pre-prederemined period of time.
8. A system, 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:
receiving a request to log in to a system for assigning access rights to resources, the request being associated with identification information representing a user;
in response to receiving the request, querying a third party data source to determine whether the identification information is associated with a human user or a bot user, the querying including identifying one or more previous interactions between a third party platform associated with the third party data source and the user;
evaluating the one or more previous interactions to determine whether the one or more previous interactions is more similar to a user profile associated with an automated entity or a user profile associated with a human entity, wherein evaluating includes data mining the one or more previous interactions to identify an affinity for one or more performers;
in response to determining that the one or more previous interactions is more similar to the user profile associated with an automated entity, inhibiting the user from accessing the system for assigning access rights; and
in response to determining that the one or more previous interactions is more similar to the user profile associated with a human user, enabling the user to access the system to request assignment of at least one access right for an event associated with the one or more performers.
9. The system of claim 8 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes a determination of less than a threshold number of friends associated with an account represented by the identification information.
10. The system of claim 8 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes a determination of more than a threshold frequency of historic ticket purchases per unit time.
11. The system of claim 8 , wherein the third party platform enables users to purchase and/or sell one or more items.
12. The system of claim 8 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes a historic record of less than a threshold average reaction time to ticket offers.
13. The system of claim 8 , wherein the operations further comprise monitoring one or more parameters identifiable from the third party platform, wherein the monitoring is performed over a pre-determined period of time.
14. The system of claim 8 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes ticket purchasing history over a pre-prederemined period of time.
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:
receiving a request to log in to a system for assigning access rights to resources, the request being associated with identification information representing a user;
in response to receiving the request, querying a third party data source to determine whether the identification information is associated with a human user or a bot user, the querying including identifying one or more previous interactions between a third party platform associated with the third party data source and the user;
evaluating the one or more previous interactions to determine whether the one or more previous interactions is more similar to a user profile associated with an automated entity or a user profile associated with a human entity, wherein evaluating includes data mining the one or more previous interactions to identify an affinity for one or more performers;
in response to determining that the one or more previous interactions is more similar to the user profile associated with an automated entity, inhibiting the user from accessing the system for assigning access rights; and
in response to determining that the one or more previous interactions is more similar to the user profile associated with a human user, enabling the user to access the system to request assignment of at least one access right for an event associated with the one or more performers.
16. The computer-program product of claim 15 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes a determination of less than a threshold number of friends associated with an account represented by the identification information.
17. The computer-program product of claim 15 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes a determination of more than a threshold frequency of historic ticket purchases per unit time.
18. The computer-program product of claim 15 , wherein the third party platform enables users to purchase and/or sell one or more items.
19. The computer-program product of claim 15 , wherein one or more parameters identifiable from the third party platform are identified, and wherein the one or more parameters includes a historic record of less than a threshold average reaction time to ticket offers.
20. The computer-program product of claim 15 , wherein the operations further comprise monitoring one or more parameters identifiable from the third party platform, wherein the monitoring is performed over a pre-determined period of time.