Flow filter based on $source

Hello @Lucia937,

Welcome back to the Community!

You’re spot on! Using the $Source field as a flow filter to target subscribers who have filled out a specific signup form - in my opinion, would be the best way to do it. My colleague, @Dov elaborated on this in a past Community post:

Additionally, instead of using a $Source property, you can also create your own hidden profile property for use which would tag users who have filled out the form. For example, if your form is set to geo-target EU customers, you can have a hidden field that would tag customers with “Signup From Region = EU” - or “Non-EU” for the opposite. 

Overall, it would achieve the same goal, just in different styles.

David

Hey @Lucia937,

This sort of behavior is typically when what you’re trying to filter or segment for is not live or has not recorded any events. I explained this further in some past Community posts which I’ve included below:

You certainly can preemptively enter the $Source value for your flow filter manually. Keep in mind though that when manually creating these definitions that the input must be in an exact match format as those input fields are spelling and case sensitive. I personally would recommend manually triggering these events though. This way you can not only make sure your signup form is working correctly, but also the experience is similar to the one your customers will be going through. 

David

Hey @Lucia937,

There really isn’t too much differences between those! $Source is usually used to identify the name of the form while the $consent_form_id is used to target the form’s ID. Both are typically the same, but using the $consent_form_id option is more beneficial if you have forms that may have longer names or very similar names. 

Whereas, $consent_form_version wouldn’t be something you want to use as it changes so frequently it isn’t static enough to target. The $consent_form_version changes every time updates or changes are made to a form. 

David