The order pool powers classic social proof: "Someone in {order_city} just bought {product_name}."
See What Is Content Source? and WooCommerce Product and Order Tags.
What data comes from an order
Typical tags filled from orders:
- Buyer first name or city (privacy-friendly snippets)
- Product name, image, and link from the ordered item
- Order date and time
- Order totals (when used in templates)
Use tags that fit your privacy policy. First name + city is common; full addresses are not recommended in toasts.
How Notifal selects an order
- Applies your order filters (status, date, products in order, etc.)
- Builds a pool of matching orders
- Picks one at random for each display
- Remembers shown orders per visitor when Show duplicate source is off
Useful filters
| Filter | Why |
|---|---|
| Order status | Only processing or completed orders (real purchases) |
| Date range | Last 7 days feels "live" |
| Product in order | Only orders containing products from a category |
| Multiple conditions (AND/OR) | Stricter pools for niche stores (Notifal Pro) |
Details: Content Source Filters.
Store with few orders
If filters are too strict, the pool may be empty and the notification will not appear on the frontend (Notifal hides it rather than showing empty or broken tags).
- Widen the date range
- Allow more order statuses your store uses
- Temporarily relax product filters
Counter tags
Pair order pools with Counter Tags to show "127 people bought this week" using the same restrictions.
In this topic
- What Is Content Source?
- Product Pool Content Source
- Order Pool Content Source (you are here)
- Post, Page, and User Pools
- Cart-Based Content Source
- Smart Targeting (Pro)
- Comment Content Source (Pro)
- Content Source Filters
- Retrigger Variants