Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Smaily Connect · Version history

Smaily Connect changelog and version history

Latest version
3.21.1
Nov 4, 2026 (5 days ago)
Releases
35
since 2025
In the last year
22
about one every 17 days
Tested up to
WordPress 7.1.4
PHP 8.0 or later

Releases each year

  • 202518 releases
  • 202617 releases

202617 releases

  1. Smaily Connect 3.21.1Latest

    • Fixed: a history import could repeat itself or stop right after it started when the plugin updated in the background. The update now also completes in the background, without a visit to wp-admin.
    • Fixed: a connected store that ran 3.21.0 and whose order history has not been sent in full with 3.21 starts the whole sequence (products, customers, orders) once more by itself. It waits while another import runs; an import you held back or cancelled stays stopped.
    • Improved: Import now says so when an import could not be started.

  2. Smaily Connect 3.21.0

    • New: connecting Campaign Intelligence imports your products, then customers, then orders, each when the one before has finished. Hold back or Cancel stops the sequence.
    • New: a connected store that never finished its customers or orders import starts it once after this update, without a click. An import you held back or cancelled stays stopped.
    • New: “Open Campaign Intelligence” in Settings opens your store’s console with a one-time sign-in link.
    • Improved: imports send faster, at a steady pace. The Orders import sends the last 18 months first, then older orders back to 60 months; older orders are not sent.
    • Improved: the import cards count the records Campaign Intelligence accepted, and the import reports its progress to it.
    • Improved: on legacy order storage, a database index added in the background speeds up the Orders import, only where the server can build it without blocking writes.
    • Changed: Campaign Intelligence gets only the customers it can use: those your contact sync sends to Smaily, those with an order in the history window, and a customer who logs in with marketing consent.
    • New: a customer who logs in with marketing consent gets the store’s visitor cookie, so the Recommendations block knows them after logout. A login no longer waits for Campaign Intelligence.
    • Improved: your store’s server sets the email-click cookies, so Safari keeps them for their full lifetime.
    • Changed: an automation card shows its workflow and settings only while it is on, and an automation that is off makes no discount code.
    • Changed: a design Campaign Intelligence delivers to Smaily as a workflow is used for emails on the Smaily account it names, transactional emails included, in your store’s default language. This replaces the 3.19.0 “main Smaily account” rule.
    • Privacy: erasing a customer’s personal data also cancels their waiting background login sync, so it cannot send the erased customer to Campaign Intelligence again.
    • Fixed: an update from 1.x or 2.0.0 removes the old abandoned-cart table only after every unsent cart is copied.
    • Fixed: the Edit design “Back to your store” link is set only for your store’s own admin address.
    • Updated to the Smaily Campaign Intelligence API contract v1.24.0.

  3. Smaily Connect 3.20.0

    • New: the welcome, first-order and abandoned-cart emails can each carry a single-use discount code. Pick a WooCommerce coupon and the number of days a code stays valid. Each code copies the coupon’s discount and restrictions, brands included, works once and only for the shopper’s email address, and…
    • New: a shopper who still has an unused, valid code from the same automation gets that code again, not a new one. No code is made for an address that WooCommerce cannot restrict a coupon to exactly; the email goes without it.
    • New: unused codes are deleted 30 days after they expire.
    • Privacy: the personal-data export lists the codes made for an address. Erasure deletes the unused ones and removes the address from the used ones.
    • Changed: Disconnect and deleting the plugin now tell Campaign Intelligence that the connection ends. Campaign Intelligence revokes the plugin’s key and, if your store has no other connection, pauses the store and keeps its data: no recommendations and none of its automated emails until you connect…
    • Updated to the Smaily Campaign Intelligence API contract v1.18.0.

  4. Smaily Connect 3.19.0

  5. Smaily Connect 3.18.0

  6. Smaily Connect 3.17.1

  7. Smaily Connect 3.16.0

  8. Smaily Connect 3.15.0

  9. Smaily Connect 3.14.0

  10. Smaily Connect 3.13.0

  11. Smaily Connect 3.12.1

  12. Smaily Connect 3.12.0

  13. Smaily Connect 3.11.3

  14. Smaily Connect 3.11.2

  15. Smaily Connect 2.0.0

  16. Smaily Connect 1.6.2

  17. Smaily Connect 1.6.1

202518 releases

  1. Smaily Connect 1.6.0

  2. Smaily Connect 1.5.1

  3. Smaily Connect 1.5.0

  4. Smaily Connect 1.4.3

  5. Smaily Connect 1.4.2

  6. Smaily Connect 1.4.1

  7. Smaily Connect 1.4.0

  8. Smaily Connect 1.3.3

  9. Smaily Connect 1.3.2

  10. Smaily Connect 1.3.1

  11. Smaily Connect 1.3.0

  12. Smaily Connect 1.2.4

  13. Smaily Connect 1.2.3

  14. Smaily Connect 1.2.2

  15. Smaily Connect 1.2.1

  16. Smaily Connect 1.2.0

  17. Smaily Connect 1.1.0

  18. Smaily Connect 1.0.0

Questions about Smaily Connect’s releases

What is the latest version of Smaily Connect?

3.21.1, released on Nov 4, 2026 (5 days ago). It’s tested up to WordPress 7.1.4 and needs PHP 8.0 or later.

How often is Smaily Connect updated?

22 releases in the last year, about one every 17 days. Its first release on WordPress.org dates from April 2025.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in Smaily Connect’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.