> For the complete documentation index, see [llms.txt](https://because.gitbook.io/because/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://because.gitbook.io/because/the-because-platform/openapi/product-recommendation.md).

# Product Recommendation

With Because Product Recommendations, you can show *relevant, personalized suggestions* based on real customer data, not static rules.

These aren’t just recommendations—they’re revenue opportunities powered by your Klaviyo and Shopify data.

<figure><img src="/files/Mk1ghVLFx4ot9W6dDcvm" alt="" width="563"><figcaption><p>Because Product Recommendation</p></figcaption></figure>

***

## **Why They Work**

* **Behavior-Based Targeting**

  Unlike Shopify’s native “You May Also Like” feature, Because lets you trigger product suggestions based on *who* the shopper is and *how* they’re shopping. Recommend bundles, upsells, or complementary products based on cart contents, location, lifecycle stage, purchase history and more.

<figure><img src="/files/4aU6H2nqhO0NBZb9smS1" alt="" width="563"><figcaption><p>Because Product Recommendation for Replenishment Flow</p></figcaption></figure>

* **Easy to Set Up, Easy to Scale**

  No developers needed. Just choose your targeting rules, select your products, and Because handles the rest.

***

## **Where Can I Use Them?**

Product Recommendations work beautifully across:

* Product pages – Suggest complementary or higher-value items.
* Cart pages – Boost AOV with targeted cross-sells.

<figure><img src="/files/B90Ko0rK8mdvyxgqhxhv" alt=""><figcaption><p>Because PDP Product Recommendation Campaign</p></figcaption></figure>

***

## **Use Cases You’ll Love**

* “Complete the look” bundles based on the current product
* Seasonal suggestions based on location or weather
* Subscription upsells (“Add this to your next order”)
* Returning shopper recs based on past behavior
* Replenishment reminders (“Time to restock your favorite face serum?”)
* Restock alerts for high-demand items (“Back in stock: Your saved pick is available again!”)

<figure><img src="/files/7bfBDASyMhntPSbl4GdP" alt=""><figcaption><p>Glorious Gaming Case Study</p></figcaption></figure>

***

## [Analytics for Product Recommendation Campaigns](/because/the-because-platform/openapi/product-recommendation/product-recommendation-analytics.md)

To provide more precise insights into your Product Recommendation campaigns, we’ve introduced enhanced analytics options. These options allow you to tailor your tracking based on specific campaign goals.

### Tracking Options

When setting up a Product Recommendation campaign, you can choose between two tracking methods:

#### **1. Track Purchases of Recommended Product Only**

* This method tracks only the purchases of the specific product recommended in the campaign.
* **How it works:** A purchase is attributed to the campaign only if the **recommended product** is added to the cart and purchased.
* **Revenue Attribution:** Only the revenue from the recommended product is included in the campaign analytics.
* **Best for:** Assessing the direct impact of a specific product recommendation.

#### **2. Track All Orders After Campaign View**

* This method tracks all purchases made after the campaign is viewed, regardless of the products purchased.
* **How it works:** Any subsequent purchases after viewing the campaign are attributed, even if the recommended product isn’t purchased.
* **Revenue Attribution:** Includes the total revenue from all products purchased after the campaign view.
* **Best for:** Understanding the broader influence of the campaign on purchasing behavior.

### How to Select Your Tracking Method

In the Because campaign editor:

1. Navigate to your Product Recommendation campaign settings.
2. Locate the “Analytics Tracking” section.
3. Select your preferred tracking option.

{% hint style="info" %}
Note: The toggle is only available for campaigns created on or after May 19, 2025.
{% endhint %}

### **Understanding the Impact**

Choosing the appropriate tracking method is crucial for accurate analytics:

* **Granular Insights:** “Track Purchases of Recommended Product Only” provides a focused view of a specific product’s performance.
* **Holistic View:** “Track All Orders After Campaign View” offers a broader perspective on how the campaign influences overall purchasing behavior.

By selecting the tracking method that aligns with your campaign objectives, you can gain more meaningful insights and make informed decisions to optimize your marketing strategies.

***

## Ready to Try It?

In the Because campaign editor, select “Product Recommendation” as your content type, then select your page type. From there, you’ll choose your product, adjust messaging and styling, and set your targeting rules.

If you have any questions about product recommendation campaigns or need assistance, don’t hesitate to contact our support team at [**support@trybecause.com**](mailto:support@trybecause.com). We’re here to help!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://because.gitbook.io/because/the-because-platform/openapi/product-recommendation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
