> For the complete documentation index, see [llms.txt](https://support.storefront.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.storefront.co.za/release-notes/enhancements/2026-enhancements/janruary-2026-enhamcements/rich-meta-facebook-pixel-tracking-for-key-store-actions.md).

# Rich Meta (Facebook) Pixel Tracking for Key Store Actions

Previously, the Meta (Facebook) pixel on your store only tracked **basic PageView events**, which limited how well you could optimise ads and retargeting.

The pixel integration has been enhanced to support the **standard e‑commerce events**, including:

* **ViewContent** – when a shopper views a product or bundle
* **AddToCart** – when a shopper adds an item to the cart
* **AddToWishlist** – when a shopper adds an item to a wishlist
* **InitiateCheckout** – when a shopper starts the checkout process
* **Purchase** – when an order is completed (with value + currency)
* **CompleteRegistration** – when a customer completes registration
* **Search** – when a shopper uses the search bar

These events are also wired through your **Opt‑in / consent** system, so tracking respects performance‑cookie consent.

**Benefits for merchants**

* Much **richer tracking** for Meta/Facebook campaigns, beyond just page views.
* Better **remarketing audiences** (e.g. people who added to cart but didn’t buy, or viewed specific products).
* More accurate **conversion tracking and ROAS** for your Meta ads.
* Stronger insight into the full customer journey: search → product view → cart → checkout → purchase.
* Tracking is aligned with **privacy and consent**, reducing compliance risk.


---

# 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://support.storefront.co.za/release-notes/enhancements/2026-enhancements/janruary-2026-enhamcements/rich-meta-facebook-pixel-tracking-for-key-store-actions.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.