ÃÛ¶¹ÊÓƵ

Documentation

Event not triggering journey in ÃÛ¶¹ÊÓƵ Journey Optimizer

Last update: Thu Apr 03 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In ÃÛ¶¹ÊÓƵ Journey Optimizer, events sometimes fail to trigger the intended journey, even when all criteria are met. This issue occurs when events are created through query services instead of being streamed to the Data Collection Core Service (DCCS). To fix this, review event configuration, stream events directly to DCCS, and perform test mode verification.

Description description

Environment

ÃÛ¶¹ÊÓƵ Journey Optimizer (AJO)

Issue/Symptoms

  • The unitary event configured to trigger a journey is not initiating the process.
  • Multiple event configurations and tests have been attempted without success.
  • Events appear on profiles but do not activate the journey.

Resolution resolution

To resolve this issue, ensure that events are properly streamed to the DCCS as follows:

  1. Verify that the event condition doesn’t use array functions with string-type fields. Use functions like equalsIgnoreCase for string comparisons to ensure accurate event triggering.
  2. Ensure that events are streamed directly to DCCS rather than being generated through query services. This is crucial for triggering journeys. Refer to Events under Journey Guardrails in the Journey Optimizer Guide for details.
  3. Use Test Mode to confirm that streaming works correctly since Test Mode inherently streams events. Refer to Test your journey in the Journey Optimizer Guide for details.
  4. Refer to Work with journey events in the Journey Optimizer guide to learn about configuring events for journeys and additional steps required for sending events effectively.

By following these steps, you should be able to configure your system so that profiles enter journeys as expected when specific events occur.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f