Katja_Keesom

Entirely true. The basic issue to understand here is that there two different unique keys in play:When a record is created in Marketo, the email address is used as the unique key. A list upload or form fill will therefore update the existing record with the same email address.When a record is create...

Totally agree there, that would cause all sorts of problems. The only viable alternative would indeed be leveraging the API (if you want an automated process) to capture the feedback and store it in a custom object or custom activity.

Would be nice to actually have the form link?

I guess there would be some use cases I can think of:First of all of course the person being deleted from the database entirely. Reasons can be data retention policy or a specific subject's request for example.I also know of situations where the selection of who should be invited for an event is man...

I think it is still a valid question, as last I checked that will only work if the different instances are under the same master agreement. If it is a totally different customer I would indeed recommend using a different email address.

@SanfordWhiteman is absolutely right. In order to add a domain you need to go into the Google reCAPTCHA account and simply add the domain there. No need to change anything in Marketo.

Hmm, does this person actually exist in your SFDC? Looks like that is not the case, so you are trying to update a campaign member status before the person is synced to SFDC.

One addition to adding custom fields to the Company object. There are actually two choices:If you want the field to be synced with SFDC it indeed needs to be created in SFDC first and then synced across (which means it ends up in the Accounts folder).If you want to create a Marketo-only field that d...

My vote is also on the mail scanner being the cause of this. How to prevent it from happening is another question.

To put @Darshil_Shah1 's comment into perspective: When you add a person to a list you ALWAYS add them to the entire database. So in order for these people not to be available for other campaigns you do need to take action to actively prevent that. Short of removing them from the database after the ...