Marketo to Marketo Webhook | Adobe Higher Education
Skip to main content
Chris_Turille
Level 2
December 7, 2021
Domanda

Marketo to Marketo Webhook

  • December 7, 2021
  • 1 risposta
  • 4511 visualizzazioni

Hi all. We are in the process of creating new instances based on region. However, we would like to be able to share leads that may find themselves in the wrong instance. Say if someone in America fills out an APAC form and vice versa. It seems like would be able to set up a webhook and push the the correct instance based on country or region. Or even a custom API. 

 

I would love to hear the best way to do this. I did see an article referencing form fills for this reason, which is great. I just was not sure the correct url (soap API), etc.

 

Thanks!

Questo argomento è stato chiuso alle risposte.

1 risposta

SanfordWhiteman
Level 10
December 7, 2021
Are you specifically talking about form fills as the method of lead creation? Because you don’t need server-side work to detect that they should’ve filled in another form based on country (and post that form in the background instead). That can be done on the client side which is far better..
Chris_Turille
Level 2
December 8, 2021

Mainly, yes. Basically we will as a company now have more than one instance. One instance will host our North America and Asia database. We will be standing up another instance just for Europe. Sometimes Someone in Europe fills out a Form hosted in the Amer/APAC instance. The idea is to get that lead over to the Europe instance into their database for their use. All the same company though. Just 2 Marketo instances. If that helps.

SanfordWhiteman
Level 10
December 8, 2021

I would definitely handle this on the browser (JS) side — submit the form to the other instance if someone’s data means they should’ve been on the other instance. This is far, far easier than building & managing a service to forward the leads to the other instance (and delete the originals).

On the other hand, if you must cover other cases beyond form fills, you will need that service, so you would standardize on that (and not build the client JS) if so.