Site Events

Every site keeps a log of what happens to its members and visitors. Some events are recorded for you; the rest your own code sends when something that matters to your business happens. Journeys, automations and the CRM react to this log. See it under Automations → Journeys → Site events. Every site event is also mirrored to your account as site.<name>, so a flow, an AI agent or a function can start from it through its own “Event (when something happens)” trigger, narrowed to one site.

Nothing in the event log is deleted automatically, and the platform never stores a visitor’s IP address. A visitor who is not signed in is known only by a random id their browser keeps for your site.

Recorded for you

These arrive without any code, the moment they happen:

member_signed_up, member_verified, member_logged_in
form_submitted — a visitor who is not signed in created a row, for example through a contact form. Carries the table, the field names and the email when the form has one.
payment_succeeded, subscription_started, subscription_renewed, subscription_cancelled

Send your own

From a backend function or a flow:

await ctx.events.emit('cart_abandoned', { total: 42, currency: 'usd' });
// optional third argument: { subjectId: '<member id>', idempotencyKey: 'cart-123' }

From a page on your published site:

fetch('/api/events', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({ name: 'video_played', properties: { seconds: 30 } }),
});

Names are lowercase letters, digits and underscores, starting with a letter. A new name registers itself in the catalog the first time it is seen, so you can pick it in a journey or an automation straight away. Properties are a small JSON object (up to 30 keys, 8 KB). Pass an idempotencyKey when a retry could send the same event twice.

Choose what is recorded

Under Site events → What this site records you can switch any built-in event off, opt a table’s row changes into the log (an orders table’s status field, say), and refuse events from visitors who are not signed in. Your own custom events are always recorded. The AI can change the same settings for you.

What reacts to events

Automations — run a function when an event happens (Automations → Functions).
Journeys — email sequences that start from an event, such as a welcome series or an abandoned-cart reminder. Coming soon.
CRM — every event appears on the person’s timeline. Coming soon.