ドキュメントJourney OptimizerJourney Optimizer ガイド

条件命令（if、then、else） conditional-instruction

最終更新日： 2026年9月5日
  • 適用対象：
  • Journey Orchestration

作成対象：

  • Experienced
  • 開発者

高度なエディターでは、条件命令（if、then、else）をサポートしています。 これにより、より複雑な式を定義できます。 条件命令は、次の要素で構成されています。

  • if：最初に評価される条件。
  • then：条件評価の結果が true の場合に評価される式。
  • else：条件評価の結果が false の場合に評価される式。
NOTE
すべての式は括弧で囲む必要があります。
if  (<expression1>)
then
   (<expression2>)
else
   (<expression3>)

<expression1> は​ ブール値 ​を返す必要があります。

<expression2> と <expression3> は、同じタイプまたは互換性のあるタイプを持つ必要があります。 サポートされているシグネチャと戻り値のタイプは次のとおりです。

boolean,boolean : boolean
dateTime,dateTime : dateTime
dateTimeOnly,dateTimeOnly : dateTimeOnly
decimal,integer : decimal
integer,decimal : integer
integer,decimal : decimal
duration,duration : duration
string,string : string
listBoolean,listBoolean : listBoolean
listDateTime,listDateTime : listDateTime
listDateTimeOnly,listDateTimeOnly : listDateTimeOnly
listDateOnly,listDateOnly : listDateOnly
listDecimal,listDecimal : listDecimal
listInteger,listInteger : listInteger
listString,listString : listString

用途

条件命令を使用すると、条件アクティビティの数を減らして、ジャーニーワークフローを最適化できます。 例えば、同じアクションアクティビティ内で、1 つの条件式のみを使用して、1 つのフィールド定義に 2 つの代替オプションを指定できます。

アクションアクティビティの例（条件命令の結果として文字列を想定するフィールドの場合）：

if (startWithIgnoreCase(@event{eventiOSPushPermissionAllowed.device.model}, 'iPad') or startWithIgnoreCase(@event{eventiOSPushPermissionAllowed.device.model}, 'iOS'))
then
   ('apns')
else
   ('fcm')
AI Knowledge Reference

This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.

For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.

  • TL;DR: This page explains the if / then / else conditional instruction available in the Journey advanced expression editor, including syntax rules, supported type combinations, and a practical usage example.

Intents:

  • Write a conditional expression using if, then, and else to return different values based on a boolean condition
  • Reduce the number of condition activities in a journey by embedding inline conditional logic within a single action activity
  • Determine which data type combinations are valid for the then and else branches
  • Apply the conditional instruction to route push notification tokens to either APNS or FCM based on device model

Glossary:

  • Conditional instruction: An if / then / else expression construct in the advanced editor that evaluates a boolean and returns one of two expressions (product-specific)
  • Advanced expression editor: The Journey Optimizer interface for writing complex expressions used in conditions, wait activities, and action parameter mapping (product-specific)

Guardrails:

  • Parentheses are required around all expressions in the if, then, and else clauses
  • The if clause (<expression1>) must return a boolean type
  • The then and else expressions (<expression2> and <expression3>) must have the same type or compatible types (e.g. decimal and integer are compatible, string and integer are not)
  • Not all type combinations are supported — only the pairs listed in the supported signatures table are valid

Terminology:

  • Canonical name: Conditional Instruction — Acronym: none — variants: if/then/else, ternary-style condition
  • Synonyms: “conditional instruction” = “inline condition” = “if-then-else expression”
  • Do not confuse: conditional instruction (inline expression) ≠ Condition activity (a journey canvas node)

FAQ:

  • Q: Does the if clause need to be wrapped in parentheses? — Yes, parentheses are required around all expressions including the condition in the if clause.
  • Q: Can I use if / then / else to return a number from one branch and a string from another? — No; <expression2> and <expression3> must have the same or compatible types.
  • Q: How does the conditional instruction reduce journey complexity? — It lets you specify two field value alternatives within a single action activity using one expression, avoiding a separate Condition activity node on the canvas.
  • Q: What type does the conditional instruction return if both branches are strings? — It returns a string.
  • Q: Can if / then / else be used to select a push notification channel? — Yes; for example, evaluating the device model to return 'apns' for Apple devices or 'fcm' for others.
recommendation-more-help
journey-optimizer-help