Integration cookbooks (map RecSys to your domain)

This guide shows how to integration cookbooks (map RecSys to your domain) in a reliable, repeatable way.

Who this is for

Integrators and platform engineers who need a quick, concrete mapping from RecSys concepts to real product patterns.

What you will get

• Three “copy this mental model” integration patterns
• What to log (and why) so evaluation and troubleshooting work
• Pitfalls that commonly break attribution and trust

Common building blocks (all cookbooks)

• Define stable surfaces (home, pdp, related, etc.).
• Generate or propagate a stable request_id per rendered list.
• Log exposures (ranked list) and outcomes (click/conversion) with the same request_id.

Read first if you haven’t yet:

• Basic integration steps: How-to: integrate recsys-service into an application
• Exposure logging & attribution: Exposure logging and attribution
• Event join logic: Event join logic (exposures ↔ outcomes ↔ assignments)

Cookbooks

• Webshop: Cookbook: integrate with a webshop
• Content feed: Cookbook: integrate with a content feed
• Event bus / streaming: Cookbook: integrate with an event bus (streaming)

Read next

• Back to How-to guides: How-to guides
• Troubleshoot integration failures: How-to: troubleshooting for integrators
• Integration contract: Integration spec