Track events
Events are what your customers do — “signed_up”, “added_to_cart”, “purchased”. Stream them to Climails and they become the fuel for segments, automation triggers and revenue attribution.
What you'll need
- An API key with permission to write events
- A backend or frontend that can POST when something happens
Send one event
POST to /v1/events with the event name, who it belongs to, and any properties. Identify the contact by id, external_id or email.
curl https://api.climails.com/v1/events \
-H "Authorization: Bearer sb_live_<prefix>.<secret>" \
-H "Content-Type: application/json" \
-d '{
"name": "purchased",
"contact": { "email": "[email protected]" },
"occurred_at": "2026-07-01T10:24:00Z",
"properties": { "amount": 49.0, "currency": "USD", "plan": "pro" }
}'Send events in bulk
Backfilling or batching? POST up to 1000 events at once to /v1/events/bulk instead of one request each.
Put events to work
- Segments — build conditions on events, e.g. did “purchased” in the last 30 days, or did it at least 3 times.
- Automations — start a flow the moment an event arrives (event trigger).
- Revenue — attach an amount property and the originating campaign to attribute revenue in analytics.
Frequently asked questions
How do I identify the contact on an event?
By id, external_id or email. If the contact doesn't exist yet, the event still associates once they're created with a matching identifier.
What's the bulk limit?
Up to 1000 events per call to /v1/events/bulk.
Can I segment on how many times an event happened?
Yes — event conditions support a count operator and a time window (e.g. ≥ 3 times in the last 30 days).
Start sending in minutes
Create a free account, connect your domain and reach your audience across every channel — no credit card needed.
Free plan forever · No credit card required · Set up in minutes