Skip to main content

The Blueshift Recommendations Studio

Great experiences start with the right recommendation. Whether it's a product, article, or offer, intelligent recommendations help customers quickly discover what matters to them — driving deeper engagement and measurable business impact.

Behind every effective recommendation is a balance of AI-powered personalization, real-time signals, and contextual understanding. Blueshift helps teams deliver personalized suggestions without complex setup or long development cycles.

By unifying behavioral data, catalog insights, and predictive models, Blueshift surfaces relevant content across key channels — email, push, SMS, in-app, and web — adapting as user behavior evolves.

Real results from leading brands

  • 🛏️ Tuft & Needle increased email revenue by 181%.

  • 🚗 CarParts.com boosted engagement by 400%.

These capabilities come together in what we call recommendation recipes — the foundation of Blueshift's personalization strategy.

Why Blueshift recipes drive results

  • Rapid deployment: Access 100+ AI-powered recipes mapped to industry goals and lifecycle stages.

  • Enterprise flexibility: Combine Blueshift's models with your own data science by importing external feeds.

Unlock the power of 100+ AI-powered recipes

AI-powered recipes for lasting customer impact — browse by vertical

Retail

Recipes for e-commerce and retail platforms, focused on product discovery and cart recovery.

Abandoned cart
Remind users and help them continue where they left off

Use cases

  • Remind users and help them continue where they left off.

  • Combine with similar items product rec­om­men­da­tions to let them explore and discover more.

  • Use multi touch rec­om­men­da­tions for high intent users and prevent lost revenue.

Re­quire­ments

  • Add_to_Cart event or equivalent with product_ids.

  • Purchase event or equivalent with product_ids.

  • Item catalogs with those product_ids.

Inputs

  1. Timeline on add_to_cart events.

  2. Timeline on purchase events.

How it works

Replay Items added to cart but not purchased during checkout process and bring back users to where they left off.

Brand affinity items
Popular, trending or recent items in affinity brands

Use cases

  • Daily/Weekly newsletter with top/trending items in user affinity brands.

  • App/Site live content with top/trending items in user affinity brands.

Re­quire­ments

  • Item catalogs with brand.

  • Items activity/event timeline.

Inputs

  1. Number of items to recommend per affinity brand (Default 2).

  2. Brand items ranking to fetch candidates.

  3. Site level backfill ranking (if rec­om­mend­ed products less than return count). Set 'None' if not required.

How it works

Popular, Trending, Recent or Deal Items in user affinity brands.

Wishlist reminders
Wishlist reminder for items not purchased

Use cases

Wish-list reminders to users for items they wish-listed but did not purchase.

Re­quire­ments

Users activity with wish-lists and purchase events.

Inputs

  1. User wish-list event and timeline.

  2. User purchase event timeline.

How it works

Items added to wish-list but not purchased yet.

Derived event - price drop
Price drop reminders

Use cases

  • Price drop reminders.

  • Combine with similar items to help users compare various products and let them explore.

  • Weekly / Monthly newsletters.

Re­quire­ments

  • Events saved on timeline with product_ids in payload.

  • Price change threshold.

  • Item Catalogs matching those product_ids.

How it works

Items with price change which have been browsed and not yet purchased by users.

Media

Recipes for streaming, publishing and content discovery, focused on engagement and per­son­al­ized feeds.

Streaming - similar shows to recent activity
Daily/Weekly newsletter to users based on recent activity

Use cases

  • Daily/Weekly newsletter to users based on recent activity.

  • Suggested content to view based on past activity in app/email.

Re­quire­ments

  • Users recent activity timeline.

  • Item catalogs matching the products engaged (episodes).

  • Episode and Show catalogs linked through parent sku 3. Tags and title in the catalogs at episode and show level.

Inputs

  1. User recent activity events and timeline.

  2. Similar tag and similar title rankings to use.

  3. Number of shows from recent activity to consider for similarity (default 1).

  4. Number of similar shows to be rec­om­mend­ed for each recent show engaged with (default: 2).

  5. Site level backfill ranking (if rec­om­mend­ed products less than return count). Set 'None' if not required.

How it works

