> ## Documentation Index > Fetch the complete documentation index at: https://docs.ycloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Goal and Exit Rule > Track Journey completion and stop follow-up when contacts meet your exit conditions. # Goal and Exit Rule Use a **Goal** to track Journey completion and an **Exit rule** to stop remaining follow-up for contacts who meet defined conditions. Both settings are optional. ## Goal A Goal helps you measure whether contacts complete the outcome you want from a Journey. When a contact meets the configured Goal conditions during the selected tracking period, the Journey records a completion. A Goal is for tracking only. Reaching a Goal does not remove a contact from the Journey or stop the remaining steps. ## Exit rule An Exit rule defines the conditions that remove a contact from the remaining Journey flow. Use an Exit rule when a contact should stop receiving the Journey's later actions after meeting a condition. For example, you can use an Exit rule to stop a follow-up flow once a contact has completed the action the flow is designed to encourage. Separate Exit Trigger and Goal settings, with an unsaved tag-based Goal and a seven-day tracking window. ## Use Goal and Exit Rule together You can configure the same conditions for both settings when you want to measure completion and stop remaining follow-up after completion. You can also configure them separately. For example, use a Goal to measure a desired outcome while using an Exit rule only for contacts who should no longer receive the Journey's messages. ## Next steps Review the [Journey components](/en/documentation/journey/components-and-features-introduction/index) and confirm that each branch in your Journey has the follow-up actions you expect. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.