# October 2026 (3)

> The HowdyGo SDK now separates application user IDs from email, preserves partial identity updates, and recommends keyed installations.

## 🧩 SDK Viewer Identity

Use `externalUserId` for your application's user ID and `email` for the viewer's email address. Supply either field first and add the other later. Partial updates preserve the rest of the viewer's profile, and you can update an email while keeping the same external ID. [Learn more](https://docs.howdygo.com/distribute/sdk/identify).

Identity now follows a consistent priority inside demos: SDK values, native lead capture forms, personalization, then URL parameters. Automatic website capture preserves the external ID and email explicitly supplied by your app.

Identified Viewers continues to group by email. Parent-page and modal event callbacks now expose viewer email as `payload.email`. [View the event reference](https://docs.howdygo.com/integrations/custom-events).

## 🔑 Keyed SDK Installation

Use a publishable key from **Settings > Integrations > Tracking Script** for SDK installations. Keyless installations and legacy manual identification fields remain supported, with console deprecation warnings. The existing SDK URLs are unchanged. [View the installation guide](https://docs.howdygo.com/distribute/sdk).

## 🐛 Bug Fixes

- Partial identity updates no longer discard omitted profile fields, traits, or stored personalization values.
- Website forms can update a previously form-captured email after a page reload while preserving emails explicitly supplied by your app.
- CTA clicks can associate identity learned during playback with the existing viewing session.
- Viewer privacy settings consistently follow the demo's owning organization.
