Message Tags

What it does

Message tags let you label every outgoing email with your own metadata. Pass an array of name and value pairs on a send, and mailkube carries them through the entire lifecycle of the message.

Tag by campaign, tenant, feature, environment, or anything else your application tracks. There is no fixed schema and no setup. You decide what the names and values mean, and mailkube keeps them attached to each message from send to delivery.

Key benefits

• Free-form name and value tags. Add as many tags as you need on a single send, over both the REST API and SMTP. A tag is just a name and a value, so campaign: spring-sale or tenant: acme both work with zero configuration.
• Filter your sending logs by tag. Narrow your log view to a single tag to answer questions fast. See every message sent for one campaign, one customer, or one release without scrolling through unrelated traffic.
• Dashboard tag breakdown. The dashboard groups your sending volume by tag so you can see at a glance which campaigns or tenants drive the most email, and how each is delivering.
• Tags in every webhook payload. Delivery, open, click, and bounce events all carry the same tags you set at send time. Route events by tenant, attribute engagement to a campaign, or update your own records without a lookup.

Getting started

1. Add a tags array to your send, with each entry holding a name and a value
2. Send over the REST API or SMTP as usual
3. Open your sending logs and filter by any tag to see matching messages
4. Check the dashboard for the tag breakdown, and read the tags back from your webhook payloads

See the API Reference for the tag object schema on the send endpoint and the webhook event payload format.