> 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/extensions/plugins/shopify-app.md).

# Shopify App

Install and validate AdPage Tagging for your Shopify store.

Use the AdPage Tagging Shopify app to add ecommerce tracking to your store.

<a href="https://apps.shopify.com/adpage-tagging" class="button primary" data-icon="shopify">Install from the Shopify App Store</a>

### Before you start

Have access to your Shopify admin and Google Tag Manager container. Remove duplicate ecommerce tracking before testing the app.

### Install the app

{% stepper %}
{% step %}

#### Install AdPage Tagging

Open the Shopify App Store listing and select **Install**. Approve the requested permissions in Shopify.
{% endstep %}

{% step %}

#### Complete the app setup

Open the app from **Shopify admin → Apps**. Follow the in-app setup steps for your store.
{% endstep %}

{% step %}

#### Publish your changes

Save the configuration and publish your Google Tag Manager container. Use preview mode before publishing production changes.
{% endstep %}
{% endstepper %}

### Validate the installation

Use Google Tag Manager Preview to test your storefront. Complete these actions during one test session:

1. View a product list and product page.
2. Add an item to the cart and begin checkout.
3. Place a test order and open the thank-you page.

Confirm the expected `trytagging_*` events appear in the data layer. Check prices, currency, product IDs, quantities, and transaction IDs.

### Available Shopify events

The app provides ecommerce events across the purchase journey:

* `trytagging_view_item_list`
* `trytagging_select_item`
* `trytagging_view_item`
* `trytagging_add_to_cart`
* `trytagging_view_cart`
* `trytagging_remove_from_cart`
* `trytagging_begin_checkout`
* `trytagging_add_payment_info`
* `trytagging_add_shipping_info`
* `trytagging_add_address_info`
* `trytagging_purchase`

It also sends `trytagging_user_data` on all pages. See [AdPage's ecommerce dataLayer](https://docs.adpage.io/extensions/cms-tracking/adpages-ecommerce-datalayer.md) for event parameters.

{% hint style="warning" %}
Do not test purchases with a live payment method. Use Shopify test mode or a test payment provider.
{% endhint %}

### Troubleshooting

If events do not appear, confirm that the app setup is complete. Check that your theme and checkout use the supported configuration.

If events duplicate, disable overlapping ecommerce or tag-manager integrations. Retest in an incognito window after clearing your cart.

### Settings

#### Enable form tracking

Normally add\_to\_cart events will be tracked via network requests on the site. By enabling this setting the plugin will listen to the form event listner that will get the info and sets it in a add\_to\_cart event.

#### Enable Cookie Restoration

This will read a first party cookie in the main domein. If cookies missing it looks for backup cookies in local. If no cookies available then generate own ID.

#### Rename dataLayer

This is a advanced option, do not change without help. This will activate a AdPage custom datalayer with name "taggingDatalayer"

#### Use order notes for webhook delivery

We send marketing information via ordernotes in Shopify. We update this information in the webhooks.\
\
The field with ordernotes is used as note in a order for instance in the purchase email.


---

# 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/extensions/plugins/shopify-app.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.
