Skip to content
Docs

Reference

Every webhook event type Emailit sends, when each one fires, which object it carries, and which types the dashboard picker leaves out.

Updated Oct 26, 2026

This is the complete list of event types Emailit sends to webhooks and records in the event stream, plus the workspace and custom events you send yourself. Each event’s data.object holds the resource it’s about; the Object column shows its object value. Select an event name for its full payload where a reference page exists.

A webhook with All events on receives every system type below except cart.updated and product.viewed, and no workspace or custom events. When you pick events in the dashboard, some types aren’t in the picker; they’re marked “Not in picker” and you can add them with Update a webhook.

Email events

Event Object When it fires
email.accepted email An email sent with the API or Compose was accepted and queued. Not sent for SMTP.
email.scheduled email An API email with a future scheduled_at was stored. Includes scheduled_at.
email.delivered email The recipient’s mail server accepted the message.
email.attempted email A delivery attempt failed temporarily and will be retried. Sent for every attempt; includes smtp_code, smtp_enhanced_code and smtp_response.
email.bounced email Delivery failed permanently, a bounce report arrived after delivery, or retries ran out.
email.failed email Processing failed because of an error, not a reply from the recipient’s server. Rare.
email.rejected email Emailit refused to send to a recipient because the workspace isn’t verified.
email.suppressed email The recipient is on the suppression list, so the email wasn’t sent.
email.held email The email was held and not sent: suspended workspace, workspace scheduled for deletion, paused domain, not enough credits, spam score of 7 or more, or an API key set to hold. Email held while the workspace is scheduled for deletion isn’t sent, even if the workspace is restored.
email.canceled email The email was canceled in the dashboard or with the API. Includes status and previous_status. Not in picker.
email.received email A message arrived on your inbound subdomain. Carries only id, from, to, subject and created_at.
email.complained email The recipient reported the email as spam through their provider’s feedback loop.
email.loaded load The tracking image was loaded. Sent for every load, not only the first.
email.clicked click A tracked link was clicked. Sent for every click; includes link.url.
email.unsubscribed email A recipient unsubscribed using the unsubscribe link or page of a campaign email. Includes campaign, contact and unsubscribed_at. Not in picker.
email.resubscribed email A recipient resubscribed from the unsubscribe page. Includes campaign, contact and resubscribed_at. Not in picker.

Email status events (email.accepted to email.complained above) carry the email’s id, from, to, subject, status and meta, plus timestamps. Click and load events carry their own id, the email_id, a nested email object (rcpt_to, mail_from, subject, campaign, meta), the matching contact if there is one, ip_address and user_agent. For what each email status means, see Email statuses.

Domain events

Event Object When it fires
domain.created domain A sending domain was added.
domain.updated domain A domain’s settings changed, for example tracking or a subdomain key. DNS verification results don’t send this event.
domain.deleted domain A domain was deleted.

Audience and subscriber events

Event Object When it fires
audience.created audience An audience was created.
audience.updated audience An audience was renamed.
audience.deleted audience An audience was deleted.
subscriber.created subscriber A contact was added to an audience.
subscriber.updated subscriber A subscriber changed, including unsubscribing from or resubscribing to the audience.
subscriber.deleted subscriber A contact was removed from an audience, including when the contact was deleted.
subscriber.resubscribed subscriber An unsubscribed contact was added to the audience again. Sent together with subscriber.updated.

Subscriber objects include subscribed, subscribed_at, unsubscribed_at, the audience (id, name) and the contact (id, email, names and custom fields).

Contact, template and suppression events

Event Object When it fires
contact.created contact A contact was created.
contact.updated contact A contact’s fields, custom fields or audiences changed.
contact.deleted contact A contact was deleted.
template.created template A template or a new template version was created.
template.updated template A template was edited or published.
template.deleted template A template was deleted.
suppression.created suppression A suppression was added in the dashboard, with the API, by CSV import, or by an automation.
suppression.updated suppression A suppression’s reason or expiry changed.
suppression.deleted suppression A suppression was removed.

Suppressions that the delivery pipeline adds automatically after a bounce or complaint don’t send suppression.created. To track those, listen for email.bounced and email.complained.

Segment events

