Currently, GoHighLevel allows us to pass certain user properties (like {{user.email}}) in custom menu links and iframes. However, we lack access to a persistent user identifier like {{user.id}}. This addition would enable more accurate and secure integrations by allowing third-party systems to identify specific users when accessing external URLs or embedded content.

Why is this important?

Enhanced Security: Email addresses can change, but a user ID is a stable, unique identifier.

Improved Data Mapping: Seamlessly connect users in GHL with external systems, maintaining consistent records.

Simplified Integrations: Reduce the need for complex email-to-ID mapping workarounds.

Consistent Experience: Leverage {{user.id}} in both custom menu links and iframes, ensuring a unified integration strategy.

Since other user properties are already available, adding {{user.id}} should be a straightforward enhancement that would significantly benefit custom integrations.

For more information on existing user properties in custom menu links and iframes, refer to the documentation here.