The client's problem
A Meta Lead event is firing on every homepage visit rather than actual lead submissions.
My analysis
1
On santassecretworkshop.com, the Lead event does not fire «on every homepage visit»: I have verified it by analyzing browser requests to Meta.
2
In the homepage HTML code, fbq('track', 'Lead') is indeed present, but it is implemented incompetently: it is located above the loading of the fbevents.js script, which it uses → it never fires and always results in an «fbq is not defined» error visible in the browser console.
3
The numerous Lead events that you claim to see in Meta Events Manager are caused by a combination of the following poor decisions:
3.1
When a visitor first visits your website, a pop-up window immediately and intrusively demands a subscription to email spam.
3.2
The overwhelming majority of sane visitors, of course, immediately close this window by clicking the ✖ button.
3.3.
You have «automatic events» enabled in Meta Events Manager (they have been enabled by default since August 3, 2026); in this mode, Meta uses its dumb AI to guess what the user wanted to do.
3.4
In the §3.2 scenario, the dumb Meta AI makes a mistake: it classifies the ✖ click as SubscribedButtonClick; I have verified it by analyzing browser requests to Meta.
3.5
Therefore, by default, you should see numerous erroneous SubscribedButtonClick events (rather than Lead events) in Meta Events Manager.
3.6
Your claim that you see Lead rather than SubscribedButtonClick means that you have created a «Custom Conversion» based on the SubscribedButtonClick event in Meta Events Manager with the «Choose a standard event for optimization» option set to Lead.