- Problem: Hubs.onCtaFormSubmitSuccess event hook was firing twice.
- Timeframe: October 27th - November 18th, 2016
- Impact: Third party platforms may have inflated or duplicate results
- Status: Fixed
Last week our team discovered a bug that caused the Hubs.onCtaFormSubmitSuccess event hook to fire twice. The problem started on October 27th (the day a production update was released) and was fixed on November 18th.
Any code using Hubs.onCtaFormSubmitSuccess fired twice, because of this bug. Typically this event hook is used in the Custom Code section, and can be applied to pass information to third party platforms such as Google Analytics or Bizible.
If your team has used this event hook to send submission data to a third party, you may notice a spike, or duplicate information, in data collected between October 27th and November 18th.
What To Do
Customers using the Hubs.onCtaFormSubmitSuccess event hook should check the data collected by the third party for any information that looks incorrect or suspicious.