SaveTo Wishlist for WooCommerce

Insights & Updates

SaveTo Wishlist Blog

WordPress guides and resources for boosting sales with SaveTo Wishlist

5 New SaveTo Wishlist Integrations: Email, Popups, Themes

5 New SaveTo Wishlist Integrations: Email, Popups, Themes

With the SaveTo Wishlist Lite v1.1.0 and v1.1.1 integrations, the free version now connects to 5 more WordPress plugins and themes.

This batch adds two email marketing bridges and a browser signal you can point at a popup. It also brings a safeguard for products that need configuring. Plus, wishlist buttons now sit correctly on the Woostify theme.

None of them need an API key, a connected account, or an outside service. Instead, the work happens on your own server or in the visitor’s browser. As a result, you’re only using plugins you already have installed.

We’ve found release notes rarely tell you the part that actually matters: what to check first. So here’s a plain-English breakdown of how each connection works.

Jump to:


5 New SaveTo Wishlist Plugin Integrations

Each of the SaveTo Wishlist v1.1.0 and v1.1.1 integrations unlocks a specific workflow. Two feed your email lists, while the others cover popups, custom product options, and theme styling. Here’s how each one works, and what you need to set up.

Hub and spoke diagram with SaveTo Wishlist at the center connected to five plugins: Email Subscribers and Newsletters (lists), Noptin (tags), Popup Maker (popups), Advanced Product Fields (product options) and Woostify (theme), each labeled with what the connection does.
The five plugins SaveTo Wishlist v1.1 connects to, and what each connection adds (click to zoom).

1. Email Subscribers & Newsletters: Add Wishlist Shoppers To Your Mailing Lists

New in v1.1.1, this integration turns a wishlist save into a mailing list signup. A shopper who saves a product has told you what they want. That’s a stronger signal than a page view. Therefore it’s worth feeding into your email marketing.

When a logged-in customer adds a product, SaveTo Wishlist Lite adds their Email Subscribers & Newsletters contact to a list. Saving a published wishlist can do the same. However, each event gets its own list mapping. As a result, you can keep them separate or point both at one list.

How it works

  • Two Events, Two Lists: One dropdown covers a successful product add. The other covers a published wishlist save. Map them to different lists, the same list, or leave one unmapped.
  • Finds Or Creates The Contact: SaveTo Wishlist looks up the contact by the customer’s account email. If there isn’t one, it creates it. New contacts get the WordPress first and last name, plus a source of saveto_wishlist. Existing contacts keep their current profile fields.
  • Follows Your Opt-In Setting: The integration reads the opt-in type already set in Email Subscribers & Newsletters. On single opt-in, the membership is written as subscribed. On double opt-in, it’s written as unconfirmed. The confirmation flow stays entirely with your email plugin.
  • No Duplicates, No Surprises: If the contact already sits on the mapped list, the integration stops there. It won’t write a second membership row. A contact marked as globally unsubscribed isn’t enrolled either.
  • Local Processing, Logged-In Only: Everything runs through your Email Subscribers plugin’s own PHP objects. It happens at the end of the same page request, with no external HTTP call and no cron job. Guest wishlist activity is skipped.
  • Removals Don’t Unsubscribe: Taking a product off a wishlist doesn’t remove list membership. This bridge only ever adds.

🔍️ One thing we commonly see with list integrations: a store owner logs in as an administrator to test it. They edit a customer’s wishlist, then report that nothing synced. That’s working as designed, because the person clicking has to be the wishlist owner. There’s no administrator override, so test with a real customer account instead.

Settings and configuration

However, this one does need setup, unlike the other four. Go to SaveTo Wishlist → Settings → Integrations tab → Email Subscribers & Newsletters. Note that this section only appears while the partner plugin is active.

  1. Turn on the Enable Email Subscribers integration switch. It’s off by default.
  2. Pick a list under Added to wishlist list and Wishlist saved list. Both dropdowns appear only once the switch is on.
  3. Save your settings.

You’ll need at least one Email Subscribers list before you start. Otherwise both dropdowns will be empty. If a new list doesn’t appear yet, wait a few minutes. That’s because the list options are cached for five minutes.

One more thing worth checking: adding a customer to a marketing list is a consent question. Your own policy decides that, not the plugin.

Full walkthrough: How to integrate SaveTo Wishlist with Email Subscribers & Newsletters.

2. Noptin: Tag Subscribers By Wishlist Activity

Because Noptin builds its automations around tags, this integration hands it three. New in v1.1.1, it applies a tag to the logged-in wishlist owner. Each of the three wishlist events gets its own tag. That gives you three separate points to build a segment from.

