events array when you create or update it. Each event arrives inside a delivery’s events array, and its data shape is described below.
Kit is rolling event types out incrementally. The events marked Available below deliver today; the rest are planned and listed so you can see what’s coming. Planned events can’t be subscribed to yet: the API rejects them with a
422 and the create panel in Kit doesn’t offer them. They become subscribable the day they ship.Subscriber events
Resource events
Payloads
Subscriber events carry thesubscriber object, plus the related resource where one exists. The subscriber object matches the shape returned by the V4 subscribers API:
subscriber.created
Fires when a subscriber is added to the account. data carries the subscriber object above.
subscriber.activated
Fires when a subscriber transitions into the active state. data carries the subscriber object above.
subscriber.unsubscribed, subscriber.bounced, subscriber.complained
Fire when a subscriber unsubscribes, when their address hard-bounces, and when they report an email as spam. Each carries the subscriber object above, whose state reflects the new status.
subscriber.subscribed_to_form
Fires when a subscriber joins a form. Includes both the subscriber and the form.
subscriber.added_to_sequence and subscriber.sequence_completed
Fire when a subscriber starts a sequence, and when they finish its last email. Both include the sequence.
subscriber.tag_added and subscriber.tag_removed
Fire when a tag is added to or removed from a subscriber. Both include the tag. Deleting a tag does not fire subscriber.tag_removed for each subscriber that had it — you get a single tag.deleted event instead (see below).
subscriber.custom_field_value_updated
Fires when a custom field value changes on a subscriber — one event per field changed. Includes the field and its new value.
sequence.created, sequence.deleted, sequence.published, sequence.disabled
Fire on the sequence itself, not on a subscriber. data carries the sequence object shown above.
tag.created and tag.deleted
Fire when a tag is created or deleted on the account. These are resource events — data carries the tag itself, no subscriber.
Deleting a tag removes it from every subscriber at once, but Kit emits only the one
tag.deleted event — there is no subscriber.tag_removed per subscriber. If you mirror tag membership, drop the tag from all subscribers when you receive tag.deleted.broadcast.created, broadcast.sent, broadcast.deleted
Fire when a broadcast is created, when its send completes, and when it’s deleted. data carries a summary of the broadcast; fetch the full representation, including content, from the V4 broadcasts API.
post.published
Fires when a post is published. data carries a summary of the post; fetch the full content from the V4 posts API.
custom_field.created and custom_field.deleted
Fire when a custom field is created or deleted on the account. These are resource events — data carries the field itself, no subscriber.