Pixel

The Pluto pixel connects the click to the order, so ad spend can be attributed to the revenue it actually produced. It is one small script on your storefront.

What it does

The pixel records anonymous browsing events: page views, product views, add to cart, checkout, and a purchase ping. When an order arrives from your store sync, Pluto joins it to the session that produced it. That join is what turns "we spent 5,000 on Meta" into "Meta produced these 37 orders".

Three things it deliberately does not do:

• No money. Events never carry amounts. Your revenue comes from the store sync and cannot be skewed by ad blockers or lost events.
• No raw personal data. If you use identify, the email is hashed in the browser before anything is sent.
• No tracking before consent. Nothing is stored on the visitor's device and nothing is sent until consent exists.

Install

Create a pixel token at app.plutoprofit.com/developers and add the script to your theme:

<script async
  src="https://px.plutoprofit.com/v1/plutoprofit.js"
  data-token="pt_plp_your_token"></script>

That is the whole install for a themed store. Page views, single-page navigation, and consent are handled automatically. The token is safe to expose: it can only append events, never read data.

Headless storefront? Use the npm package instead: see the collect API reference.

Consent

The pixel reads your existing consent setup. Shopify's Customer Privacy API and Cookiebot are detected automatically; other banners can pass consent explicitly with one call. If no signal can be read, the default is no tracking in the EEA, UK, and Switzerland.

When a visitor withdraws consent, the pixel stops immediately and deletes what it stored.

Accuracy expectations

Pixels are best-effort by nature: ad blockers, private browsing, and Safari's storage limits all cost events. That is fine here, because the pixel only assists attribution. Your order counts, revenue, and profit come from the store sync and stay exact regardless of pixel coverage.