Sandy, what would we need to do to create/configure something like this on our own server? Might be a good blog topic for http://blog.teknkl.com/.
Hi Sanford Whiteman - circling back on this, would this be complex to create/configure on our end? If you can detail out the requirements, that would be great.
Do you currently use AWS? Or is that prohibited due to the MS connection?
I wouldn't have an applicable recipe for Azure -- just AWS CloudFront or IIS w/ARR + URLRewrite (in the latter case, anyone who knows ARR would already know how to do this).
I created the 'localhost' duplicate solution you are using in 2011 and it has always been an unsupported solution. However, it has worked successfully ever since. The '302' response is the expected response. It is because the Form is trying to redirect you to the thank you page. There may be a delay in the new record showing up in the search due to the indexing delay. It is fine to use this solution as long as it works, but indeed, if anything goes wrong, support won't be able to help with this.
It would be a better solution solution to use a Webhook to call a proxy service outside of Marketo, which then creates the new Lead record in Marketo using the REST API. Azure Functions would be an ideal environment to build such a service (Azure Functions—Serverless Architecture | Microsoft Azure ). Potentially even better is to add the Lead to a Static List and have the external service poll the List. This is more scalable and allows for better error handling and retries.
Nevertheless, based on the write-up above I am not sure that anything is going wrong in your setup. The 302 message is expected and the Lead not showing up in the search could be due to indexing delay, If there really is a Lead visibility issue, it should also occur with Leads created via normal Form submissions.
Hope this helps.
Hi Jep Castelein - appreciate your reply here. We learned a while back that the 302 message was not an actual error. But what we found was that there were certain leads that didn't get duplicated - even though they qualified for the trigger campaign that kicks off the process. Who knows - maybe it was one of the issues with trigger campaigns - and not the webhook - but nevertheless, the duplicate didn't get created. There was no pattern or timeframe - completely random/inconsistent.
To be on the safe side, it's probably best that we develop a more scalable, reliable and supported approach. We have some professional services hours that we need to use before the end of August. Do you have the time (and be willing) to help build this solution? I have a call with our internal team next week - to see if it's something they can support. But they may not be familiar with Marketo or working with the API. Send me an email if you want to discuss further (email@example.com).
Have the same problems stated here and we use MSD 365 online:
1. we create lead duplicates via webhook
2. are seeing the error 302
3. duplicate lead email address is missing in Marketo and CRM
1. How to check if the webhook is working?
2. 302 error, not a problem? is this still true?
3. Any answers for the missing email address?
Would really appreciate if you could share any better solution you found in these years.
Thank you for sharing the details.
302 is the expected HTTP response code from the forms /save endpoint. Not an error.
Do you also have a SC running to change the email address? Please show your whole setup.