Skip to main content
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.
  • A connector: the WordPress plugin reports WooCommerce orders and abandoned baskets; n8n and Zapier have a “record an event” action. See 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.
The events of a subscriber

What a customer did, on her record: two orders and a basket left behind.

​
Two names that mean something

Every other name is yours.

​
What you can do with events

Start an automation

The trigger The person does something: each time the event is reported, the person enters.

Build a segment

The condition Something the person did: ordered in the last 30 days, never ordered, ordered at least five times.

Write with it

{{ event.total }}, {% for item in event.items %} in the e-mails of the automation the event started.

See it

A subscriber’s record shows what the person did, most recent first, across all their lists.

​
The condition in segments

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

​
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.