Only tracked segments send these events. The first count after a tracked segment is created, or after tracking resumes, doesn’t send any. Segments are in alpha and open to the Emailit team only, so only their workspaces see these events.

Event Object When it fires
segment.contact_added segment_membership A contact started matching a tracked segment. Includes joined_at.
segment.contact_removed segment_membership A contact stopped matching a tracked segment. Includes left_at. Not sent for deleted contacts.

Segment membership objects include the segment (id, name), the contact (id, email, names and custom fields) and a reason: contact, schedule or segment_updated. Changes with segment_updated, caused by editing the segment, don’t start automations.

Email verification events

Event Object When it fires
email_verification.created email_verification A single address verification was requested.
email_verification.updated email_verification A verification finished and its result is available.
email_verification_list.created email_verification_list A verification list was created.
email_verification_list.updated email_verification_list A list finished processing. Includes status and stats.

The dashboard picker also lists email_verification.deleted and email_verification_list.deleted. Emailit doesn’t send these events.

Campaign events

Campaign events aren’t in the dashboard picker. They reach webhooks with All events on, or you can add them with the API. Each carries a campaign object with id, name, status, subject, from_email, from_name, scheduled_at, sent_at and created_at. Status changes also include previous_status.

Event When it fires
campaign.created A campaign was created.
campaign.updated A campaign’s content, sender or recipients changed.
campaign.deleted A campaign was deleted.
campaign.scheduled A campaign was scheduled for a future time.
campaign.queued A scheduled campaign reached its send time and was queued.
campaign.sending A campaign started sending.
campaign.testing A campaign entered the testing status.
campaign.sent A campaign finished sending.
campaign.canceled A campaign was canceled.
campaign.archived A campaign was archived.

Form events

Sent for Forms, which is in beta. In the dashboard picker, form.submitted is under Forms.

Event Object When it fires
form.submitted form_submission Someone submitted a form, on its last step for multi-step forms. Sent once per submission.

The object includes the submission’s id (fsub_…), the form (id, name), the variant that was shown, the contact for the submitted email address (null without one), the payload with the submitted values keyed by each field’s property name, and created_at.

Commerce events

Sent for the orders, carts and product views of Commerce. Commerce is in alpha, so only the Emailit team sees these events in the dashboard picker, under Commerce.

Event Object When it fires
order.placed order An order was stored for the first time. Not sent for historical imports.
order.updated order A stored order changed, for example its status or a refund. When the status changed, it includes previous_status.
cart.updated cart A cart was created, or its items, total, status or contact changed.
cart.abandoned cart A contact’s cart with items wasn’t updated for the cart abandonment delay.
product.viewed product_view The tracking script recorded a product view.

Order objects include the items and the attribution: the campaign or automation email the order is credited to.

cart.updated and product.viewed come from site traffic. Like workspace and custom events, All events doesn’t include them, so a webhook only receives them when you subscribe to them by name.

Workspace and custom events

Workspace (w:) and custom (c:) events are the ones you send with the tracking script or the API. All events doesn’t include them, so a webhook only receives them when you subscribe to them:

Subscription Receives
w:customer.type That workspace event.
c:order.completed That custom event.
w:* Every workspace event, including ones you define later.
c:* Every custom event.

In the dashboard they’re in the Workspace & custom events group of the picker. The request’s type is the event’s type, such as c:order.completed, and data.object holds the event:

JSON
{
  "object": "custom_event",
  "name": "order.completed",
  "properties": { "order_id": "1001", "total": 59.9 },
  "contact": { "id": "con_2wPq7Lm3XcN8bV1zKd4RtY6sHf9", "email": "jane@example.com" },
  "anonymous_id": null,
  "occurred_at": "2026-10-19T09:30:00.000Z",
  "source": "api"
}

Workspace events have object set to workspace_event. source is api, js (tracking script) or dashboard, and events from the tracking script also carry context with the page and campaign. Payload filters reach the properties as properties.<name>, for example properties.total.

Deprecated event names

The Deprecated group in the dashboard picker lists names from an older version of Emailit: email.sent, email.opened, email.softfail, email.hardfail, email.error, email.delayed and email.processed. They aren’t sent any more. Use email.delivered, email.loaded, email.attempted and email.bounced instead.

The envelope every event is wrapped in.
Choose events and filters.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.