Product

Changelog

Every release of the EngageIQ platform — new features, improvements, bug fixes, security patches, and breaking changes — in reverse chronological order.

Effective June 12, 2026
Last updated June 12, 2026
v1.3

Release 1.3.0

1.3.0LatestJune 12, 2026

This release ships the churn-risk model into general availability, adds one-click unsubscribe header support for all sending domains, and includes a significant API performance improvement for high-volume event ingestion.

  • FeatureChurn-Risk Model (GA): The AI-powered churn prediction engine is now generally available for all Pro and Enterprise plans. Scores update in real time based on contact event activity. Configure score thresholds in Settings → Churn Risk to trigger automated re-engagement flows.
  • FeatureOne-Click Unsubscribe (RFC 8058): All campaigns now include a List-Unsubscribe-Post header automatically, satisfying Google and Yahoo's February 2024 bulk-sender requirements. No action required from senders.
  • FeatureSegment Conditions — Email Engagement Filters: Segments now support filtering by open rate, click rate, and last-engagement date within any look-back window. Build re-engagement audiences in seconds from the Segment Builder.
  • ImprovementEvent Ingestion Throughput +40%: Internal pipeline refactoring reduced p99 latency for the POST /events endpoint from 180ms to 108ms under sustained load. Burst capacity increased to 50,000 events/second per workspace on Enterprise plans.
  • ImprovementCampaign Analytics — Cohort View: The analytics dashboard now shows opens and clicks by delivery cohort (hour), making it easy to identify the optimal send time for your audience.
  • ImprovementDMARC Status Dashboard: Domain settings now display a live DMARC alignment status indicator, with actionable guidance for p=none → p=quarantine progression.
  • SecurityDependency updates: Upgraded 14 transitive dependencies addressing 3 moderate and 1 high CVE in indirect dependencies (none affecting the public API surface).
  • FixFixed a race condition in the segment-refresh worker that could cause a contact's segment membership to lag by up to 5 minutes under high-write workloads.
  • FixFixed an issue where soft-bounce retries were not respecting the workspace-level suppression list introduced in v1.2.0.
  • FixResolved an edge case in the Flow Builder where a branch with zero contacts would cause the workflow to stall indefinitely rather than completing the branch gracefully.
v1.2

Release 1.2.0

1.2.0StableMay 19, 2026

Introduces workspace-level suppression lists, the transactional email template versioning system, and a full API key scope model for fine-grained access control.

  • FeatureWorkspace Suppression Lists: Manage a unified suppression list per workspace covering hard bounces, spam complaints, unsubscribes, and manual suppressions. Suppressions are enforced automatically across all send types (transactional and campaign).
  • FeatureTransactional Template Versioning: Templates now support named versions. You can promote a draft version to active, roll back to a previous version, and view a diff between any two versions directly in the dashboard.
  • FeatureAPI Key Scopes: API keys can now be created with specific permission scopes (e.g., events:write, contacts:read) for the principle of least privilege in integrations.
  • FeatureWebhook Signing: All outbound webhooks are now signed with an HMAC-SHA256 signature using a per-workspace secret, enabling you to verify payload authenticity.
  • ImprovementContact Import Performance: Bulk CSV import now processes at 50,000 contacts/minute (up from 12,000/minute in v1.1). Duplicate detection uses a streaming deduplicate pass, eliminating memory spikes on large imports.
  • ImprovementFlow Builder UX: Node connection handles are now larger on touch/trackpad devices. Long-running workflows now display a live progress indicator per branch.
  • SecuritySession security hardening: Refresh tokens are now single-use (rotation on each use). Concurrent session detection alerts are sent to the account email when a new device signs in.
  • FixFixed a timezone handling bug where scheduled campaigns in UTC+N timezones would fire one hour early during daylight saving time transitions.
  • FixFixed an issue where deleting a contact did not remove them from in-progress workflow steps, causing phantom delivery attempts.
v1.1

Release 1.1.0

1.1.0April 7, 2026

