Catalog Management empowers technical users to view, manage, diagnose, and explore data across all the catalogs in their account. It covers the entire experience of managing the data integration process, from feeding data into a Discovery catalog all the way to configuring and verifying the data in our Search and Suggest APIs. Check out the articles below to learn more:
- Catalog Management feature page
1.1 Understanding Feed & Configuring Attributes
1.2 Promoting Changes & Viewing Jobs
1.3 Exploring Catalog Data & Customizing API
We have updated our SSO documentation to answer your frequently asked questions about setting up an SSO connection with the Bloomreach IAM.
An interesting update for all Developers using our documentation! The Developers section has been revamped to have a new home. It now also lists down the necessary resources for help regarding all technicalities related to Bloomreach Discovery. Developers can find detailed guides for integration and other configurations, along with API references and even FAQs.
The Algorithm Controls feature enables you to configure 4 of our search algorithms via API calls directly. We have created a dedicated article on how this feature works. Visit this guide to learn more about this feature's benefits, uses, and implementation.
We have also added new pieces of documentation that dive deeper into the functioning of our search algorithms. Check out the revised algorithm documentation here:
The Recommendations and Pathways API Reference got an exciting update this month. We’ve added a new page consisting of an exhaustive list of all the parameters used in all of the Recommendations and Pathways APIs. Since a lot of the parameters are common for all APIs and a few of them are specific to some APIs, having a one-stop destination with details about every parameter can prove to be very useful for your developers.
We’ve detailed the What, Why, and How of each parameter and which APIs they can be used with. You can also find real-life example values for the parameters. Next time you need additional information on any parameter while using the Recommendations and Pathways APIs, just head over to the Recommendations and Pathways parameters reference!
We are excited to share the dedicated documentation for the Real-time Customer Segments for Discovery feature. This feature makes it easy to personalize search results at the most granular level by combining Engagement's powerful CDP and Discovery's extensive search algorithms. Check out the articles about this feature on Discovery and Engagement documentation.
With Pixel Monitor Phase 2 launch, you can now monitor your pixel health at the site level. Also, new pixel checks are available for Relevance by Segment and Content Search. We have added the following articles to help you learn about this feature:
Welcome to the new home of Bloomreach Discovery documentation! Our move to Readme comes with many improvements, especially to our API documentation:
- Improved API documentation
- Unified documentation
Readme’s Try It! feature allows you to make authenticated calls and receive real responses within the documentation. This allows your developers to explore our APIs and check if your calls are set up correctly.
Please note that this feature requires proper authentication to receive a response. We have also provided test values that you can use.
Readme provides a stylized parameter reference, which better highlights each parameter and their requirements. This is also where you enter values for Try It!
Did you notice the GET tags on the left? Any page detailing operations on an API will have a matching tag in the navigation menu. This should help you find detailed API information more easily.
Our new documentation site now provides unified access to documentation for each of Bloomreach’s products. Quick access is located at the top of any page.
In addition to the migration, we have also taken this opportunity to restructure the Discovery documentation and clean up all of the pages. The page categories have been renamed and rearranged to more accurately reflect their contents, and we have removed some duplicate or redundant pages to reduce clutter. Many pages have also been revised for clarity.
Readme’s navigation menu and search function should also feel smoother. In particular, you can filter searches by product (Engagement, Content, or Discovery) and section (Guides, Reference, etc.), and search results are displayed within the documentation instead of a separate search results section. This should reduce the amount of time spent loading pages and help you find specific pages more easily.
On our end, Readme will make it easier for us to make and manage our documentation. We hope that you find our documentation site to be more usable and friendly to your needs as well. We welcome your feedback, which you can submit at the bottom of any page.
Updated about 1 month ago