You can target emails and reports by core fields and custom fields that aren't already included in normal targeting. This lets you target by an activist's city, email address or any custom fields you've created.
On the email or reports targeting page, click on the Tags, Sources, and Fields section and select Add under Field Values.
A box will pop up that prompts you to select which field name you want to target.
First, select which field you want to target from the dropdown menu "Include/Exclude activists who filled out the field named." You can select any custom field you've created or core fields (address, city, email, first name, last name or zip code).
Below that, you will put in the value you want to target. There's a couple different ways you can do this, depending on what you're trying to target.
Values will return exact matches, but you can use the wildcard % symbol to target parts of a field value. The example below shows how you would target activists who live in the zip code 20036.
You can also interpret custom fields as numbers or dates and target with greater than or less than operations using << or >>. For example, <<1 will target every activist with a custom field value number less than 1. >>2017/12/01 will target everyone with a custom field value date after December 1st, 2017. The format for dates must be yyyy/mm/dd. Time is optional.
You can also use regular expressions, so [0-9] will target any activist with any of the characters 0-9 in that form field. The wildcard character can be combined with regular expressions. (For more detail on our regular expression parser and syntax, see here.)
Wildcard Examples
If you select the Emails field, you'll see an option to automatically include all Gmail, Yahoo, AOL, etc. address on your list.
You can use our wildcard to target parts of a field value. It can be used in a variety of ways.
1. To target activists who have any value for a particular field, you would use the %.
For example, if you want to target anyone who filled out the field for mobile number, you would enter %
2. %abc will return any activist who has a value ending with abc. For example, if you want to exclude activists with a .edu email, it would look like this: %.edu
3. abc% will return any activist who has a value starting with abc and those who only have abc the value in the field. For example, if you want to include activists with a phone number that starts with 202, it would look like this: 202%.
4. You can also use multiple % characters, so %1% matches anyone who has a value of 1 in any part of the form field you're targeting. If you wanted to target everyone who said they would be interested in canvassing, it would look like this: %canvassing%
5. You can interpret custom fields as numbers or dates and target with greater than or less than operations using << or >>. For example, <<1 will target every activist with a custom field value number less than 1. >>2024/12/01 14:00:15 will target everyone with a custom field value date after December 1st, 2024, 2:00pm and 15 seconds. The format for dates is yyyy/mm/dd hh:mm:ss. Time is optional.
6. You can also use relative days instead of writing out the exact date and time. Using ">>X_days" will return values closer to the present than X days ago. For example, if it is currently January 10th, and I want to include people with values from the last week, I would enter ">>7_days". This will capture everyone whose date in the field ranges from January 3rd to present.
Using "<<X_days" will return values prior to X days ago. If it is currently January 10th, and I want to include people with values before the last week, I would enter <<7_days". This will capture anyone whose value the field is before January 2nd.
You can combine relative dates in the include and exclude columns to capture people with values in a range of dates. If I wanted to return values from between 30-60 days ago I would enter >>60_days under the include column (left) and << 30 days under the exclude column (right).