This release focuses on domain management, GDPR tooling, and the introduction of the multi-step Flow Builder for lifecycle automation.

  • FeatureFlow Builder (Beta): Visual drag-and-drop workflow editor for building multi-step lifecycle journeys. Supports trigger events, time delays, audience branches, email actions, and contact attribute updates. Available to all plans in beta.
  • FeatureCustom Sending Domains with DKIM Auto-Setup: EngageIQ now automatically generates and rotates your DKIM key pair and publishes CNAME records for one-click DNS verification. SPF and DMARC guidance is shown inline.
  • FeatureGDPR DSR Toolkit: Account admins can now trigger contact export, redact contact PII, and permanently delete a contact and all associated events directly from the dashboard — no API call required.
  • FeatureContact Activity Timeline: Each contact now has a full chronological activity timeline showing all emails sent, events received, segment memberships, and workflow entries.
  • ImprovementSegment Evaluation Speed: Segment condition evaluation was re-written to use database-native query pushdown, reducing segment rebuild time by ~65% for workspaces with > 500K contacts.
  • SecurityPassword policy enforcement: New accounts must now set a password meeting minimum entropy requirements (12 characters, mixed case, numbers). Existing accounts are prompted on next login.
  • FixFixed a bug where campaign delivery reports would omit click events for links containing query parameters with URL-encoded ampersands.
  • BreakingThe GET /api/v1/contacts/:id/events endpoint now returns events in descending chronological order (newest first) by default. Pass order=asc to restore the previous behaviour.
v1.0

Release 1.0.0 — General Availability

1.0.0March 1, 2026

EngageIQ 1.0 is the first general availability release of the unified customer engagement platform. It replaces the beta program that ran from October 2025 to February 2026. Thank you to the 180+ beta testers who shaped the product.

What's included at GA

  • FeatureTransactional Email: Send template-based or API-rendered transactional emails with full delivery analytics, custom sending domains, and per-message tracking.
  • FeatureCampaign Engine: HTML and plain-text campaigns with scheduling, audience targeting, A/B subject-line testing, and delivery-time optimization.
  • FeatureContacts & Segments: Unified contact profiles with arbitrary attribute support, real-time behavioral event tracking, and dynamic rule-based segmentation.
  • FeatureEvent Ingestion API: High-throughput REST API and JavaScript/Node SDK for tracking behavioral events. Compatible with Segment event schemas for easy migration.
  • FeatureDomains & DKIM: Full sending domain management with DKIM signing, SPF guidance, and deliverability health scores.
  • FeatureWorkspace & Team Management: Multi-workspace support, role-based access control (Owner, Admin, Member, Viewer), and audit logging.
  • FeatureBilling & Plans: Starter, Growth, and Pro tiers with monthly/annual billing via Stripe. Enterprise contracts available.
  • FeatureREST API: Full REST API (OpenAPI 3.1 spec available at /docs) covering all platform resources.
v0.9

v0.9 Beta — February 2026

0.9.0 (Beta)February 3, 2026

The final beta release before GA. Focused on performance hardening, security review findings, and API stabilization.

  • SecurityCompleted independent penetration test (Q1 2026). All critical and high findings resolved. Full report available to Enterprise customers on request.
  • SecurityEnabled AWS WAF on all public-facing load balancers. Rate limiting tightened on authentication endpoints (10 requests/minute per IP).
  • ImprovementAPI response times improved by 28% on average following database query optimization and connection pool tuning.
  • BreakingAPI base path change: All API endpoints moved from /v1/ to /api/v1/. The old path is no longer supported as of v1.0.
  • DeprecationThe legacy x-api-key header authentication is deprecated in favour of Authorization: Bearer tokens. Support will be removed in v1.4.
——

Stay Updated

Get release notifications

Subscribe to the changelog via our newsletter or RSS feed to receive notifications when new versions are released. You can also follow us on X / Twitter where we announce major releases.

For real-time system health, visit the System Status page. For breaking changes and migration guides, see the API documentation.

Read next

System Status