> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/installation/shopify-checkout-limits.md).

# Shopify Checkout Limits

What Shopify's checkout sandbox does not let any app do on the Checkout, Thank You, Order Status and customer account pages

Surveys on Shopify's Checkout, Thank You, Order Status and customer account pages run inside Shopify's checkout sandbox. Shopify only lets apps draw with its own set of interface components there, and it blocks custom scripts, custom styling and pop-ups. These limits apply to every app, not just Zigpoll.

If your survey needs something on this list, run it on your storefront instead. You can also send it by email or SMS, or share a survey link.

## No popups or modals

You can't show a popup survey on the Thank You, Order Status or checkout pages. A checkout block sits inside the page, in the spot where you placed it in Shopify's checkout editor. It cannot open as a pop-up, a slide-in or a launcher tab. It also cannot float over the page.

To get more people to answer an inline block:

* Drag the Zigpoll block higher on the page in the checkout editor, so buyers see it without scrolling.
* Offer a reward for finishing the survey. See [Reward Question](/tutorials/reward-question.md).

## Colors, fonts and background come from Shopify, not your Design settings

Checkout blocks ignore the survey's **Settings → Design** tab and your account's **Design Defaults**. That covers colors, fonts, custom CSS, launcher shape and position, and header images. Shopify styles the block with your store's checkout branding, which you set in Shopify's checkout editor.

This is why a survey can look one way in your Zigpoll preview and another way on the Thank You page.

You can adjust the block in two places:

* **Your checkout branding.** Colors, corner radius and typography come from Shopify admin → **Settings → Checkout → Customize**.
* **The block's own settings.** Click the Zigpoll block in the checkout editor. Each of these optional settings picks from Shopify's preset styles:
  * **Main Copy Size** and **Main Copy Color**
  * **Additional Copy Size** and **Additional Copy Color**
  * **Fine Print Size** and **Fine Print Color**
  * **Answer Apperance** (Bold or Regular)
  * **Background** (Transparent, Base or Subdued)
  * **Button Color** and **Button Type**
  * **Reward Banner Size** and **Reward Banner Color**
  * **Discount Code Appearance**

These Zigpoll settings still carry over to a checkout block:

* Your questions, answers, logic and translations.
* The **Progress Indicator** setting from **Settings → Design → On-Site**, on the Thank You and Order Status block only. The Checkout Survey and customer account blocks don't show progress.
* **Hide close button** and **Hide back button**, in the **Closing** card on the survey's **Settings → General → Behavior** sub-tab.
* Anonymous mode.

{% hint style="info" %}
The block also has a **Preview survey** setting. It only changes what you see inside the checkout editor. Buyers always see the survey your Zigpoll dashboard serves. See [Checking it works without placing a real order](/faq/why-is-my-survey-not-showing.md#i-want-to-check-it-works-without-placing-a-real-order).
{% endhint %}

## Custom fonts can't load

Shopify doesn't let apps load their own font files in the checkout. A block uses the typography from your checkout branding, even if you set a custom font for your storefront surveys.

## Answer rows wrap on small screens

A block fills the width Shopify gives it. Answer scales with up to five options sit in one row. Longer scales, such as a 0–10 NPS question, pack in as many buttons as fit. On a narrow phone screen they wrap onto a second row.

To keep a scale on one line, use five options or fewer. You can also move the block to a wider part of the page in the checkout editor.

## No traffic source, UTM or landing page data

Checkout blocks cannot read the address your customer arrived from. They also cannot read the storefront session. Responses collected on the Thank You and Order Status pages have no UTM parameters, referrer or landing page.

To learn how customers found you, ask them. An attribution question on the Thank You page answers this directly. See [Attribution Surveys](/tutorials/attribution-surveys.md).

## Surveys during checkout need Shopify Plus

The Thank You, Order Status and customer account blocks work on every Shopify plan. Shopify only lets **Shopify Plus** stores add third-party app blocks to the checkout steps themselves (Information, Shipping and Payment). This rule applies to Zigpoll's **Checkout Survey** block.

See [Checkout Steps Surveys](/installation/activating-zigpoll-on-shopify-checkout-extensions.md#checkout-steps-surveys-checkout-survey-block).

## No exit intent on checkout pages

Exit intent watches the mouse and scrolling on your storefront. Zigpoll can't do that inside the checkout. An exit-intent survey only runs on storefront pages, where the theme App Embed loads Zigpoll.

To ask buyers something before they finish paying, Shopify Plus stores can place the **Checkout Survey** block on a checkout step. It appears inline, not as an exit pop-up.

## Related pages

{% content-ref url="/pages/UZJFw4wmRdrtb9JR0GUo" %}
[Activating Zigpoll on Shopify Checkout Extensions](/installation/activating-zigpoll-on-shopify-checkout-extensions.md)
{% endcontent-ref %}

{% content-ref url="/pages/onmDspDrHwKj3b6fjzsZ" %}
[Why Is My Survey Not Showing?](/faq/why-is-my-survey-not-showing.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zigpoll.com/installation/shopify-checkout-limits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.