widget.visitor.identified

​

Payload

{
  "id": "whd_7Gx2dR5nM",
  "event": "widget.visitor.identified",
  "createdAt": "2026-09-11T13:05:02.884Z",
  "data": {
    "visitorId": "wv_5Hc2pR",
    "name": "Ada Lovell",
    "email": "ada@ravennafoods.com",
    "phone": null
  }
}

​

Worth knowing

• The details are self-reported. They are whatever the visitor typed, and nothing checks them. Treat email as a lead rather than a verified address.
• Every submission fires it, including one that repeats details the visitor already gave.
• A blank answer keeps the earlier value. Only the details the visitor filled in are written, so a detail given earlier stays in the payload.
• Verified visitors never fire it. A visitor your site signs in through widget visitor identity carries details your server vouched for, and the widget refuses to overwrite them from the visitor’s side.
• No conversation id. The details belong to the visitor across all of their chats. Match visitorId against widget.conversation.started to connect the two.

​

Example

custral.on("widget.visitor.identified", async (event) => {
  const {visitorId, name, email} = event.data;
  if (!email) return;

  await marketing.upsertLead({
    email: String(email),
    name: name ?? undefined,
    source: "website-chat",
    visitorId,
  });
});