Catalog browser enhancements
If a client searches for a specific product ID or category ID, they are now taken directly to the product or category landing page. On product detail pages, we now display the entire category ancestry for each category the product belongs to. This allows users to quickly see the root categories of products.
- Clients can remove categories selected in a Recommendation restriction rule.
- In Advanced Merchandising, the link to the product detail page is fixed.
- Strategy settings in the catalog browser work properly in Firefox and Internet Explorer.
- In Advanced Merchandising, clients no longer see an error when changing the start date after creating a rule.
- In Engage, the segment export listing search feature works correctly.
- The site copy user interface prevents clients from clicking the copy function multiple times. It was accidentally creating multiple versions of rules and configurations.
- In Advanced Merchandising, the display bar shows the correct price percentage information.
CNET retailer catalog mapping
A new version was released by CNET for the retailer catalog mapping service. This work adopts the new process and provides an enhancement to our existing mapping by making updates faster and more reliable.
One-time historical transaction upload
Clients that want to enhance transaction history to improve recommendations can now provide RichRelevance a one-time batch upload of historical transactions. This helps new clients avoid the "cold start" experience, and reduces the listening period. It also helps existing clients enhance purchase history with offline transaction information.
These transactions come from different offline channels: in store, call centers, or historical online transactions. RichRelevance can take up to 90 days of data to build out behavioral strategies. If the intent is to leverage user-level purchase data for personalization, it can take on even more transactional data if associated to a user's historical purchases for reference in the User Profile Service (UPS).
The one-time historical file needs to be the same format as omnichannel feed files. The only difference is that the one-time historical zip file requires a prefix of historical_ that is uploaded to the same FTP location as omnichannel feed files.
Read more about specific instructions for clients: One-Time Historical Transaction Upload
- The recsForPlacements API now supports regions and URLs.
Content grouping for de-duping
We now support grouping of content for de-duping. This is particularly useful for clients that have banners with the same messaging in multiple sizes. Configuring tags for de-duping means only one banner of a particular size could qualify for display, and the remaining are disqualified due to de-duping being applied.
By assigning which tags should be considered for de-duping (this is done through Site Config, Engage, Tags for de-duping), any content with such tags will not appear twice on the same page. Currently, this has to be activated by Client Services on the RichRelevance Site Config page. To form a group with multiple tags, use a comma for tag separation, and then use a pipe for group separation. Example: sale,shoes|flowers
In the future, we plan to add administration of content grouping for de-duping in a client-facing tag management page.
We made a backend change to our site configurations for all Engage clients. This includes clients that have enabled the Engage dashboard for testing purposes. This change is expected to be transparent to all users. It's required for continued, seamless access to the Engage dashboard.