> 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/product-recommendation-analytics.md).

# Product Recommendation Analytics

### **💡 What’s New?**

You can now choose how Because tracks purchases for each Product Recommendation campaign. Whether you want precise attribution or a broader view of influence, we’ve got you covered.

***

### **🔍 Why This Matters**

Historically, analytics for Product Recommendation campaigns tracked **all purchases made after a campaign was viewed** — even if the shopper didn’t purchase the recommended product. This was especially helpful for A/B tests to measure engagement and general conversion lift.

Now, we’ve introduced a more **granular tracking option**:

* **Track Purchases of Recommended Product Only**

<figure><img src="/files/IOauFvksuSrjKHWFC2Q6" alt=""><figcaption><p>Product Recommendation Analytics Options</p></figcaption></figure>

This gives you clearer insight into how often the product you’re recommending actually gets purchased.

***

### **⚙️ Analytics Options**

When setting up a Product Recommendation campaign, you’ll now see an **Analytics Option toggle** in the Editor. Here’s what each option means:

#### **1. Track Purchases of Recommended Product (Default for new campaigns)**

* Tracks only the orders that include the specific product you recommended.
* Shopper must add the item to their cart via the campaign and complete the purchase.
* Revenue tracked includes **only** the recommended product.

{% hint style="info" %}
**Best for:** Precise performance tracking of the product you’re promoting
{% endhint %}

***

#### **2. Track All Subsequent Purchases After Campaign View**

* Tracks **all** purchases made after the campaign is viewed — even if the recommended product isn’t purchased.
* Offers a broader attribution model.

{% hint style="info" %}
**Best for:** Looser attribution and general influence tracking.
{% endhint %}

***

### **🕒 Default Settings**

* **New campaigns** (created after **June 12, 2025**) will default to **Track Purchases of Recommended Product Only**.
* **Existing campaigns** (created before **June 12, 2025**) will continue using the original setting: **Track All Purchases After Campaign View**.
  * These cannot be changed to preserve consistency in attribution models.

***

### **✅ How to Update Analytics Settings**

1. Open the campaign in the **Editor**.
2. Scroll to the **Analytics Options** section.
3. Select the tracking method that best fits your campaign goals.
4. **Save and publish** your changes.

***

### **💬 Need Help?**

Not sure which setting is right for your campaign?

Chat with us in-app or email [support@t](mailto:support@becauseintelligence.com)[rybecause.com](http://rybecause.com)— we’re happy 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/product-recommendation-analytics.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.