Integration Help. I'm desperate :(

[Anonymous]

Hi All,

We are having a huge problem on our duplicate and one of the source that we have notice is that.

We have a Portal Account(third party form) and when they register they are sync firms on salesforce as (contact or person account) then sync to marketo.

And if the record sign up first on marketo forms like free trials. A record will be created first at marketo then will remain in marketo until it reach our threshold.

That is why we have a huge problem on our duplicate.

Because if they sign up first on marketo form (a record will be created on marketo only because they have not reach or threshold) and for example they sign up on our portal the sameday they will have a new record on salesforce either person account or contact.

We have a lot of combination of duplicates.

Marketo only records and SFDC Person account

Marketo only records and SFDC Contact

Marketo only records and SFDC Lead

Any suggestion would be greatly appreciated.

And also what do you think  about our portal form wherein all prospect will already become a contact and person account without being lead even tho they don't have any engagement?

Note: They told me before that a contacts are the one who are already qualified by our inside sales to have an opportunity or will be useful soon. but they created a portal account and now our list of salesforce contacts are 98% unqualified most of them don't even have any engagement just sign up and will never go back

Thanks,

Jas

[Anonymous]

Hi,

Maybe you'd like to put some credits on my idea, too?

I have a problem with de-duplication, too.

I used before IBM Marketing Cloud where you're able to de-duplicate any field you like.

It was very easy and comfortable to figure out duplicate contacts with custom fields or combinations of it.

For e.g. customer number or contact ID of your CRM system.

Best Johanna

[Anonymous]

Jas,

To associate your SalesForce lead or contact with the Marketo person, you'll need to be able to pass their Munchkin ID to the portal and get them to store it into a SalesForce field. Do you have any control over the portal?

We also have leads / contacts being created in SalesForce from another source. Luckily I was able to get them to store the Marketo Id into a SalesForce field. Digital Pi helped me out with code to associate the SalesForce lead/contact with the Marketo person to stop our duplicate problem. It also let me preserve the record of how these people were getting to our site (ads, social, etc.) for our reporting.

Good luck!

[Anonymous]

Thanks Sharon,

I am already asking our salesforce admin about this.

This is really helpful thank you

Ron

[Jep_Castelein2]

Hi Jas, while it would be ideal to prevent duplicates from being created, in reality this is not always possible. It sounds like it will be hard to prevent duplicates in your situation. Marketo has developed an ongoing deduplication solution that will merge duplicates almost immediately after they are being created. This is the successor to the Marketo EasyMerge service, which can only do one-time cleanup, not ongoing. Your Customer Success Manager can tell you more about the new deduplication solution.

[Anonymous]

Hi Jep,

I will create a ticket to learn more.

Thank you so much Jep

Ron

[SanfordWhiteman]

As long as you continue to have competitive "sources of truth" you won't be able to solve this (except partially by using a 3rd-party dedupe tool).

Even syncing all SFDC to Marketo -- while better than what you have -- won't be a complete solution because a Marketo form could create someone in the interim period before the next SFDC sync. If your source forms are closely linked on your website such that someone could easily hop from one to the other, this'll still be a problem.

From the description you've provided, it sounds to me like you should standardize on SFDC as the source and stop using Marketo forms.

[Anonymous]

Hi Sanford,

i appreciate your prompt response to this matter. I haven't really though about usign one form only by sfdc which is I think i could also ask them about it.

Thanks alot Sanford

Regards,

Ron

[Eric_Hollebone1]

Hi Jas/Ron

Sanford is correct until you have control over your entry points in getting form data into Salesforce, then you will continue to have duplicate issues. However, if you would like to align your web history in Marketo and use Salesforce as your form entry point, you might consider trying a process something like this which I call Marketo connect that links the SF record by via munchkin cookie to its anonymous record in Marketo:

It also supports deduping tools as long as they respect Salesforce custom objects when updating either the lead or contact ids. This has been tested with CRM Fusions DupeBlocker offering.

In considering this type of solution, you really need to be sure that the effort of tying all these pieces together is worth the return. This is not a simple solution but it prevents the duplication problem between Marketo and Salesforce when using non-Marketo forms that send the data to Salesforce.

Contact me directly if this is interesting to you.

Cheers,

Eric

[Anonymous]

Hi Eric,

Wow that's a great diagram.

This is super helpful. Will show this to my manager and would contact you directly after i get a feedback.

