> 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/custom-pixel-for-tracking-checkout-steps.md).

# Custom Pixel For Tracking Checkout Steps

Custom Pixel For Tracking ATC Events

### Tracking checkout-related events with Fueled with the Web Pixel API

Merchants can leverage the Web Pixel API for tracking checkout-related events, such as <mark style="color:red;">`Add Payment Info`</mark>, by setting up a Custom Pixel in the Shopify Admin, which leverages this API.

#### Step 1: Setting up a Custom Pixel in the Shopify Admin UI

To set up a Custom pixel, go to:

<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)*

Here, you should see the screen below:

<figure><img src="https://1909034781-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylSuLl56TLCrQceIL9Bo%2Fuploads%2Fc3bDZEbgNAqHbWkQqLeC%2Fimage.png?alt=media&amp;token=6fae3d50-bf78-4d51-8d0e-978772b5fcd7" alt=""><figcaption><p>Screenshot of the custom events configuration page.</p></figcaption></figure>

From this screen, click “Add custom pixel”, and name it <mark style="color:red;">`Fueled Custom Pixel`</mark>:

This will take you to a screen where you can enter the Custom Pixel code:

<figure><img src="https://1909034781-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylSuLl56TLCrQceIL9Bo%2Fuploads%2Fn8Ju1IPO3KiovgqJZUHf%2FZight%202025-02-04%20at%205.33.38%20AM.jpg?alt=media&amp;token=123db940-27df-4dac-8509-e9222a24d384" alt=""><figcaption><p>Screenshot of the Shopify user interface for adding custom pixel code.</p></figcaption></figure>

On this screen, you will want to enter the code snippet found on the first tab of the Fueled App in Shopify:

<figure><img src="https://1909034781-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylSuLl56TLCrQceIL9Bo%2Fuploads%2FNA8gZ1P3O76JbhKgaSmv%2FZight%202025-02-04%20at%205.16.48%20AM.jpg?alt=media&amp;token=a8f1fdee-7cf3-4034-9313-7885915adf73" alt=""><figcaption><p>Inserting Fueled's Custom Pixel.</p></figcaption></figure>


---

# 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://learn.fueled.io/apps/shopify/shopify-event-tracking/custom-pixel/custom-pixel-for-tracking-checkout-steps.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.