Skip to content

Kentro GO · Kentro Pixel

A first-party ecommerce pixel that applies consent before it sends anything

Kentro Pixel collects events from your site with a small browser snippet and from your backend with a signed server API. It checks each visitor’s consent, drops what measurement does not need and forwards conversions to the destinations you enable. It is part of Kentro GO.

  • Part of Kentro GO
  • No fingerprinting
  • Global Privacy Control honored
  • Destinations off until you enable them
Events flowing from a store to the destinations a brand enabled

What is a first-party ecommerce pixel?

A first-party ecommerce pixel is tracking code you run under your own account that records visits, carts and orders on your store, instead of leaving that to each ad platform’s script. Kentro Pixel collects those events from the browser and from your server, applies each visitor’s consent, and forwards conversions to the ad and analytics tools you enable.

What it does

Collect, check consent, then forward

Two sources, one event format

A browser snippet records page views and the events you track. A signed server API records what your backend knows for certain: paid orders, refunds, subscriptions and qualified leads. Both use the same event names, and revenue reports trust the server events.

  • A dependency-free browser SDK, served unminified so you can read it
  • Server events signed with HMAC-SHA256
  • Every event checked against a schema
  • Retries are safe: events are deduplicated by id
A paid order, sent from your server
{
  "events": [
    {
      "event_id": "order-1001-paid",
      "event_name": "commerce.order_paid",
      "order_ref": "order-1001",
      "properties": {
        "order_id": "order-1001",
        "total": { "amount_minor": 4999, "currency": "USD" }
      }
    }
  ]
}

What it collects, and what it throws away

Kentro Pixel keeps what measurement needs and drops the rest when the event arrives.

  • Page URLs lose every query parameter except UTM tags and ad click ids
  • Raw click ids are kept only with marketing consent
  • Email addresses and phone numbers are stored as SHA-256 hashes
  • The raw IP address is never stored
  • Referrers are reduced to a host name, user agents to a device class
  • Payloads that look like health data, secrets or card numbers are quarantined
An event with its sensitive fields removed

Consent decides what is processed

Every event carries the visitor’s consent for analytics, marketing and functional purposes. An event without the consent its purpose needs is not processed. It is recorded as suppressed, in a minimal form, so you can measure how much traffic consent covers.

  • Consent per purpose: analytics, marketing, functional
  • Unknown consent counts as denied by default
  • Global Privacy Control denies marketing by default
  • Consent is checked again before anything is exported
  • A strict privacy mode that never sends to ad networks
  • No fingerprinting, and no estimates for blocked visits
Consent states for analytics, marketing and functional purposes

Destinations that send nothing until you enable them

Forward conversions to the Meta Conversions API, to GA4 and to your own signed webhooks. Each destination starts in test mode, can be checked with a synthetic event and exports nothing until you enable it. Every delivery is listed with its outcome.

  • Meta Conversions API
  • GA4, through the Measurement Protocol
  • Signed webhooks to your own endpoint
  • Retries with backoff, and a delivery history
Destinations connected to Kentro Pixel

Analytics and audiences on consented events

Kentro GO shows sessions, visitors, conversions, top sources and campaigns, funnels and attribution from Pixel data, with a note on how much traffic consent suppressed. Rule-based audiences are built from consented events.

  • Funnels of 2 to 8 steps
  • Attribution by first touch, last touch, linear or position based
  • Audience membership synced to your signed webhook
A funnel and an attribution report built from consented events

Destinations

Where Kentro Pixel can send conversions

Three destination types. Each one starts in test mode and exports nothing until you enable it.

Kentro Pixel destinations and the consent each needs
DestinationWhat it receivesConsent needed
Meta Conversions APIMapped conversion events, such as Purchase and LeadAn explicit marketing grant and no Global Privacy Control signal
GA4Mapped events, through the Measurement ProtocolThe purpose you set on the destination
Signed webhookMapped events and audience membership, signed with HMAC-SHA256The purpose you set on the destination

Kentro cannot recall data a destination has already received. These webhooks belong to Kentro Pixel: the Kentro Channel API has no outbound webhooks.

Checked on November 17, 2026

Privacy

Privacy requests, and the limits we state up front

File a request for one person, and Kentro Pixel exports, deletes or anonymizes their data, or records a withdrawal of consent, across every identifier it knows for them. Requests run in the background and report their status.

