topic Re: Custom Behavioral Events in Dashboards & Reporting

Custom Behavioral Events

CreatoChris — Fri, 10 Mar 2023 13:40:40 GMT

So we have the following problem. We are using "Segment" to track the behavior of our users and store all in-app events into it. Basic stuff like what features are used, where they are clicking what they are using, etc. So these events have custom attributes for us (HubSpot is calling them properties but in fact they are attributes). For example, all of the things created in our platform have a unique identifier called a "hash". So the fun begins, going into Reports>Analytics tools> Custom behavioral events and here I have the possibility of creating a custom event. I create the event and then go into property mapping where Hubspot tells me they have a default mapping that tracks 32 properties.

My question is, can I access that default list somewhere or create my own list of custom properties that I can assign to events? or do I have to manually create and assign the properties to each event? We have a lot and that would mean, days of manual labour to create each event, and also create the property that I need to assign to them.

Attached an image for reference.

It would be great if we could somehow save the properties to apply them as we create the events.

Hopefully, I am missing something and I won't have to do intensive manual labor.

Thank you!

Re: Custom Behavioral Events

PamCotton — Fri, 10 Mar 2023 22:00:42 GMT

Hello @CreatoChris happy Friday!

I want to invite our top experts to help @Josh @franksteiner79 @GuyTaylor any recommendations for @CreatoChris matter?

Thank you,

Pam

Re: Custom Behavioral Events

CreatoChris — Mon, 13 Mar 2023 10:22:16 GMT

We have since discovered that we can pull these properties as raw metadata and it will be displayed as a string of characters. It's not great but it works. We can't use these in reporting though but luckily we don't need to.

It would be great if hubspot would allow you to save attributes for my custom behavioral events so that we can apply them directly. Currently each attribute(property) has to be created individually as a string for each custom event. Kinda hard when you have over 100 events each with 2-5 attributes.