New customer filter options
Why?
For even more granular filtering of the contacts in your segments.
You can now filter customers and contacts based on changes to their lifecycle status, e.g. an active customer about to become at risk, or a customer who lapsed recently.
What’s new?
Access the 'Customer Filter' from the following screens:
- Customer > Segment Explorer > Filter Customers
- Broadcast Campaigns > Segment node > Filter Customers
- Automation Campaigns > Segment node > Configure
Click + ADD CONDITION.
All of the new filter options are in the Customer Attributes tab:
The options are:
| Field | Description |
| 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 a lead was acquired. |
| 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 last purchased from. |
| Store of customer's first order | Filter based on the store the contact made their first purchase from. |
| Date contact acquired | Filter based on the date the contact entered your lists. |
| Date created in Ometria | Filter by the date the contact was created in 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’. |
For the date fields, you have further options which can be used to add even more granular detail to your filters:
| Option | Description |
| before | Filters contacts whose lifecycle status changed (or order was placed) before the selected date. E.g. contacts that became 'at risk' before 1 January 2020 |
| before (relative) | Filters contacts whose lifecycle status changed (or order was placed) before the selected time period (in hours, days or weeks). E.g. contacts that became 'at risk' before 8 hours ago (i.e. excluding the past 8 hours) |
| after | Filters contacts whose lifecycle status changed (or order was placed) after the selected date. E.g. contacts that became 'at risk' after 1 January 2019 |
| after (relative) | Filters contacts whose lifecycle status changed (or order was placed) after the selected time period (in hours, days or weeks). E.g. contacts that became 'at risk' after 8 hours ago (i.e. in the past 8 hours) |
| on | Define a date upon which a contact's lifecycle status changed or an order was placed. E.g. contacts that became 'at risk' on 1st January 2019 |
| on (relative) | Define a time (in hours, days or weeks) upon which the contact's lifecycle status changed, or their order was placed. E.g. contacts that became 'at risk' 8 weeks ago (i.e. on this date 8 weeks ago) |
| between | Set a date range during which contacts' lifecycle status changed, or their order was placed. E.g. contacts that became 'at risk' between 1 January 2020 and 15 January 2020 |
| between (relative) | Set a time period (in hours, days or weeks) during which contacts' lifecycle status changed, or their order was placed. E.g. contacts that became 'at risk' between 6 hours and 1 day ago |
| day of month is | Define a day of the month (e.g. enter '15' for the 15th) upon which a contact's lifecycle status changed, or their order was placed. This filter returns contacts that became 'at risk' (for example) on that date for any month, e.g. 15th June 2016, 15th July 2018 etc. |
| day of week is | Define a day of the week upon which a contact's lifecycle status changed, or their order was placed. This filter returns contacts that became 'at risk' (for example) on that day for any week, e.g. 15th June 2016, 15th July 2018 etc. |
| month is | Define the month (e.g. January) in which a contact's lifecycle status changed, or their order was placed. This filter returns contacts that became 'at risk' (for example) during that month for any year, e.g. January 2020, January 2019, January 2017 etc. |
| year is | Define the year (e.g. 2019) in which a contact's lifecycle status changed, or their order was placed. This filter returns contacts that became 'at risk' (for example) at any point during that year. |
| anniversary is today | This filters contacts whose lifecycle stage changed (or order was placed) on today's date. e.g. If today is 1st January 2020 and you selected 'contacts that became at risk - anniversary is today' it will return contacts that became 'at risk' on 1st January 2019, 1st January 2018, 1st January 2017 etc. |
| anniversary was | Define (in days) the anniversary of the contacts' lifecycle change (or order was placed). e.g. If today is 1st January 2020 and you selected 'contacts that became at risk - anniversary was 8 days ago' it will return contacts that became at risk on 24th December 2019; 8 days prior to today. |
| which is known | Filters all contacts with the lifecycle status you have selected - i.e. the lifecycle status is known, and it is 'at risk' (for example). |
| which is not known | Filters all contacts whose lifecycle status is unknown. |
Ometria Blueprints for Broadcast
Why?
Save time and get started with broadcast campaigns as quickly as possible by using our three ready made blueprints to segment your contacts and create instant variant waterfalls.
What’s new?
From the broadcast campaigns builder’s ‘Recipients’ tab, select APPLY BLUEPRINT from the left hand panel:
Our ready made blueprints are:
- Lifecycle Stage - This is great for reactivation campaigns, launching new products and identifying and targeting your leads.
- Customer Frequency - Very useful for reporting - for example, if you launch the sale of a new product you can identify whether you’re getting more interaction from your one-time shoppers or loyal customers.
- Customer Value - Another great strategy for reporting - see if your VIPs are interacting with campaigns for your new product lines.
The Ometria blueprints display at the top of the blueprints list:
These blueprints cannot be deleted, but you can make changes to the segments/conditions of an Ometria blueprint and then save it for future use by clicking SAVE NEW.
Suppressed recipients count
Why?
Ometria automatically suppresses a number of contacts when you create a broadcast campaign, but until now there was no easy way to find out how many contacts were suppressed per campaign.
Contacts might be suppressed for any of the following reasons:
- Email addresses that hard bounce (i.e. the recipient server reports a permanent delivery failure).
- The email address is invalid - e.g. because of a typo in the address - which results in a hard bounce.
- You (the client) included the contact in a suppression list sent to us during your onboarding.
What's new?
You can now easily see how many contacts were suppressed per broadcast campaign.
Go to: Campaign Performance > Broadcast Campaigns
Scroll down to your 'CAMPAIGNS LIST' and select the 'Suppressed recipients' KPI from the columns dropdown.
Your suppressed recipients per campaign display in the campaigns list.
You can also select any broadcast campaign for the individual performance overview.
The number of SUPPRESSED CONTACTS displays in a tile on the 'OVERVIEW' tab.
Comments
0 comments
Article is closed for comments.