customer-account.
A static extension target that is rendered below the footer on all customer account pages (Order index, Order status, Profile, Settings and new pages added by Full-page extensions).
To prevent layout shifting, avoid dynamic data fetching & rendering in this target. If you need to render dynamic content, consider reserving space for your content while it is loading. See: Spinner, SkeletonText, or BlockSpacer.
Anchor to standardapiStandardApi
The base API object provided to this and other customer-account extension targets.
Methods for interacting with Web Pixels, such as emitting an event.
Requires to connect a third-party domain to Shopify for your customer account pages.
Allows setting and updating customer privacy consent settings and tracking consent metafields.
Requires the capability to be set to true.
Requires access to protected customer data.
Information about the authenticated account.
Customer privacy consent settings and a flag denoting if consent has previously been collected.
Meta information about the extension.
Utilities for translating content and formatting values according to the current localization of the user.
Details about the language of the buyer.
Used to query the Storefront GraphQL API with a prefetched token.
See storefront api access examples for more information.
Provides access to session tokens, which can be used to verify token claims on your app's server.
See session token examples for more information.
The settings matching the settings definition written in the shopify.ui.extension.toml file.
See settings examples for more information.
When an extension is being installed in the editor, the settings will be empty until a merchant sets a value. In that case, this object will be updated in real time as a merchant fills in the settings.
Key-value storage for the extension target.
Methods to interact with the extension's UI.
The renderer version being used for the extension.
The identifier that specifies where in Shopify’s UI your code is being injected. This will be one of the targets you have included in your extension’s configuration file.
Deprecated as of version 2023-07, use extension.target instead.