MEET FINGERLYA clearer picture of every session.Explore the signals
Account connections

Different accounts. One device.

Fingerly does not know your accounts, and it should not. It gives every request a visitor ID. Store it beside the account, the order or the claim, and the connections between them are a query away.

  • Visitor IDOn every response.
  • Your tagYour own reference, echoed back.
  • LookupsEvents by visitor ID.
  • WebhooksVisitor IDs pushed to you.

Three steps to a connection.

The link between an account and a device lives in your data, where your team already investigates.

  1. 01 Tag the request

    Identify at signup, login or checkout, with your own reference as the tag. It comes back on the event and the webhooks.

    identify({ tag: "signup:acct_4821" })
  2. 02 Store the visitor ID

    Save the visitor ID your server verified next to the account or order it belongs to.

  3. 03 Look up the device

    Query your own records for other accounts with the same visitor ID, and read that device’s recent events from the API.

    GET /api/v1/events?visitor=X9pL2mRc7KvT4bQw8NdF

Every recent event from one device.

With a secret key, list the events for a visitor ID in the key’s environment, over any window inside the last 30 days.

Node.js
import { load } from '@fingerly/node'

const fingerly = load({ secretKey: process.env.FINGERLY_SECRET_KEY })

// Everything this device did in the last week
const { rows } = await fingerly.events.list({
  visitor: 'X9pL2mRc7KvT4bQw8NdF',
  from: new Date(Date.now() - 7 * 864e5).toISOString(),
  limit: 200,
})

const tags = new Set(rows.map((event) => event.tag).filter(Boolean))
// tags now holds every account reference this device was identified with

The console’s Events view filters by visitor ID too, for investigations by hand.

A lead, not a conviction.

Shared devices are ordinary. Connections are where an investigation starts.

Households and shops

Families share a tablet and shops share a till. Weigh how many accounts share a device, and what they did, before acting.

Add the device signals

Many accounts on one device is far more telling when that device is an emulator, a cloned app or part of a device farm.

Scoped to your organisation

Visitor IDs only connect traffic inside your own organisation. They never link your customers to anyone else’s.

About account connections.

How to connect accounts by device responsibly.

Talk to the team
Does Fingerly store my user accounts?

No. Fingerly stores identifications, each with a visitor ID and your optional tag. The connection between a visitor ID and an account is a record you keep in your own systems.

How far back can I look up a device?

Events are readable through the API for 30 days. To connect accounts over a longer period, store the visitor ID with the account when it is created.

Can a visitor ID connect accounts across different products?

Only inside one organisation. All of your keys share the same visitor IDs, and no other Fingerly customer sees them.

[ IDENTIFY ][ UNDERSTAND ][ DECIDE ][ FINGERLY ]
Less guessing. More knowing.

Make the next connection a trusted one.

Start with the signals, keep your own decisions, and pay only for what you identify. No credit card needed.