SanfordWhiteman

Pretty straightforward. Don’t hide/show the proxy Email field directly when the person clicks the link. Instead, update another hidden field — a Form Visibility Manager (FVM) field. This is just a string field you use for special form behaviors. Then use standard Visibility Rules based on the FVM f...

Not sure what’s inconsistent? You either allow Marketo’s SFDC user to see everything, or you don’t. It’s all in how you set up the SFDC user. Marketo doesn’t know (nor care) why it can’t see an object if it can’t see it now and has no memory of seeing it in the past. To use a custom sync filter inst...

I did not set up the sharing rule for the marketo sync user,but there was no problem with the sfdc integration. I'm very confused.There was no “problem” with the SFDC integration, but there was the exact behavior you described above where people are automatically synced if visible. If you don’t want...

As far as I know, sharing rules are the role of expanding access, not reducing it.Yes, sharing rules dictate which leads will be visible. “Hide” means exclude them from the sharing rule based on some combination of field values.

OK. You did leave something very significant out of your earlier posts: the fact that people are being taken to a page without the mkt_tok! The mkt_tok is key to all (native) Pre-Fill functionality. (* However, we do not fully trust email pre-fill based on browser cookies. We found that if a single ...

@Thorsten that’s a 10% exaggeration lol!

If you cannot delete them, use an SFDC Sharing Rule to hide those people from the SFDC user used by Marketo. Note this will stop the people from being recreated by the SFDC sync. It will not stop them from being created in Marketo via list uploads, form fillouts, etc. This also means if the person r...

OK, this is describing a very different scenario (though as you’ve noted, one that still requires a custom solution if you need it fixed ASAP). Your original post mentioned a client certificate. In this setup, a cert specific to your account is generated on the server side and needs to be preshared ...

@lbell for proper ordering of Call Webhook, trigger on Webhook is Called to continue execution.