Shows with similar title and tags to recently watched.

Feed type

Product-Product

Publishing - new items from authors you like
New items from authors based on prior purchases and wishlists

Use cases

  • Alert users to new arrivals / launches from authors based on prior activity or wishlist.

  • Backfill other recommendations.

Re­quire­ments

  • Events with product_ids in payload.

  • Item Catalogs matching those product_ids.

  • Author attribute on items.

Inputs

  1. Recent activity timeline.

  2. Favorite Author Attribute on User profile 2. One of the precomputed rankings for each author.

How it works

New items from authors you purchased from or liked.

Tag affinity items
Popular or recent items from users affinity tags

Use cases

  • Per­son­al­i­za­tion related to tags inclination for popular / trending items.

  • Daily / Weekly newsletter feed to recommend popular / trending content by tags.

Re­quire­ments

  • Tags at sku and/or parent_sku level.

  • Users activity/event timeline.

Inputs

  1. Number of items per tag affinity.

  2. Popular Tags ranking to fetch candidate items.

  3. Site level backfill (optional).

How it works

Popular or recent items related to the tags users have affinity towards.

Streaming - continue watching
Content users started watching but haven't finished

Use cases

  • Remind users to continue watching video or audio or text content where they left off.

  • Combine with similar items product rec­om­men­da­tions to let them discover related content.

Re­quire­ments

  • Media start event or equivalent with product_ids.

  • Media finish event or equivalent with product_ids.

  • Item catalogs with those product_ids.

Inputs

  1. Timeline on media_start events.

  2. Timeline on media_finish events.

How it works

Replay items watched on sites or apps but have not yet been completed and remind them to continue watching.

Marketplaces

Recipes for multi-seller platforms, focused on seller-based rec­om­men­da­tions and time-sensitive listings.

New/trending from your favorite sellers
Re-engage users based on past activity

Use cases

  • Re-engage users based on past activity.

  • Expand item discovery based on users activity.

  • Daily/Weekly customised feed to users.

Re­quire­ments

  • Item catalogs with seller.

  • User recent activity timeline.

Inputs

  1. Recent event timeline.

  2. Seller top items ranking to use for each seller.

  3. Site level backfill ranking (if rec­om­mend­ed products less than return count). Set 'None' if not required.

  4. Apply size filter?

  5. If yes, provide recent activity to use for determining size filter.

How it works

Based on recent activity sellers, recommend top ranking products from the sellers with size filter.

Ending soon items
Alert users to expiring items and promote related discounts

Use cases

  • Alert users to expiring items and promote related discounts.

  • Daily or Weekly Newsletters.

  • Backfill for other recommendations.

Re­quire­ments

  • Catalog of items.

  • end_date attribute in ISO8601 format.

Inputs

Site wide pre-ranked list of items sorted by end_date timestamp.

How it works

Items in catalog with end_date less than next few days indicating expiry or removal.

Next Best Items
Post activity follow up alerts

Use cases

  • Post activity follow up alerts.

  • Abandoned search/​browse/​cart follow ups.

Re­quire­ments

  • View or equivalent events with product_ids.

  • Item catalogs with matching product_ids and size in tags ( as applicable).

Inputs

  1. Recent activity timeline.

  2. Precomputed rankings based on other users with similar activity => Next best product, Cross-sell products.

  3. Category backfill.

  4. Site backfill.

How it works

Top items to consider after recent activity based on users with similar history and custom filters.

Feed type

Product-Product

Store name affinity items
Popular, Trending or Recent Items by user affinity store names

Use cases

  • Daily/Weekly newsletter with top/trending items in user affinity store names.

  • App/Site live content with top/trending items in user affinity store names.

Re­quire­ments

  • Item catalogs with store name.

  • Items activity/event timeline.

Inputs

  1. Number of items to recommend per affinity store name (Default 2).

  2. Store Name Ranking.

  3. Site-wide Backfill (if rec­om­mend­ed products less than return count). Set 'None' if not required.

How it works

Popular, Trending or Recent Items by user affinity store names.

Automotive

Recipes for auto parts and vehicle-specific rec­om­men­da­tions based on year, make and model.

