Event Hook Firing Twice May Have Resulted in Inaccurate Data

November 22, 2016 Uberflip Customer Success

Basic Information

  • 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.

Please contact support if you have any questions.

Previous Article
February 10, 2017
February 10, 2017

A list of fixes and updates that were released during the week of February 10, 2017

Next Article
January 26, 2016
January 26, 2016

Multiple Fixes include for Canonical URLs and Stream RSS Feeds