Identification & Personalization

Tell HowdyGo who is viewing the demo and substitute personalization tokens with real values from your app. Identified viewers show up in the Identified Viewers dashboard.

identify(userInfo)

Tell the SDK who the current user is. The information is forwarded to every HowdyGo demo on the page.

howdygo.identify({
  userId: "user@example.com", // User's email
  name: "Jane Smith", // Display name
  company: "Acme Corp", // Company name
  phone: "+1234567890", // Optional
});

personalize(replacements)

Replace placeholder tokens in your demos with real values. See Personalization for how to add tokens to a demo in the editor.

howdygo.personalize([
  { token: "token1", value: "Acme Corp" },
  { token: "token2", value: "Jane Smith" },
]);

Setting both at once

A common pattern is to call identify() once after login, then personalize() whenever the values you want to substitute change.

howdygo.identify({
  userId: "jane@techcorp.com",
  name: "Jane Smith",
  company: "Tech Corp",
});
 
howdygo.personalize([
  { token: "token1", value: "Tech Corp" },
  { token: "token2", value: "Jane" },
]);

Listening for demo events

Subscribe to events emitted by the player.

howdygo.on("demo-interaction", (event) => {
  console.log("User interacted with demo:", event);
});

Advanced methods

These methods manage stored viewer identity and share the same plan gating as identify().

getStoredIdentity()

Get the user information currently stored by the SDK.

clearIdentity()

Clear stored user data.

setOptOut(true | false)

Let viewers opt out of identity storage.