Content Recommendations are a powerful tool that can be used to increase user engagement by presenting users with relevant content that resonates with them. By utilizing the Lytics Topic Taxonomy and powerful Machine-Learning algorithms, Lytics is able to make data-driven Content Recommendations within milliseconds. Powered by over 500 features, and the flexibility to customize your recommendations, Lytics' Content Recommendation API removes the heavy-lifting when it comes to content personalization via web, email, etc.
Out of the box, Lytics' Content Recommendations can be leveraged in 3 ways:
Recommend content with Lytics Personalization
Recommend content with Pathfora JS
Pathfora JS is capable of taking a content collection and fetching and displaying the recommended content for the current user. Read more about it in the Pathfora JS Docs.
Recommend content with Lytics APIs
The Lytics content recommendation API takes a handful of parameters, including the user the recommendation is for and an optional content collection to recommend from. Read more about it in the Lytics API Docs.
Using content collections in recommendations
Content collections are commonly used in content recommendations. By selecting a content collection as the source of your content recommendation, you're limiting which content the recommendation engine can select from. This is desirable for most use cases, because by default Lytics will scrape any and all pages of your website that users are visiting. Without a content collection defined, the recommendation engine will return what is most relevant to the user regardless of the context. For example, in a marketing context you wouldn't want to promote your careers page, even if it is the most relevant piece of content to the user in question.
Size of the collection is also an important factor when using a collection for recommendation. The more content the recommendations engine has access to, the better, more personalized recommendations it can serve. If you can, try to make sure your content collection is of a decent size, and at the minimum fits the following requirements:
- Documents are valid (return a 200-status from an HTTP get request)
- Documents have been enriched by Lytics
- Documents have topics associated with them
If none of the documents in your collection fit these conditions, the recommendation engine may have issues returning recommendations as it doesn't have enough information to make a recommendation. If you would like assistance setting up these filters in your collection or to set up a collection with content published less than 1 week in the past, contact Lytics Support.
Content collections in Lytics Personalize campaigns
When setting up a recommend content campaign through the Lytics UI, you will be asked to select an existing content collection or build a new collection to use in the campaign. For more information on this, see our documentation on the editor for choosing content.
Using collections in custom content recommendations
If you're using the Lytics API to recommend content, you can use the
contentsegment query parameter to define the content collection you want to use. The value of this parameter should be the ID of the content collection.
You can locate the ID of the collection from the URL on the summary page. The ID will come after
/collections/ in the URL, and will end before the beginning of the query parameters.