Customer Events pixel extension

How Ordinary's Shopify Customer Events pixel works and how to check that it is connected and sending storefront activity.

Ordinary Written by The Ordinary Team · Updated
On this page

Ordinary uses Shopify’s Customer Events pixel to understand how shoppers move through your storefront. It helps power sessions, funnel reports, and attribution. Shopify runs the pixel in its own isolated environment; you don’t need to paste a script into your theme.

What it records

The pixel records storefront activity such as page and product views, cart changes, and checkout progress. Browsing activity uses pseudonymous visitor identifiers. If a shopper enters contact details during checkout, Shopify’s checkout events can include those details even when the checkout is not completed. Ordinary uses them to connect checkout activity with the shopper’s order and reports; the pixel does not record payment-card details.

For the full description of what Ordinary collects and how it is handled, see our Privacy Policy and Data handling and privacy.

Check that it is connected

  1. Open your Shopify admin and go to Settings → Customer Events.
  2. Under App pixels, find Ordinary.
  3. Confirm its status shows Connected.

If it says Disconnected, see Pixel says “Disconnected”.

Check the pixel from Ordinary

  1. In Ordinary, open Settings → Shopify.
  2. Next to the Shopify card’s title, look for the Pixel active badge. Pixel disconnected means Shopify reports the pixel isn’t running.

A connected pixel can still miss some visits when a browser blocks tracking or a shopper does not grant the consent required by the store’s settings. This is why pixel coverage is useful: it shows how often storefront orders can be linked to a tracked visit. Orders placed outside the storefront, such as point-of-sale orders, are shown separately where relevant.

If you see two Ordinary pixels

Keep the Ordinary app pixel under App pixels connected. If you also have an older Ordinary-labelled pixel under Custom pixels, disable the custom one to avoid duplicate events.

Did this answer your question?

Thanks for your feedback! 🙌

Related articles