Resurrecting this old thread.   I recently changed jobs and inherited an instance of Marketo and its challenges.  We have an issue with lead duplication.   First off, we do allow purposeful duplicates in SFDC and Marketo as a way to indicated multiple product interests.  This isn't something I'm going to be able to change.   However, here's my user story: I was asked to look into why we're getting dupes from APIs.  Most of these are quite old so it's really difficult to know what was going on at the time, but I see some records where a person was created in Marketo via SFDC in like 2015.  Then in 2017 it looks like a duplicate (based on email) was created via an API.  I have no clue which API created it, who wrote the API, etc.     @SanfordWhiteman - if I'm reading what you wrote above correctly, there's a setting or method for writing an API call that will check to see if the record exists prior to upserting, and if that method/call/procedure isn't used correctly the API will default to an insert regardless of whether or not the lead already exists. ... View more

Yeah, and my suggestion is that they look for a way to fix it. ... View more

And now I see that this has been proposed as far back as 2011.   Apparently this isn't in their roadmap. ... View more

We see problems often around this time of year when new campaigns are being created in SFDC and perhaps it wasn't set to In Progress before lead routing was set up, or when existing programs in Marketo haven't been updated to route leads to In Progress campaigns in SFDC and failures occur.  Likewise, something SFDC updates might change a setting that causes leads to not sync over.  We have to manually hunt these down and it's time consuming and inefficient. ... View more

Is this still the case or is there an update? ... View more

Tagging Stephen Usher​ ... View more

Channelling it through my internal team but wanted to see if there was anyone knowledgeable about it already in here as I know we've never discussed it. ... View more

I'm involved in a project for Germany where we have to do the double opt-in vs the parts of europe where the double opt is not mandatory.  My concern is over how this will be judged. Suppose someone purposely enters an bad email address either directly into my form or into a tradeshow that then passes that bad data on to me. I catch it and re-enter it, corrected. (For example, then ended their email address with .dx instead of .de). And now, a fresh record with no bounce on it exists in my database. I now send them the double-opt in email. Could this be used against my company in any legal way? I'm wondering if there are loopholes in this law where unscrupulous firms could try to draw other companies into violations. ... View more

I'm thinking about it from a GDPR perspective. ... View more

I'm unfamiliar with the filters you mentioned ... View more

Recommended Reading:The Seven "Oops" email moments you will have with Marketo ... View more

There are a few reasons why this isn't very feasible. Let's start with stating the obvious, that an email is really just a text file shipped from one ESP to another, routed to your user account and stored there. The emails are received regardless of who they're from - there's no middle-ware gatekeeping the email from shipping from one box to another. Once it arrives, the ESP chooses what to do with it: deliver, block, or move to a folder (ex: Spam). There's some validation done to see if it's really from that sender (DKIM, DCAR) but in reality most emails are received unless the IP sending it is blocked. Now you have the email somewhere in your email program, be it an inbox, spam folder, etc.  Most email programs then take the step of downloading it to your device so you have it for off-line reading. This is one MAJOR barrier to recalling. You can recall, but I'm on a plane not connected to internet. I'm going to receive that message. Another reason is that, as you know, anyone can say that an email is from anyone else. Any one of us here could quite easily send, for example, your mom an email from your email address and she'd be none the wiser. Because there's no REAL credential matching and because Marketo is often used to send emails from different email addresses, there's no way to know that the request to delete the email is real. For such technology to work, you'd need a way to verify to my email service provider that you delivered the email and that you want to delete it. As stated earlier, an email is nothing more than a text file delivered from one IP address to another and in many cases a person can switch IP addresses at any point in a day so there's no way to certify that you're authorized to delete it. Now, these two come down to a MAJOR security no-no, which is authorizing a system to remotely delete files from a device without authorization. If technology existed (and I'm not saying it doesn't...) that would allow me to access storage on your phone and choose to delete a file without your consent then what's to stop the Evil Russian Hackers from accessing other files and deleting or downloading them? In reality, it's very much similar to postal mail. If you accidentally send me a blank check for $10,000 that you meant to send to someone else, you don't exactly have permission to break into my house and take it back, nor am I obligated by anything other than my morals and scruples to return it to you upon request. ... View more

Yep, I think it's concatenating everything on the right side of the OR ... View more

You would create a Smart List with a filter of Filled Out Form and then enter the form name. ... View more

Also, putting hidden text in a field is something that spam checkers watch for. You might actually be better off changing the description of your banner to the pre-header text instead of putting in hidden text. A spam checker will look for 0 size blocks, hidden blocks, white text, etc. You also might want to check your subject line / pre-header to make sure it doesn't use any of the spam trigger words or phrases: The Ultimate List of Email SPAM Trigger Words ... View more