Two limits are worth knowing. Kentro cannot pull back what a destination already received, so a finished request lists each destination and what to do there. And when a visitor blocks the snippet, that visit is missing: Kentro does not model or estimate it.

Kentro Pixel is not the KentroGO crawler. The crawler reads a brand’s own website during brand setup and is described on the Kentro GO page.

  • Export, delete, anonymize or withdraw consent
  • One person per request, across browser and customer identifiers
  • Sensitive URL paths you list are redacted
  • Data stored in the United States
About the KentroGO crawler
A privacy request for one person

One job, three ways

Check that paid orders reach your ad platform, three ways

Check that paid orders reach your ad platform

  1. In the app

    Open Pixel in Kentro GO. The debugger shows the newest events, the health tab shows what was accepted and rejected in the last 24 hours, and each destination lists its deliveries with their outcome.

    The Pixel health tab in Kentro GO
  2. With Kentro AI

    Kentro AI reports on orders, not on site traffic. Ask "How many paid orders came in yesterday?" and compare the answer with the conversions your destination accepted. It reads. It cannot enable a destination.

    Kentro AIIn Kentro
    1. you ›How many paid orders came in yesterday?
    2. getOrdersSummaryRead order totals for yesterday
    3. Here is yesterday’s order count and revenue. Pixel deliveries are listed in Kentro GO, under Pixel, Destinations.

  3. With your agent

    Your backend sends events through the Pixel server API with a signed request, and manages properties and destinations through the Pixel management API with a key that holds the pixel:manage permission. There are no MCP tools for Pixel.

    A signed server request
    POST https://pixel.kentro.live/v1/server/events
    Content-Type: application/json
    X-Kentro-Key-Id: sk_...
    X-Kentro-Timestamp: <unix seconds>
    X-Kentro-Signature: sha256=<hmac of timestamp.body>

Questions about Kentro Pixel

What does Kentro Pixel collect about my visitors?

Page views and the events you track, such as a product view, an add to cart or a signup, plus UTM tags, ad click ids, the referrer’s host name, a device class and a locale. Email addresses and phone numbers are stored as SHA-256 hashes, the raw IP address is never stored, and other query parameters are removed from page URLs. Kentro Pixel does not fingerprint browsers.

How does Kentro Pixel handle consent and Global Privacy Control?

Every event carries the visitor’s consent state for analytics, marketing and functional purposes, reported by your consent banner. By default an event needs the consent of its purpose, unknown counts as denied, and a Global Privacy Control signal denies marketing. An event without consent is recorded as suppressed, in a minimal form, and is not processed. Before anything goes to an ad platform, the person’s consent record is checked again.

Why send orders from my server instead of the browser?

Because the browser is not a reliable witness for revenue. A shopper can close the tab before the confirmation page loads, or block scripts. Kentro Pixel accepts a browser order event as a signal, but revenue reporting trusts the order your backend sends through the signed server API, such as commerce.order_paid. Refunds and cancellations sent the same way correct the numbers afterward.

Which destinations does Kentro Pixel support?

The Meta Conversions API, GA4 through the Measurement Protocol, and signed webhooks to your own endpoint. Every destination starts in test mode, can be checked with a synthetic event and sends nothing until you enable it. Audience membership syncs to your signed webhook, and every delivery is listed with its outcome, so you can see what each destination accepted.

Can I delete one person’s data from Kentro Pixel?

Yes. File a privacy request with the person’s email, phone or ids, and choose export, delete, anonymize or consent withdrawal. A delete removes their events, sessions and consent history and ends their audience memberships. Kentro cannot recall what a destination already received, so the finished request lists each destination with the step to take there, such as a deletion request in Meta’s business tools.

What does Kentro Pixel cost?

Kentro Pixel is part of Kentro GO, which is included in every Kentro OS plan or $50 a month on its own. The same price covers the AI Manager, social posting, ads connections and landing pages. Because Kentro GO is sold on its own, you can use Kentro Pixel without a Kentro OS plan.

Measure your store with consent built in

Kentro Pixel comes with Kentro GO. Get started, or read the docs before you decide.

Choose what this site may use. Necessary storage is always on.

  • Necessary

    Remembers this choice for 12 months and keeps forms safe from spam. No tracking.

    Always on

Cookie policyPrivacy policy