Forum Discussion
Error to implement recaptcha v2 in Customer Insights - Journeys
Hello community, I currently have a persistent error. I have several forms in Customer Insights - Journeys, and a few days ago I configured reCAPTCHA v2 (check) on one of them. After that configuration, the other forms stopped working, showing this error when submitting the form. The actions I’ve taken so far include removing the reCAPTCHA configuration; however, the error persists.
Failed to create/update target entity: reCAPTCHA validation failed.
4 Replies
- mickel98Copper Contributor
thanks for sharing
Hello FJHF1998, it seems that reCAPTCHA is enabled at environment level.
When you turn on a custom reCAPTCHA v2 for one form, the platform expects a valid reCAPTCHA token on every form submission. So other forms that don’t send g-recaptcha-response start failing with "reCAPTCHA validation failed", even if you later remove it from a single form.
You should fixing the proble with one of this options:
- Fully disable reCAPTCHA globally in Form settings, then republish the affected forms/pages, and retest with a hard refresh/incognito.
- If you want reCAPTCHA, add it to all embedded forms so every submit includes a valid token.
In short: it's not per-form; it's a global toggle, so either switch it off everywhere or implement it everywhere.
Let us know if it runs fine.
- FJHF1998Copper Contributor
Thank you for your help, it's just that at the end of the steps the goal was not achieved and the problem persists.
Thanks for the update.
If the issue persists after removing reCAPTCHA from the form, it usually means the reCAPTCHA flag is still active at environment level.
A few things to double-check:
1. Ensure reCAPTCHA is fully disabled in Customer Insights > Journeys > Settings > Forms, with no site/secret keys configured
2. Republish all affected forms and pages (not just save)
3. Verify the embedded HTML no longer loads the Google reCAPTCHA script and that a fresh embed code is used
If even a newly created test form fails, this indicates an environment-level issue that typically requires Microsoft Support to reset the reCAPTCHA state.
Hope this helps.