Skip to main content
Silvio6
Level 6
Apr 22, 2026 6:29 PM UTC
Question

Reaction node: When to use "open" or "click" after a push?

Hi everyone,

I am currently validating the behavior of the Journey Reaction Activity for Push Notifications and have observed a discrepancy in how interactions are tracked across different Operating Systems.

In our implementation, we use a click_action key in the Custom Data section of the Push payload (e.g., click_action: "OPEN_BENEFITS"). Our data analysis in the Experience Event Dataset shows the following:

  • On Android (FCM): The interaction is captured as eventType: pushTracking.customAction.
  • On iOS (APNS): The interaction is captured as eventType: pushTracking.applicationOpened.

This seems to be due to how the Mobile SDK interprets the payload on different platforms when no physical action buttons are present in the template.

My question is: When using a Reaction Node in a Journey set to listen for a "Clicked" interaction, does the AJO orchestration engine perform a logical "OR" to include both applicationOpened and customAction?

I want to ensure that users on both platforms are correctly moved to the success path of the journey regardless of the specific eventType name assigned by the SDK.

Thanks!

    4 replies

    Pulkit_Jain_
    Adobe Employee
    Adobe Employee
    Apr 24, 2026 11:55 AM UTC

    ​@Silvio6 

    Ideally, AJO Reaction nodes evaluate “Clicked” based on interaction classification (open/click), not based on the raw eventType and since Android and iOS emit different eventTypes, the system should normalize them to the user interaction → “Clicked”. So both Android’s and iOS’s push should satisfy Clicked in the Reaction node thus both will correctly move the user down the Clicked path.

    Translate
    Silvio6
    Silvio6Author
    Level 6
    Apr 29, 2026 3:17 PM UTC

    Hi! and where is that  interaction classification happening?

    Translate
    Pulkit_Jain_
    Adobe Employee
    Adobe Employee
    Apr 30, 2026 9:45 AM UTC

    Interaction classification happens inside AJO Reactions Listener backend service that converts raw push tracking eventTypes (iOS or Android) into normalized interaction types (open / click).

    Translate