Trials are for trying, once.

Stop endless trials from the same machine with new emails, and turn repeat trial users into paying ones.

SignalsmultiAccount
scenario
Step 3 of 3Third trial: ask for paymentBlock
Figure 1Trial starts from one device. Illustrative data. Hover or focus to pause; pick a step to scrub.

How it plays out

The attack, what the verified event shows, and what your code does about it.

01 · The attack

How it usually goes

  1. Trial cyclingA new email every 14 days.
  2. Team on trialsEach teammate starts their own trial on one machine.
  3. Throwaway cardsVirtual cards to pass the card check.
02 · What Trace sees

Fields on the verified event

  • deviceIdStore it with every trial you grant.
    "deviceId": "Xk3pQ9vLmT2aR7sBn4Wc"
  • multiAccountMany accounts on the device.
    "multiAccount": {  "detected": true,  "details": { "accountsOnDevice": 3, "threshold": 2 }}
03 · What you do

Decide, with your own thresholds

  • AllowFirst trial
  • ChallengeSecond trial on device: offer a discount
  • BlockThird trial: ask for payment
Read the guide

Decision lab

Switch signals on and off. The score is a plain sum of weights.

decision lab
Signals

Weights are the defaults in scoring.default.json. The cut-offs at 25 and 60 are examples; your app sets its own.

25suspectScore / 100
ChallengeAsk for a code, or send to review.
25/ 100
reasons
  • multiAccount+25

Implementation

One browser call, one server check.

01IdentifyCall the SDK on the action and send the eventId with it.
02VerifyYour server reads the event with a secret key.
03DecideAllow, challenge or block, with your own thresholds.
identify.ts
const trace = createClient({ apiKey: 'pk_...', endpoint: 'https://id.example.com' });

// On the action (signup, login, checkout), then send eventId with the form.
const { eventId } = await trace.get();
Example response, illustrative
{  "eventId": "evt_example"}

Start in shadow mode. Block later.

Log the decision for a week, check who it would have stopped, then turn it on.