Browse the docs

Identify signed-in users

Attach a verified user ID, email and name to every report from people signed in to your app.

Identifying users is on the Enterprise plan. When your app runs the widget for signed-in people, your server can sign a short-lived token that says who they are. The widget sends it with each report, and FeedbackDots checks the signature before it trusts the identity. Reports from identified users show a Verified badge, carry the user ID and attributes you sent, and the widget hides the name and email fields for them.

The token only proves who filed a report. It grants no access to FeedbackDots or to any data.

Set it up

  1. In the project's settings, open Capture → Identify signed-in users.
  2. Click Create secret and store the fdid_… value as a server environment variable. It is shown once.
  3. Set the mode to Verify when present and save.

Sign a token on your server

The token is a JWT signed with HS256 and the identity secret. Any JWT library works. In Node with jose:

import { SignJWT } from 'jose';

const secret = new TextEncoder().encode(process.env.FEEDBACKDOTS_IDENTITY_SECRET);

export function feedbackDotsToken(user) {
  return new SignJWT({ email: user.email, name: user.name, attributes: { plan: user.plan } })
    .setProtectedHeader({ alg: 'HS256' })
    .setSubject(String(user.id))
    .setAudience(process.env.FEEDBACKDOTS_WIDGET_KEY)
    .setIssuedAt()
    .setExpirationTime('1h')
    .sign(secret);
}
ClaimRequiredMeaning
subYesThe user's ID in your app, up to 255 characters.
audYesThe project's widget key (the data-key in the snippet), so a token for one project fails on another.
iatYesIssued-at time.
expYesExpiry, at most 24 hours after iat. One hour is recommended.
emailNoUsed for the "fixed" email, in place of anything typed in the widget.
nameNoDisplay name.
attributesNoUp to 10 string or number values, such as plan or company. Keys up to 40 characters, values up to 200. Anything else is dropped.

Only HS256 is accepted.

Pass it to the widget

Add this after the widget script. The stub queues the call, so it works before the widget has loaded:

<script>
  window.FeedbackDots = window.FeedbackDots || { q: [] };
  FeedbackDots.identify =
    FeedbackDots.identify ||
    function (t) {
      FeedbackDots.q.push(['identify', t]);
    };
  FeedbackDots.identify('TOKEN_FROM_YOUR_SERVER');
</script>

Single-page apps call FeedbackDots.identify(token) after sign-in and FeedbackDots.reset() on sign-out.

Without a backend you can call FeedbackDots.identify({ name, email }) with plain values. That fills in the form for the user, but the report is saved as unverified.

When a token is rejected

A missing or invalid token never blocks a report: it arrives as an ordinary, unverified report. The reason for the last rejected token, such as an expired token or the wrong audience, is shown in the project's settings.

In the API and webhooks

Reports carry reporter.verified and reporter.id (the token's sub) in the REST API, the MCP server and webhook payloads. In the dashboard, searching the reports list for a user ID finds that user's verified reports.

Rotating the secret

Rotate secret creates a new one. The old secret keeps verifying tokens for 7 days, so you can deploy the new one without dropping identities.

Privacy

You are the data controller for your users' identities. Only sub is required. Email, name and attributes are optional, and all of it is deleted with the report. Mention in your privacy policy that feedback reports include the signed-in user's identity.