TrackLayer 2026.05 release notes

2026.05 emphasizes operator confidence: fewer blind spots when debugging delivery, sharper audience authoring, and small but loud quality-of-life fixes requested by design partners during April office hours.

Audiences & analytics

You can now snapshot SQL audience definitions to versioned artefacts for internal review—or attach them to change tickets without leaving the workspace. Exports include parameter metadata so BI can reproduce the same cohort on a warehouse mirror with minimal translation.

Predictive score cards surface feature coverage per decile, making it obvious when a model is starved of fresh signals instead of when creative is "just tired." We also tightened default holdout tooling so uplift reads line up across Meta and internally blended reports.

Ingestion & routing

Replay sandboxes gained a -since watermark that respects original messageId chains, preventing double-count nightmares when QA replays subsets of prod traffic against staging destinations. TikTok integrations picked up enrichment toggles for product categories where catalog sync is partial—disable enrichment per feed without pausing the whole destination.

Consent propagation now logs jurisdiction decisions at ingestion time, shortening security reviews where regional routing was previously inferred only downstream.

Reliability & UI

Incident banners pull from /status with explicit maintenance windows counted down in the operator navbar. Loading states across delivery diagnostics were rewritten to skeleton patterns so engineers stop mistaking sluggish API calls for "zero failures."

Deprecation notice: legacy client SDK v3.2.x enters EOL on 2026-07-01—upgrade to v4.x for first-party persistence defaults. Ping support if you still require an extension beyond that cut-off.

Ship early, iterate with partners, document honestly—see you in June.

Known issues

Under rare load, the delivery diagnostics export can take longer than thirty seconds for accounts with more than fifty active destinations; pagination improvements land in 2026.06. Safari 17.4 occasionally double-fires consent signals on hard reload—client SDK v4.1.2 mitigates; patch before Black Friday rehearsals.

Upgrade notes

Operators on custom transformation packs should re-pin digest hashes after this release because we normalized whitespace in template serialization—no semantic change, but checksums moved. CI pipelines comparing artefact signatures should pull the refreshed golden files from the examples repo tag release-2026.05.

Thank-yous

Shout-out to the merchant who reported skewed holdout bucketing in multi-store configs; your repro trace shortened the fix from days to hours. Keep the feedback coming via Slack, GitHub discussions, and Friday office hours—we actually read the notes.

API & security

REST endpoints that list transformation packs now return ETag headers for cheap polling; conditional requests return 304 when nothing changed. Webhook signing secrets can be rotated without downtime using overlapping validity windows—docs include copy-paste examples for Node and Go.

TLS cipher suites were tightened on public ingress to drop legacy RSA key exchange on paths that still saw occasional old embedded browsers; if you integrate from ancient appliances, open a support ticket—we maintain a narrow compatibility bridge with mutual monitoring.

Partner ecosystem

The Shopify app received a quality-of-life release: bulk reconnect for stores that rotate API tokens during security reviews, plus clearer error text when rate limits come from Shopify rather than TrackLayer. Klaviyo batch exports gained optional gzip for large historical pulls.

None of these headlines rival a fresh ML model, but they remove the sand from the gears that make operators swear at otherwise solid infrastructure. May your pipelines stay boring and your dashboards honest.

2026.06 planning is already chewing on streaming audience diffs and richer replay visualizations—tell us which operator pain ranks highest in your shop and it might jump the queue.

Until then, update clients, skim the changelog for breaking notes, and keep those diagnostic exports handy—engineering reads them verbatim when chasing ghosts.