Event tracking changelog

October 2026

1. Oct 20, 2026

   New

   A/B tests, sending options and reports for campaigns, and Commerce in alpha

   CampaignsAutomationsEvent tracking

   • A/B tests: test up to five versions of a campaign and send the winner by open or click rate. See A/B testing.
   • Sending options: smart sending, skipping unengaged contacts, UTM parameters, tags, and sending throttled, at each recipient’s local time or at their best hour. Recipients’ time zones come from the tracking script. See Sending options.
   • Reports: opens by email client, device and country, a click map, follow-ups to contacts who didn’t open or click, a campaign calendar and Retrieve campaign statistics.
   • Fixed: Send or schedule a campaign, with the API or the MCP server, returns 422 for a campaign that is already sending or was sent, instead of sending it again.

   Commerce in alpha

   Commerce is open only to the Emailit team while we test it, so customer workspaces don’t see it yet. See Who can use Commerce.

   • Shop data: products, orders and carts from the Products, Orders and Carts APIs, which also take Events Only keys, or from the tracking script. Orders are credited to the campaign or automation email the buyer last clicked or opened, and Email Marketing > Commerce shows revenue from email, top products and top campaigns. See Commerce and Connect your shop.
   • In the event log: orders, carts and product views are system events (order.placed, order.updated, cart.updated, cart.abandoned, product.viewed) on the Events page, in contact activity and for webhooks.
   • Products, coupons and the cart in emails: product grids and recommendations, a unique coupon code for every recipient, the contact’s cart and their purchase data. See Products, coupons and the cart.
   • Revenue in campaigns: revenue, orders and conversion rate in reports, and A/B tests won by orders or revenue.
   • Segments and automations: segment rules for orders, spend, churn risk, products bought or viewed, carts and coupons (see Activity rules), and Placed an order and Abandoned a cart triggers with ready-made recipes.
2. Oct 20, 2026

   New

   Event tracking: workspace and custom events

   Event trackingAPI keysWebhooks

   You can now send your own events next to the ones Emailit records, such as an order, a plan change or a product view. They’re on the new Workspace events and Tracking tabs of Email API > Events.

   • Two scopes. Workspace events (w:<name>) are declared first with typed properties, and Emailit rejects events that don’t match. Custom events (c:<name>) take any JSON object. The event log has a Scope filter, and the List events API a scope parameter.
   • From your servers. Send an event records one event, and Send events in a batch up to 100. They work with the new Events Only API keys, which can send events but can’t read data or send email.
   • From your website. The tracking script sends events with a public tracking key that you can limit to your own sites. identify ties a visitor’s events to a contact.
   • Contacts and webhooks. Events show in the contact’s Activity log. Webhooks receive the types you pick, or every workspace or custom event with w:* and c:*.
   • API and MCP. The Workspace events and Tracking keys APIs, and the send-event and workspace event tools in the events MCP toolset.
   • Plans. Event tracking and the tracking script are included with Pro, Business and Custom plans. Pro can use 100 event types, Business 1,000, and Custom has no limit. See Limits.

   See Event tracking.