Skip to content

Events

Turn events into personal email.

Connect purchases, signups and product activity to customer context. Follow up with a message that fits.

HaldenWorkflow · Refill after an order

EventOrder completed
ProductHouse Espresso

Customer record

Last order
House Espresso
Brewer
V60 pour-over
Likes
Bright, fruity coffee
Preference
Try a lighter roast

Check what changed before you send.

A purchase, signup or completed lesson starts the journey. Check their progress after the wait, so people who already acted can skip the reminder.

Example journey

What happened

Order completed

Halden store 09:41

Order
H1048
Product
Sierra Filter · 250 g

Who it matters to

Nora Silva

Customer

Related order
H1048 · fulfilled
Brewing preference
Pour-over · whole beans
Newer purchaseNone recorded

A timely refill

Configured journey
  1. WaitWait 14 days
  2. QueryLook for a newer purchase
  3. If ElseStill needs a follow-up
  4. Send EmailSend a refill invitation

Adaptyle writes from this context.

No newer purchase is recorded.
What if they act during the wait?
Personal emailRecipient preview
To Nora SilvaAnother cup of Sierra Filter?

Let their activity shape your audience.

Turn event history into order counts, spend totals and last-purchase dates. Use those attributes in audiences and journey checks.

Nora’s recorded ordersExample
20 Aug
Sierra FilterOrder H1012
$18
2 Sep
Decaf HouseOrder H1027
$24
18 Sep
Sierra FilterOrder H1048
$18

Orders in 30 days

3Count recorded orders

Data through 18 Sep, 09:41 UTC

Computed attributes publish on a schedule. “Data through” tells you how current the result is.

Explore computed attributes

The customer. And the business around them.

Attach events to customers or business objects. A subscription, workspace or order can give your next message the context it needs.

Explore connected records
Business eventSubscription renewed

About this record

Subscription S-204
Plan
Monthly coffee
Next delivery
2 October

Related customer

Nora SilvaPour-over · whole beans

Collect the signals that matter.

Define the event and its fields. Connect your website or backend. Give every action a clear meaning before it enters a journey.

Act on a confirmed purchase.

Send purchases, signups, and other business events from your backend to start the journeys you configure.

Example event
order-completed

Existing customer record

eventIdstring
order_h1048
contactIdrecord ID
CONTACT_RECORD_ID
productstring
Sierra Filter
amountnumber
18
  1. Authenticated by your server

    A workspace API key authorizes the business event.

  2. Connected to the customer

    Use the customer’s maxclicks record ID as contactId.

  3. One identity for each occurrence

    Retry with the same eventId and payload to recover its receipt.

What the response means

202 Accepted

The API returns an acceptance receipt. Preparation, journey execution, and email delivery have their own status.

order-completed.shRead the events API
curl --fail-with-body \
  https://api.maxclicks.ai/v1/events/order-completed \
  -H "Authorization: Bearer $MAXCLICKS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "eventId": "order_h1048",
    "contactId": "CONTACT_RECORD_ID",
    "product": "Sierra Filter",
    "amount": 18
  }'

Use your event schema’s ID or slug and declare its product and amount fields. Replace contactId with an existing customer record ID.

Follow the event from acceptance to delivery.

  1. Keep the receipt.

    The POST response returns data.id to identify this occurrence. Your eventId is the key for retrying the same input.

  2. Check readiness.

    Use data.id with the status endpoint. A ready result means prepared for downstream use; it does not confirm email delivery.

    Read the status contract
  3. Inspect the journey.

    Open the workflow’s Runs tab to inspect its path and the Send Email step’s delivery status.

    Inspect a workflow run

Bring your next customer goal.

See what maxinja and Adaptyle can build for your customers.

Book a demo