Items by user vehicle's year, make and model
Items by user's vehicle

Use cases

  • Items by user's vehicle.

  • Backfill Recommendations.

  • Daily Newsletters.

Re­quire­ments

  • Catalog with product_ids.

  • User year, make and model attributes.

Inputs

  1. User Vehicle Year Attribute.

  2. User Vehicle Make Attribute.

  3. User Vehicle Model Attribute.

How it works

Items based on user vechicle's year, make and model.

Similar items to previous block by user's vehicle year, make, model and category
Best Sellers by user's year, make and model at a given category level

Use cases

  • Best Sellers by user's year, make and model at a given category level.

  • Top viewed by user's year, make and model at a given category level.

  • Promotional content by user's year, make and model at a given category level.

  • Trending items by user's year, make and model at a given category level.

  • New additions by user's year, make and model at a given category level.

  • Homepage recommendations.

Re­quire­ments

  • Catalog with category and product_ids.

  • User year, make and model attributes.

  • Pre-computed rankings.

Inputs

  1. Previous block name.

  2. Item Category Level. The default value is Leaf level.

  3. User Vehicle Year Attribute.

  4. User Vehicle Make Attribute.

  5. User Vehicle Model Attribute.

  6. Vehicle year/make/model by Category Ranking 1. Select None, if not needed.

  7. Vehicle year/make/model by Category Ranking 2. Select None, if not needed.

  8. Vehicle year/make/model by Category Ranking 3. Select None, if not needed. 9 Vehicle year/make/model by Category Ranking 4. Select None, if not needed. 10. Site-wide Backfill. Select None, if not needed.

How it works

Top engaged items by user's vehicle year, make, model and previously interacted categories by previous block items.

Category affinity items by user's vehicle year, make, model
Best Sellers by user's year, make and model by category affinity

Use cases

  • Best Sellers by user's year, make and model by category affinity.

  • Top viewed by user's year, make and model by category affinity.

  • Promotional content by user's year, make and model by category affinity.

  • New additions by user's year, make and model by category affinity.

  • Price ordered items by user's year, make and model by category affinity.

  • Homepage recommendations.

Re­quire­ments

  • Events with product_ids.

  • Catalog with brand and product_ids.

  • User year, make and model attributes.

  • Pre-computed rankings.

Inputs

  1. User Vehicle Year Attribute.

  2. User Vehicle Make Attribute.

  3. User Vehicle Model Attribute.

  4. Enter the number of user category affinities to consider.

  5. Vehicle year/make/model by Category Ranking 1. Select None, if not needed.

  6. Vehicle year/make/model by Category Ranking 2. Select None, if not needed.

  7. Vehicle YMM Backfill Ranking. Select None, if not needed.

How it works

Top category affinity items by user's vehicle year, make and model.

Live content - Next Best Items to seed items + category level trending items
Next best items based on seed items in live context payload…

Use cases

Live content on site or in app when users are actively in session to suggest next best items to purchase.

Re­quire­ments

  • Live Content request payload with seed_items.

  • Item Catalogs with matching seed_items.

Inputs

  1. Name of event payload attribute for seed_items.

  2. Name of event payload attribute for exclude_items.

  3. Name of event payload attribute for exclude_​categories.

  4. Next best product ranking.

  5. Category backfill level.

  6. Upto 3 category rankings.

How it works

Based on seed items in rec­om­men­da­tion context, recommend next best products and category top items. Category will be collected based on seed item and next best item. Category level can be defined as leaf, parent or root. If leaf - leaf level trending items will be added, if leaf + parent, then leaf + parent level trending items will be added. If leaf + parent + root, then the 3 level trending items will be added. Upto 3 category rankings can be selected.

Feed type

Product-Product

Online learning

Recipes for educational platforms, focused on course, teacher and content recommendations.

Courses for you
Homepage rec­om­men­da­tions

Use cases

  • Homepage recommendations.

  • Next Best Courses to take.

Re­quire­ments

  • User language attributes.

  • Catalog with relevant item ids.

