Dan_Stevens_

You still need to replace the DVC filter with the actual attribute. DVC will not affect net new people to your database.

But you don't have any triggers here - just filters. What you want is a "Fills out form" trigger along with a "How can we help you" filter (where the value = "Anaconda Enterprise Sales") - instead of a DVC filter. DVC only affects existing people in your DB - not net new ones.

Hi Greg - the reason why we don't do this is because of the specific scenarios when we are sending specific audiences an email and it falls under "legitimate interest". For example, after a client event, we'll send out post-event communications that relate directly to the event. But that's it - th...

We are not associating "not opt-in" to "unsubscribe". Rather, we're just making sure that - unless the person has "opt-in = true" - they won't receive marketing emails. Actually, in our case, our main opt-in field - the one that appears on all of our forms - is an opt-in to all marketing emails. ...

I’d be interested to learn more about this bug - and the reason for the two different behaviors that occur when yes/TRUE are used.

We use a similar process to keep the opt-in value persistent if a user doesn't check the opt-in field on subsequent form submits - primarily on our website where we use embedded forms and you can't evaluate the prefill value of another field (like "opt-in date") to determine visibility rules of the ...

Here's some more info on Marketo Sales Engage (ToutApp was the basis for this when Marketo acquired it): Sales Engage Overview - Marketo Docs - Product Documentation

Here's a recent/prior thread that contain a lot of useful information around this issue (and unfortunately, no solution):Re: [Shared Blog]: I Want to Believe, But: Your Email Link Clicks Aren’t Real

Fantastic recap, Justin!

Josh - here’s a perfect example on where it would be so useful to block field updates based on CRM entity type: [Accounts Tip] Company Name Mismatch