Skip to main content

Location-Based Business Recommendation Recipes

Recipes that use location data such as city, state, zip code and coordinates. Featured recipes (☆) are listed first. Expand a recipe to see its use cases, requirements and how it works.

Recipes for other industries: Cross-industry · Retail · Media · Marketplaces · Automotive · Online Learning

New users

For users who have recently joined or started engaging.

☆ Featured · 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.

City popular, trending, recent items
Popular or trending or recent items by city

Use cases

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

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

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

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

  • Backfill other recommendations.

Re­quire­ments

  • Events with product_ids in payload.

  • Item Catalogs matching those product_ids.

  • City attribute in item catalogs.

Inputs

  1. City Name.

  2. One of the precomputed rankings for each city.

How it works

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

Zipcode popular, trending, recent items
Popular or trending or recent items by zipcode

Use cases

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

  • Alert all users to recent additions to your catalogs by specific zipcode.

  • Alert all users to seasonal or sponsored promotions by specific zipcode.

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

  • Backfill other recommendations.

Re­quire­ments

  • Events with product_ids in payload.

  • Item Catalogs matching those product_ids.

  • Zipcode attributes in item catalogs.

Inputs

  1. Zipcode Name.

  2. One of the precomputed rankings for each zipcode.

How it works

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

Active users

For users who engage regularly.

Similar items to previous block with custom filters per selection
Use products in previous blocks to recommend similar items

Use cases

  • Use products in previous blocks to recommend similar items.

  • Multi block per­son­al­i­za­tion based on recent activity.

Re­quire­ments

  • Events with product_ids.

  • Item catalogs with matching product_ids.

Inputs

  1. Previous block name.

  2. Number of items to consider from recent activity. Default value is 1.

  3. Max radius within which properties to be recommended.

  4. If insufficient properties, should zip and msa level backfill be considered?

  5. Price variance percentage for filtering. Enter as number (e.g. 15 for 15%).

  6. Should bathrooms also be matched? Currently matching for full bathrooms only. Not half baths.

How it works

Items related to previous block with backfills. Similarity is based on user session and trans­ac­tion activity with other users. Various filters to be applied can be selected.

Feed type

Product-Product

Next best items
Post activity follow up alerts

Use cases

  • Post activity follow up alerts.

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

  • Homepage recommendations.

  • Engagement recommendations.

Re­quire­ments

  • View or equivalent events with product_ids.

  • Item catalogs with matching product_ids.

Inputs

  1. Recent activity timeline.

  2. Number of items to be considered from recent activity.

  3. Product similarity rankings based on other users with similary activity.

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

  5. Zipcode level backfill. Select None, if not required. For rec­om­mend­ed items count < return count.

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

How it works

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

Feed type

Product-Product

Similar items to previous block
Use products in previous blocks to recommend similar items

Use cases

  • Use products in previous blocks to recommend similar items.

  • Multi block per­son­al­i­za­tion based on recent activity.

  • Homepage recommendations.

Re­quire­ments

  • Events with product_ids.

  • Item catalogs with matching product_ids.

Inputs

  1. Previous block name.

  2. Number of items to consider from previous. Default value is 2.

  3. Number of items to recommend per previous block item. Default value is 2.

  4. City-State Level Ranking.

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

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

How it works

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

Next best items
Post activity follow up alerts

Use cases

  • Post activity follow up alerts.

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

  • Homepage recommendations.

  • Engagement recommendations.

Re­quire­ments

  • View or equivalent events with product_ids.

  • Item catalogs with matching product_ids.

Inputs

  1. Recent activity timeline.

  2. Number of items to be considered from recent activity.

  3. Product similarity rankings based on other users with similary activity.

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

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

How it works

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

Similar items to previous block with custom filters per selection v2
Use products in previous blocks to recommend similar items

Use cases

  • Use products in previous blocks to recommend similar items.

  • Multi block per­son­al­i­za­tion based on recent activity.

Re­quire­ments

  • Events with product_ids.

  • Item catalogs with matching product_ids.

Inputs

  1. Previous block name.

  2. Number of items to consider from recent activity. Default value is 1.

  3. Bedroom filter.

  4. Price variance percentage for filtering. Enter as number (e.g. 15 for 15%).

  5. Use user affinity categories to identify candidate products.

  6. Max radius for search - WIll be used as default if user max radius or neighbourhood radius not available.

How it works

Items related to previous block with backfills. Similarity is based on user session and trans­ac­tion activity with other users. Various filters to be applied can be selected.

Intermittently active users

For users who engage now and then.

New in building floorplans
Show new floorplans based on past user activity

Use cases

Show new floorplans based on past user activity.

Re­quire­ments

  • Events with product_ids.

  • Item catalogs with matching product_ids.

Inputs

  1. Bedroom filter, property filter price filter to be applied.

  2. Custom prioritization.

How it works

New floorplans in buildings user has previously engaged with filtered on basis of recent activity to show items with custom filters (price, bedrooms, property type) and stepped relaxation of filters as pre-configured.

Churned users

For users who have stopped engaging.

☆ Featured · 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.

All users

For users at any lifecycle stage.

☆ Featured · 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.

☆ Featured · 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.

Items matching user city attributes
Popular items matching user attribute joined on city attribute

Use cases

  • Popular / Trending items per­son­al­i­za­tion based on specific user attribute.

  • Mix and match with pre-computed user rankings.

  • Daily / Weekly Newsletters.

  • User specific promotions / sponsored items.

Re­quire­ments

User attribute value matching city values from product catalog.

Inputs

  1. User City Attribute Name.

  2. City Ranking.

How it works

Popular items from user city attribute joined with item catalogs. The string attribute must match what is available in catalogs and are case sensitive.

Live content - popular items by city-state
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 city & state.

  • Item Catalogs with matching city-state.

Inputs

  1. City-State level rankings.

  2. Name of event payload attribute for city & state.

  3. Number of items to be rec­om­mend­ed per city-state combination.

  4. Side-wide Backfill. Select None, if not required.

How it works

Based on city & state in rec­om­men­da­tion context, recommend other popular city-state items.

Items matching user zipcode attribute
Popular items matching user attribute joined on zipcode attribute

Use cases

  • Popular / Trending items per­son­al­i­za­tion based on specific user attribute.

  • Mix and match with pre-computed user rankings.

  • Daily / Weekly Newsletters.

  • User specific promotions / sponsored items.

Re­quire­ments

User attribute value matching zipcode values from product catalog.

Inputs

  1. User Zipcode Attribute Name.

  2. Zipcode Ranking.

How it works

Popular items from user zipcode attribute joined with item catalogs. The string attribute must match what is available in catalogs and are case sensitive.

Live content - popular items by zipcode
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 zipcodes.

  • Item Catalogs with matching zipcodes.

Inputs

  1. Zipcode level rankings.

  2. Name of event payload attribute for zipcodes.

  3. Number of items to be rec­om­mend­ed per zipcode combination.

  4. Side-wide Backfill. Select None, if not required.

How it works

Based on zipcodes in rec­om­men­da­tion context, recommend other popular zipcode items.

Connect with Blueshift for personalized recommendations

Whether you're exploring new ways to use recommendation recipes or looking to design a custom model for your business, our team can guide you through the next steps.

Reach out to [email protected] or your Customer Success Manager (CSM) for assistance.

What's next

Learn how Recommendations Studio works and understand the workflow for creating personalized recommendations.
​How Recommendations Studio works →

Did this answer your question?