Curious to understand where you saw Clearbit as the issue - I want to know where to look if the issue persists.
In the Clearbit JS loader you can see the button click’s default action (that is, submitting the form) is aborted using preventDefault():
"g4bq": [function(require, module, exports) {
"use strict";
function e(e, t) {
var n = document.createElement("script")
, r = new URL(e)
, o = window.location.pathname;
r.searchParams.set("page_path", o),
n.setAttribute("src", r.toString()),
t && (n.onerror = t),
document.body.appendChild(n)
}
function t(e) {
e.preventDefault(),
e.stopPropagation()
}
Also just so I understand, how can I/do I stop Clearbit from loading is cookies are rejected? Unclear where to make this update.
I don’t use the CookieYes library so couldn’t tell you — usually there’s a way to change the script type to a data block, like <script type="conditionally/loaded" class="enrichment"> so that way the real script won’t be injected at all unless the matching cookie type is accepted. Your JS dev should be able to figure that out quickly.
.png)