> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/components/component-library/cart-components/component-button.md).

# Component: Button

**Purpose:** The Button component provides Limio Commerce users with greater flexibility in designing their user journeys. It allows the Limio Commerce user to send an end user to any destination they wish, from anywhere on the Limio page.

{% embed url="<https://69c2cf3a42a094f3cd354b8d-lmmwbskrwp.chromatic.com/?path=/story/shop-components-checkout-button--default&full=1&shortcuts=false&singleStory=true&embed=true>" %}

**Props**

| **Prop Label** | **Type** | **Default Value** | **Info**                                                             |
| -------------- | -------- | ----------------- | -------------------------------------------------------------------- |
| Button Label   | string   | Click here        | Defines the call-to-action (CTA) text displayed on the button.       |
| Redirect URL   | string   | /default          | Defines the destination that the user will get sent to when clicking |

**Redirect URL details**

When a customer clicks the Button component, they will be redirected to the destination defined in the Redirect URL prop, which can either be a Limio page or a non-Limio page.

* For a Limio page, the user can just enter the page tag (e.g. /cart)
* For a non-Limio page, the user must enter the full URL

If an invalid URL is configured in the Redirect URL prop - the button does not send the user anywhere.

Any tracking tags present in the URL should persist to the next page.


---

# 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.limio.com/components/component-library/cart-components/component-button.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.