Ometria’s customer filter allows you to filter all of your contacts by 63 different metrics and conditions.
You can use the customer filter to report on your contacts’ activity, as well as to create and save new segments.
Find the customer filter in any of the following screens:
- Customer > Segment explorer > Filter Customers
- Broadcast Campaigns > Select a segment node > Filter Customers
- Automation Campaigns > Select a segment node > Configure
- Reports >
Select any of the following options from the drop-down:
- everyone (default) - filter on all contacts in your account
- customers - filter on all contacts who have placed at least one order
- leads - filters on all contacts who have not yet placed an order (regardless of subscription status)
The number of contacts you are filtering displays in the top-left of the window, along with the percentage of your total contacts this number represents.
Next, choose from:
- Select [segment] who match all of these blocks - the contacts generated will meet all of the conditions you define.
- Select [segment] who match any of these blocks - the contacts generated will meet at least one of the conditions you define, but not necessarily all of them.
Click +ADD CONDITION to start choosing your filters. You can add as many as you need, and your contacts count in the top-left will automatically update with the number of contacts which meet the conditions.
Conditions are linked using AND OR logic.
Once you’re happy with your conditions, click Apply filter to update the data on the screen you’re viewing.
You can also select Save as new segment to save your filter as a dynamic or static segment.
Customer filter conditions
There are four filter categories, which can be used in combination with each other:
Further filtering is available once you have selected your condition.
Customer attributes
Condition |
Description |
Name |
Filter based on the contact's first name. |
Last name |
Filter based on the contact's last name. |
|
Filter based on the contact's email. |
Customer ID |
Filter based on the contact’s customer ID. |
Customer tag |
Filter based on the 'customer tag'. |
Customer belongs to segment |
Filter based on a customer belonging to a segment. |
Customer lifecycle stage |
Filter based on the customer's lifecycle stage. |
Customer frequency band |
Filter based on the customer's frequency band. |
Customer value band |
Filter based on the - customer's value band. |
Customer email engagement band |
Filter based on the customer’s email engagement band. |
Country |
Filter based on a customer's country. |
Gender |
Filter based on a customer's gender. |
Age |
Filter based on a customer’s age. This is calculated using the customer's date of birth (if known). |
Date of birth |
Filter based on customer’s date of birth. |
Date subscribed |
Filter based on date of subscription (marketing_optin timestamp). |
Date unsubscribed |
Filter based on date of the contact’s first unsubscription (marketing_optout timestamp). |
Accepts email marketing |
Filter based on email subscription status (subscribed vs. unsubscribed). |
Phone number |
Filter based on phone number pushed to Ometria (phone_number). |
Phone number country |
Filter based on the phone number's country code. |
Has account |
Filter based on whether the contact has a customer ID associated with their profile. |
Date created in Ometria |
Filter based on the date the contact was created in Ometria (i.e. ingested via form, API, contact upload etc.) |
Date contact became at risk |
Filter based on the date a contact became 'at risk' of lapsing. |
Date customer became lapsed |
Filter based on the date a contact's lifecycle stage became 'lapsed'. |
Date lead was acquired |
Filter based on the date that the lead was acquired by you - this might have taken place outside of Ometria, e.g. before you started using Ometria. |
Date customer was won back |
Filter based on the date a contact transitioned from 'lapsed' to 'active' again. |
Date customer was saved |
Filter based on the date a contact transitioned from 'at risk' to 'active'. |
Store of customer's last order |
Filter based on the store the contact’s last valid order was placed with. |
Store of customer's first order |
Filter based on the store the contact first purchased from. |
Date contact acquired |
Filter based on the date that the contact was acquired by you - this might have taken place outside of Ometria, e.g. before you started using Ometria. |
Date customer will become at risk |
Filter based on the date a customer will transition to 'at risk'. |
Date customer will become lapsed |
Filter based on the date a customer will transition to 'lapsed'. |
Accepts SMS marketing |
Filter based on the contact’s SMS opt-in status:
|
Accepts push notifications |
Filter based on whether or not the contact has enabled push notifications:
|
Mobile app installed |
Filter based on whether or not the contact has installed your mobile app to their device. |
Subscription updated (SMS) |
Filter based on the most recent date the contact changed their SMS opt-in status. |
Date first subscribed (Push) |
Filter based on the first time the contact enabled push notifications. |
Date first unsubscribed (Push) |
Filter based on the first time the contact disabled push notifications. |
Date last subscribed (Push) |
Filter based on the most recent date the contact enabled push notifications. |
Date last unsubscribed (Push) |
Filter based on the most recent date the contact disabled push notifications. |
Language |
Filter based on the contact's preferred language. |
Predicted next order date |
Filter based on the predicted date of the contact's next order. |
Purchase activity
Condition |
Description |
Has placed an order that matches... |
Filter that looks at any order in the customer's order history that matches X condition (choose from drop-down for that specific order).
Note: This filter looks at product attributes at the time the order was processed.
|
Products interacted with |
Filter looks at products the customer has interacted with. |
Has purchased product with price |
Customer has an order with a line item - this filter looks at the total price for the line item, not the unit price. |
Customer Lifetime Value (CLV) |
Sum of all orders for this customer (all time), using the Grand Total field. |
Average Order Value (AOV) |
Average of all orders for this customer (all time), using the Grand Total field.
Note: AOV in Ometria is calculated with tax included.
|
Has used coupon code |
Filter looks at whether the customer has used coupon code which is X. |
Has ever used a coupon code |
Filter looks at whether the customer has ever used a coupon code. |
Date of first order |
Filter based on the date of the customer's first valid order. |
Date of last order |
Filter based on the date of the customer's most recent valid order. |
City of last order |
Filter based on the city listed in the billing address of the customer’s last order. |
State of last order |
Filter based on the state listed in the billing address of the customer's last order. |
Postcode of last order |
Filter based on the postcode listed in the billing address of the customer’s last order. |
Country of last order |
Filter based on the country listed in the billing address of the customer’s last order. |
Number of valid orders |
Filter based on the number of orders a customer has with a status of 'valid'. |
Number of attempted orders |
Filter based on the number of valid and invalid orders a customer has. |
Store purchased from |
Filter based on the store a customer has purchased from. |
Web activity
See also: Segmenting contacts by visit
Condition |
Description |
Has made a visit that matches... |
Filter that looks at any visit in the contact's visit history that matches X condition (choose from drop-down for that specific interaction). |
First visit captured |
Filters if the source of the customer’s first visit was captured (based on UTMs). |
First visit medium |
The medium the contact’s first visit is attributed to, e.g. social, CPC (cost per click), search, referral, etc. |
First visit name |
The name of the source the contact’s first visit was attributed to, e.g. Ometria, Facebook, Google, etc. |
First visit campaign |
The campaign (if any) the contact’s first visit was attributed to. |
First visit domain |
The domain the contact’s first visit was attributed to, e.g. facebook.com, yoursite.com, etc. |
First visit terms |
The search terms a contact used to arrive at your site on their first visit, e.g. ‘dresses’, ‘red handbag’ etc. |
Date first seen |
Filter based on date the contact first visited the website. |
Date last seen |
Filter based on the timestamp of the most recent visit. |
Number of visits |
Total of visits tracked by the JavaScript tracker. |
Store visited |
Returns contacts that have visited your specified store (at any time in their customer lifecycle), based on the storeID pushed via JavaScript tracker. |
Email activity
Condition |
Description |
Date of last delivered email |
Filter based on the date of the contact’s last delivered email. |
Date of last opened email |
Filter based on the date of the contact’s last opened email. |
Date of last clicked email |
Filter based on the date of the last clicked email. |
Date of last bounced email |
Filter based on the date of the last bounced email. |
Interacted with a specific broadcast campaign |
Filter based on a contact's interaction with a specific broadcast campaign, including unsent campaigns (future campaigns).
Tip: If you choose to filter on non-interactions, e.g. contacts who have not opened a campaign, Ometria will include all contacts who did not open that campaign, including those who were not sent the campaign in the first place. To filter these contacts out of your segment, add an additional condition to your filter, e.g. "Contact received X campaign" AND "Contact did not open campaign". See also: Customer filter: AND OR logic
|
Interacted with a specific automation campaign |
Filter based on a contact's interaction with a specific automation campaign.
Tip: If you choose to filter on non-interactions, e.g. contacts who have not opened a campaign, Ometria will include all contacts who did not open that campaign, including those who were not sent the campaign in the first place. To filter these contacts out of your segment, add an additional condition to your filter, e.g. "Contact received X campaign" AND "Contact did not open campaign". See also: Customer filter: AND OR logic
|
Received specific broadcast campaign variant |
Filter based on a contact interacting with a specific broadcast variant. |
Custom events
If you have custom events set up for your Ometria account, these also display as filter options.
For example:
- wish list event
- customer requested a brochure
- customer visited an offline store
- customer has visited a specific webpage or has completed a specific action on a website.
See Segmenting contacts by custom event for more information.
‘Which’ filters
Most filters have further options to help define your segments with even more granularity, e.g. Filter based on Customer name:
Select your filter condition, enter a keyword (if required) and select from any of the following:
which is
The filter is limited to a single criterion.
E.g. If you select ‘Customer name which is - Jones’, all contacts with the name ‘Jones’ will meet the filter conditions.
which is not
The filter excludes a single criterion.
E.g. If you select ‘Customer name which is not - Jones’, all contacts whose name is anything but ‘Jones’ will meet the filter conditions.
which is one of
The filter is limited to multiple specified criteria.
E.g. If you select ‘Customer frequency band which is one of - Loyal, VIP’, all contacts whose frequency band is Loyal or VIP will meet the filter conditions.
which is not one of
The filter excludes multiple specified criteria.
E.g. If you select ‘Customer frequency band which is not one of - Loyalty, VIP’, all contacts whose frequency band is anything other than Loyal or VIP will meet the filter conditions.
which contains
The filter contains the term or keyword entered.
E.g. If you select ‘Customer name which contains - Jones’, all contacts whose name includes ‘Jones’ will meet the filter conditions (e.g. ‘Smith-Jones’ will qualify).
which doesn’t contain
The filter does not contain the term or keyword entered.
E.g. If you select ‘Customer name which doesn’t contain - Jones’, all contacts whose name doesn’t include ‘Jones’ will meet the filter conditions.
which starts with
The filter includes contact data which begin with the letters entered.
E.g. If you select ‘Customer name which starts with - Jones’, all contacts whose name begins with ‘Jones’ will meet the filter conditions, i.e. ‘Jones-Smith’ meets the conditions, but ‘Smith-Jones’ does not.
which doesn’t start with
The filter excludes contact data which begin with the letters entered.
E.g. If you select ‘Customer name which doesn't start with - Jones’, all contacts whose name begins with anything except ‘Jones’ will meet the filter conditions, i.e. ‘Jones-Smith’ doesn't meet the conditions, but ‘Smith-Jones’ does.
which is known
The data selected is known by Ometria.
which is not known
The data event selected is not known by Ometria.
Date filters
You can use the Customer filter to create very specific segments based on the date of an event.
For example, by using Date of first order, you can create a segment of all contacts who made their first purchase in the last year.
When you select a date event in the Customer Filter, there are further options to configure and specify your filter.
See also: Segmenting contacts by date
Comments
0 comments
Article is closed for comments.