Offer Effectiveness & Catalog

Report type key: recommender_offer_markdown
Configuration type: Interactions
Group: Interactions

Offer presentation and uptake, rank behavior, product-catalog snapshots, catalog changes, utilization, and experiments.

The experimentation UI family also lands here.

How to get it

Create and save an Interactions configuration.
Enable: Interactions family offers.
Run the job and wait until completed.
Open Reports (/reports), select that job, and choose this type.

Markdown viewer: /markdown/JOB_ID/recommender_offer_markdown
API: GET /reports/JOB_ID/recommender_offer_markdown

The offers family was off or the step failed. Check job logs and Analysis & LLM.

What it contains

Offer effectiveness table — presented, accepted, uptake per presentation, lift vs overall.
Daily presented vs accepted volume and uptake ratio.
Product×day peaks (compact; full offer_time stays in JSON).
Offer matrix / catalog snapshot — status, snapshot count, unique versions and offers.
Ranking effectiveness — uptake by presented rank; accepted vs non-accepted score separation when scores exist.
Catalog quality (missing descriptions, negative-value findings, field inventory).
Utilization (offers never presented) and catalog change history.
Recommended actions to drive product success — evidence, action, measure, guardrail (advisory).

“Selling” in this report means presented-then-accepted until a purchase event is linked.

How to read

Read uptake per presentation, then rank 1 vs lower ranks. A catalog offer that never appears in slates is a utilization issue, not a Financial KPI.

Companion artifacts

Key	Artifact
`recommender_offer_markdown`	Markdown report
`recommender_offer_notebook`	Jupyter notebook
`recommender_offer_results`	JSON results
`recommender_offer_graphs`	Rank / uptake graphs

Markdown, notebook, and graphs for the same family usually land together. JSON feeds Analysis Insights.