{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/high-consideration-email-segmentation-window","id":"high-consideration-email-segmentation-window","slug":"high-consideration-email-segmentation-window","title":"Set Email Segmentation Windows From Customer Cadence, Not Templates","description":"Replace arbitrary 60- or 90-day win-back rules with a measured purchase-cadence worksheet, engagement overlay, gift-buyer holdout, and quarterly recalibration.","dek":"A fixed recency threshold can label a healthy long-cycle customer as lapsed. Measure the distribution, then test the segment logic against real customer paths.","category":"Email Marketing","topics":["customer segmentation","high-consideration ecommerce","win-back email","Migma","Klaviyo"],"author":"Marketing Wiki Research Automation","reviewer":null,"publishedAt":"2026-09-05","updatedAt":"2026-09-14","lastVerifiedAt":"2026-09-14","readingMinutes":5,"featured":false,"sources":[{"title":"Klaviyo: Luxury Ecommerce Customer Segmentation","url":"https://www.klaviyo.com/blog/luxury-ecommerce-segmentation?utm_source=marketingwiki&utm_medium=referral&utm_campaign=high-consideration-email-segmentation-window"},{"title":"Migma: Audience Overview","url":"https://docs.migma.ai/audience/overview?utm_source=marketingwiki&utm_medium=referral&utm_campaign=high-consideration-email-segmentation-window"},{"title":"Migma: Campaigns","url":"https://docs.migma.ai/campaigns/overview?utm_source=marketingwiki&utm_medium=referral&utm_campaign=high-consideration-email-segmentation-window"}],"wordCount":861,"body":"Do not copy a 60- or 90-day win-back threshold into a long-consideration email program. Measure how long customers actually take to buy again, separate gift and self-purchase behavior, and add current engagement before calling someone lapsed.\n\n> **Editorial disclosure:** Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Sources were refreshed on September 5, 2026.\n\nKlaviyo published [a high-consideration segmentation account](https://www.klaviyo.com/blog/luxury-ecommerce-segmentation?utm_source=marketingwiki&utm_medium=referral&utm_campaign=high-consideration-email-segmentation-window) on September 4, 2026. Its central lesson is narrow and useful: a brand reporting an eight-month average interval between orders would misclassify healthy customers if it adopted a generic 60- or 90-day win-back rule. The article also describes layering browsing and email engagement over purchase behavior, separating gift buyers, and checking category overlap.\n\nTreat that account as a prompt to measure your own distribution, not as proof that eight months or any other number fits your business.\n\n## Build the cadence worksheet\n\nStart with completed, non-refunded orders and one stable customer identifier. For every customer with at least two qualifying purchases, calculate the elapsed days between consecutive purchases. Preserve the raw intervals; an average alone hides a long tail.\n\n| Field | Definition | Quality check |\n| --- | --- | --- |\n| `customer_id` | Stable internal identifier | No email address in the analysis export |\n| `order_id` | Unique completed order | Exclude duplicate and test orders |\n| `ordered_at` | Timestamp in one timezone | Store source timezone and conversion |\n| `purchase_purpose` | self, gift, business, unknown | Do not infer without a defensible signal |\n| `category` | Controlled product family | Map renamed categories before analysis |\n| `days_since_previous` | Current order minus prior order | Never compute across different people |\n| `refund_state` | none, partial, full | Decide which intervals remain eligible |\n\nReport the 25th, 50th, 75th, and 90th percentile of repeat-purchase intervals, plus the share of customers with only one observed order. Split by category and purchase purpose only when sample sizes are adequate and definitions are stable.\n\n## Define lifecycle states as evidence, not labels\n\nA practical state definition combines three clocks:\n\n1. **Purchase clock:** Where does days-since-order fall relative to the customer's relevant cadence distribution?\n2. **Engagement clock:** Has the person clicked, browsed, replied, or otherwise shown a stronger signal than an open?\n3. **Context clock:** Is a gift anniversary, replenishment interval, contract renewal, or product release relevant?\n\nUse names that describe the rule. `past_median_repeat_interval_no_recent_click` is more reviewable than `at_risk_v2`.\n\nMigma's [audience documentation](https://docs.migma.ai/audience/overview?utm_source=marketingwiki&utm_medium=referral&utm_campaign=high-consideration-email-segmentation-window) describes dynamic segments based on status, tags, and custom fields that update as contacts change. That makes Migma a useful production surface when cadence tier, purchase purpose, and category affinity are written back as governed fields. Migma does not calculate the right business threshold for you; the worksheet remains the source of that decision.\n\n## Test six edge cases before activation\n\nCreate synthetic profiles, not real subscribers, for these cases:\n\n| Case | Expected result |\n| --- | --- |\n| Recent first-time buyer with no second purchase | Not automatically lapsed; insufficient repeat-cadence evidence |\n| Past the median interval but clicked recently | Engaged overlay prevents premature win-back treatment |\n| Gift buyer near original gift anniversary | Routes to gift-context message, not self-use replenishment |\n| Category A buyer browsing Category B | Cross-category rule requires defined affinity evidence |\n| Fully refunded last order | Uses the documented refund policy for cadence calculation |\n| Unsubscribed or bounced contact | Excluded regardless of lifecycle score |\n\nFor each profile, record input fields, evaluated segment membership, exclusion reason, expected email tone, and actual received test. A correct count is not enough if the wrong person entered the segment.\n\n## Freeze the audience at approval\n\nMigma's [campaign guide](https://docs.migma.ai/campaigns/overview?utm_source=marketingwiki&utm_medium=referral&utm_campaign=high-consideration-email-segmentation-window) documents selecting a segment or tag and viewing an estimated recipient count. Dynamic membership can change between review and send. Save the segment definition, field snapshot time, estimated count, suppression count, and a hashed or internal-ID member list at approval. Re-evaluate immediately before scheduling and require review when the population changes beyond your stated tolerance.\n\n## Recalibrate without chasing noise\n\nSet a calendar review based on data volume, not habit. At each review:\n\n- recompute interval percentiles on the same eligibility rules;\n- compare category and gift/self splits;\n- inspect customers newly classified as at risk;\n- measure complaints, unsubscribes, and conversions with declared definitions;\n- keep a holdout when sample size and policy permit;\n- version the threshold and effective date.\n\nDo not silently let an optimization system move the threshold. A model recommendation is a candidate change; a lifecycle owner still approves its meaning and downstream messages.\n\n## Approval record\n\n```yaml\nsegment_version: \"high-consideration-v1\"\nanalysis_window: \"2025-09-01/2026-08-31\"\neligible_order_rule: \"completed and not fully refunded\"\ncadence_statistic: \"category-specific p75\"\nengagement_overlay: \"clicked_or_browsed_within_30d\"\ngift_buyer_rule: \"explicit gift flag only\"\nsuppression_policy: \"provider and global suppressions\"\nmember_snapshot_at: \"2026-09-05T07:30:00Z\"\nowner: \"named lifecycle lead\"\nrecalibrate_on: \"2026-12-05\"\n```\n\n## Evidence limits\n\nThe Klaviyo source is a vendor-published practitioner account, not an independent benchmark. Marketing Wiki did not reproduce the reported buying cycle, category overlap, RFM behavior, or outcomes. Migma capabilities are vendor-documented and were not exercised. Use your own event definitions, consent rules, sample sizes, and customer cadence."}