Release 1.314

TL;DR: This release adds voucher support and SMS/omnichannel campaigns to the Loomi Marketing Agent, improves Omniconnect reliability, adds direct PostgreSQL and Redshift imports for Item collections, extends outbound IP coverage, and brings external deliverability data into the email deliverability dashboard.

Release date: 22.7. - 27.7.2026

Loomi Marketing Agent for campaigns

Vouchers

The Loomi Marketing Agent for campaigns can now add vouchers (discount codes) to email campaigns email campaigns it builds, including unique per-customer codes from your existing voucher pools.

What's new

• Unique codes from a pool: Ask for unique per-customer codes, such as "Send a summer sale email with a unique discount code for each customer from our SUMMER2026 pool." The agent draws a unique code per recipient and, by default, saves each customer's code so follow-up emails reuse the same one.
• Existing voucher attributes: Reference a voucher already assigned to your customers, such as "Send a welcome email with our Welcome_10 voucher." The agent reads the code from each customer's profile.
• Shared codes: Supply a single code to include for all recipients.
• Real codes only: The agent only uses voucher pools and attributes that already exist in your project. If nothing is configured, it tells you instead of inventing a code.

Access

Requires existing voucher pools or attributes configured in Engagement.

SMS and omnichannel campaigns

The Loomi marketing agent for campaigns can build SMS and omnichannel campaigns that combine email and SMS in a single flow. Describe the campaign you want in plain language, and the agent sets up the right channel and reflects it in the campaign brief.channel and reflects it in the campaign brief.

What’s new

• SMS campaigns: Ask for an SMS send, such as "text everyone who's opted in to SMS about our flash sale." The agent recognizes the channel and writes copy for SMS—concise, personalized, and within message limits.
• Omnichannel (email and SMS): Describe a campaign that uses both channels in one prompt, such as "email the whole database about our summer sale, then follow up a day later with an SMS to everyone opted in." The agent builds a single scenario spanning both channels—no need to manage separate email and SMS campaigns.
• Respects your project setup: SMS is only offered when SMS is set up on your project. The agent follows your project-wide settings, including silent hours and frequency caps.

Access

SMS must be configured on your project.

External deliverability data in email deliverability dashboard

Monitor your sender reputation and inbox-placement signals from Google Postmaster Tools and Microsoft SNDS directly in the email deliverability dashboard—no more switching between external portals.

What's new

• Track spam rate, email authentication pass rates, and Gmail compliance status in one place.
• Monitor Microsoft filter results, complaint rate, and spam trap hits for Hotmail and Outlook recipients across your sending IPs.
• Access up to 13 months of historical data once connected, so you can track trends and investigate issues over time.

Access

Requires Google Postmaster Tools and/or Microsoft SNDS integration to be set up. See Set up external deliverability data integrations.

Omniconnect—reliability improvements

Omniconnect has a new architecture with runtime and ingestion guardrails. Processing is reliable and predictable, with tenant isolation that prevents one integration from affecting others.

What's new

• New architecture scales to 100 million requests per month per tenant.
• New monthly limits and cap for processing rate. Requests above rate limit are accepted and queued.
• Tenant isolation ensures one high-volume integration can't affect other customers on shared infrastructure.
• Usage is now visible on the usage dashboard—track your monthly request volume and processing rate against your allowance.

Access

Available to all customers on unified instances. Processing limits depend on your plan.

Import directly from PostgreSQL and Amazon Redshift

Import product data from PostgreSQL (v14+) or Amazon Redshift into Bloomreach using a SQL SELECT query—no file exports or staging required.

What's new

• Connect directly to PostgreSQL or Redshift and import using query mode or table mode.
• One connector works for both Data Hub item collections and Engagement general catalogs.
• Redshift support is included—no separate tile or credentials needed.
• Column mapping, scheduling, SSL/TLS, and fixed outbound IPs all work the same as existing imports.

Access

Included in every package with data imports.

Fixed outbound IPs

Fixed outbound IP addresses cover all import and export integrations.

What's new

• Newly covered imports: S3, Azure Blob / ADLS Gen 2, MSSQL / Azure SQL, Snowflake, Databricks, SQL over SSH tunnels.

• Newly covered exports: S3, Azure Blob.

• Find the IP list in Settings > Security, on each connector screen, or fetch it via public API—useful if you maintain firewall rules programmatically.

• The Use static IPs checkbox is removed for newly covered connectors—fixed IPs are always on for these. Webhooks and channels remain opt-in.

• Nothing changes for existing imports.

Access

Available to all customers.