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_startedand the automatic page view. AconsentChangedoridentifyqueued in the page now applies to those two events; version 1.4.0 sent them first, with the consent ofinitalone and no identity token. Queuedtrackcalls 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. Thefieldsof the matched mapping entry now filldataonkentro.pixel.eventpayloads, as described in Webhooks; until nowdatawas never sent. TherequestRedactedof an event delivery names the matched entries (targets,mapping). Deliveries queued before the change go out withoutdata; 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
suppressedwithaudience_deleted; until now it failed and put the destination intoerror, 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-Teststill 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-Keyno 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-schemasis public on the management host too (Schema registry). Google Ads destinations take no audience membership, soCUSTOMER_MATCH_TERMS_REQUIREDandno_order_refare 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 lists409 DESTINATION_UNSUPPORTEDand409 GO_CONNECTION_NOT_GOOGLE. - Privacy requests erase the processing queue. A
deleterequest removes the person's events that are still waiting in the processing queue or could not be processed, and ananonymizerequest rewrites them. Anexportlists them in a new section,unprocessed_events. See What a delete or anonymize request erases. - Privacy requests erase stored endpoint answers. A
deleteoranonymizerequest replaces the storedresponseof every delivery of the person's events with{ "erased": true, "reason": "privacy_request" }. Deliveries of audience membership and theerrortext of a delivery are not covered. - New counts on privacy request results.
result.countscan carryunprocessedEvents,unprocessedEventsDeleted,unprocessedEventsAnonymized,deliveryResponsesErasedandunprocessedEventsUnreadable. - 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_OLDnow answersA 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 ForbiddenwithYou need permission to view Kentro Pixel. Ask an administrator for access.(reads) orYou need permission to manage Kentro Pixel. Ask an administrator for access.(writes), instead of the permission key.DESTINATION_NOT_ENABLEDnow answersDestinations 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:autoatinit,spaon a route change.pagecalls 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 withTRACKING_OFFwhilesettings.tracking.autoPageviewsorsettings.tracking.spaRoutesisfalse. Nothing of a discarded event is kept, not even a rejected-event sample.settings.tracking.formFieldAllowlistnow 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 answer409 GO_STOPPED. See When Kentro GO is stopped and 409 GO_STOPPED. - Kentro GO navigation. The
PixelandAudiencesentries are shown to users withpixel:readorpixel:manage.
2026-11-16
- Audience membership to Meta. A
meta_capidestination with a linked ad account (config.adAccountIdandconfig.goConnectionId) receives audience syncs as a Meta Custom Audience. Destinations reportaudienceSync; Google Ads destinations reportfalseand take no audience membership. See Audience membership. - Google match keys. From a raw
emailorphone, the collector also derivesemail_google_sha256andphone_e164_sha256for Google Ads matching. See Email and phone identifiers.
2026-11-14
503 SERVICE_UNAVAILABLE. A request that finds the database briefly unavailable answers503 SERVICE_UNAVAILABLEinstead of500 INTERNAL_ERROR, on the collector and the management API. Retry it with backoff. A failed ingestion transaction still answers503 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
formcommand: 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-emptyallowed_originscontaining 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.openedandemail.clickedare reserved names: every customer route answersRESERVED_EVENT, andGET /v1/event-schemaslists them withreserved: true. See Reserved for Kentro. - Email touchpoints. A click on a tracked Kentro Email link records an
emailtouchpoint that attribution can credit.
2026-10-28
- Audiences. The
/v1/audiencesroutes serve Pixel audiences only; Kentro Email contact segments are managed in Kentro Email and answer404on these routes.
2026-10-26
- Fewer false quarantines for retail GLP-1 traffic.
GLP-1is now a generic health word: it counts only on health-vertical properties. A page that names a drug (semaglutide), or a clinical word such asprescriptionin 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.
trackacceptsrefs.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.subscribedandemail.unsubscribedare reserved names recorded by Kentro Email.

