Pass Leads Between Two Marketo Instances

As far as I'm aware, this isn't very easy to do. Maybe something with the API? But I feel like they wouldn't be pushing this as an easy-to-use feature because of the regulations around collection/storage of personal information as well as opt-ins, etc.

Technically it's possible - it would be ugly through the API. A simpler solution would be connecting to a data warehouse platform like Informatica. I am with Dory though, it isn't something you should want to do with opt-in and other regulations.

How far are you trying to lead gen for them? Can you just use a Form they build and place it on your websites? Are you going all the way to where you are ready to send them to a Salesforce instance?

Marketo -> Marketo sync should definitely be last resort and even then I would say don't do it.

You can, both simply and scalably, echo Marketo form data to two different Marketo instances at the same time.

I wouldn't push back on this the way Dory and Chris are. Truly *syncing* 2 instances --sure, that'll be painful and prone to errors and security vulnerabilities. Merely pushing form posts to 2 instances -- painless and, for situations like yours, powerful.

If you are looking to run separate forms the comments above would provide you what you need. There are some cases when a form by itself does not do the trick. That was the situation I was in before. In a previous life I had two instances of Marketo, (result of an acquisition) each tied to it's own SFDC system. We were not able to integrate or merge the SFDC systems and had to keep the instances separate. We also had to sync some leads back and forth between Marketo instances as we combined our websites for branding purposes. So One website, two Marketo instances each tied to their own SFDC system and our reporting/attribution running out of one instance of Marketo.

To sync information between the two instances we set up an API and Webhook process with a small server in-between. In our process we set up the main instance to call a webhook and pass our information to the external server. From there the external server would insert the lead into the other instance using the API process. If the lead existed already it would update the record. We had the exact same process to pass information back if needed. It took us a couple of hours to get the API and webhook process set up with the pass-through server but it worked like a charm afterwards. It was also set up to not have to go through the entire process again if we needed to add fields to the payload. We simply added the fields needed to the payload, making sure we had the API name of the field set properly in the payload.

Hopefully this helps.