How it works

  • Three Event Tags: SaveTo Wishlist submits Wishlist - Product Added, Wishlist - Product Removed, and Wishlist - Saved. Point a Noptin automation at whichever one fits your campaign.
  • Tags Add Up Rather Than Swap: Every event asks Noptin to add a tag. None of them ask Noptin to take one away. One contact can therefore carry all three at once. Treat each tag as a record that something happened, not a live state.
  • Automatic Contact Creation: A logged-in shopper who isn’t in Noptin yet gets submitted as a new contact. It uses their account email and a source of SaveTo Wishlist. The starting status follows your Noptin double opt-in setting: pending when on, subscribed when off.
  • Unsubscribed Contacts Stay Untouched: An existing Noptin subscriber with the status unsubscribed is left alone. The integration returns without submitting anything, tag included.
  • Owner Only, Guests Skipped: The person clicking has to be the wishlist owner. An administrator or invited editor working on someone else’s list won’t tag that customer. Logged-out visitors are ignored.
  • Two Developer Filters: Use stwlite_noptin_event_tags to rename the tags or drop an event. Use stwlite_noptin_subscriber_status to set the starting status for new contacts.

🔍️ What we’ve seen: Store owners often ask about building a “lost interest” segment from the Wishlist - Product Removed tag. We’d be careful there. The tag records a removal action, and it never comes off afterwards. So a shopper who removes one item and saves five more still carries it.

Settings and configuration

There’s nothing to configure here: no switch, no tag fields, no API key. Instead, the integration registers itself when both plugins are active. Your three tags are created on the Noptin side as they’re used. From there, build your Noptin automations to listen for them.

A few paths deliberately fire no tag. Save Cart to Wishlist is one, as is a direct write through the REST item-save action. Meanwhile, the automatic removal after an item goes into the cart is another. Draft wishlist saves fire nothing either, so don’t rely on them while testing.

Full walkthrough: How to integrate SaveTo Wishlist with Noptin.

3. Popup Maker: Trigger Popups Right After A Save

The seconds right after a save are a good moment to say something. In practice, that could be a discount code, a shipping threshold, or a nudge toward a related item.

Shipped in v1.1.0, this integration gives you two browser-side signals after a successful save. Popup Maker then decides what to do with them, or your own snippet does. However, SaveTo Wishlist never opens a popup itself.

How it works

  • A DOM Event For The Same Page: SaveTo Wishlist dispatches stwlite_added_to_wishlist on document. Its detail carries productId and collectionId. Register your listener on document before the click, because the event isn’t replayed later.
  • A Cookie For Later Pages: It also writes a stwlite_wishlist_added cookie with a 30 day lifetime. The cookie uses path=/ and SameSite=Lax, plus Secure on HTTPS. It holds one product ID, and the next qualifying save overwrites it.
  • Two ID Values To Watch For: A guest save reports collectionId: 0, because guest lists live in browser storage. A Save Cart to Wishlist operation reports productId: 0. That one fires once for the whole cart, not once per item.
  • Only On Real Successes: For a logged-in single-item save, the signals fire only on a confirmed add. A failed save restores the button, shows a retry notice, and emits nothing.
  • You Wire Up The Popup: Popup Maker’s cookie features exist to stop a popup repeating, not to open one. There’s no built-in condition that reads another plugin’s cookie. Opening a popup takes a few lines of JavaScript. It listens for the event, or reads the cookie, then calls PUM.open() with your popup ID.

Settings and configuration

There are no settings for this integration. Instead, the event and the cookie are generic browser interfaces. They fire whenever the frontend script loads and a save succeeds. That happens whether or not Popup Maker is installed.

Still, one nearby setting is worth knowing about. At SaveTo Wishlist → Settings → General, the Add to wishlist button option sets what a shopper sees after clicking. The choices are Redirect, Popup, or Fade. Note that Popup here means SaveTo Wishlist’s own confirmation modal, not a Popup Maker popup.

However, Redirect needs one extra thought. A logged-in shopper starts navigating away right after the event fires. A synchronous listener still runs, though slower work can get cut off. Read the cookie on the destination page instead.

Full walkthrough: How to integrate SaveTo Wishlist with Popup Maker.

4. Advanced Product Fields: Keep Custom Orders Complete

Advanced Product Fields (Product Addons) for WooCommerce lets shoppers personalize a product. Engraving text, file uploads, and dropdown choices are typical examples. Wishlists don’t store those choices, though. As a result, a saved item could previously reach the cart with its details missing.

Added in v1.1.0, this integration is a routing and cart-protection safeguard. Instead of letting an unconfigured item through, it sends shoppers back to the product page.

How it works

  • Detects Products With Field Groups: SaveTo Wishlist asks Advanced Product Fields whether a product has a field group attached. If it does, the item gets marked as needing configuration first.
  • Swaps The Cart Control: Those items offer Select options instead of the usual add to cart control. The link points at the product permalink. It applies in table and grid views, on guest and logged-in lists alike.
  • Excluded From Bulk Adds: Items needing configuration stay out of Add All to Cart and Add Selected to Cart. The rest of the list carts as normal.
  • Server-Side Backstop: The same check runs again on SaveTo Wishlist’s own add-to-cart endpoint. If something tries to force an unconfigured item through, the endpoint stops first. WooCommerce never gets called, and the response returns the product URL with a short message.
  • What It Doesn’t Do: The wishlist doesn’t store or replay the field values. Shoppers fill them in fresh on the product page. Detection also works at the product level, so variation-specific fields aren’t covered.

