Rules Based on Contact Data

For this example, we will look at segmentation rules using the built in contact fields in WhatCounts. These fields correspond to the basic contact data fields default in each Realm and include Email Address, First Name, Last Name, Phone Number, Fax, Address, City, State, and Zip Code


https://zetaglobal.atlassian.net/wiki/download/attachments/569151546/678640f1ceb3d.image20.png?version=1&modificationDate=1736851697972&cacheVersion=1&api=v2

Let’s start with a contact’s location, perhaps we want to target only those in San Francisco


https://zetaglobal.atlassian.net/wiki/download/attachments/569151546/678640f2a7ed5.image1.png?version=1&modificationDate=1736851698747&cacheVersion=1&api=v2

In the above example we have selected “Equals” as our operator. This means for the given example we will only select contacts whose city is matches San Francisco exactly.


https://zetaglobal.atlassian.net/wiki/download/attachments/569151546/678640f36d511.image15.png?version=1&modificationDate=1736851699511&cacheVersion=1&api=v2

In addition to matching Equals and Not Equal to for text fields, In and Not In allow you to provide a comma-delimited list of values, Like and Not Like with text phrase to match “begins with,’ “ends with,” or “contains.” This can be helpful for geographic segmentations like above (i.e. match all cities that begin with San) however, a more practical use may be targeting contacts by email provider.


We can use the Like operator here to say we want to select all contacts whose address ends with @gmail.com



https://zetaglobal.atlassian.net/wiki/download/attachments/569151546/678640f42c6a1.image3.png?version=1&modificationDate=1736851700279&cacheVersion=1&api=v2

Of course, WhatCounts also supports including any of your own custom fields to build segmentations as well.