Pixel changelog

Dated changes to Kentro Pixel, its browser SDK and this documentation since the first public page on 2026-10-15.

This page lists what changed in Kentro Pixel since its documentation was first published on 2026-10-15, newest first. For changes across all Kentro APIs, see the developer center changelog.

2026-11-20

  • Browser SDK 1.4.1: queued calls first. When the SDK starts from the snippet's queue, it now replays the calls queued before it loaded, then sends marketing.session_started and the automatic page view. A consentChanged or identify queued in the page now applies to those two events; version 1.4.0 sent them first, with the consent of init alone and no identity token. Queued track calls keep their order. A browser can run the cached 1.4.0 for up to an hour. See Automatic page views.
  • Webhook deliveries carry data. The fields of the matched mapping entry now fill data on kentro.pixel.event payloads, as described in Webhooks; until now data was never sent. The requestRedacted of an event delivery names the matched entries (targets, mapping). Deliveries queued before the change go out without data; a replay puts failed ones back with it.
  • A deleted audience no longer flags destinations. An audience page still waiting when its audience is deleted is recorded suppressed with audience_deleted; until now it failed and put the destination into error, whatever its type. See Deliveries.
  • Full membership after test mode. The first audience sync after a webhook leaves test mode sends the full membership, so a receiver that discards pages marked X-Kentro-Test still gets every member; until now it sent only the changes since the last test page. See Audience membership.
  • No client IP hash on idempotency records. The idempotency record of a server batch sent with X-Kentro-Idempotency-Key no longer keeps the salted client IP hash; the receipt every request leaves keeps it for 30 days, as before. See Retention.
  • Documentation corrections. GET /v1/event-schemas is public on the management host too (Schema registry). Google Ads destinations take no audience membership, so CUSTOMER_MATCH_TERMS_REQUIRED and no_order_ref are no longer listed. Retention now says that archived audiences keep their members from removal, and how long attribution runs and background job records are kept (Retention). The test send lists 409 DESTINATION_UNSUPPORTED and 409 GO_CONNECTION_NOT_GOOGLE.
  • Privacy requests erase the processing queue. A delete request removes the person's events that are still waiting in the processing queue or could not be processed, and an anonymize request rewrites them. An export lists them in a new section, unprocessed_events. See What a delete or anonymize request erases.
  • Privacy requests erase stored endpoint answers. A delete or anonymize request replaces the stored response of every delivery of the person's events with { "erased": true, "reason": "privacy_request" }. Deliveries of audience membership and the error text of a delivery are not covered.
  • New counts on privacy request results. result.counts can carry unprocessedEvents, unprocessedEventsDeleted, unprocessedEventsAnonymized, deliveryResponsesErased and unprocessedEventsUnreadable.
  • Events that could not be processed are kept. They stay in the processing queue, without raw click ids, the raw page URL and the user agent, until a privacy request for the person removes or rewrites them; until now they were deleted after 30 days. See Retention.
  • Replay refusal in plain words. 400 REPLAY_RANGE_TOO_OLD now answers A replay covers the last 30 days. Choose a start date on or after <day>., naming the oldest day a replay can start on. See Replays.
  • Permission refusals in plain words. A missing Pixel permission now answers 403 Forbidden with You need permission to view Kentro Pixel. Ask an administrator for access. (reads) or You need permission to manage Kentro Pixel. Ask an administrator for access. (writes), instead of the permission key. DESTINATION_NOT_ENABLED now answers Destinations export nothing until someone with permission to manage Kentro Pixel enables them.

2026-11-19

  • Browser SDK 1.4.0: marked page views. The page views the SDK sends on its own carry context.trigger: auto at init, spa on a route change. page calls carry none. See Automatic page views.
  • The collector applies the property's settings. A browser event from a page that matches a sensitive path pattern is discarded with SENSITIVE_PATH; until now its path was only redacted. A page view the SDK sent on its own is discarded with TRACKING_OFF while settings.tracking.autoPageviews or settings.tracking.spaRoutes is false. Nothing of a discarded event is kept, not even a rejected-event sample. settings.tracking.formFieldAllowlist now limits which lead form values are hashed or kept. See Consent and privacy.
  • Kentro GO stop. While the Kentro GO kill switch is on, or its autonomy level is Emergency disabled, Kentro Pixel sends nothing to destinations: deliveries wait, and test sends and audience syncs answer 409 GO_STOPPED. See When Kentro GO is stopped and 409 GO_STOPPED.
  • Kentro GO navigation. The Pixel and Audiences entries are shown to users with pixel:read or pixel:manage.

2026-11-16

  • Audience membership to Meta. A meta_capi destination with a linked ad account (config.adAccountId and config.goConnectionId) receives audience syncs as a Meta Custom Audience. Destinations report audienceSync; Google Ads destinations report false and take no audience membership. See Audience membership.
  • Google match keys. From a raw email or phone, the collector also derives email_google_sha256 and phone_e164_sha256 for Google Ads matching. See Email and phone identifiers.

2026-11-14

  • 503 SERVICE_UNAVAILABLE. A request that finds the database briefly unavailable answers 503 SERVICE_UNAVAILABLE instead of 500 INTERNAL_ERROR, on the collector and the management API. Retry it with backoff. A failed ingestion transaction still answers 503 INGEST_UNAVAILABLE.

2026-11-09

  • Documentation. The single Kentro Pixel page is now this category of eleven pages. The overview keeps the slug kentro-pixel, so existing links still work.

2026-11-08

  • Browser SDK 1.3.0: signup forms. New form command: on the submit of a matched form, and only when its consent checkbox is checked, the SDK posts the email address and first name to Kentro Email's signup capture (https://t.kentro.email). The capture requires a non-empty allowed_origins containing the page's host. See Signup forms.

2026-10-31

  • Kentro Email sending events reserved. email.sent, email.delivered, email.delivery_delayed, email.bounced, email.complained, email.rejected, email.rendering_failed, email.opened and email.clicked are reserved names: every customer route answers RESERVED_EVENT, and GET /v1/event-schemas lists them with reserved: true. See Reserved for Kentro.
  • Email touchpoints. A click on a tracked Kentro Email link records an email touchpoint that attribution can credit.

2026-10-28

  • Audiences. The /v1/audiences routes serve Pixel audiences only; Kentro Email contact segments are managed in Kentro Email and answer 404 on these routes.

2026-10-26

  • Fewer false quarantines for retail GLP-1 traffic. GLP-1 is now a generic health word: it counts only on health-vertical properties. A page that names a drug (semaglutide), or a clinical word such as prescription in free text, is still detected on every property. See Sensitive-data quarantine.

2026-10-22

  • Retention. People records of Kentro Email contacts, and people linked to a contact's customer record through an authorized CRM link, are no longer removed by the inactivity rule.

2026-10-20

  • Browser SDK 1.2.0: your own event ids. track accepts refs.event_id (8 to 128 letters, digits, _, ., : or -), so a browser event and a server event that share an id count once. See Browser and server copies.
  • Kentro Email consent events reserved. email.subscribed and email.unsubscribed are reserved names recorded by Kentro Email.