Are you sure you want dupes and not just field blocking on certain fields?
You can have Marketo turn off deduping, but it is not recommended. You could also push the leads through another system to SFDC where they would not be deduped necessarily.
Do you want to keep the multiple submission values for one field ? Many fields ?
The simplest way it to use some workflow in SFDC that collect all the infos you want to keep and write them in another long text, concatenating with previous entries, together with a date.
When you will look at this field, it will give you all the submissions, by date in ascending or descending order, depending on how you do the concatenation.
You can also vote for this idea : Flow steps to create/update/delete custom object instance
We have one form with many fields that we want to keep with the submission.
What kind of information is this form collecting?
In general, creating duplicate records is a really bad idea unless the duplicates are intended to be handled by distinct teams. It sounds like maybe this is part of some kind of survey? If so, I recommend checking out launchpoint.marketo.com. The SurveyMonkey integration is good for that.
Otherwise, you might consider having a custom form, and using the REST API to make a record of a custom object in Marketo:
Custom objects have a many-to-one relationship with leads, so you could have multiple custom objects associated with the same lead.
Keep in mind that would require the assistance of an experienced developer, and it's not something we in Support can help with
We are capturing information that would go to the sales team. The entire submission would need to go to SFDC. But the person could do multiple submissions each with different information for the sales team.
The information will be deduped after reaching SFDC.
We were thinking of allowing every submission to go to SFDC even if it were duplicates and allowing the sales team to sift through the information because there will be some pieces of the submissions that actually different.
1 of 1 people found this helpful
We need to better define what you are hoping to achieve because I suspect Greg's recommendation for concatenation and using that with Tasks for each submission is FAR better, less resource intensive, and less complicated than purposeful dupes.
Can you share with us the workflow you hope will happen from the Form itself (what's on this form that would be different each time?) to what Sales is expected to do?
Why not create a task for each submission using the flow step Create SFDC Task?
Like the other guys, I feel -- so far -- like this is a really strange reason to create duplicates. It's the same human and the same sales owner?
We're trying to allow duplicate leads from a certain form as well. A lead could use the same email address and be viewed as a new lead and be sent to SFDC as a new lead each time. The reason we want to do this is because our users commonly have separate stores, and every time they fill out the form to sign up for the product it needs to be viewed as a new lead.
Will I be able to do that with the link you provided above that I've included below?
Nicole, multiple custom objects still wouldn't constitute multiple leads in SFDC.
If you want to remove the email address as the primary identifier, you should still figure out what data points make up a "compound primary key" for your ecosystem. For example, if someone enters the same store twice, that shouldn't be a new lead: the same store+email is the same lead. So you need to figure out how to identify store+email. How would you uniquely identify a store (if that is even possible)?