> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/integration/web-push/web-sdk-changelog.md).

# Web SDK Changelog

This changelog highlights customer-visible changes to the Pushly Web SDK.

{% updates format="full" %}
{% update date="2026-10-15" %}

## v3.8.0

**New**

* `consent` load option and `consent` command for sites with a consent management platform. 
  {% endupdate %}

{% update date="2026-10-05" %}

## v3.7.0

**Added**

* New `opt_out` command to withdraw a visitor's consent for that browser. `opt_in` reverses it on the next page load.

**Changed**

* Opt-out and deletion requests that cannot reach Pushly are now retried on later page loads until they are confirmed.
* `suppress_prompts` now takes down a prompt already on screen. Prompt theme images must use https.
  {% endupdate %}

{% update date="2026-09-21" %}

## v3.6.1

#### Fixed

* Resolved an issue where event-only domains did not properly read origin domain subscription status.
  {% endupdate %}

{% update date="2026-09-17" %}

## v3.6.0

#### Changed

* The 2-step Slide prompt is now embedded direclty within the SDK.
  {% endupdate %}

{% update date="2026-08-27" %}

## v3.5.1

#### Fixed

* Improve backoff/retry mechanism for tracking calls that receive non-200 responses
  {% endupdate %}

{% update date="2026-08-27" %}

## v3.5.0

#### Added

* Added support for scroll-depth prompt triggers
  {% endupdate %}

{% update date="2026-08-24" %}

## v3.4.2

#### Fixed

* Fixed a repeated base64 decode error in the browser console when reading stored subscriber data.
  {% endupdate %}

{% update date="2026-08-03" %}

## v3.4.1

#### Fixed

* Resolves issue with evaluating prompt conditions with anchored regexes.
  {% endupdate %}

{% update date="2026-07-22" %}

## v3.4.0

#### Added

* Added ability to [Suppress](/integration/web-push/sdk/methods.md#suppressing-and-allowing-prompts-dynamic-blocking) opt-in prompt/dialog during page load.
  {% endupdate %}

{% update date="2026-07-15" %}

## v3.3.1

#### Fixed

* SDK will properly emit page URLs for debug events.
  {% endupdate %}

{% update date="2026-07-14" %}

## v3.3.0

#### Added

* All SDK events now include an ephemeral session identifier.
  {% endupdate %}

{% update date="2026-06-15" %}

## v3.2.4

#### Fixed

* On event-only domains (e.g. a separate checkout or cart subdomain), subscription-gated events such as add\_to\_cart could be silently dropped even for users with an active subscription on the primary domain.
  {% endupdate %}

{% update date="2026-06-10" %}

## v3.2.3

#### Fixed

* Two-step prompts were not shown to visitors in iOS standalone (PWA) mode due to incorrect Safari detection when window\.safari is absent in that context.
  {% endupdate %}

{% update date="2026-06-08" %}

## v3.2.2

#### Fixed

* Stale pre-subscription events that had accumulated in the queue no longer fire in a burst at subscribe time. Events like page views and tag visits are now discarded if they predate the subscription rather than sending with skewed timestamps.
* A race condition between permission observation and the prompt grant flow that could emit a duplicate subscribed event has been resolved.

## v3.2.1

#### Fixed

* Allow and Dismiss buttons on Slide prompts now properly respond to user interaction.
  {% endupdate %}

{% update date="2026-06-08" %}

## v3.2.0

#### Added

* Service-worker push handling is hardened against malformed payloads, with clearer diagnostics.
* Prompt outcomes now flush when a visitor leaves the page, so they're no longer lost when someone leaves immediately after responding to a prompt.
* Page views are now event-driven with live permission-change detection.

#### Fixed

* Eliminated intermittent duplicate "This site has been updated in the background" notification that could appear on Chrome for macOS.
* Duplicate service-worker registrations and duplicate subscriptions that could orphan a device's live push endpoint are now prevented and cleaned up.
  {% endupdate %}

{% update date="2026-03-18" %}

## v3.1.1

#### Fixed

* Sanitize multiple leading slashes when provided in `sw` and `swScope` load.
  {% endupdate %}

{% update date="2026-02-02" %}

## v3.1.0

#### Added

* [Added Subresource Integrity (SRI)](/integration/web-push/sdk/delivery-and-security-sri.md) support for pinned SDK assets
  {% endupdate %}
  {% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.pushly.com/integration/web-push/web-sdk-changelog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.