Hi guys,
My company is a longtime user of Marketo. We are currently looking at re-implementing the way we have things set up and are curious if there is a concept of using multiple databases within Marketo? If not, we are wondering if there is a way to use custom objects to accomplish the same goal.
Our problem: We have several systems that use the same instance of Marketo. Sometimes, these systems are simultaneously used by those we are marketing to (the end-user). There is potentially a few issues. It is possible for our end-user to enter invalid emails upon the creation of a lead (let's say for example that they enter test@test.com). When another user enters test@test.com, both of our leads get tied to this test@test.com record in Marketo. These are actually not the same user and within Marketo, the two end up getting merged. Also, say that the user enters a valid email and exists in multiple systems. When we sync to Marketo, information that might be relevant to a Campaign in one system could potentially be overridden by a second system. Finally, when a user updates their email address, a new lead gets created within Marketo.
Questions: 1. Is there a concept of having more than one database instance in Marketo to help normalize the data that is being sync'd?
2. Is it possible to leverage Marketo Custom objects to achieve some separation of responsibility between the data for each system?
3. Is it a bad idea (or even possible) to leverage a field other than email address for syncing a lead using their SOAP API? (This would help us resolve the issue of updating email addresses)
.png)