Plan: Trial, Non-API Enterprise
Platform: All platforms
Applies to: Tracking pages
Overview
Segmentation shows different Tracking pages to different shoppers from the same link, based on rules you set. Learn how to show each shopper the right Tracking page using AfterShip Tracking. This guide walks you through creating a segment, scheduling it, mapping it to a page, ordering your rules, using links that follow the rules, reviewing your default page, and testing. Once live, one shopper sees the page you built for wholesale customers and another sees the retail one, with no extra work from you.
Before you begin
Requirements
The Tracking pages you want to show each segment, created before you assign them to a rule
Limitations
Segmentation applies to Tracking pages only. Returns and Warranty pages don't use segmentation
Order, Product, and Customer conditions need the order data that comes with a connected store
A shipment created through the Tracking API has no order data, such as order tags, to match
Shipment and Custom field conditions work for every shipment, however it reached AfterShip
A segment can have up to 32 conditions
Step 1: Create a segment
A segment is a group of shoppers defined by conditions. You create the segment here and map it to a Tracking page in Step 3.
Go to Branded pages > Segmentation and open the Segments tab.
Click Create segment.
Enter a name you'll recognize later, such as EU shoppers, VIP customers, or Black Friday 2025. Shoppers don't see this name.
Choose how conditions combine: All conditions are met or Any condition is met.
Add conditions under the group they belong to: Order, Product, Customer, Shipment, or Custom field. For each condition, pick a field, an operator, and the value or values to match.
The Segmentation screen has 2 tabs.
Segments lists the groups you define.
Tracking page segmentation sets which page each segment sees. You can also start from Set segmentation rules on a page's {⋯} menu in the Branded pages list.
The Segmentation page under Branded pages
How the two combine options work:
All conditions are met: every condition must be true (AND). Use it for shoppers who bought the summer collection and used a coupon code.
Any condition is met: one condition is enough (OR). Use it for shoppers who bought the summer collection or the spring collection.
For list operators such as is any of, enter several values. For example, an Order tag condition can take USA, Clothing, VIP and Female.
Creating a segment: segment name and conditions
Important: Choosing the wrong option between All conditions are met and Any condition is met is the usual reason a rule matches nobody, or everybody.
Supported conditions
Group | Field | Operators | Value |
Order | Total billing amount | is greater than or equal to, is greater than, is less than or equal to, is less than, is equal to, is not equal to | Amount and currency |
| Order tag | is any of, is none of, contains, does not contain | Tags |
| Order number | starts with, ends with, contains, does not contain | Text |
Product | Product SKU | starts with, ends with, contains, does not contain | Text |
| Product type | is any of, is none of, contains, does not contain | Pick from your store's product types |
| Product collection | is any of, is none of, contains, does not contain | Pick from your store's collections |
| Product tag | is any of, is none of, contains, does not contain | Pick from your store's product tags |
Customer | State | is any of, is none of | States |
| Postal code | starts with, ends with, is any of, is none of | Postal codes |
| Country/region | is any of, is none of | Countries or regions |
| Customer tag | is any of, is none of, contains, does not contain | Tags |
| Customer role | is any of, is none of | Roles |
Shipment | Carrier | is any of, is none of | Pick from carriers |
| Destination state | is any of, is none of | Pick from states |
| Destination country/region | is any of, is none of | Pick from countries or regions |
| Destination postal code | starts with, ends with, is any of, is none of | Postal codes |
| Shipment tag | is any of, is none of, contains, does not contain | Tags |
| Shipment title | starts with, ends with, contains, does not contain | Text |
| Shipment status | is any of, is none of | Pending, Info received, In transit, Out for delivery, Attempt fail, Delivered, Available for pickup, Exception, Expired |
| Signature requirement | is any of, is none of | No signature required, Indirect signature required, Adult signature required, Signature required |
| Failed attempts | is greater than or equal to, is greater than, is less than or equal to, is less than, is equal to, is not equal to | Number of failed delivery attempts |
| Historical events | is any of, is all of, is none of | Checkpoint events the shipment has had (for example, Delivery attempt failed, Held by customs, Returned to sender, Delayed, Picked up) |
| Latest event | is any of, is all of, is none of | The shipment's most recent checkpoint event, from the same list |
Custom field | Any custom field | is any of, is none of, contains, does not contain | Enter the field name and the value |
Shipment and Custom field conditions work for every shipment, however it reached AfterShip. Order, Product, and Customer conditions need the order data that comes with a connected store.
How the operators behave
is any of / is none of: the field matches (or doesn't match) at least one value in your list. AfterShip matches whole values only.
contains / does not contain: the field includes the text you enter anywhere. For example, an SKU condition
contains PO-TSmatchesPO-TS000.starts with / ends with: the field begins or ends with the text you enter.
is equal to / is not equal to and is greater than / is less than (or equal to): compare amounts and counts.
is all of (events only): the shipment has had every event in your list.
Step 2: Schedule the segment
Set when the segment is active. While a scheduled segment is active, matching shoppers see its page. Once the window ends, they see the default Tracking page.
In the segment's Active time settings, choose Always or Specific time windows. Always keeps the segment active with no time restriction.
If you chose Specific time windows, set the start time, end time, and timezone.
Click Save.
Segment Active time with specific time windows
Important: A page set to end at midnight ends at midnight in the timezone you pick. Choose a timezone that matches where your shoppers are.
Step 3: Map the segment to a page
A rule connects a segment to a Tracking page. You can map different segments to different pages, or to the same page. But one segment can only be applied once to a page.
Open the Tracking page segmentation tab.
Click Create rule.
Choose the segment and the Tracking page it should show.
Click Create.
Creating a Tracking page segmentation rule
If the segment doesn't exist yet, click Create segment in the dialog. To change a rule's name, page, or conditions later, click the rule.
Example mappings:
Shoppers who bought from the women's collection → Tracking page 1
Shoppers who bought from the men's collection → Tracking page 2
Shoppers who bought from both collections → Tracking page 3
Orders with tag X → Tracking page 4
Customers with the
Subscribertag → Tracking page 5
Step 4: Set the rule order
AfterShip evaluates rules top to bottom and shows the page from the first rule a shopper matches. Shoppers who match no rule see the default Tracking page.
Open the Tracking page segmentation tab.
Drag the rules to reorder them.
Place your most specific rules at the top.
Important: A broad rule above a narrow one takes the traffic the narrow rule was written for. The narrow rule then looks broken, when AfterShip never reaches it.
Step 5: Use links that follow segmentation rules
Rules only apply when shoppers arrive through a link that respects them. A specific page URL always shows that page and ignores your rules.
Use the Universal URL in your notification emails and storefront links.
For a Shopify proxy URL or iframe, select Default page or follow segmentation rules instead of Specific page.
In notifications, use the Tracking URL or Order URL merge tags.
Tracking URL opens the page for an individual shipment. Order URL opens the page for the order, with all its shipments. Both show the default page or the segment's page, based on your rules.
How the Universal URL works
The shopper opens the Universal URL, for example from your store navigation.
The shopper enters their order number and email, or their tracking number, on the lookup page.
AfterShip checks your segmentation rules.
AfterShip shows the shopper the Tracking page of the matching rule.
One shopper may see Tracking page 1, while another sees Tracking page 2, depending on which segment they fit.
Note: If a rule looks correct but nothing changes for shoppers, check the link they arrive on before you check the rule. See Learn about page URLs and domains.
Step 6: Review your default Tracking page
Every organization has a default Tracking page. Shoppers who match no rule see it, and so do shoppers who haven't entered an order or tracking number yet.
Check that your default page works as a general-purpose page, not only as a fallback.
To make another page the default, click Change page.
Note: You can't delete the default page. Set another page as the default first.
Step 7: Test your rules before you publish
Segmentation problems are invisible from the admin. The page looks fine, but AfterShip shows it to the wrong shoppers.
Open your Universal URL.
Look up a real order that should match a rule, and confirm you see that rule's page.
Look up a real order that shouldn't match the rule, and confirm you don't see that rule's page.
To change a rule after you publish, click the rule on the Tracking page segmentation tab.
What your users will experience
After completing these steps:
Shoppers who use the Universal URL see the Tracking page from the first rule they match
Shoppers who match no rule see your default Tracking page
Shoppers in a scheduled segment see its page only during the time window you set
You manage segments on the Segments tab and page mapping on the Tracking page segmentation tab
Scenario: You want VIP customers who place a large order during the holiday season to see a Tracking page with gift-wrap details and an early-access offer.
Segment: VIP holiday orders
All conditions are met
Order: Total billing amount · is greater than or equal to · 200 USD
Customer: Customer tag · is any of ·
VIPActive time: Specific time windows, starting November 15, 2026, 12:00 am and ending December 14, 2026, 11:59 pm, in your shoppers’ timezone
Rule: VIP holiday orders → Holiday VIP tracking page, placed above any broader VIP rule.
What shoppers see
Shopper | Order | Date | Page shown |
A | VIP tag, $250 | December 1 | Holiday VIP tracking page |
B | VIP tag, $80 | December 1 | Default Tracking page (fails the amount condition) |
C | No VIP tag, $300 | December 1 | Default Tracking page (fails the tag condition) |
A | VIP tag, $250 | December 20 | Default Tracking page (time window ended) |
If you switch the segment to Any condition is met, shoppers B and C also see the Holiday VIP page, since each meets one condition. This shows why the combine option is the most common cause of rules matching too many or too few shoppers.
Troubleshooting
Problem | Cause | Solution |
A rule matches nobody, or everybody | The segment uses the wrong combine option | Switch between All conditions are met and Any condition is met to match your intent |
A rule never seems to apply | A broader rule sits above it and matches first | Drag the more specific rule above the broader one |
Shoppers still see the same page after you set rules | Shoppers arrive on a specific page URL, or the proxy URL or iframe uses Specific page | Use the Universal URL, and set the proxy URL or iframe to Default page or follow segmentation rules |
Order, Product, or Customer conditions never match some shipments | Shipments created through the Tracking API have no order data | Use Shipment or Custom field conditions for those shipments |
A scheduled page starts or ends at the wrong time | The segment uses a different timezone from your shoppers | Set the segment's timezone to match where your shoppers are |
FAQs
1. Which Tracking page do shoppers see when an order contains several products?
Shoppers see the page of whichever rule any product in the order matches. If a sofa matches rule A and a candle matches nothing, the shopper sees page A. If the sofa matches rule A and the candle matches rule B, the higher-priority rule wins.
2. What happens if a condition's field doesn't exist on the shipment or order?
AfterShip skips the condition and doesn't route the shopper to that segment. For example, an Order tag contains summer rule never matches a shipment created through the Tracking API, because that shipment has no order tag field.
3. What happens if a condition's field exists but is empty?
AfterShip counts it as a mismatch. An order with an empty tag list doesn't match an Order tag contains summer rule.
4. Can I use segmentation for banners and shipment alerts?
Yes. You can target banners and shipment alerts inside a Tracking page at a segment.
5. What are common ways to use segmentation?
Use it for region or language, with different pages for different markets. Use it for customer tier, with a different experience for VIP or wholesale orders based on order tags. Use it for order value, with a higher-touch page above a threshold, or for campaigns, with a seasonal page that a time window retires automatically.
Key takeaways
Segmentation shows different Tracking pages to different shoppers from the same link
AfterShip evaluates rules top to bottom, and the first matching rule decides the page
Segmentation is available on Trial and Non-API Enterprise plans, for Tracking pages on all platforms
Shoppers who match no rule see your default Tracking page
Rules only apply when shoppers arrive through the Universal URL or a link set to follow segmentation rules




