What Swish sends
Swish sends all standard integration events to Bloomreach, including:product_savedandproduct_unsaved- when a customer saves or removes a productsaved_product_back_in_stock- when a saved product becomes available againsaved_product_low_stock- when inventory drops below the configured thresholdsaved_product_price_drop- when the price of a saved product decreasessaved_items_activity- when a customer interacts with saved items (once per session)
Payload format
Bloomreach uses a schema-less NoSQL data structure. Nested objects would be stored as raw JSON strings inside single fields, making them inefficient to query, filter, and segment on. To avoid this, Swish flattens the standard event payload so that every value is a discrete, queryable field in Bloomreach. The data is identical to the standard payload - only the structure changes:- Nested object keys are joined with underscores:
product.category.namebecomesproduct_category_name - Array items include their index:
variant.selectedOptions[0].namebecomesvariant_selectedOptions_0_name
Example flattened payload
Example flattened payload
A
saved_product_price_drop event as received by Bloomreach:How to use the data
- Trigger scenarios from wishlist events - send an email or push notification when a saved product comes back in stock or drops in price.
- Enrich customer profiles with wishlist signals - use saved item data to improve product recommendations and personalization.
- Build segments using wishlist behavior - target customers based on the categories, price ranges, or brands they save.
Get started
Integrations are set up by the Swish team and availability depends on your subscribed plan. Contact support@swish.app to enable Bloomreach for your store.