> For the complete documentation index, see [llms.txt](https://docs.yaycommerce.com/yayboost/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yaycommerce.com/yayboost/other-links/changelog.md).

# Changelog

#### **Aug 1, 2026 – Version 1.3.0**

* Added: Promotion Popup feature with a visual block builder (text, image, button, form, spacer, countdown timer, news ticker, coupon)
* Added: Sale Countdown Timer feature
* Added: Recently Viewed Products feature
* Added: Stock Scarcity Gutenberg block
* Added: Unlock notification for Free Shipping Bar
* Updated: Tested up to WordPress 7.0 and WooCommerce 10.9.4

#### **May 29, 2026 – Version 1.2.0**

* Added: Card & Badge styles for Purchase Activity Count (Pro)
* Added: IP/Geolocation restriction for Exit Intent Popup (Pro)
* Added: Rich content for features
* Added: Indicator text for Live Visitor Count
* Added: Quick config/presets for Purchase Activity Count
* Updated: Customer now can select variants for Order Bump
* Updated: More impression tracking

#### **Apr 17, 2026 – Version 1.1.0**

* Added: Recent Purchase feature
* Added: Order Bump feature
* Updated: Admin Logo
* Updated: YayMenu
* Fixed: Frequently Bought Together bug
* Fixed: Admin dashboard analytics

#### **Jan 26, 2026 - Version 1.0.0**

* Initial release


---

# 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://docs.yaycommerce.com/yayboost/other-links/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.