> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/data-and-insights/marketing-integrations/shopify.md).

# Shopify

Connect your Shopify store for orders, products, customers and stock — and the Shopify-only sections of Data Studio.

Connect Shopify so AdPage reads your orders from the shop itself rather than inferring them from tracking. Order data from the source is what makes revenue in your reports match what you actually banked.

{% hint style="info" %}
This integration is released per customer. If you do not see the tile, ask <support@adpage.io> to enable it.
{% endhint %}

### Before you start

You need to be **staff with app-install rights** on the Shopify store, or the store owner.

Have your **myshopify domain** ready — `yourstore.myshopify.com`. This is the permanent internal domain, not your customer-facing one. Find it in Shopify under **Settings → Domains**; it is also visible in the browser address bar while you are in the admin.

You can type either form into AdPage — `yourstore` or the full `yourstore.myshopify.com` — and it will be completed for you. A custom domain such as `www.yourstore.com` will not work here.

### Connect Shopify

{% stepper %}
{% step %}

#### Open the tile

Go to **Integrations**, select the container, and open the **Shopify** tile.
{% endstep %}

{% step %}

#### Enter your myshopify domain

Type the store address and select connect. AdPage sends you to your own Shopify admin to install the app.
{% endstep %}

{% step %}

#### Approve the app in Shopify

Shopify lists what the app will be able to read. Approve, and you are returned to AdPage with the store connected.
{% endstep %}
{% endstepper %}

### What you get

Shopify unlocks the widest data set of any integration, because the shop knows things tracking never sees — refunds, discount codes, repeat purchases, stock.

* **Orders and revenue** — what was really sold, including cancellations and refunds.
* **Product performance** — what sells, what is returned, what sits.
* **Customer insights** — new versus returning, repeat rate, customer value over time.
* **Drop Performance** — sell-through for a launch, hour by hour.
* **Influencer ROI** — revenue per influencer or discount code, next to the traffic it brought.
* **Back-in-Stock Demand** — what people wanted while it was unavailable.

The last three exist only with Shopify connected; no other source carries what they need.

### Cost prices for Profit on Ad Spend

Shopify also carries what your products cost you, in the **Cost per item** field on each variant (Products → a product → the variant's **Inventory** section). Connect Shopify and that becomes a cost source for [Profit on Ad Spend](https://docs.adpage.io/optimize-your-setup/profit-on-ad-spend), so your reports and your ad platforms can bid on margin instead of revenue. Nothing to export and no feed to build.

Two things decide whether it works:

* **The `read_inventory` permission.** The app only started asking for it once this feature existed, so a store connected before that does not grant it. If you connected a while ago, open the AdPage app once from your Shopify admin and approve the permissions it asks for.
* **The field being filled.** An empty **Cost per item** is by far the most common reason for zero cost prices, and it is the one thing only you can fix.

Shopify stores this excluding VAT, which is the basis the margin is calculated in. Include import duties and other landed costs so it is a real purchase price.

Your shipping, payment and packaging costs are set separately — see [Cost Items](https://docs.adpage.io/optimize-your-setup/profit-on-ad-spend/cost-items). With Shopify connected, the cost table can be filled from the shipping and payment methods your shop actually used, which matters because those names are matched as exact strings.

### Reading the numbers

**Shopify is the authority on revenue.** Where Shopify and a tracked figure disagree, Shopify is right about what was sold. Tracking is right about where the visit came from. They answer different questions.

**Refunds are backdated.** A refund lowers the revenue of the original order date, so last month's total can drop after month end. That is correct behaviour, and it is why a report run twice can differ.

**Test orders count.** Orders placed through Shopify's Bogus Gateway or by staff testing checkout are real orders to the API. Cancel or archive them, or expect a small distortion on quiet days.

**Multi-currency is reported as presented.** Stores selling in several currencies through Shopify Markets report in the presentment currency per order.

### Troubleshooting

**"Enter a valid myshopify.com address".** You entered a custom domain. Use the `.myshopify.com` one from **Settings → Domains**.

**The install screen says you do not have permission.** Your staff account cannot install apps. The store owner can either install it or grant you the permission.

**You are returned to AdPage but nothing is connected.** Usually the container was not selected before starting, so there was nothing to attach the store to. Select the container first, then reconnect.

**Revenue does not match Shopify Analytics.** Check whether Shopify's report includes taxes and shipping and whether yours does, and whether refunds have been applied since. Those two explain nearly every mismatch.

**Orders stop arriving after a store migration.** A replatformed or renamed store is a different store to the API. Disconnect and reconnect.

**No cost prices, while Cost per item is filled.** The `read_inventory` permission is missing. Open the AdPage app once from your Shopify admin and approve the permissions. See [Choose your cost source](https://docs.adpage.io/optimize-your-setup/profit-on-ad-spend/choose-your-cost-source).

Still stuck? Contact <support@adpage.io> with the container and the myshopify domain.


---

# 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.adpage.io/data-and-insights/marketing-integrations/shopify.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.
