Need suggestion for ReCaptcha 3 threshold configuration

[ids]

I ended up creating a ticket. I'm not sure anyone would have been able to help.

Found out that the client's version of Shadows was old enough that it's not automatically compatible with ReCaptcha 3. Some template changes will need to be made. (I still need to do that.)
One conclusion I've made, If you're not on the latest Shadows or have a different them you may need to modify templates so the Action triggers ReCaptcha properly.

The other aspect, I don't recall an answer if there was a way to specifically test that it was working.

Scott

[William Davis]

My client doesn't get a lot of customer creations, but, appears to have been attacked where thousands of accounts were created. IMO, A setting of 0.0 really won't help Google build a history for this. So I am not clear where the value might be effective and minimally intrusive to the customer of the store.

But also, I'd to make sure the module it's functional for the action we're listening to. Could I set the threshold at 1.0 for testing? When I tried this, I did see the default Alert from the module that the action could not be run at this time. But, setting it to 0.9 still didn't check that the user was a human.

Scott

Wow, no one ever replied.

[ids]

My client doesn't get a lot of customer creations, but, appears to have been attacked where thousands of accounts were created. IMO, A setting of 0.0 really won't help Google build a history for this. So I am not clear where the value might be effective and minimally intrusive to the customer of the store.

But also, I'd to make sure the module it's functional for the action we're listening to. Could I set the threshold at 1.0 for testing? When I tried this, I did see the default Alert from the module that the action could not be run at this time. But, setting it to 0.9 still didn't check that the user was a human.

Scott