Create and send

Customer events

Track product behavior and use it throughout Email Bump.

Event model

An event connects a named customer action to an email address. Add properties for context and optional value, currency, and quantity fields for revenue reporting.

Track an event

POST/v1/events

Send events from your server with an API key — the full field list is on the Events API page.

cURL

curl -X POST https://emailbump.com/api/v1/events \
  -H "Authorization: Bearer ebk_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "jamie@example.com",
    "event": "Purchased",
    "properties": { "product": "Pro plan", "billing_period": "annual" },
    "value": 249,
    "currency": "USD",
    "quantity": 1
  }'

Keep the key server-side

An API key can read and write everything in the project, so track events from your backend — never from browser code. There is no browser-safe ingestion key yet.

Use events

Trigger flowsStart a journey when a customer acts.Build segmentsTarget people by behavior and properties.Measure revenueConnect email performance to purchase value.

Revenue attribution

An event with a value above zero is revenue, and we credit it to the email that earned it: the last campaign or automation email the contact clicked within your attribution window, or, if they clicked nothing, the last one they opened. The window is 5 days unless you change it under Settings → Revenue attribution.

That is what fills the revenue figures in Analytics and on each campaign and automation. Transactional email never earns credit. The full rules are in Revenue attribution; the Stripe integration uses the same rules for payments.