> For the complete documentation index, see [llms.txt](https://docs.adobesandbox.com/comprehensive-technical-tutorial-archive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adobesandbox.com/comprehensive-technical-tutorial-archive/module7/summary.md).

# Summary and benefits

Congratulations and thank you for investing your time in learning about Adobe Journey Optimizer and Adobe Experience Platform! In this module, you've learned how to configure an account creation journey by using Adobe Journey Optimizer which is triggered in real-time when the customer creates an account on the website.

Adobe Journey Optimizer is your one stop shop for creating seamless, 1:1 omnichannel experiences. By listening to real-time customer interaction or location events you can now orchestrate 1:1 journeys, leveraging the Real-time Customer Profile along with optional 3rd party data sources to deliver the right message within the right channel at the right time.

## Benefits

Let's highlight the benefits of defining journeys in Adobe Journey Optimizer in combination with Adobe Experience Platform:

* Communication with customers needs to be real-time and contextual. With Adobe Journey Optimizer, you now have the ability to listen for specific customer-initiated events and carefully curate a contextual journey if and when the customer is going through that specific journey.
* Orchestrating a journey can involve wait times, conditions whereby data in Adobe Experience Platform is verified to then send the journey into a different path and also, custom actions whereby any application with an API can receive instructions from Adobe Journey Optimizer on what content to show to which customer.
* Personalizing engagements can now truly happen across any channel that is used to interact with the customer.

For example, you can now –

* Tailor the experience based on the real time customer data profile, contextual data received from the event, or other proprietary / 3rd party data sources.
* Deliver a consistent message through broader Adobe applications or leverage any third party service such as chatbots or smart devices.
* Use insights to further understand your customers’ needs in the moment, and use a mix of tactics to create frictionless opportunities for conversion, along with the data to support attribution efforts.
* Continue to develop the relationship by understanding what the customer needs at that point in time and coordinating a timely and contextual follow up which will drive repeat purchases and increase customer lifetime value

## Check this out

* Tech Blog: [Journey Orchestration in an Omnichannel World](https://medium.com/adobetech/journey-orchestration-in-an-omnichannel-world-3a2d32d556d9)
* Tech Blog: [Demonstrating the Power of Adobe’s New Journey Orchestration Service to Build Personalized Omnichannel Experiences in Real-Time](https://medium.com/adobetech/demonstrating-the-power-of-adobes-new-journey-orchestration-service-to-build-personalized-aa60d88cd34)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adobesandbox.com/comprehensive-technical-tutorial-archive/module7/summary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.