thank you so uch Eric

Thanks,

Ron

[SanfordWhiteman]

Calling the Munchkin API from a webhook is how we do this. I would never use the Marketo REST API for this application, as you create an DoS vulnerability against all your integrations just by having somebody fill out your forms. 

[Eric_Hollebone1]

This is a high-level conceptual diagram and I purposely did not get into the details of the data exchanged or rates. The various connections in this process are asynchronous and data-driven in nature due to race conditions brought about by the design of both the Marketo and Salesforce platforms and the Marketo CRM sync. A fact, I have put that to good use in a couple of implementations.

Further, this process cannot be accomplished solely using Munchkin. It must use REST/SOAP for the merge function. Even then, the REST API is executed from within a controlled Salesforce environment and is rate-limited by several factors and the payload data is sanity-checked for injection and buffer overload before use. There isn't a DoS vulnerability created by this process.

[SanfordWhiteman]

Further, this process cannot be accomplished solely using Munchkin. It must use REST/SOAP for the merge function.

Munchkin's Associate Lead accomplishes the same function with no REST/SOAP utilization. We execute a webhook when the lead has synced to Marketo for the first time and when there's been a change (i.e. addition) to the lead's cookie history.

While it's true that webhooks themselves don't have unlimited capacity, the practical daily count is far higher than the REST max, and we can rest assured that our API integrations won't ever be affected by end-user-driven activity.

There isn't a DoS vulnerability created by this process.

Are you making sure that this application can never step on the API calls used by all your other integrations?

To be clear, it's not about buffer overload or other security concerns -- just a matter of how many of your Marketo API calls I can use by posting to your endpoints repeatedly, and whether I can do this in such a way as to quench the limits either of this app or of all your connected apps.

I understand there may be a cap placed by one or more of the other tiers of the architecture, in which case the Marketo API is protected in turn.

[Josh_Hill13]

Hi Eric Hollebone​ how are you?

Great diagram.

[Liz_Medeiros1]

Hi Jas,

As you pointed out, it might be a good idea to sit down with your sales team and decide what happens to your portal signups... it might make more sense to have them created as leads, rather than accounts and contacts since they need to go through a qualification process. Also, when your leads signup via Marketo, maybe it would make sense to sync them over as leads earlier. That way if they also sign up for something via your portal, they are already in the database.  There are several AppExchange tools that can help you manage duplicates like DupeCatcher, DupeBlocker, etc.

Best,

[Anonymous]

Hi Liz,

I have been askign them about this question. And It guys just told me that leads can't have a portal accoutn only PA and Contact. I am also thinking of suggesting synching them all but we have millions of marketo only records. I don;t iknow how can it affect us regarding on cost or on IT side.

Thanks,

Jas

[SanfordWhiteman]

You literally have millions of Marketo-only leads that aren't aging out? That sounds pretty strange to me.

[Anonymous]

Hi Sandord,

Thank you for this reply. Well yes. Most of them are the leads from our previous marketing automtion platform. we just imported it. I really want to delete those records specially most of them don't have any activity and they are on our deadbase. They don't want to delete those record because they ask "WHAT IF THEY WILL COME BACK". We have 3 million marketo only leads and most of them are not being nurture since they are on deadbased. If only we could delete that and maybe we can sync all records.

anyway thanks and can I also ask about your opinion about what do you think about our IT making prospect a Person account/contact already after signing up on our account?

Thank you so much!

jas

[Josh_Hill13]

• Sync all records
• Install deduping system on both ends (RingLead, LeanData, or whatever)
• Consider having the Portal send data to Marketo API instead of SFDC. But I don't understand your current use case, so you'd really have to map that out before you do so.

[Anonymous]

Hi Josh,

i appreciate your prompt response to this matter,

I am also thinking of the same just like what you have write on your marketing rockstar guide and just put those unqualified on queue but the problem is we have millions on marketo only record. How can it affect our cost of storage on sfdc?

We are currently using dupeblocker and dupecatcher but it can only be use if they are already in sfdc.

I will try to look for that marketo API since We are b2c and b2b I don't know yet how can it affect our software portal account and if they both a license for our software or webstore booking ect. But this is noted. Thanks Alot Josh

Thanks,

Jas

[SanfordWhiteman]

Marketo API won't help, only hurt. The complex routing you're doing needs to happen in SFDC.