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.  ## 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.