Skip to main content
Automatically generated — Upstack creates this event from your purchase events. You don’t fire it.
Fires when a customer’s previous order was 12 or more calendar months ago.

How It Works

Upstack checks every purchase event that has a customer ID and an order ID:
  1. Previous order lookup. Upstack finds the customer’s most recent earlier order in its order records. The order being processed is left out.
  2. Lapsed check. If at least 12 months have passed since that earlier order was created, Upstack generates a lapsed_purchase event.
  3. Forwarding. The event is sent to your configured destinations.

Lapsed Customer Definition

A customer is lapsed when their previous order was created 12 or more calendar months before Upstack processes the new purchase. The threshold is calendar months, not a fixed number of days, and it’s measured in UTC. A customer whose last order was on March 15, 2025 counts as lapsed from March 15, 2026. A first-time customer has no earlier order, so their purchase never generates lapsed_purchase.

Parameters

You don’t send this event. Upstack creates it from purchase, so it carries the same standard parameters and user data.

Destination Mapping

Meta needs each custom event approved before you can optimize on it. See How to approve Meta custom events.

Metrics Available

In the Upstack dashboard, you can view:

Customer Lifecycle Context

lapsed_purchase doesn’t replace rc_purchase. Upstack decides each one separately for every purchase, so a returning customer’s order can generate both. A customer who orders again within 12 months gets no lapsed_purchase.