Skip to content
Optima docs
ConsoleCampaignsJourneys

Decide node

Rank offers for each profile inside a journey, carry the winner forward, and optionally choose catalogue items to show with it.

A decide node asks the next-best-action engine which offer is best for this profile right now. It ranks the offers, applies each offer's eligibility rules, consent, caps and control groups, and stores the winner on the profile's run. A later Send node attaches that offer to its message with Offer from. A decide node can also pick catalogue items, such as trending products, to be shown alongside.

Who uses it

Campaign creators. Changing the node needs campaign_editor, or another role your administrator has given access to this area — see Licences and roles. The decide node itself, shared offer catalogues as an Offer source and item recommendations need the Decision package.

Fields

FieldMeaningValid valuesDefault
Offer sourceWhere the offers come from: this campaign's own offers, or a shared offer catalogue with the same entity type as the campaign. A missing or inactive catalogue gives an empty decision at run time and never fails the run.This campaign's offers or a catalogue (inactive ones are marked)This campaign's offers, or the campaign's configured catalogue
Offer tag filterOnly catalogue offers carrying all of these tags are ranked. Shown once a catalogue is chosen.TagsNone
Top NHow many offers to keep.Whole number, 1 to 101
Decision contextValues an offer's eligibility rule and score can read as context.name, for example a channel or a page. Values can be personalization values, resolved per profile when the run reaches the node. The journey's own state is always available as context.state.Name and value pairsNone

Items

An optional second part picks catalogue items for the profile and stores them in the run alongside any offer decision, in the same shape as the items helper in message templates.

FieldMeaningValid valuesDefault
Item catalogueThe recommendation catalogue to rank.A catalogue, or noneNone
StrategyHow items are ranked.Trending, Recently viewed, Similar to, AffinityTrending
CountHow many items.0 to 103
Seed — item key or expressionFor Similar to only: the item to be similar to, such as SKU-123, or an expression such as .Run.State.seed.TextEmpty

Blended rankings and hand-pinned item selections are not available here. Use the items composer in a message template for those. If your licence does not include item recommendations the field says so, and if no recommendation catalogue exists you are asked to create one under Recommendations first.

Actions

  • The decide node has one unlabelled outgoing edge. The winning offer lands in the run under decide:NODE and is available to later steps. A Send node picks it with Offer from; if the decide node chose nothing, that send is skipped.
  • Test the node with Pre-flight. The simulation shows the Decision at each decide step.
  • On the campaign page, Test decide in Offers & decisioning ranks offers for one profile and explains why each offer was chosen or excluded.

Examples

Win-back offer. Offer source your Winback offers catalogue, Offer tag filter winback, Top N 1. The following Send step sets Offer from to this node and uses the offer's payload in the email.

Channel-aware ranking. Decision context channel = email. An offer's eligibility rule can read context.channel.

Show products with the offer. Add Item catalogue Products, Strategy Recently viewed, Count 3.

Common problems

  • The editor says Top N must be a positive integer. Enter 1 to 10.
  • The following send was skipped. The decide node chose nothing: no offer was eligible, or consent, a frequency cap, a fatigue policy or a control group excluded them all.
  • The decision is always empty. The chosen catalogue is missing or inactive. Check Offer source.
  • Item recommendations are not on this account's licence. The Decision package is not part of your licence.
  • Offers are missing from the catalogue. The catalogue's entity type must match the campaign's.
  • Save is refused with recommendation catalogue does not exist. The Item catalogue must name a recommendation catalogue that exists under Recommendations, spelled exactly as it is there, including upper and lower case. It is checked when you save; a name that differs only in case is refused with a did you mean hint. If Optima cannot reach the catalogue list at that moment, the save goes through unchecked.

On this page