# Recommendations

Use **Recommendations** to highlight themed, seasonal, or top-selling products in a curated way. Whether you're boosting "Winter Favorites", promoting a "Local's Pick", or featuring a "Family Bundle", this module helps you deliver smarter suggestions to your users.

***

### What Is a Recommendation?

A **Recommendation** groups together one or more products under a shared label and time window. This allows you to:

* Promote specific products on your landing pages.
* Guide users to relevant content.
* Schedule featured products based on seasons or campaigns.

### Sample Output

```json
{
  "recommendation_id": "3743",
  "recommendation_title": "Christmas Special",
  "recommendation_description": "Hot selling",
  "recommendation_start_date": "2025-12-01T00:00:00Z",
  "recommendation_end_date": "2025-12-31T23:59:59Z",
  "recommendation_products": [
    "PRODUCT_ID_123",
    "PRODUCT_ID_456"
  ]
}
```

### Time Windows

Use `recommendation_start_date` and `recommendation_end_date` to **schedule** when a recommendation should be shown.

* Omit both to show the recommendation always.
* Set future dates to preload campaigns.
* Expired recommendations will automatically stop showing.

> All dates follow the ISO 8601 format (`YYYY-MM-DDTHH:MM:SSZ`) and are in UTC.

### Example: Seasonal Campaign

Let’s say you want to create a recommendation titled **“Amsterdam Winter Picks”**, showing three products from December through January.

```json
{
  "recommendation_id": "WINTER2025",
  "recommendation_title": "Amsterdam Winter Picks",
  "recommendation_description": "Cozy up with these bestsellers!",
  "recommendation_start_date": "2025-12-01T00:00:00Z",
  "recommendation_end_date": "2026-01-31T23:59:59Z",
  "recommendation_products": [
    "PRODUCT_ID_CANALTOUR",
    "PRODUCT_ID_ICEBAR",
    "PRODUCT_ID_LIGHTFESTIVAL"
  ]
}
```

***

### Use Cases

| Scenario               | Example                                        |
| ---------------------- | ---------------------------------------------- |
| **Thematic Promo**     | `"recommendation_title": "Spring Adventures"`  |
| **Flash Sale**         | `"recommendation_description": "48h only!"`    |
| **Localized Curation** | `"recommendation_title": "Top Picks in Paris"` |
| **Recurring Campaign** | Same title & products, different date ranges   |

### Best Practices

* **Localize Titles & Descriptions** for international audiences.
* **Avoid Clutter**: Limit each recommendation to 3–8 products for visual clarity.
* **Use Descriptions** to hint at urgency, value, or context (e.g., “Popular with families”).
* **Respect Date Logic**: Don’t forget to end expired campaigns.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.prioticket.com/key-concepts/additional-capabilities/recommendations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.