So you only have one form, correct? I'm assuming you're using a field, "I would like to," to determine the initial selection. You can use visibility rules to determine the additional fields that display after the initial selection (e.g. if "I would like to" = "Qualify for free trial" then show fields A/B/C, and so on).
You will need 3 distinct smart campaigns:
- Trigger = Fills Out Form, Form Name = Contact Us. Add a filter to the smart list where field I would like to = [Contact Customer Support]. Then you can have your flow to send the alert to email@example.com
- Trigger = Fills Out Form, Form Name = Contact Us. Include filter I would like to = [Qualify for a free trial]. Then you can have your flow to send the alert to firstname.lastname@example.org
- Similar approach for your third radio button
Okay so I would create 3 smart campaigns, one for each value and my smart
list would look as such for each value...?
Trigger: Fills out Form
Form Name: is Contact Us
Filter: I would like to
I would like to: is Contact Customer Support
Marketing Analyst II
Inventory Locator Service,® LLC
That is what I would do. Sanford has a good point, but I have found this to be reliable in the past, even for very large volumes of form fills.
But you wouldn't really know when it failed, that's what makes the problem so pesky. Same with all the data race conditions (filters on data values that aren't committed to the db, etc.).
Glad you realized this is tricky -- though perhaps you didn't realize why.
The standard answer to this, but not necessarily the best (sorry, Rachel!) is to filter the trigger SC on the form value.
However, that won't work as reliably as people think, because the filter is not actually acting as a constraint on the form data. It's looking at the field value at the time the trigger runs. That may not be the value posted with the form, and IMO that's too fragile for a multi-purpose form like this.
The more reliable way to capture the data is to add a #hash to the URL on submit, indicating the "sub-form" they filled out. Then you can constrain each Filled Out Form activity on that value, without any confusion due to data changing in the background.