Shoppertainment

The Shoppertainment area in My Relewise helps you monitor and configure Relewise's feed-based discovery experiences. It currently contains Adaptive Discovery reporting and Adaptive Discovery feed configuration.

Shoppertainment in My Relewise is separate from Administration feeds. Administration feeds are used to import entity data into Relewise. Adaptive Discovery feed configurations control which Product and Content sources can be used inside an Adaptive Discovery experience.

For the product and implementation overview, see Shoppertainment and Adaptive Discovery.

Shoppertainment Overview

The Shoppertainment overview page introduces the available Shoppertainment features for the selected Dataset. Use it to navigate to Adaptive Discovery and to understand which Shoppertainment capabilities are enabled for your Dataset.

If the Shoppertainment feature is not enabled for your license or Dataset, the Shoppertainment pages may not be visible in My Relewise.

Adaptive Discovery

The Adaptive Discovery page shows activity for Adaptive Discovery requests in the selected date period.

Use this page to:

• Review Adaptive Discovery request volume over time.
• Inspect live Adaptive Discovery requests as they are sent to Relewise.
• Confirm that feed requests are reaching the Dataset.
• Navigate to Adaptive Discovery feed configurations.

The live view works like other My Relewise live views: it is intended for recent activity and troubleshooting, not long-term reporting. If no Adaptive Discovery requests appear, expand the selected date period or trigger a new Adaptive Discovery request from your storefront.

Feed Configuration

The Feed Configuration page lists the Adaptive Discovery feed configurations available for the Dataset.

Use feed configurations to define how an Adaptive Discovery feed can pull Products and Content from different source strategies. A configuration can be active or inactive, and one active configuration can be marked as the default.

Each configuration has:

• ID: The internal configuration ID.
• Key: The key used to identify the configuration.
• Name: The display name shown in My Relewise.
• State: Whether the configuration is active or inactive.
• Default status: Whether the configuration is used as the default.
• Product sources: Sources that produce Product items for the feed.
• Content sources: Sources that produce Content items for the feed.

Active and Default Configurations

Turn Status on to activate a feed configuration. Turn it off to deactivate it.

Use Is the Default to make an active configuration the default configuration. The default configuration is used when the implementation does not request a specific feed configuration.

Feed Sources

Feed sources define how Adaptive Discovery builds the next Product or Content candidates for the feed. Sources are grouped into Product and Content sections.

You can enable or disable individual sources, drag sources to reorder them, and place multiple sources at the same priority. When sources share a priority, the tie breaker controls their relative weight.

Shared Source Settings

Most feed sources include these settings:

• Enabled: Controls whether the source can produce feed items.
• Priority: Controls source order. Lower priorities are considered before higher priorities.
• Tie Breaker Probability: Controls the relative weight between sources with the same priority.
• Max Results: Limits the total number of items the source may return.
• Max Results Per Chance Given: Limits the number of items the source may return each time it gets a chance to contribute to the feed.
• Randomization Window: Controls how much local randomization is applied after the source has ranked or selected candidates.

Product Sources

Product sources produce Product items for Adaptive Discovery.

Purchase Popularity

Produces Products based on purchase popularity within the selected popularity window. Use this when the feed should include Products that are currently selling well.

View Popularity

Produces Products based on view popularity within the selected popularity window. Use this when the feed should include Products that shoppers are currently browsing.

Products From Content Data

Reads Product IDs from a configured Content Data Key and produces those Products. Use this when Content entities contain curated or editorial Product references.

The Content Data Key must contain Product IDs that match Products in the Dataset.

Purchased With Product

Produces Products that are commonly purchased together with Product seed items already known to the feed. Use this to continue discovery from Product interest into complementary Products.

Viewed After Product

Produces Products that shoppers often view after Product seed items. Use this to continue browsing paths from Products already shown or interacted with.

Viewed After Content

Produces Products that shoppers often view after Content seed items. Use this when Content is used as an inspiration step before Product discovery.

Content Sources

Content sources produce Content items for Adaptive Discovery.

Content Popularity

Produces Content based on content popularity. Use this when the feed should include Content that currently receives strong engagement.

Product Popularity From Content

Reads Product IDs from a Content Data Key and ranks Content using the popularity of the referenced Products. Use this when Content should be selected based on the Product interest it represents.

This source can also use:

• Product Popularity Window Minutes: The time window used to calculate referenced Product popularity.
• Product Popularity Dimension: The popularity dimension used when scoring referenced Product IDs.
• Aggregation: How popularity scores are combined across referenced Product IDs.
• Content Popularity Threshold: How many popular Content items are considered.
• Max Product IDs Per Content: How many Product IDs are read from each Content item.

Overlapping Content Data

Produces Content based on overlapping values in configured Content Data Keys. Use this when Content items should continue a theme, topic, category, or other shared data value from Content already used as a seed.

Viewed After Content

Produces Content that shoppers often view after Content seed items. Use this to continue content-led discovery.

Viewed After Product

Produces Content that shoppers often view after Product seed items. Use this to mix Product-led browsing with relevant Content.

Seed-Based Settings

Several Product and Content sources use seed items from the current feed context.

• Max Seed Items limits how many seed items are considered when building the result queue.
• Max Look Behind Count controls how many previous Content items are considered before moving to the next feed source.
• Max Look Behind Distance controls how close newly produced Product items should be to previously shown Content items.

Use these settings to control how strongly the feed follows recently shown or interacted-with items.

Troubleshooting

If a feed configuration does not behave as expected:

1. Confirm that the configuration is active.
2. Confirm that the intended configuration is marked as default, or that the implementation requests the correct configuration key.
3. Check that the relevant Product and Content sources are enabled.
4. Review priorities and tie breakers to confirm that the intended sources get a chance to contribute.
5. Check result limits if a source appears to return too few items.
6. For sources that use Content Data Keys, confirm that the Content entities contain the expected Product IDs or data values.
7. Use the Adaptive Discovery live view to confirm that requests are reaching Relewise.