Choice Condition Glossary

Hi Alex,

Not statements in the rules generally refer to people who have not taken an action, so in this instance, everybody on your database who runs through this who has not had this webhook called will be added to the list.

Continuing Josh's response and adding my own take, in general the activity-related choices create more confusion than they're worth, as they can (and usually do) refer to activities that have nothing to do with the current campaign.

One word of caution, there are limitations to using choices in the flow step versus using the same filters/triggers in smart lists.

An example and something else to be weary of: 'Not webhook is called' is not the same as 'webhook is called' with constraint Error Type = HTTP Error 400: Bad URL request. <= you can't add constraints in your flow step choices

Lastly, choices are filters and if you're trying run activities through choices when you only want to match the most recent instance of that activity, you can't, because it will return true as long as any historical activities match the criteria.

Hi guys, 

Thanks for the quick response. 

I assumed that the choice condition referred to the previous flow step, however as Jay pointed out, I'm guessing Marketo checked to see if the Webhook had ever been sent to that account (I had previously sent this SMS to them as they were test accounts). 

I filtered our database into lists before sending comms and this seems to have solved the problem. 

Btw, is there actually a glossary for filters/triggers, like they have for icons, or do you need to just figure them out over time? 

Thanks again, 

When all else fails, use "Member of Smart List" as your choice filter.  Creating smart lists allow you to extend the functionality of the "choice" options and customize your criteria in a smart list you create.