Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Recommended Items


FREE x
TEAM x
BUSINESS
ADDON

With Recommended Items, you can add personalized item recommendations as a computed trait to each user profile.

Based on a user's past interactions, this trait generates a list of up to 5 items, like products, articles, or songs, that each user is most likely to engage with.

Segment designed Recommended Items for cases where you want to personalize experiences, like email content, in-app recommendations, or website suggestions, to fit each user's unique preferences.

On this page, you'll learn how Recommended Items works, how to create a Recommended Item trait, and best practices to get the most out of your recommendations.

The Select Computed Trait screen in the Segment UI, showing options like Predictions, Recommendation (selected), Event counter, Aggregation, and Most frequent. The Recommendation option description reads 'Recommend personalized products' and includes additional details about Cross Sell, Personalization, and Next Best Action use cases.

.

Exclusion rules

exclusion-rules page anchor

Exclusion rules let you filter out specific items from recommendations, helping keep suggestions relevant and valuable. For example, you could use them to remove items a user has already purchased or exclude products above a certain price.

There are two types of exclusion rules:

  • Item information: This filters out items based on product catalog metadata. For example, you can exclude items over a certain price, from a specific category, or by a particular brand.
  • Past user action: This filters out items based on a user's interaction history. For example, you can remove items a customer already purchased or previously added to their cart.

Example use case: personalized album recommendations

example-use-case-personalized-album-recommendations page anchor

Suppose you're managing a music streaming app and want to give each user personalized music recommendations based on their listening habits.

Here's how you could configure this trait:

StepConfiguration
Select usersUse an audience based on up to 2 million active, non-anonymous listeners who played at least one song in the past month.
Item typeSelect Albums as the item type to recommend. Because you have an extensive catalog of music, this lets each listener receive recommendations tailored to their interests.
Number of item typesYou decide to return a maximum of 5 albums for each profile, keeping the recommendations relevant and concise.
CalculateClicking Calculate gives you an overview of how many users will receive the album recommendations. Use it to ensure your conditions and catalog mapping meet your criteria.
Sync to destinationsThis optional step lets you sync the trait to third-party destinations to deliver album recommendations over email, in-app messaging, or push notifications.
Trait namingName your trait Personalized Album Recommendations, making it easy to identify for future campaigns.

By setting up a trait like this, each user profile now includes personalized recommendations that reflect individual tastes. You can use these recommendations across a range of touchpoints, like in-app sections, personalized email content, or targeted messaging, to create a more engaging and customized user experience.


Keep the following in mind as you work with Recommended Items:

  • Limit recommendations to key items: Start with 3-5 items per profile to keep recommendations concise and personalized.
  • Consider audience size: Larger audiences can dilute engagement rates for each recommended item. Focusing on the top 20% of users keeps recommendations relevant and impactful.
  • Give the system time to build the trait: Recommended Items traits can take up to 48 hours to generate, depending on data volume and complexity. Segment recommends waiting until 48 hours have passed before using the trait in campaigns.