Adobe Journey Optimizer

Ajo_WisdomChase · 8/9/24

Hi ,

Anyone Explain these points in journey action and provide example for understand?

Three retries are systematically performed in case of an error. You cannot adjust the number of retries according to the error message received. Retries are performed for all HTTP errors except for HTTP 401, 403 and 404.
The built-in Reaction event allows you to react to out-of-the-box actions. Learn more in If you want to react to a message sent via a custom action, you need to configure a dedicated event.
You cannot place two actions in parallel, you must add them one after the other.
A profile cannot be present multiple times in the same journey, at the same time. If re-entrance is enabled, a profile can reenter a journey, but cannot do it until he fully exited that previous instance of the journey.

dugganab · 8/9/24

Hi,

#1 - Suppose a journey sends an API request to an external service (say to retrieve temperate based on city). If the request fails due to a network issue (e.g., timeout), AJO will automatically retry the request up to three times. However, if it still fails after three attempts, the journey will move on without allowing you to configure different retry limits based on the type of error.

If a journey makes an API call and receives a

HTTP 404 error (indicating the resource was not found),
HTTP 401 (Unauthorized, Indicates that the request lacks valid authentication credentials),
HTTP 403 (Forbidden, Indicates that the server understood the request but refuses to authorize it) , AJO will not retry the request. However, if it receives an HTTP 500 error (indicating a server issue), it will retry up to three times.

#2 - If you have a journey where an email is sent to a user and you want to follow up if they open the email, you can use a Reaction event to trigger a different action (e.g., send a second email) based on the email open event.

If your journey involves sending a message through a third-party service that isn't natively integrated with AJO, you would need to configure a custom event to react to any responses or actions resulting from that message (e.g., tracking clicks on a custom link executed from a different system).

#3 - Ex:- If you want to send an email and a push notification at the same time, you can't do this in parallel. You would need to configure the journey to send the email first, followed by the push notification.

#4 - If a customer enters a journey, they must complete or exit the journey before they can re-enter it. This prevents cases where a customer might receive duplicate or conflicting communications from the same journey. Suppose a journey is designed to engage customers who abandon their shopping cart. If a customer abandons their cart today and enters the journey, they can't trigger the journey again tomorrow until they have exited the journey (e.g., by making a purchase or reaching the end of the journey).

View solution in original post

dugganab · 8/9/24

Hi,

#1 - Suppose a journey sends an API request to an external service (say to retrieve temperate based on city). If the request fails due to a network issue (e.g., timeout), AJO will automatically retry the request up to three times. However, if it still fails after three attempts, the journey will move on without allowing you to configure different retry limits based on the type of error.

If a journey makes an API call and receives a

HTTP 404 error (indicating the resource was not found),
HTTP 401 (Unauthorized, Indicates that the request lacks valid authentication credentials),
HTTP 403 (Forbidden, Indicates that the server understood the request but refuses to authorize it) , AJO will not retry the request. However, if it receives an HTTP 500 error (indicating a server issue), it will retry up to three times.

#2 - If you have a journey where an email is sent to a user and you want to follow up if they open the email, you can use a Reaction event to trigger a different action (e.g., send a second email) based on the email open event.

If your journey involves sending a message through a third-party service that isn't natively integrated with AJO, you would need to configure a custom event to react to any responses or actions resulting from that message (e.g., tracking clicks on a custom link executed from a different system).

#3 - Ex:- If you want to send an email and a push notification at the same time, you can't do this in parallel. You would need to configure the journey to send the email first, followed by the push notification.

#4 - If a customer enters a journey, they must complete or exit the journey before they can re-enter it. This prevents cases where a customer might receive duplicate or conflicting communications from the same journey. Suppose a journey is designed to engage customers who abandon their shopping cart. If a customer abandons their cart today and enters the journey, they can't trigger the journey again tomorrow until they have exited the journey (e.g., by making a purchase or reaching the end of the journey).