> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flexype.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Purchase Driven

> Target customers by what they bought before — past coupon use, order value, or order count.

Every other coupon type looks at what's in the cart right now. Purchase Driven looks at what the customer did **before**. It's the retention tool: win-backs, loyalty rewards, and offers aimed at people who used a specific campaign in the past.

<Info>
  Shared setup, eligibility, and usage limits are covered in [Coupons](/features/coupons/overview). This page covers only what's specific to this type.
</Info>

## An extra step

Purchase Driven is the only type with **six** steps. A **User Behaviour** step sits between Setup and Condition:

**Setup → User Behaviour → Condition → User Eligibility → Usage Limits → Preview**

<Frame caption="Setup is the familiar code and discount value — the difference comes next.">
  <img className="rounded-lg" src="https://mintcdn.com/flexype/bFr-dWxa-QGiY3oF/images/features/coupons/purchase-driven-setup.png?fit=max&auto=format&n=bFr-dWxa-QGiY3oF&q=85&s=428eb3fd8872dae0d41575f660454007" alt="Purchase Driven setup step with a six-step progress bar showing Setup, User Behaviour, Condition, User Eligibility, Usage Limits, and Preview" width="1512" height="801" data-path="images/features/coupons/purchase-driven-setup.png" />
</Frame>

## The User Behaviour step

<Frame caption="User Behaviour: which past action qualifies a customer, and the window it's measured over.">
  <img className="rounded-lg" src="https://mintcdn.com/flexype/bFr-dWxa-QGiY3oF/images/features/coupons/purchase-driven-behaviour.png?fit=max&auto=format&n=bFr-dWxa-QGiY3oF&q=85&s=d97f38fd79c0aa51f06086fd39896a14" alt="User Behaviour step showing behaviour period with start date and optional end date, and customer behaviour options for use coupon codes, minimum order amount, and minimum number of orders" width="1512" height="801" data-path="images/features/coupons/purchase-driven-behaviour.png" />
</Frame>

### Customer behaviour

Pick the past action that qualifies someone:

| Option                       | Qualifies customers who                                            |
| ---------------------------- | ------------------------------------------------------------------ |
| **Use coupon codes**         | Previously used a specific coupon — pick it with **Select Coupon** |
| **Minimum order amount**     | Previously placed at least one order meeting an amount threshold   |
| **Minimum number of orders** | Have at least a set number of past orders                          |

### Behaviour period

A start date and an optional end date. **The past activity only counts if it happened inside this window.**

This is what makes the type precise. Without it you'd be targeting all-time behaviour; with it you can target "customers who bought during the festive sale" or "anyone who used our launch code in March".

<Note>
  The behaviour period describes **when the customer's past activity happened**. The active period, set later under Usage Limits, describes **when this new coupon can be used**. They're different dates and they're easy to confuse.
</Note>

## How it calculates

| Behaviour rule              | Behaviour period | Qualifies?                                              |
| --------------------------- | ---------------- | ------------------------------------------------------- |
| Used coupon `FESTIVE20`     | 1–31 Oct         | Customer used it 12 Oct → **yes**                       |
| Used coupon `FESTIVE20`     | 1–31 Oct         | Customer used it 3 Nov → no                             |
| Minimum order amount ₹5,000 | Last 6 months    | Customer's biggest order in window was ₹5,200 → **yes** |
| Minimum number of orders 3  | Last 12 months   | Customer has 2 orders in window, 5 all-time → no        |

## Examples

<AccordionGroup>
  <Accordion title="Win back festive buyers" icon="rotate-left">
    **Setup:** Coupon code `WELCOMEBACK` · 15% off
    **User Behaviour:** Use coupon codes → `FESTIVE20` · behaviour period covering the festive window

    Reaches exactly the people who bought on discount last season, and nobody else.
  </Accordion>

  <Accordion title="Reward loyal customers" icon="award">
    **Setup:** Coupon code `LOYAL15` · 15% off · cap ₹500
    **User Behaviour:** Minimum number of orders 3 · behaviour period covering the last year

    Recognises repeat buyers without opening the discount to first-timers.
  </Accordion>

  <Accordion title="Upgrade big spenders" icon="arrow-trend-up">
    **Setup:** Coupon code `VIP500` · fixed ₹500 off
    **User Behaviour:** Minimum order amount ₹5,000
    **Condition:** Minimum purchase amount ₹4,000

    Targets customers who've spent big before, and asks for a substantial cart again.
  </Accordion>

  <Accordion title="Re-engage a lapsed segment" icon="clock">
    **Setup:** Automatic · 10% off
    **User Behaviour:** Minimum number of orders 1 · behaviour period ending several months ago

    Because the window closed months back, this reaches people who bought then and haven't since.
  </Accordion>
</AccordionGroup>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Nobody is qualifying for my coupon.">
    Usually the **behaviour period** is too narrow, or it's set to a future or current window when you meant a past one. Check that real orders exist inside those dates.
  </Accordion>

  <Accordion title="What's the difference between this and User Eligibility's Total order count?">
    **Total order count** is a simple lifetime count. Purchase Driven measures behaviour inside a date window and can key off order value or a specific past coupon. Use eligibility for "has ordered before", Purchase Driven for anything more targeted.
  </Accordion>

  <Accordion title="Can I target people who used one of several coupons?">
    The behaviour rule selects one coupon. For several, create one Purchase Driven coupon per source campaign.
  </Accordion>

  <Accordion title="Does the customer need to be logged in?">
    Their past orders have to be identifiable, so the discount resolves once the customer is identified at checkout.
  </Accordion>
</AccordionGroup>

<CardGroup cols={2}>
  <Card title="All coupon types" icon="ticket" href="/features/coupons/overview">
    Shared setup, limits, and combining rules
  </Card>

  <Card title="Orders" icon="receipt" href="/features/orders">
    Check a customer's past order history
  </Card>
</CardGroup>
