- Basics
- Getting started with LimeLM
- Types of software licensing
- What are Activations & Deactivations?
- How hardware-locked licensing and online activation works
- How to switch your licensing to LimeLM, TurboActivate, and TurboFloat
- Frequently asked questions (FAQ)
- Adding users to manage your LimeLM account
- Custom license fields
- Extra activation data
- Using TurboActivate
- Timed trials in your app
- Basics for TurboFloat (floating licenses)
- TurboFloat Server
- Using TurboFloat
- Advanced
- Account security
- Offline activation
- How to generate product keys after an order
- SaaS and time-limited licensing
- Proxies in TurboActivate
- Licensing multiple products per process
- Licensing from inside a virtual machine or hypervisor
- Web API
- LimeLM web API functions
- Overview
- Encoding
- Response Formats
- REST
- JSON
- feature
- add
- delete
- edit
- getAll
- pkey
- activity
- advancedSearch
- deactivate
- delete
- find
- generate
- getDetails
- getID
- manualActivation
- manualDeactivation
- removeTag
- revoke
- setDetails
- setTags
- prod
- getAll
- create
- createVers
- changeName
- editVers
- tag
- delete
- test
- echo
- trial
- advancedSearch
- manualVerifiedTrial
- trialExtension
- delete
- generate
- getDetails
- getID
- search
Extra activation data
When customers activate your software, or if they use verified trials, you can pass along extra information to the activation servers that will help you identify the customer. This extra data will be visible to you on the product key page next to the other information like the IP address and the date activated:
In this example you can see many activations behind the same IP address. The way you can tell activations apart is by the extra data. In this example the computer user's name is used. However you can use anything you want for extra data.
How to pass extra data to LimeLM
Passing extra activation data to the servers is as simple as calling the TA_Activate() function. In C++ passing extra data would look like this:
ACTIVATE_OPTIONS opts = {0};
opts.nLength = sizeof(ACTIVATE_OPTIONS);
opts.sExtraData = "Here's some extra data";
HRESULT hr = TA_Activate(taHandle, &opts);For all other languages (C#, Java, etc.) the Activate() function is overridden to allow a string "extra data" parameter. So, in C# passing extra data would look like this:
ta.Activate("Here's some extra data");It's similar for the other language integrations of TurboActivate. If you're using the TurboActivate wizard to activate a customer then you can pass extra data to the wizard by using the "--extradata" commandline option:
TurboActivate.exe --extradata="Here's some extra data"
Here's an example of passing extra data with verified trials in C/C++:
uint32_t trialFlags = TA_VERIFIED_TRIAL | TA_SYSTEM;
HRESULT hr = TA_UseTrial(taHandle, trialFlags, "Here's some extra data");And in C# this same functionality would look like this:
TA_Flags trialFlags = TA_Flags.TA_SYSTEM | TA_Flags.TA_VERIFIED_TRIAL;
ta.UseTrial(trialFlags, "Here's some extra data");Limitations
The maximum size of the extra data is 255 UTF-8 characters.
How the extra data is used
The extra data you pass to LimeLM is for your use only. It's to help you distinguish between multiple activations. The extra data is not used in TurboActivate's "fingerprinting" algorithm.