How to call reCaptcha Webhook in less than 2 minutes | Community
Skip to main content
Pavel_Plachky3
Pavel_Plachky3
New Participant
February 7, 2020
Solved

How to call reCaptcha Webhook in less than 2 minutes

  • February 7, 2020
  • 1 reply
  • 4807 views

We implemented reCaptcha with Marketo forms, but are struggling with Marketo performance. After the form data is submitted to Marketo, a webhook has to be called that requests validation of reCaptcha fingerprint and email address. Unfortunately the webhook has to be called within 2 minutes, otherwise reCaptcha returns error "Timeout-or-Duplicate".  For a few leads (perhaps 10%) Marketo calls the webhook more than 2 minutes after the form fill. In the activity log I can see that at 4:30 the form was filled and at 4:32 the webhook was called, apparently too late:

 

 

I already tried to increase the priority of the campaign by a few tricks:

* Simplest smart list as possible (Person is created by form fill-out, form name is not specific form)

* Include send email in the flow

 

The campaign indeed runs as the first on a new lead, but still sometimes it takes more than 2 minutes for the webhook to be called.

 

I cannot believe I am the only one running into this issue. Did anybody implemented reCaptcha successfully and solved this problem?

 

Many thanks for any suggestions.

 

Pavel

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

I've had to struggle with persistent delays in one Marketo instance that I couldn't work around directly (as you can imagine being the "pioneer" of reCAPTCHA w/Marketo I've rolled it out many times). 

 

In that case, it wasn't a question of overall load or db size, and every other action depended on the Webhook is Called response (which is the correct order-of-operations). Just a very slow instance for whatever historical reason. So we had to do something, er, pretty special. We set up a separate endpoint to which the reCAPTCHA user fingerprint was also sent before the Marketo form submission. That separate endpoint checked Google (always instantly) and kept a log of successful fingerprints (the db itself timed out each entry after an hour, but that was just to keep the db clean). Then the Marketo Call Webhook checked the intermediate server at its relative leisure, instead of checking Google.  That setup is still up and running, so I know it can work.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
February 7, 2020

I've had to struggle with persistent delays in one Marketo instance that I couldn't work around directly (as you can imagine being the "pioneer" of reCAPTCHA w/Marketo I've rolled it out many times). 

 

In that case, it wasn't a question of overall load or db size, and every other action depended on the Webhook is Called response (which is the correct order-of-operations). Just a very slow instance for whatever historical reason. So we had to do something, er, pretty special. We set up a separate endpoint to which the reCAPTCHA user fingerprint was also sent before the Marketo form submission. That separate endpoint checked Google (always instantly) and kept a log of successful fingerprints (the db itself timed out each entry after an hour, but that was just to keep the db clean). Then the Marketo Call Webhook checked the intermediate server at its relative leisure, instead of checking Google.  That setup is still up and running, so I know it can work.

Pavel_Plachky3
Pavel_Plachky3Author
New Participant
February 11, 2020

Thanks, Sanford, for sharing this experience. I very much appreciate it.

Terms & ConditionsAccessibility statement

Loading footer...