Differentiate data value change triggered by contact vs. Marketo user/flow Hi, we are refining our double opt-in flow for a specific country (Germany in this case). We have two separate flows: one that should be triggered by the contact actively changing the data (eg, form submit) and another for when the change is initiated on our side (smart campaign, sync, import, etc). My question is how can we best distinguish these two scenarios, given that data value change trigger has limited constraints. For purposes of this discussion, let’s assume the double opt-in flows work fine, and it’s just the triggers that matter. In fact, a solution to this problem would have applications beyond double opt-in. Triggers: Lead Created and Data Value Change (country)*If you'd like the specific use cases for these triggers, I'm happy to provide, but may be unnecessary.The lead created trigger is simple to implement since the constraint allows source type. To distinguish a record creation initiated by the contact vs. one by a Marketo user/flow, one trigger listens for lead
.png){kind=icon}