If you already use the PPOM integration from v1.0.9, this will feel familiar. Both hang off the same underlying check. Either plugin therefore gets the same protection.

Settings and configuration

There’s nothing to configure and no switch to turn on. Instead, the safeguard becomes active once Advanced Product Fields is installed and its field-group check is available. Without that plugin, the integration marks no product as needing configuration.

Full walkthrough: How to integrate SaveTo Wishlist with Advanced Product Fields.

5. Woostify: Wishlist Buttons That Match Your Theme

A wishlist button that sits a few pixels off undercuts an otherwise tidy shop page. One tucked behind a product image is worse. Because Woostify has its own product card and gallery markup, that’s where the drift shows up.

New in v1.1.1, SaveTo Wishlist Lite now loads a compatibility stylesheet built for Woostify’s layout. The button then sits where you’d expect on shop, category, archive, and single product pages. Plus, Woostify has over 40,000 active installs, so this covers a fair few stores.

How it works

  • Automatic Theme Detection: When the active template is Woostify, SaveTo Wishlist loads one extra stylesheet. It loads after whichever base stylesheet you’ve selected. Child themes built on Woostify count too, since detection reads the parent template.
  • Layout Only, Not Styling: The stylesheet adjusts stacking on the image-corner placements. It also handles alignment and spacing inside Woostify’s product card and single-product summary. It assigns no colors, fonts, borders, or button sizes. Your button settings and Frontend CSS Loading mode stay in charge of appearance.
  • Two Placements To Avoid: On shop and archive pages, skip Below the Add to Cart Button. Woostify renders that row inside a fixed-height animated area on desktop, where the button can get clipped. On single product pages, skip both on-image placements. Woostify’s custom gallery doesn’t display them reliably.
  • Nothing Else Changes: There’s no Woostify-specific PHP, JavaScript, REST endpoint, or database work involved. Button visibility, placement, and guest access all run on your normal settings.
  • Known Scope: The stylesheet targets standard WooCommerce and Woostify markup. It doesn’t establish support for page-builder grids or block-based product grids. Quick views, custom product loops, and Woostify’s premium companion plugins are also outside it.

🔍️ Here’s what we’ve seen catch people out on a fresh Woostify install: In v1.1.1 the placement options aren’t written to the database on activation. The settings screen and the frontend fallback can therefore disagree. Open both Button Placement dropdowns, pick a recommended placement, and press save even if it looks right.

Settings and configuration

There’s no Woostify-specific setting, and no way to toggle the stylesheet by itself. Everything worth adjusting already lives at SaveTo Wishlist → Settings → Button Placement & Styles. The Shop Page and Product Page sections are separate there.

Guest visibility is unchanged as well. With Disable Guest Wishlist turned on, logged-out visitors see no button on a Woostify store either. Our guide covers how guest wishlists work in more detail.

Full walkthrough: How to integrate SaveTo Wishlist with Woostify.


Also New:

Alongside the five integrations above, the latest updates brought a handful of quality-of-life changes. Here’s a quick summary of what else is new.

  • Hide Disabled Cart Buttons: A new option hides unusable Add to Cart buttons on the wishlist page.
  • A Faster Settings Screen: The settings header and sidebar now stay put as you scroll. The button preview sits beside the style fields, so you see changes as you make them.
  • Better Inline Spacing: There’s more room between the Add to Cart and Save to Wishlist buttons on the Inline placement.
  • The Wishlist Block: A native Wishlist block you can drop in from the block inserter. It renders exactly what the [saveto_wishlist] shortcode renders, because it reuses the same code. An optional Wishlist ID field in the sidebar matches the shortcode’s id attribute. Leave it empty to show the current customer’s wishlist. It also works in the Site Editor, and your existing shortcodes keep working.
  • Direct to Checkout: An After Add All to Cart option that routes shoppers to Cart or Checkout. It applies once they’ve used Add All to Cart on the wishlist page. For a customer who wants the whole list, that’s one less page before paying. Out-of-stock items stay out of the bulk add, as they do elsewhere.

Our full guide to the Wishlist Block and Direct to Checkout walks through both in detail.


Ready To Upgrade Your Wishlists?

The SaveTo Wishlist Lite v1.1.0 and v1.1.1 integrations push the free plugin past a simple list of saved products. Two of them feed your email lists. One hands you a trigger for on-site messaging. Meanwhile, another protects your custom orders, and the last one fixes theme styling.

Three of the five need no setup at all. Email Subscribers & Newsletters takes a switch and two dropdowns. Popup Maker needs a short JavaScript snippet. That said, the Woostify placement check above is worth two minutes of your time.

Missed any of the details? Jump right back to a specific integration to review how it works:

Update SaveTo Wishlist Lite today and start connecting the plugins you already run!

author avatar
Michael Logarta

Get The Best WooCommerce Wishlist Plugin

Create wishlist functionality and grow your store quickly & easily.
Get SaveTo Wishlist Now

Share article

Complete Your Purchase