> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wisepim.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Content impact

> See how a product sold before and after a change you published went live, next to the credits the project used. What changed, not what caused it.

You rewrote a description, published it, and want to know whether it did anything. Content impact answers that with the only evidence it has: the product's orders in the days before the change went live, and the days after. It does not claim the change caused the difference, and it says so on the page.

**What this page enables:** you check the sales of a product around a verified publication, compare several changes at once, and see the credits the project used in the same period, all without reading an attribution model into the numbers.

**Where to find it:** open **Analytics**, expand the **Catalog** group in the sidebar and click **Content impact**.

> [!NOTE]
>
> The **Traffic & SEO** group has an item with almost the same name, **Content Impact**. That one is the GA4-based [Enrichment Impact](https://docs.wisepim.com/en/analytics/enrichment-impact.md) report, which compares views, carts and sales from Google Analytics. This page uses your imported orders.

![WISEPIM Content impact page comparing a product's sales before and after a published change](https://mintcdn.com/swiftsyncai/MllHzI8wlqBZvkUg/images/marketing-screenshots/analytics/order-evidence-outcomes-light-branded.webp?fit=max\&auto=format\&n=MllHzI8wlqBZvkUg\&q=85\&s=daa687a09bbd6192ebd8223bb3f9f429)

> [!NOTE]
>
> A change only counts once WISEPIM has seen it live in the store, in a specific language. That evidence comes from [Listing history](https://docs.wisepim.com/en/analytics/listing-history.md). The product also needs to be linked to its order lines; see [Unmatched products](https://docs.wisepim.com/en/analytics/unmatched-products.md) if it is not.

## Changes we're watching

The top of the page lists the product changes WISEPIM is following under **Changes we're watching**. Each card shows the product and store, a status, and two comparisons: the product's own sales before and after (**This product**) and the store's sales over the same days (**Whole store**), so you can tell a product effect from a store-wide swing.

| Status | Meaning |
| - | - |
| **Maturing · N of N days** | The after-window is still running. WISEPIM follows a published change for 28 days |
| **Ready** | Both windows are complete and the comparison can be read |
| **Too few orders to tell** | The product did not sell enough in either window to say anything |

If nothing is listed yet, the page explains: when you publish a product from WISEPIM, it follows the product's orders for 28 days and reports back here.

## Compare one change

Open **Advanced** to compare a specific change yourself.

**1. Describe the change**

Fill in the **Product ID**, the **Store (store key)**, the **Currency**, the **Version** of the product and the **Language** it was published in. The store key is the platform and store number, such as `shopify:12`; you find it in the store tooltip on any order page.

**2. Pick the window**

Set **Days before and after (7, 14, 28, 56 or 90)**. 28 is the recommended value because it smooths weekly cycles.

**3. Compare**

Click **Compare before and after**. The result shows **Before**, **After**, **Difference** and **Change (%)**, plus the exact dates of both windows. The day the change went live is left out of both.

When WISEPIM cannot give a result, it tells you why instead of showing a zero:

| Reason | What it means |
| - | - |
| **We haven't seen this version live in this language.** | Listing history has no observation of this version, so there is no "after" to compare |
| **The days after the change aren't over yet.** | Wait for the window to close |
| **Another change to this product falls in the same period.** | Two changes overlap, so neither can be read on its own |
| **Too few similar, unchanged products to compare with.** | There is no comparison group of similar products in the store |
| **This product isn't linked to its orders yet.** | Link it under [Unmatched products](https://docs.wisepim.com/en/analytics/unmatched-products.md) first |
| **Our order history for these days isn't confirmed, so we don't assume zero sales.** | A gap in the imported history falls inside a window |
| **We can't confirm that stock and price stayed the same in this period.** | A stock-out or price change would explain the difference on its own |
| **The change went live outside the dates you picked.** | Widen the date range in the scope bar |

> [!WARNING]
>
> This shows what changed, not what caused it. Price, stock and other changes can explain the difference. Treat a positive result as a reason to look closer, not as proof that the new content did it.

## Compare several changes

**Compare several changes** adds up the differences of up to 20 product changes. The periods must not overlap for the same product, store and currency. Add each change with **Add change**, then click **Compare selected changes**.

The result shows the **Total difference**, marked **Known so far** when some changes could not be read, and the line **N changes with an unknown result**. Losses are added up as well as gains, so the total is not a best case.

## Credits used in this project

The **Credits used in this project** card shows every credit used and refunded in the project between the selected dates, including failed tasks: **Credits used**, **Credits refunded** and **Net credits**, with a row per task and a **Not linked to a task** row for the rest.

> [!NOTE]
>
> Credits aren't split per product or turned into money, and credits aren't converted to money, so WISEPIM does not show a return on spend. If you want a cost-per-change figure, you have to decide yourself which tasks belong to which product.

## Act on what you find

> **A change reads Ready and the product is up while the whole store is flat**
>
> That is the pattern worth acting on. Open the product, note what changed in the version you published, and apply the same approach to similar products with an [enrichment run](https://docs.wisepim.com/en/essentials/enriching-products.md). Then watch them here once they are seen live.

> **The product is up, but so is the whole store**
>
> Read it as a store-wide swing, a promotion or the season. The change may still have helped, but this page cannot separate it. Check [Orders](https://docs.wisepim.com/en/analytics/orders.md) for what moved in the same period.

> **Every comparison says the version was not seen live**
>
> The export was accepted, but WISEPIM never observed the content in the store in that language. Open [Listing history](https://docs.wisepim.com/en/analytics/listing-history.md) for the product: if the latest event is **Accepted, not seen live yet**, check that the channel actually published it.

> **You want to know what the enrichment cost per product**
>
> The credits card gives project totals only. Open the [Process Tracker](https://docs.wisepim.com/en/other-features/process-tracker.md) to see which tasks ran on which products, then attribute the credits yourself.

## Related

> **[Listing history](https://docs.wisepim.com/en/analytics/listing-history.md)**
>
> The export and seen-live events that decide when a change counts.

> **[Enrichment Impact](https://docs.wisepim.com/en/analytics/enrichment-impact.md)**
>
> The GA4-based view of the same question, using views, carts and sales.

> **[Orders](https://docs.wisepim.com/en/analytics/orders.md)**
>
> Recent sales changes by store and product, for context around a change.

> **[How Order Numbers Work](https://docs.wisepim.com/en/analytics/how-order-numbers-work.md)**
>
> Complete days, trust marks and why unknown is never shown as zero.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.