Inputs

  1. Use language filter. Tick checkbox, is teachers are to be filtered based on language.

  2. User language attribute name. If selected, mention language attribute for user.

  3. Catalog language attribute name. If selected, mention language attribute from catalog.

  4. Courses Ranking.

How it works

Courses to consider based on user's language attributes at account level.

Live content - Popular items matching seed_tags in payload
Live content on site or in app when users are actively in session

Use cases

Live content on site or in app when users are actively in session.

Re­quire­ments

  • Live Content request payload with seed_tags.

  • Item Catalogs with matching tags.

Inputs

Name of event payload attribute for seed_tags.

How it works

Based on seed tags in rec­om­men­da­tion context, recommend other popular tag items.

Teachers for you
Post activity follow up alerts

Use cases

  • Post activity follow up alerts.

  • Incomplete search/​browse/​course follow ups.

  • Homepage recommendations.

Re­quire­ments

  • View or equivalent events with product_ids.

  • Item catalogs with matching product_ids.

Inputs

  1. Recent activity timeline.

  2. Use language filter. Tick checkbox, is teachers are to be filtered based on language.

  3. User language attribute name. If selected, mention language attribute for user.

  4. Catalog language attribute name. If selected, mention language attribute from catalog.

  5. Precomputed rankings based on other users with similar activity.

  6. Tags Similarity Ranking.

  7. Site-wide backfill. For rec­om­mend­ed teachers < return count. Select None, if not required.

How it works

Teachers to recommend based on other users with similar event activity and user's language attributes.

User feeds
Bring your existing user to item rec­om­men­da­tions as feed imports

Use cases

  • Bring your existing user to item rec­om­men­da­tions as feed imports.

  • Mix and match with pre-computed user rankings.

  • Alert users across channels including In-App or Onsite.

  • Newsletters.

  • User specific promotions / sponsored items.

Re­quire­ments

  • User profiles.

  • User feeds.

Inputs

  1. User feed ranking.

  2. Site-wide backfill (optional).

How it works

Per­son­al­ized list of items per user as indicated in external feed uploaded by customer.

Feed type

User-Product

Location-based

Recipes that use location data such as city, state, zip code and coordinates.

City-state popular, trending, recent items
Popular or trending or recent items by city and state

Use cases

  • Show case your most popular or trending offerings to your new customers by specific city and state.

  • Alert all users to recent additions to your catalogs by specific city and state.

  • Alert all users to seasonal or sponsored promotions by specific city and state.

  • Win back your inactive customers with exclusive but popular items by specific city and state.

  • Backfill other recommendations.

Re­quire­ments

  • Events with product_ids in payload.

  • Item Catalogs matching those product_ids.

  • City and State attributes in item catalogs.

Inputs

  1. City-State Name.

  2. One of the precomputed rankings for each city state combination.

How it works

Popular, Trending, Recent items based on all user activity on your sites and apps by each city and state.

Live content - similar items to seed_items
Use products in seed items to recommend similar items

Use cases

  • Use products in seed items to recommend similar items.

  • Multi block per­son­al­i­za­tion based on seed items.

  • Homepage recommendations.

Re­quire­ments

  • Events with product_ids.

  • Item catalogs with matching product_ids.

Inputs

  1. Seed Items Array.

  2. City-State Level Ranking.

  3. Zipcode Backfill. Select None, if not required. For rec­om­mend­ed items count < return count.

  4. Site-wide backfill. Select None, if not required. For rec­om­mend­ed items count < return count.

How it works

Items related to seed items with backfills. Similarity is based on user session and trans­ac­tion activity with other users.

Items based on user lat/long
To provide rec­om­men­da­tions for new users with insufficient history

Use cases

To provide rec­om­men­da­tions for new users with insufficient history.

Re­quire­ments

  • User profile with lat/long.

  • Product catalog with lat/long.

Inputs

  1. User lat/long variables.

  2. Radius for search.

How it works

Retrieve lat/long from user profile Find nearest products. Since this is meant for new users, there will be no filters as there will not be sufficient activity. For recent activity based rec­om­men­da­tions, use other recipes.

Similar Items per alert attributes with custom filters per selection
Similar items per alert attributes set by user with custom filters…

