Web SDK release notes

Every version of the Web SDK, newest first. For setup, see Web SDK.

Web has no 0.4.0: deep links apply to mobile apps only, and the push button work first built as 0.4.0 shipped in 0.6.0.

1.0.0 — 1 November 2026

Package	Requirements
@trueengage/web@1.0.0	Browsers that support ES2018

What's new

• First stable release. No API breaks: everything that worked in the previous release works unchanged. Includes the SDK Logger.

0.9.0 — November 2026

Package	Requirements
@trueengage/web@0.9.0	Browsers that support ES2018 · the SDK Logger needs the November 2026 API

What's new

• SDK Logger. Start a session under Developers → SDK Logger, open the pairing link (?te_logger=…) in the tab you want to watch, or call TrueEngage.debug.startLoggerSession(code), and the SDK's own log lines appear in the console as they happen. debug.onLoggerSession tells your page when a session starts and ends so you can show a banner; debug.endLoggerSession() stops it. → Web SDK

Improvements

• Masked before it leaves the page. Logger lines have emails, phone numbers, tokens and app keys masked on the page and again on the server. Test sessions carry every level for 60 minutes; Live sessions carry info and above for 30 minutes.

0.8.2 — 31 October 2026

Package	Requirements
@trueengage/web@0.8.2	Browsers that support ES2018 · web push needs service worker support

What's new

• Browser and operating system. Events now carry the browser name and version and the operating system, so the model and OS columns in the console are filled for web users. → Web SDK
• More page views tracked. Page views are also recorded for routers that bypass history.pushState, through the Navigation API and hashchange, so hash-based single-page apps are covered. → Web SDK
• Bottom sheets and full-width images. In-app messages support the bottom_sheet layout, full-width images and tappable images. → Create an in-app message

Improvements

• Network type. Each batch reports wifi, cellular, none or unknown. A connection type of none is now reported as none, ethernet is reported as wifi (as on Android and iOS), and a browser whose connection API throws is reported as unknown instead of failing. Browsers that do not say what kind of network they are on, such as Safari, Firefox and desktop Chrome, report unknown while online. The README now has a support table. → Web SDK

Fixes

• Batches sent when a tab is hidden or closed. These were lost in some browsers because the request was rejected before it was sent. They are now sent with a keep-alive request. → Web SDK

0.8.1 — 24 October 2026

Package	Requirements
@trueengage/web@0.8.1	Browsers that support ES2018 · web push needs service worker support

What's new

• Ad identifiers cleared on opt-out. optOut() and optOut('tracking') delete the stored advertising id and click-id touch, and tell TrueEngage to delete what it holds, even with flushOnOptOut set to false. Sent only if an ad identifier was ever reported. → When ad identifiers are cleared
• clearAdIdentifiers(kinds?). Clear ad identifiers without opting the person out. Leave out kinds to clear everything. → When ad identifiers are cleared

Works with the matching server release. An older server stores the message as an ordinary ad click event.

0.8.0 — 22 October 2026

Package	Requirements
@trueengage/web@0.8.0	Browsers that support ES2018 · web push needs service worker support

What's new

• Ad click capture. When the landing URL carries utm_*, gclid, gbraid, wbraid, gad_source, gad_campaignid or fbclid, the SDK records one touch, with the _fbp and _ga cookies when readable. It captures on page load, and when tracking consent is granted later. Nothing is captured while tracking is opted out. → See where each user came from
• Shared event ids. track() now returns { eventId } and accepts eventId in its options. Pass the same id to your Meta pixel to avoid duplicates. → Avoid duplicate events with your browser pixel
• storeLink. Returns your registered Play Store URL with the visitor's campaign values in the install referrer, so the install keeps its source. → See where each user came from

Improvements

• Event id property. track() always sets the event_id property (unless you set one yourself), so the server copy of a conversion dedupes against your browser pixel.
• Message ids. Message ids for caller-supplied event ids are now hashed from the full id, which fixes a collision between different ids.
• Return value. track() returned nothing before. Code that ignores the return value is unaffected.

0.7.0 — 21 October 2026

Package	Requirements
@trueengage/web@0.7.0	Browsers that support ES2018 · web push needs service worker support

What's new

• In-app messages. Modals, banners, cards and bottom sheets built in the console are fetched after initialize() and shown when their event or screen trigger fires. Self-handled campaigns are not drawn: you receive the message and show it yourself. → In-app campaigns
• Cards feed. TrueEngage.cards gives you a persistent inbox of cards with a synchronous unread count, and mark read, clicked and dismissed actions. You draw the UI. Opting out of in-app stops fetching, showing and stats.
• Verified identity. identify(id, attrs, { token }), setIdentityToken(token) and setIdentityTokenProvider(fn) send a signed token your backend issues, so messages and cards with personal data reach only proven users. → Verify your users

0.6.0 — 21 October 2026

Package	Requirements
@trueengage/web@0.6.0	Browsers that support ES2018 · web push needs service worker support

What's new

• Push action buttons. The service worker shows template buttons as notification actions. A click records Push Clicked with the button id and label, and opens the button link. → Push notifications
• Web conversions from smart links. When a smart link sends a visitor to your verified web app, initialize() reads and removes te_clid, credits the visit to the link and hands you the link payload. → Link domains
• Service worker version. Receipts report the real SDK version instead of 0.1.0.

0.5.0 — 18 October 2026

Package	Requirements
@trueengage/web@0.5.0	Browsers that support ES2018 · web push needs service worker support

What's new

• Referral links. createLink makes a short smart link for in-app content. It needs in-app links turned on in Smart Links settings. → Links API and webhooks

0.3.0 — 13 October 2026

Package	Requirements
@trueengage/web@0.3.0	Browsers that support ES2018 · web push needs service worker support

What's new

• Opt-in device location. requestLocationPermission() and updateLocation() use the browser's location prompt. The SDK sends coordinates only, with no city lookup in the browser. The server resolves the place. → Device location
• Location permission events. Location Permission Granted and Location Permission Denied are recorded when the user decides. → Device location

0.2.0 — 11 October 2026

Package	Requirements
@trueengage/web@0.2.0	Browsers that support ES2018 · web push needs service worker support

What's new

• Country from the browser language. Each batch includes deviceCountry when the browser's language carries a region, for example en-IN. It is the weakest signal, and the server uses it only behind the request address. → Device location
• setRegion(). A typed setter for the user's state or province. → Events and identity

0.1.0 — 19 September 2026

Package	Requirements
@trueengage/web@0.1.0	Browsers that support ES2018 · web push needs service worker support

What's new

• Event tracking. Queued, batched sending with retries, plus track, page and flush. → Events and identity
• Identity and attributes. identify, logout, reset and typed attribute setters. → Events and identity
• Web push. requestPushPermission, subscribePush and the pushClicked event, with a service worker that records receipts, clicks and dismissals. → Push notifications
• Consent. optOut and optIn per scope (tracking, push, inApp, all). → Consent
• Debugging. enableValidation() and debug.getInfo(). → Web SDK

Fixes

Added on 9 October 2026, still reported as 0.1.0:

• Push events carry the variant. Service worker push events now include the campaign variant code, so results split correctly by variant. → Push notifications
• Malformed push payloads are ignored. A push with a broken payload no longer raises an error in the service worker.