We are aware that we can pass extra data to TA_UseTrial, but we don't seem to be able to retrieve them later on or update them which defeats the purpose in our case
Verified Trial Extra DataAnswered
We are looking into a way to associate extra data (that we can modify & look-up) to verified trials.
Our use case is to limit free-trials to a number of projects (e.g:) created in the app. We would store in there some UUID of the projects so that the user cannot abuse it.
Is there anyway to accomplish this with limelm ?
Our only resort, would be to make our own fingerprint of the hardware and store it on our servers, which is silly knowing limelm does just that.
Answer
I'm not sure what the question is: Trials and activations already support extra data.
The 3rd parameter of TA_UseTrial(…) is STRCTYPE extra_data.
Verified trials are more for simple use-cases. Basically letting customers use your software or not use your software based on whether the trial period is expired or not.
You can use product keys and custom license fields for more complicated use-cases like what you’re looking for.
I understand, but knowing the number of free trial customers, this would dramatically up our subscription (to wyday) price, for customers that are not paying. Some of them would never pay anyway, but we'd still like to increase our userbase
You can delete product keys when you’re done with them (thus freeing up the activation slot). So you will use more activations than if you just used them for actual customers.
But that really comes from an atypical trial offering. The easier thing to do is offer a full trial for a period of time (what verified trials do). And if they want more time to evaluate, then give them a trial extension.
Limiting specific data on a per-trial basis is beyond of the scope of typical trials.
You can however limit functions in your app when you’re in the trial period. If you’re trying to to limit to X uses then you’ll need to track things locally (which then can be wiped out).
So, you have a lot of options. Personally we recommend against overly complicated trials. They’re confusing for the customer, they require a ton of engineering to get right, and the difference in conversion rate is negligible.
Thanks for your feedback. We went our own way using our webserver to store data related to our own custom made fingerprint. We do this on top of limelm free trials.
This type of free trial is not so atypical, many web appication do this nowadays.
For instance Rive https://rive.app/pricing
But also some desktop apps have the same model, like Autodesk Fusion 360