> For the complete documentation index, see [llms.txt](https://docs.humblytics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humblytics.com/split-testing-overview/creating-a-b-page-variants-for-split-testing/conversion-goals/reach-destination-page.md).

# Reach Destination Page

The **Reach Destination Page** goal measures how many visitors successfully complete a **multi-step journey** and arrive at a specific page — such as a checkout confirmation, signup success page, or onboarding completion step.

\
This goal helps you understand and optimize your **conversion funnels** by testing how layout, copy, or navigation changes impact the user’s ability to reach key milestones.

Use this goal when your main objective is to **guide more visitors to a final destination page** in a flow.\
Ideal for:

* Checkout or purchase completion pages
* Signup or onboarding success pages
* Booking confirmation pages
* Multi-step forms or funnel completion pages

> Great for optimizing **multi-step experiences** where you want users to complete a sequence — not just click once.

#### What It Tracks

Humblytics automatically tracks the number of visitors who:

* Start on your test page (Control or Variant)
* Successfully reach the designated **destination URL** (e.g., `/thank-you`, `/success`, `/confirmation`)

It then compares completion rates between the two test versions to show which version leads to more users finishing the journey.

#### How It Works

1. Visitors are randomly assigned to **Control (A)** or **Variant (B)**.
2. Humblytics tracks whether each visitor reaches the **destination page URL** you specify.
3. The system calculates the **conversion rate** (visitors who reached destination ÷ total visitors).
4. Real-time analytics show which version leads to higher completion and funnel success rates.

#### Common Test Ideas

* Compare different **checkout layouts** (single page vs. multi-step).
* Test **onboarding flows** with or without progress indicators.
* Experiment with **navigation clarity** (simplified menus vs. full navigation).
* Test different **call-to-action placements** leading to final conversion pages.
* Try alternative **funnel sequences** to reduce drop-offs.

#### Steps to Set Up

1. Click the **Split Testing** menu in your Humblytics dashboard.
2. Click **Start Creating Experiment**.
3. Under **Select Testing Goal**, choose **Reach Destination Page**.
4. Enter your **Destination Page URL** (e.g., `/thank-you` or `/confirmation`).
5. Choose your **Experiment** and **Test Type**.
6. Add your **Control (A)** page URL.
7. Configure **Visitor Assignment** (allow or prevent overlap).
8. Apply **Restrictions** (Geo or Audience filters as needed).
9. Launch your test and monitor destination page completions in real-time.

By running this test, you’ll gain insights into which experience helps users complete your desired flow — resulting in:

* Higher **checkout completion rates**
* Improved **onboarding success**
* Better **funnel performance and reduced drop-offs**


---

# 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.humblytics.com/split-testing-overview/creating-a-b-page-variants-for-split-testing/conversion-goals/reach-destination-page.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.