一种在线免费试用的防滥用系统设计
我目前正在以小额支付价格出售基于时间的在线服务访问通行证。
付款后，客户将获得一组仅在购买期间有效的凭证。当访问通行证过期时，客户必须购买一组新的凭证。 所以基本上凭证只能一次性（一段时间）使用。
我想为这项服务提供 x 分钟的免费试用，以便潜在客户能够意识到它运行良好，可能会增加总销售额。
我的问题是，您将如何阻止滥用者？< /em>
也就是说，人们应该只被允许免费尝试一次，如果不可能，至少让他们经历一个过程/测试，这（如在共享软件中）对他们来说太麻烦或烦人，无法继续尝试。
显然，总有人会绕过它。我正在为大多数不熟悉 IT、时间有限或懒得滥用 IT 的人寻找解决方案，而不是简单地支付少量费用。
我想到了一些方法，但也希望受到其他人的启发。
该服务是使用 LAMP 开发的。
I am currently selling time based access passes to an online service at micro payment prices.
After payment the customer gets a set of credentials that is only valid for the purchased period. When the access pass expires the customer has to buy a new set of credentials.
So basically the credentials are one-time(period) use only.
I would like to offer a free-trial of x minutes to this service so potential customers can realise it works fine, possibly increasing total sales.
My question is, how would you stop abusers?
That is, people should only be allowed to try for free once, and if that is not possible at least make them go through a process/test which (as in shareware) is too cumbersome or annoying for them to keep trying it.
Obviously there is always someone who will bypass it. I am looking for a solution for the majority of people who are either not IT savvy, time constrained, or simply too lazy to bother abusing it, instead of simply paying the tiny fee.
I have some approaches in mind but would like to be inspired by other people too.
The service is developed with LAMP.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
在他们的浏览器中放入 cookie。在他们重新使用您的服务之前强制稍微延迟一下，或者让他们不厌其烦地删除 cookie。如果他们阻止 cookie，请礼貌地请求他们允许。如果您允许进行多次试验，并且将麻烦降到最低，您可能会获得更多的商业成功。
Put a cookie in their browser. Force a small delay before they can re-use your service, or make them go to the trouble of deleting the cookie. If they block cookies, politely ask them to allow them. You might have more business success if you allow several trials, with a minimum of hassle.
如果你环顾四周，就会发现每个提供免费试用的人都将其与信用卡绑定——不是为了收费，而是为了验证用户的身份。这是我能想到的防止虐待的唯一可行方法。
任何其他想法将取决于您提供的服务类型。例如，StackExchange 可以提供 45 天的试用，无需信用卡，没问题，仅仅是因为构建 SE 的努力网站是如此之大，开始多个试用期（并且每次都必须配置新网站并建立新社区）是行不通的。
类似的东西可能是您可以在试用期内注册的唯一登录名，如果您不将其转换为付费订阅，则必须放弃，诸如此类。实际上取决于您的服务性质。
If you look around, everybody who gives out free trials binds them to a credit card - not to charge them, but to verify the user's identity. That's about the only feasible way to prevent abuse I can think of.
Any other idea will depend on the kind of service you are offering. StackExchange for example can offer a 45 day trial without a credit card no problem, simply because the effort to build a SE site is so huge, starting multiple trial periods (and having to configure a new site and build a new community every time) just wouldn't work.
Something similar could be unique login names that you can register during your trial period, and would have to give away if you don't convert it into a pay subscription, things like that. Really depends on the nature of your service.
想要通过试用再次尝试你的产品的用户是高转化用户，因为他们已经知道产品的价值。
挑战在于检测他们，然后将他们转化为付费用户。
可以使用各种信号来完成检测，包括：
每个单独的信号都有其挑战，例如。 IP 可以更改并在大量受众之间合法共享，例如通过运营商级 nat。
短信验证在大多数市场中都很好，但会增加摩擦并为您和您的用户带来潜在成本。
像 Upollo.ai 这样的东西可以为你解决所有困难的部分，所以值得未来面临这些问题的人看看
The users who want to try your product again via a trial are highly convertible users because they already know the value of the product.
The challenge is detecting them and then converting them to paying users.
Detecting can be done using a variety of signals including:
Each individual signal has its challenges eg. IPs can change and are legitimately shared among large audience such as via carrier grade nat.
SMS verification is good in most markets but adds friction and potentially cost for you and your users.
Something like Upollo.ai solves all the hard parts for you so worth a look for people facing these problems in future
我最终在短时间内使用了尽可能小的支付金额，但足以以非常低的货币风险让用户满意。
自从我问起以来，我实际上认真考虑过使用 Flash cookie，很少有人知道（即使它们存在）如何删除。
另一个简单的（尽管不是免费的）是使用绑定用户手机号码的短信确认选项。作为手机号码，您只需不要像电子邮件地址那样丢弃，那么这也是一种安全的限制方法。
I ended up using the smallest possible payment amount for a short time span, but enough to get the user satisfied at very low monetary risk.
In the time past since I asked I actually seriously considered using Flash cookies which very few people know (even that they exist) how to remove.
The other simple (although not-free) is using a SMS confirmation option which binds the user's mobile phone number. As a mobile phone number you just do not throw away like you do with email addresses then this is also a safe limitation method.