Skip to main content

Header

The header area appears at the top of the Thank you page, directly below the store logo and navigation. Extensions in this area add high-visibility content to the post-purchase experience that buyers see immediately after completing their order.

  • First-time buyer welcome: Display a personalized welcome message for new customers and encourage account creation to build long-term engagement.
  • Post-purchase surveys: Collect buyer feedback through a compact form.
  • Loyalty program enrollment: Prompt unenrolled buyers to join a rewards program, or show enrolled buyers how many points they earned from the purchase.
  • Referral program prompts: Generate shareable referral URLs tied to the completed order, with a copy-to-clipboard action for easy sharing.
  • Order tracking and delivery estimates: Display expected delivery information or show a map for local pickup orders.
  • App install prompts: Encourage buyers to download the store's mobile app for order tracking and reorder convenience.

Use this static extension target to extend the area directly below the Thank you page header. This target supports the full checkout component set, including form fields, banners, images, and interactive elements. The examples demonstrate using the Order API for order data and API properties for reading checkout state.

purchase.thank-you.header.render-after

Adds persistent content directly below the header on the Thank you page. The Order API provides read access to order data, including the order number and whether it's the customer's first order.

Extensions also have read access through API properties to shop information, buyer identity, cost breakdowns, cart lines, delivery groups, discount codes, localization, and other checkout state. The Storefront API is available through the query method for fetching additional data like product recommendations. Write access isn't available on Thank you page targets because the order is complete.

Support
Components (55)
APIs (24)

  • Reserve space for dynamic content: Layout shifts are highly visible in the header. If you load data asynchronously, use a skeleton paragraph or spinner to hold space while content loads.
  • Use the Storage API to track interactions: Record whether a buyer has already submitted a survey or dismissed an enrollment prompt so it doesn't re-show on page refresh.

Was this page helpful?