> For the complete documentation index, see [llms.txt](https://learn.fueled.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.fueled.io/apps/shopify/shopify-event-tracking/custom-pixel.md).

# Custom Pixel

Fueled leverages a Custom Pixel for tracking Checkout-related steps and Purchases client-side.

## If You Installed Fueled Before February 4, 2025

If you installed the Fueled app before February 4th, 2025, your instance of the Fueled app tracked website purchases client-side using a "Script Tag."

Shopify is deprecating Script Tags in August 2025, so you will need to either install or update Fueled's Custom Pixel and disable this Script Tag for the best purchase-related tracking experience.

To do so:

First, go to the first tab at: <mark style="color:red;">`https://admin.shopify.com/store/[YOUR-STOREFRONT]/apps/fueled-7`</mark>&#x20;

Copy Fueled's Custom Pixel v2 code:

<figure><img src="/files/hVfRNxsOZc67X6DHjxBl" alt=""><figcaption><p>Copy/paste Fueled's Custom Pixel code into a new or existing Custom Pixel.</p></figcaption></figure>

Either replace or create a new Fueled Custom Pixel at:&#x20;

<mark style="color:red;">`https://admin.shopify.com/store/[your-store-name]/settings/customer_events`</mark>

*(The click-through path to this configuration screen is: Settings > Customer Events)*

Second, disable Fueled's Script Tag in the Fueled App settings:

<figure><img src="/files/w6VDAqw7Ro2lFcKBJSg3" alt=""><figcaption><p>Disable Fueled's Script Tag.</p></figcaption></figure>

## If You Installed Fueled On or After February 4th, 2025.

If you installed Fueled on or after February 4th, 2025, you do not need to disable Fueled's Script Tag, as it will not be installed.

Simply follow the instructions to set up a new Custom Pixel for Fueled.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.fueled.io/apps/shopify/shopify-event-tracking/custom-pixel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.