Use cases

Use alert attributes to recommend items that fit that at regular cadence via newsletter Use alert attributes to recommend items that fit when user visits app/website.

Re­quire­ments

  • Events with product_ids.

  • Item catalogs with matching product_ids.

  • User profile with alert attribute.

Inputs

  1. Previous block / recent activity.

  2. Custom filters (bedroom, price, property type).

  3. Supplement with user affinity categories?

  4. Custom Priority.

How it works

Items on the basis of alert attributes supplemented with recent activity products that are provided as previous block. Similarity is based on user session and trans­ac­tion activity of all users. Various filters to be applied can be selected.

Cross-industry

These recipes work across industries and use common per­son­al­i­za­tion patterns.

Next best items/Similar items using LLM
Cross-catalog rec­om­men­da­tions based on rich text similarity using LLMs

Use cases

Cross-catalog rec­om­men­da­tions based on rich text similarity using LLMs.

Re­quire­ments

Catalogs with rich text data.

Inputs

  1. User recent activity / previous block.

  2. Next best item/Similar Item LLM rankings.

  3. Backfill ranking based on category/site if insufficient results.

How it works

Recommend items from other categories based on text similarity using LLMs.

Recent activity
Wishlist reminders

Use cases

  • Wishlist reminders.

  • Re-order reminders.

  • Replay Purchase history.

  • Replay Cart history.

  • Replay Watch / Read / Stream history.

Re­quire­ments

  • Events saved on timeline with product_ids in payload.

  • Item Catalogs matching those product_ids.

How it works

Use items and their attributes from last 366 days of events to per­son­al­ize templates and messaging across all channels.

Site-wide popular, trending or recent items
Popular, trending, recent items across all of your sites and apps

Use cases

  • Show case your most popular or trending offerings to your new customers.

  • Alert all users to recent additions to your catalogs.

  • Alert all users to seasonal or sponsored promotions.

  • Win back your inactive customers with exclusive but popular items.

  • Backfill other recommendations.

Re­quire­ments

  • Events with product_ids in payload.

  • Item Catalogs matching those product_ids.

Inputs

One of the precomputed rankings across site wide activity or catalogs.

How it works

Popular, Trending, Recent items based on all user activity on your sites and apps.

Category affinity items
Daily or weekly news­let­ters

Use cases

  • Daily or weekly newsletters.

  • Backfill for other recommendations.

Re­quire­ments

  • Events with product_ids.

  • Catalog of items with those product_ids.

  • Category attribute for each item in the catalog.

Inputs

  1. Pre-computed category level rankings.

  2. Number of items to consider per category. Default value is 2.

  3. Site wide backfill if user does not have sufficient affinities or items. Select None, if not required.

How it works

AI generated list of items per­son­al­ized to each user based on categories they have affinity towards. The list of categories is updated daily based on user activity across all sites and apps.

Choosing recipes by user lifecycle

Recipes can be mapped to different stages in the user lifecycle. Consider selecting a recipe based on your intended audience.

User lifecycle stage

Sample recipes

New users

  • Popular or trending items site-wide or by category

Active users

  • Similar items to recent activity

  • Similar items other users like them consider

  • Next best items based on recent activity

  • Related items based on frequent visits

  • Related items to current session viewing history

  • Affinity items ordered by popularity or auto-optimized

  • Items based on explicit user preferences

  • Alerts like price drops, low stock, or new arrivals

  • Predictive content feeds auto-optimized based on engagement

Intermittently active users

  • Affinity items ordered by recency or auto-optimized

  • Alerts like new collections, seasonal discounts, or restocks

  • Predictive content feeds based on prior activity

Churned users

  • Winback promotions ordered by popularity

  • Predictive content based on previous transactions

  • Promotional content related to prior activity

  • Affinity items ordered by recency or auto-optimized

All users

  • Predictive content based on user attributes

  • Seasonal items ordered by popularity or auto-optimized

  • Newly added items ordered by recency

  • Editorial or curated items

What's next

Browse our library of ready-to-use recommendation recipes designed for common use cases across industries.
​Explore recommendation recipes →

Did this answer your question?