One subscription, how many devices?

Count the distinct devices behind each account and turn heavy sharing into a prompt to upgrade or sign in again.

SignalsaccountSharing
scenario
Step 4 of 4Device 6: accountSharingChallenge
Figure 1Devices on one subscription, 30 days. 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. Password sharingOne paid plan used by a whole group.
  2. Resold accountsLogins sold on to strangers.
  3. Seat dodgingA team on a single-seat plan.
02 · What Trace sees

Fields on the verified event

  • accountSharingDistinct devices per account in the window.
    "accountSharing": {  "detected": true,  "details": { "devicesForAccount": 6, "threshold": 5 }}
  • deviceIdBrowsers on one machine count once.
    "deviceId": "Qp8wL2mXv7RtN4sKe9Ya"
03 · What you do

Decide, with your own thresholds

  • AllowDevice 1
  • ChallengeDevice 6: accountSharing
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.

10suspectScore / 100
AllowLet the action through.
10/ 100
reasons
  • accountSharing+10

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.