> ## 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.

# Listing history

> Follow one product through its timeline: when it changed in WISEPIM, when an export was accepted, and when the content was seen live in a store.

An export that was accepted is not the same as a listing that is live. Listing history keeps the two apart. For one product, one store and one language, it shows every change saved in WISEPIM, every export the channel accepted, and every time WISEPIM saw the same content visible in the store.

**What this page enables:** you answer "is the new version actually live?" with evidence instead of assuming it from a green export, and you know which version of the content a customer could see on a given day. [Content impact](https://docs.wisepim.com/en/analytics/content-impact.md) uses these events to decide when a change counts.

**Where to find it:** open **Analytics**, expand the **Data & setup** group in the sidebar and click **Listing history**.

![WISEPIM Listing history timeline with product changes, accepted exports and seen-live events for one product](https://mintcdn.com/swiftsyncai/MllHzI8wlqBZvkUg/images/marketing-screenshots/analytics/order-evidence-publication-light-branded.webp?fit=max\&auto=format\&n=MllHzI8wlqBZvkUg\&q=85\&s=634f5d03eb5f83bc331fd5f8ccd4118a)

> [!NOTE]
>
> WISEPIM records changes from the moment tracking was turned on. A listing counts as live once WISEPIM saw the same content, in that language, visible in the store. Earlier history is not reconstructed.

## Pick a product

The page starts with a **Recently published** list, so the products you just exported are one click away. For anything else, use the picker: pick a product, one store and a language, optionally narrow to a **Version (optional)**, and click **Show listing history**.

## Read the timeline

The timeline has four columns:

| Column | What it holds |
| - | - |
| **Time (UTC)** | When the event was recorded, in UTC |
| **Event** | **Product changed**, **Export accepted** or **Seen live** |
| **Matched by** | How the event was tied to this store and language: **Seen in this store and language** for a direct observation, or **Product change linked to this store and language** for a catalog change that was later exported there |
| **Status** | What the event proves, see below |

| Status | Meaning |
| - | - |
| **Change saved** | The product was edited in WISEPIM. Nothing has left the catalog yet |
| **Accepted, not seen live yet** | The channel accepted the export. WISEPIM has not yet observed the content in the store |
| **Seen live with this version** | WISEPIM observed the store showing exactly this version of the content in this language |
| **Content seen, version not confirmed** | The store shows content for this product, but WISEPIM could not match it to a specific version |

The line **First seen live:** gives the earliest moment this version was observed. A button reading **Review N waiting or incomplete items** collects the events that are still waiting for an observation or could not be matched.

> [!NOTE]
>
> The timeline shows the latest 200 events. Earlier ones may exist. Narrow to a version to see further back for that version.

## Why the distinction matters

An export receipt proves that the channel accepted the data. It does not prove that the listing is visible, or that a shopper saw the new text. Only **Seen live with this version** does. That is why [Content impact](https://docs.wisepim.com/en/analytics/content-impact.md) starts its after-window from the seen-live event, and why a change stays **Maturing** until 28 complete days have passed since then.

## Act on what you find

> **The last event is Accepted, not seen live yet, and it has been days**
>
> The channel took the data but is not showing it, or WISEPIM has not been able to observe the page. Check the product on the storefront yourself. If the old content is still there, look at the channel's own publishing queue or cache. If the new content is there, check that the store's product URL is reachable from your sitemap, because that is how WISEPIM finds the page to observe.

> **Status says Content seen, version not confirmed**
>
> The store shows this product, but the content does not match any version WISEPIM exported, in that language. Usually something edited the listing in the store after export, or a translation was changed on the channel. Re-export from WISEPIM to bring the two back in line.

> **No listing history for a product you know you exported**
>
> Tracking starts when it was turned on, and events are kept per store and language. Make sure you picked the store and language the export went to. If the export predates tracking, there is nothing to show; the next export will be recorded.

> **You applied fixes from the Fix queue and want to confirm they reached the store**
>
> Export as usual, then open the product here. Applying a proposal only produces a **Product changed** event; the **Export accepted** and **Seen live** events follow the export.

## Related

> **[Content impact](https://docs.wisepim.com/en/analytics/content-impact.md)**
>
> Compare sales before and after a change that was seen live.

> **[Fix queue](https://docs.wisepim.com/en/analytics/fix-queue.md)**
>
> Fix the products that sell first, then follow them here.

> **[Exporting Products](https://docs.wisepim.com/en/essentials/exporting-products.md)**
>
> How exports reach your channels.

> **[Integration Health](https://docs.wisepim.com/en/analytics/integration-health.md)**
>
> Sync status per channel, under the Connections tab of Data health.


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