> For the complete documentation index, see [llms.txt](https://docs.selvette.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selvette.com/insights/attribution.md).

# Orders and attribution

Orders are reported separately from the storefront funnel because they use a different unit.

## Attributed orders

For a connected Shopify store, Selvette attributes an order when:

1. the shopper added a product from inside the try-on interface;
2. the order's cart token matches that add; and
3. the purchase occurs within seven days.

Attribution is last-touch: the most recent qualifying Selvette add for that cart receives credit.

## What the card shows

* **Attributed orders** — matching orders;
* **Attributed revenue** — revenue from those matching orders, when available; and
* **Store orders total** — all orders in the reporting scope.

Orders without a matching cart remain unattributed. They are not forced into the Selvette funnel.

Custom-site cart hooks support add-to-cart tracking, but Shopify order attribution depends on the connected Shopify order data.

Next: [Date ranges and timezones](/insights/date-ranges-and-timezones.md)


---

# 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://docs.selvette.com/insights/attribution.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.