AFI
WCBoost Wishlist
WCBoost Wishlist adds wishlists to WooCommerce stores for both logged-in customers and guests. Advanced Form Integration captures wishlist additions and routes the data to any of 200+ destinations.
What you’ll need
- WooCommerce and the WCBoost Wishlist plugin installed and activated.
- The wishlist button enabled on your product pages.
- The Advanced Form Integration plugin installed and activated.
When the trigger fires
AFI registers a single Product Added To Wishlist trigger for WCBoost Wishlist. It fires when a visitor adds a product to a wishlist and the item is persisted.
Data captured
| Field | Field key | Format |
|---|---|---|
| Product ID | product_id |
Numeric ID |
| Product Name | product_name |
Text |
| Product URL | product_url |
Absolute URL |
| Wishlist ID | wishlist_id |
Numeric ID |
| User ID | user_id |
Numeric ID, 0 for guests |
| User Email | user_email |
Email address, empty for guests |
Create the integration
- Go to WP Admin → AFI → Add New.
- Enter an Integration Title, e.g.
WCBoost Wishlist: Product Added To Wishlist → Mailchimp. - In Trigger → Form/Data Provider, select WCBoost Wishlist.
- In Form/Task Name, choose Product Added To Wishlist.
- In Action → Platform, pick the destination and complete the field mapping.
- Optional: configure Conditional Logic so only matching events are sent.
- Click Save Integration.
How AFI listens for wishlist activity
AFI hooks wcboost_wishlist_add_item, fired from the add_item() method in includes/wishlist.php after the item has already been saved. The plugin explicitly skips it during initial data-store loading (! $this->get_data_store()->is_reading()), so it fires for a genuine new addition and not every time a wishlist is read back from the database. The owning wishlist and its user are loaded separately through $item->get_wishlist_id(), following the same WC_Data CRUD pattern WooCommerce itself uses. Registration is guarded by defined( 'WCBOOST_WISHLIST_VERSION' ).
Guests have no email
User ID is 0 and User Email is empty for guest wishlists, which are session-based. If your campaign needs an address on every event, require login before wishlisting, or pair this trigger with Conditional Logic that only dispatches when User ID is not 0.
Troubleshooting
Removals do not fire
This trigger covers additions only.
The same product fires repeatedly
A customer can remove and re-add an item. Deduplicate on User ID plus Product ID at the destination if you only want the first add.