Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Thanks for the response, Greg. We use various custom objects ranging from transactional nature (e.g. order history) to a reference table (e.g. onboarding status). The dedupe fields are usually a custom row ID with the link field either being email address or SFDC ID.As for the scripts, some are #for...
As we continue to try and roll out Related Contact functionality, we still have an issue with duplicates in Marketo--mostly leads and contacts with matching email addresses. Normally for basic batch campaigns this isn't a big concern (besides some attribution and reporting issues); however, for emai...
We ended up creating a Marketo custom object which is updated via the API whenever a new 1:N relationship is added in Salesforce. It's incredibly flexible and useful but becomes an issue if you rely on Velocity Script to populate emails via (because of duplicate records).
A question I'm sure Kiersti Esparza may be familiar with.
Removing the .get(0) or checking to ensure there's no duplicate record with a matching email address are two steps maybe to try as well.
From experience, Marketo's ability to trigger off-of Account updates isn't 100% reliable. However, batch campaigns are more accurate when qualifying records based on Account-level fields. Currently we're facing issues with Opp constraints preventing triggers from working but yet batch campaigns work...
This is a big use case for Uber. In a restaurant Franchise model, Contact1 could own 5 different locations. Thus we "related" Contact1 across 4 other Accounts. We have a Contact Account Relationship custom object which allows us to bring back some 1:many Account 2 through 5 fields but isn't feasible...
Hi John Mattos,Do you know how to bulk delete via REST API? Pasting all the different marketoGUID's or dedupeFields I want to delete seems really painful. Is there a wildcard or another way to delete in mass?
Thanks for the tips, Sru. Actually ended up using a similar constraint on the custom object (a date field). I think your additional 2 recommendations will help narrow things down should this design also lead to poor performing scripts. I'll post back once we have some more testing under our belt.
I've already tried using similar unique qualifier. The issue is, Marketo's smart list aren't only bringing back that record--it brings back the oldest version of that record. One thing I can try testing is if a duplicate record is created, backdate the Created Date on the record I want to tie the cu...