See Behavior Event Tracking Tags/Target

[MGoswick2]

Maybe I'm missing something, but in the old events tracking tool, you could edit and update events, as well as see what the current event was tracking (i.e. if you selected "Clicked Element", the next screen showed you the ID/Class/Jquery selector currently being used), but it does not seem that is possible with the new events tracking tool. I imagine this has to do with the new structure of the tracking tool, but if HubSpot is creating event listener JS that is placed in the tracking snippet, then that should be accessible somewhere to review/edit. Is there any way within the new events tool to see what is actually triggering the event, so see all events currnetly on a page?

[kvonloesecke]

Hi @MGoswick2,

Thanks for reaching out!

I wanted to add our experts to see if they have any advice.

Hi @danmoyle, @NicoleSengers, @Mike_Eastwood, @himanshurauthan - Do you have any recommendations for @MGoswick2?

Thank you!

Best,

Kristen

[danmoyle]

Thank you for the tag @kvonloesecke. I'm not as familiar with the behavioral events as I should be. Sorry @MGoswick2 but I don't have an answer. Maybe another of our awesome community members will! 

One quick addition - if this is something that changed, I might look at the ideas forum to see if others have asked to bring it back. Or you can submit the idea and see if others can upvote it. 

[MGoswick2 · Accepted solution]

Figured out how to at least see the list of events (although it seems it cannot be updated without using the API, only deleted and recreated), so posting the answer in case someone else runs into this issue.

When you place the HS tracking code and use the new custom behaviors, there will be a script placed https://js.hs-analytics.net/analytics/[server-ID?]/[portal-ID].js 

Within this script, it will list all events at the top as _hsq.push events. Those events will contain the targets, as well as the name of the event. 

[kvonloesecke]

Hi @MGoswick2,

Glad to hear you were able to resolve this!

Thanks for sharing the solution with the Community 🙂

All the best,

Kristen