LoginSign Up
← Back to all sparks
Bloomreach logo

Bloomreach

MKT AUTO
Velocity2.5

Commerce experience platform with marketing automation

www.bloomreach.com ↗

Bloomreach Engagement turns event-driven — API triggers, JWT-secured tracking, and contextual AI personalization.

customer-engagementmarketing-automationai-personalizationdeveloper-apienterprise-securityshopify-integration
◆Current state
Engagement is on a steady biweekly cadence (1.296 through 1.304) with a coherent direction: more event-driven activation, stricter security defaults, and AI personalization expanded across scenario channels. Recent releases ship API triggers for real-time event response, JWT authentication for tracking data, list-attribute filtering, Shopify post-purchase events, and CSP-compliant personalization for sites with strict security headers. Two of the captured entries are cookie-consent banner scrapes from the marketing site — feed-source artifacts unrelated to product changes.
◆Where it's heading
Bloomreach is repositioning Engagement from a campaign tool into an event-driven activation layer that security and platform teams can approve. The combination of JWT auth, CSP-compliant personalization, event stream permissions, and API triggers is targeted at enterprise buyers who previously rejected MarTech tools on infosec grounds. Mobile SDK and AI personalization investments continue alongside, but the more interesting story is the developer-platform direction.
◆Prediction
Expect the API-trigger surface to grow into a fuller webhooks-and-actions automation layer in the next two releases, plus deeper AI personalization tied to those triggers. The cookie-banner entries are also a reminder that Bloomreach should investigate whether its release feed is exposing the right pages to the crawler — these will keep recurring otherwise.

◆Recent moves

  1. 2mo ago

    1.307 URL parameters fix, API trigger personalization & Mobile SDK updates

    View source ↗
  2. 2mo ago

    Cookie banner text (feed artifact, not a release)

    Cookie-policy banner text scraped as a release entry. No product change — a feed-source artifact from the marketing site rather than the engagement changelog.

    View source ↗
  3. 2mo ago

    Cookie consent text (feed artifact, not a release)

    Second cookie-consent text fragment scraped as a release entry. Again, no product change behind this — the crawler is hitting the consent layer on bloomreach.com instead of the documentation changelog.

  4. 2mo ago

    1.306 API triggers, JWT authentication, Catalog schema automation & Prediction templates updates

    View source ↗
  5. 2mo ago

    API triggers and JWT-secured tracking land in Engagement

    ⚡ SPARK

    April release adds API triggers for real-time event response, JWT authentication for tracking data, automated catalog schema creation, and customizable prediction templates. The combination shifts Engagement from scheduled-campaign tooling toward event-driven activation that an enterprise security team can sign off on.

  6. 2mo ago

    1.297 Weblayers in scenarios, Media in grid & Mobile SDK updates

    View source ↗