Skip to content

A custom event's fully qualified name, used to send and read it, is `pe<hubId>_<name>`, so it differs per portal; its definition also gets an event type ID `6-<n>`. Key definitions on `name` or `objectTypeId`.

Documented and measured

Checked

Checked October 21, 2026 on a HubSpot developer test account
Checked October 16, 2026 on a HubSpot developer test account

Area

Tags

events, custom-events, name, event-type-id

More facts from this area

Custom behavioral events need an Enterprise subscription.Source pending
Dated (2026-09) custom event definition reads carry labels.singular and labels.plural, and no label.Source pending
A flow or list filter's eventTypeId equals the custom event definition's objectTypeId (6-<definition id>); HubSpot's own events appear as 4-<n>.Measured
Custom event property enumeration options are stored with their value exactly as sent.Source pending
A custom event defined on a custom object takes the object's short name as primaryObject. The object type ID (2-…), the portal-qualified p<hub>_<name> and the upper-cased name are rejected.Measured

Spriggit uses these facts when it plans changes. See something out of date? Email [email protected]