---
title: "Item-level attribution with persisted properties"
description: "Tie a persisted property to a specific item inside a cart event so each item keeps the search term, recommendation, or promo that drove it."
product: data
lang: en
last_updated: 2026-11-20
token_estimate: 833
---
# Item-level attribution with persisted properties

Item-level attribution typically powers merchandising analyses. It ties a persisted property to a specific item inside a cart event, rather than to the user or session as a whole.

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

This pattern builds on [Set up a persisted property](https://amplitude.com/docs/data/persisted-properties/set-up).

When a cart contains multiple items, each item keeps its own persisted context (the search term, recommendation, or promo that influenced that specific item). Metrics such as `Revenue` reflect the source that drove each item individually.

This is the configuration that powers the [Product Discovery hub](https://amplitude.com/docs/analytics/ootb-ecommerce-analytics#product-discovery) in Out-of-the-box E-commerce Analytics.

For example, a single cart contains three items, and the user discovered each one a different way:

- The user discovered Item 1 through Search.
- The user discovered Item 2 from the Popular Products display.
- The user discovered Item 3 from Recommendations.

Without item-level attribution, Amplitude credits all conversion events for the entire order to a single discovery method. With Original allocation, on-site Search receives all the credit. With Most Recent, Recommendations receives the credit.

Item-level attribution instead credits the correct discovery method to each item in the cart.

## Set up the persisted property

1. Create a new persisted property called `Most recent Finding Method`.
2. Select the event property you want to persist. For this example, use `discovery_method`.
3. Choose an **Allocation** method. Because you want the last touchpoint, select **Most Recent**.
4. To credit the first touchpoint instead, select **Original**.
5. Set the **Expiration**. By default, the persisted property expires at the end of the session.

After you create the property, configure item-level attribution.

## Configure item-level attribution

1. Select the product identifier you use. Ideally, use an item property in an `Object Array` such as `product.item_id`. For more on object arrays, refer to [Cart Analysis](https://amplitude.com/docs/analytics/charts/cart-analysis).
2. Select one or more **linking events**. These are events that carry both the persisted property value (such as `discovery_method`) and the item identifier (`product.item_id`). These are typically the events where the user interacts with an item, such as `View Item Details`, `Home Hero Clicked`, `Promotion Clicked`, `Recommendation Clicked`, or `Add to Cart`. Linking events let Amplitude tie the engagement signal to the specific item.

Amplitude then carries the persisted value forward to cart events (`Add to Cart`, `Remove from Cart`, `Purchase`) per item, using the product identifier as the join key.

## Verify the setup

After you save the property, the persisted value appears as a column on the linking and cart events. Use the [Verify a property with item-level attribution](https://amplitude.com/docs/data/persisted-properties/verify-persisted-properties#verify-a-property-with-item-level-attribution) section of the verify guide to confirm each item shows the expected value.

