Use case · Multi-accounting & bonus abuse
One person, forty accounts, one cluster.
One person, forty accounts, one device cluster.
The pattern
Promo launches, referral loops, airdrops: the same device or card shows up behind many different users, spaced out to look organic.
The tags
cluster.size_5pluscluster.shares_device_with_bannedpromo.multi_claimreferral.self_looppayment.instrument_reuseddevice.shared_with_bannedThe preset
| When | Then |
|---|---|
promo.multi_claim | block promo |
cluster.size_5plus | review |
referral.self_loop | void referral |
first hour of a launch | review only (quiet window) |
Ship it
Send promo_claim and referral events with the user and device. Autopilot on promo.multi_claim once you trust it.
Recommended mode · Recommend
your backend
await ordent.events.send({
type: "promo_claim",
user: { id: user.id },
device: req.ordentDevice,
context: { promo: "welcome_bonus", amount: 500, currency: "INR" },
});What you'll see
Cluster explorer: the accounts, the shared edges, and why. One click to label the cluster and every account in it.
Start today
Your risk team starts here.
$99 a month, 10,000 events, sandbox before you pay, money back in 14 days if it doesn't fit.