Merchants have diverse needs and some use cases won't fit into extension targets on existing customer account pages. For example, to create extensions for popular use cases like loyalty programs, wishlists, subscriptions, returns, and exchanges, a separate page is required. In these cases, build a full-page extension. Full-page extensions render UI in a new page, below the header and above the footer. ![A desktop view of the header and footer of customer accounts. The entire main content area between the header and footer is occupied by a large blue dotted-line box that says Full-page extension, indicating that this area can be populated by a full-page customer account UI extension.](/assets/apps/customer-accounts/full-page-extensions/full-page-extension.png) ## How it works There are two full-page extension targets available: - [customer-account.page.render](/docs/api/customer-account-ui-extensions/targets/full-page/customer-account-page-render): Use this target if the page you’re building is not tied to a specific order. - [customer-account.order.page.render](/docs/api/customer-account-ui-extensions/targets/full-page/customer-account-order-page-render): Use this target if the page you’re building is tied to a specific order. Each full-page extension has a unique URL. You can build other extensions that link to a full-page extension URL. ### Allow or prevent direct linking Full-page extensions using the `customer-account.page.render` target allow direct linking by default. Merchants can add the link to these full-page extensions to their online store or customer account navigation menus. They can also copy the page URL and add it anywhere. The following video shows the merchant experience of adding a page to the customer account menu: To prevent direct linking, you can declare this intent using allow_direct_linking = false in your extension configuration file.

Full-page extensions using the `customer-account.order.page.render` target do not allow direct linking. Instead, you can create an [order action](/docs/apps/build/customer-accounts/order-action-extensions) or extend the [**Order status** page](/docs/apps/build/customer-accounts/order-status-page) to link to your full-page extension. ## Limitations Each extension can only extend the full-page extension target once. You can create multiple new pages by creating multiple extensions. We recommend dedicating one page per use case. A full-page extension target ([customer-account.page.render](/docs/api/customer-account-ui-extensions/targets/full-page/customer-account-page-render) or [customer-account.order.page.render](/docs/api/customer-account-ui-extensions/targets/full-page/customer-account-order-page-render)) cannot coexist with any other targets in the same extension. ## Developer tools and resources

Target overview

Explore all extension targets available for customer account UI extensions.

Customer account UI extension components

Learn about the components that you can use to build customer account UI extensions.

Checkout UI extension components

Learn about the Checkout UI extension components that you can use to build customer account UI extensions.

## Next steps

Build a full-page extension

Build a full-page extension for customers to manage a wishlist of products.