Build the segments
เนื้อหานี้ยังไม่มีในภาษาของคุณ
A segment is a saved group of shoppers who match your conditions, for example shoppers who added a product to the cart and did not order. You can send a one-time push, in-app message, or email to a segment, or use it in a journey to decide who enters and which message each shopper gets. Build the segments before the journeys.
How to create segments
Anchor link toCreate each segment in Audience → Segments with the filters from the tables below.
There are several ways to build a segment. This page covers segments by events and by tags. You can also build segments from:
- Existing segments
- Anniversary dates
- User ID
- An imported file
- Geolocation
- A description in plain words, with AI
For all the ways, see How to create segments.
Ready-made RFM segments
Anchor link toRFM segmentation groups shoppers by how recently, how often, and how much they buy, and builds the segments for you, such as Champions and At risk. To build them:
- Open Audience → RFM segmentation.
- Select
PW_Conversionas the Purchase Event and itsvalueattribute as the Monetary Attribute.PW_Conversionappears in the list after the firstOrder placedwith__amountand__currencyarrives. See Track revenue from orders. - Click Calculate.
Pushwoosh builds 10 segments, refreshes them every 24 hours, and scores only the last 90 days. An application keeps one RFM setup. Shoppers with no order in the last 90 days are not in these segments. See RFM segmentation.
Segments by events
Anchor link toThese segments are built from the main events that shoppers trigger in the app. Use them as a starting point or for inspiration. Change the numbers, such as the days, or build your own segments. The number of days depends on how often your customers buy. For example, a store that sells groceries needs shorter windows than a store that sells furniture. To set the filters, see Build segments by events.
Most of them feed a journey from Build the journeys, so build the ones for the journeys you plan to launch.
| Segment | Filters | Use it to |
|---|---|---|
| Cart abandoners |
| Remind shoppers about products they put in the cart and did not order. The journey for this case starts on the event, so use the segment for a one-time campaign, for example a weekend reminder. See Cart abandonment |
| Browsers without a cart |
| Reach shoppers who looked at products several times and added nothing to the cart. Feeds the Reminder about viewed products journey |
| Wishlist shoppers |
| Send a promotion to shoppers who saved a product and have not ordered. The product back in stock journey starts on its own event |
| First-time buyers |
| Tell a shopper’s first order from later ones. Shoppers who ordered before you started tracking orders also count as first-time buyers. Feeds the Second order offer journey |
| Repeat buyers |
| Give shoppers who order again their own offers, for example early access to a sale. Feeds the Early access for loyal customers journey |
| Recent buyers |
| Tell buyers apart from other shoppers, for example to leave them out of a first-order promotion |
| At-risk customers |
| Win back shoppers who ordered before and have been quiet for two months. This is the first stage of win-back. Feeds the Win-back for inactive customers journey |
| Lapsed customers |
| Win back shoppers who have not ordered for half a year, with a bigger offer than for At-risk customers. The second filter leaves out shoppers with no orders recorded. Feeds a copy of the Win-back for inactive customers journey |
Segments that start empty
Anchor link toThe At-risk customers and Lapsed customers segments find shoppers who ordered before and then stopped. They need order history, so right after you set up the Order placed event they are empty. At-risk customers start to fill 60 days after the first events arrive, and Lapsed customers after 180 days.
To fill these two segments sooner, use the PW_ApplicationOpen event instead of Order placed in their filters. The segments then go by app opens, so they also take in shoppers who stopped opening the app but never ordered.
Filters with never
Anchor link toA filter with never counts a device only if it has a push token. A device gets the token when the app asks for push permission, whatever the shopper answers. Until then, the shopper is not in such segments as Cart abandoners, Browsers without a cart, Wishlist shoppers, At-risk customers, and Lapsed customers. To include shoppers earlier, ask for permission earlier. See Ask for push permission at the right moment.
Segments by tags
Anchor link toThese segments are built from shopper tags. Use them as a starting point or for inspiration. Change the values, or build your own segments. To set the filters, see Build segments by tags.
Most of them need the tags from Store shopper data in tags.
| Segment | Filter | Use it to |
|---|---|---|
| Shoppers without push | Push Alerts Enabled is false | Find shoppers who declined or never allowed notifications, for example to ask them again with an in-app message or to reach them by email |
| VIP customers | loyalty_tier is gold | Give top customers their own offers and early access. Feeds the Early access for loyal customers journey |
| Sneaker fans | favorite_category is sneakers | Announce a new collection to the shoppers who buy this category most |
| Members | is_subscriber is true | Send offers meant for members of your program |