Product / Service Finder

Published July 28, 2026

Product / Service Finder turns participant answers into ranked, explainable recommendations. It uses a reusable Offer Catalog, one or more Finder Question blocks, and a Personalized Recommendations results block.

How the parts work together

• Offer Catalog: Workspace-level business data containing matching criteria, offers, actions, and fit signals.
• Finder Question: Collects one criterion, such as goal, budget, experience level, or service need.
• Personalized Recommendations: Securely ranks eligible offers and presents the strongest matches with optional match strength and reasons.
• Product Cards: Manually merchandises fixed offers; it does not calculate a match.

Offer Catalogs are separate from the Asset Library. The Asset Library stores reusable files, images, and links. An Offer Catalog stores structured business logic and may reference Asset Library images.

Build a finder

1. Open Offer Catalogs from the dashboard.
2. Create a catalog and add at least one matching criterion with two or more answer options.
3. Add at least two active offers.
4. For each offer, choose how strongly every relevant answer fits and add a short participant-facing reason.
5. Set the offer action to a website URL, booking page, or no action.
6. Use Test matching to review ranking, exclusions, and explanations.
7. Publish the catalog to create an immutable version.
8. Open a Flow and add a Finder Question for each criterion you want to ask.
9. Add Personalized Recommendations after those questions.
10. Choose the result count, minimum match strength, and whether to show strength and reasons.
11. Preview the full path, then save and publish the Flow.

Matching behavior

Strong fits rank above good, neutral, and poor fits. An explicit exclusion removes an incompatible offer. A criterion marked Required compatibility also removes offers that do not define compatibility for the participant's selected answer.

Ties are deterministic: match strength, score, offer priority, and catalog order are applied in sequence. Published Flows keep using the catalog version they reference until the builder intentionally selects a newer published version.

Security and privacy

Matching runs on the QuizFlow Labs server. Public Flow definitions contain catalog and version references, but not internal offer names, SKUs, vendors, fit weights, exclusion rules, or catalog administration data. Finder requests contain only Flow answer option identifiers needed for matching.

Analytics

Block Performance records recommendation impressions, no-match states, and offer interactions. Each interaction includes the recommendation block and selected offer identifier, so you can compare which matches participants see and which actions they take.

Troubleshooting

• No catalog appears: publish an Offer Catalog with at least one valid criterion.
• No recommendations appear: confirm offers are active, review exclusions and required compatibility, then lower the minimum match strength if appropriate.
• A question has old options: select the current published catalog and criterion again, then save the Flow.
• The catalog changed but the Flow did not: publish the catalog and intentionally update the Finder blocks to the new immutable version.