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

# Events

> What people did — an order, a basket left behind — and what Lekalao does with it.

A field says what a person **is**. An event says what they **did**, and when: placed an order, left a basket, saw a page, renewed. Your shop or your application reports events; Lekalao keeps them on the person's profile and lets you act on them.

## Where events come from

* **The API**: `POST /v1/events`, one event or a batch of up to 1,000. See [Events through the API](/developers/events).
* **A connector**: the WordPress plugin reports WooCommerce orders and abandoned baskets; n8n and Zapier have a "record an event" action. See [Connectors](/developers/connectors).

An event has a **name** you choose (`order`, `cart.abandoned`, `trial.started`), optional **properties** (the items, a link, a total), an optional **value** with its currency, and an optional **reference** of yours: the same reference sent twice is recorded once.

The person does not have to be a subscriber yet. The event is kept under their address and joins their profile the day they subscribe.

<Frame caption="What a customer did, on her record: two orders and a basket left behind.">
  <img src="https://mintcdn.com/lekalao/L23y78v0n8Vzliow/images/en/subscriber-events.png?fit=max&auto=format&n=L23y78v0n8Vzliow&q=85&s=09ac6c18a5a937680ada20c16a51a1df" alt="The events of a subscriber" width="704" height="502" data-path="images/en/subscriber-events.png" />
</Frame>

## Two names that mean something

| Name             | What Lekalao does with it                                                                                                                                   |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `order`          | With a `value`, it is counted as **revenue** and credited to the last e-mail the person opened or clicked. See [Statistics](/campaigns/statistics#revenue). |
| `cart.abandoned` | Starts the ready-made **Abandoned basket** journey. See [Automations](/automations/overview#ready-made-journeys).                                           |

Every other name is yours.

## What you can do with events

<CardGroup cols={2}>
  <Card title="Start an automation" icon="play" href="/automations/triggers#the-person-does-something">
    The trigger **The person does something**: each time the event is reported, the person enters.
  </Card>

  <Card title="Build a segment" icon="filter" href="/contacts/segments">
    The condition **Something the person did**: ordered in the last 30 days, never ordered, ordered at least five times.
  </Card>

  <Card title="Write with it" icon="pen" href="/content/personalization#what-an-event-brings">
    `{{ event.total }}`, `{% for item in event.items %}` in the e-mails of the automation the event started.
  </Card>

  <Card title="See it" icon="eye" href="/contacts/subscribers#a-subscribers-record">
    A subscriber's record shows what the person did, most recent first, across all their lists.
  </Card>
</CardGroup>

## The condition in segments

**Something the person did**, then the name of the event, then one of:

| Operator                          | Example                                    |
| --------------------------------- | ------------------------------------------ |
| happened in the last (days)       | `order` happened in the last 30 days       |
| did not happen in the last (days) | `order` did not happen in the last 90 days |
| has happened                      | `trial.started` has happened               |
| has never happened                | `order` has never happened                 |
| happened at least (times)         | `order` happened at least 5 times          |

## How long events are kept

Events are kept with the person. Erasing a person under the GDPR erases their events; exporting their data includes them. See [Privacy](/account/privacy).