October 30, 2026

Knowledge Base Home

Journeys

Triggered Journeys: Form Submit and Interaction Submit Triggers

Journeys can now start the moment a contact takes action, rather than on a scheduled audience send. Two new trigger elements are available on the Journeys canvas:

• Form Submit starts a journey when a contact submits an Omeda Form Builder form.

• CredSpark Interaction Submit starts a journey when a contact completes a CredSpark interaction.

Each trigger can listen to multiple forms or interactions at once, and contacts enter the journey as soon as they submit.

A triggered journey uses a single trigger as its starting point in place of the Audience and Schedule elements. Triggers can connect directly to Email, SMS, Personalization, and Metering elements. Only forms that are published, active, and have Run Processor enabled are available to select for Form Submit or Interaction Submit triggers.

Triggered journeys follow their own lifecycle, so they only begin listening when you’re ready. After publishing, select Activate to move the journey to “Active.” Submissions received while a journey is published but not yet active will not enter the journey.

CDP

Content Recommendations: Attribute Targeting

Content recommendations use behavior-based scoring to surface relevant content for each visitor. Until now, those recommendations couldn’t be scoped differently from one personalization to the next. If you wanted a placement to focus on a specific sponsor or topic, there was no way to set that up on the personalization itself.

This release moves the “Is this a Content Recommendation?” question and behavior picker into the Basic Info step of the Personalization setup, so all recommendation settings are in one place. Basic Info also adds a new Attribute Targeting section, where you can choose which Olytics attributes and values a page must have, or must not have, to be recommended. You can combine multiple rules using And/Or logic.

Each content recommendation personalization can now draw from its own content pool, while your scoring models still decide what’s most relevant to each visitor. Personalizations that don’t use Attribute Targeting will continue to work as they do today.

Internal note: This was requested by Endeavor for sponsored-content placements. Only defined-value attribute types under the 500K-value limit are available in the setup, so that limit is the likely cause if a client can’t find an attribute.

Audience Builder

Save Queries from the Audience Builder Agent

The Audience Builder agent can now save the segments it builds. Once the agent has put together your audience, tell it to save and give it a name. You can also add keywords so it’s easier to find later. The saved audience shows up in Audience Builder, where you can reuse it, edit it, or use it elsewhere in the Omeda platform.

CDP

CDP Renamed to Web Behavioral Tracking

The CDP section in the navigation has been renamed to Web Behavioral Tracking, and the page title has been updated to match. The new name better describes what this area covers: Olytics, Personalizations, and Metering. This is a name change only, so everything works exactly as before and no action is needed.

Form Builder

Self-Service Refund and Cancel Form

Clients can now build a Refund and Cancel form in Form Builder so their customers can manage an order themselves without contacting customer service. Customers can choose “Refund and cancel me,” which shows their refund amount, then cancels the order and refunds the remaining balance to the original payment method. Or they can choose “Stop billing,” which turns off auto-renewal and keeps access through the end of the current term.

Subscriptions

CSV Option Now Available for the Stripe Daily Transactions Report

The Stripe Daily Transactions Report now supports CSV exports in addition to JSON. Customers who prefer to review this report directly, instead of routing it through a data pipeline, can now schedule their daily download as a CSV that’s ready for immediate use.

Customer and Order Metadata on Stripe Reporting

Stripe Connect customers can now see Omeda order details in their own Stripe reporting. This information appears in Payments List exports from the Stripe Express Dashboard. It’s also included in the itemized scheduled options in Omeda’s versions of the Balance Summary and Payout Reconciliation reports. This makes it easier to match payouts and balance activity to specific Omeda orders.

The new fields are Omeda’s Transaction ID, Sales Channel, Promo Code, Stripe’s Charge ID, the Payment Type, and the Card Last 4. These fields will appear for payments processed after the release. No setup is needed.