We are trying to connect Skilljar to our Hubspot CRM through the integration, but on testing, we can’t get it setup to track correctly. I have followed these articles, and can’t figure out where we went wrong, or how to fix it;
I have setup custom events to trigger for registration and completion of courses through Skilljar. Registration works OK, but Completion events are triggering automatically on registration, and then firing again on course completion, thus duplicating results.
I have been through it extensively with Skilljar devs, and they say the javascript is firing correctly on their end, so it’s most likely something on the Hubspot end. Is there someone who might be able to figure out where we went wrong, and how to fix it?
For posterity, @pschuppe and I have corresponded directly.
We believe these issues are due to nested event JavaScript snippets.
Per this article, JavScript placed in the Custom JavaScript field of a custom [Enterprise] JavaScript event will fire with the HubSpot tracking code.
Thus, if you're already firing the event with the Events JavaScript API, your event may fire twice unless you've included extra logic in the Custom JavaScript field. See the screenshot below for reference.
I will mark this as the solution for now, however if Peter and I find a different cause, I will update accordingly.
I've reviewed the email chain with Skilljar; thank you for sharing it!
Could you could provide links to a few contacts showing multiple event triggers at the same time? I'd like to dig in a bit further! Feel free to send them to the email thread we have.
For posterity, @pschuppe and I have corresponded directly.
We believe these issues are due to nested event JavaScript snippets.
Per this article, JavScript placed in the Custom JavaScript field of a custom [Enterprise] JavaScript event will fire with the HubSpot tracking code.
Thus, if you're already firing the event with the Events JavaScript API, your event may fire twice unless you've included extra logic in the Custom JavaScript field. See the screenshot below for reference.
I will mark this as the solution for now, however if Peter and I find a different cause, I will update accordingly.