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

# Commerce

The Commerce add-on tracks Umbraco Commerce orders per visitor and adds shopping-based segment rules for personalization.

The Commerce add-on connects Umbraco Engage to [Umbraco Commerce](https://docs.umbraco.com/umbraco-commerce). It tracks visitor orders and lets you personalize content based on shopping behavior.

## What it adds

* Order tracking per visitor. Created and completed Umbraco Commerce orders are linked to the visitor profile.
* A **Commerce** view on the visitor profile in the Engage section, showing the orders placed by that visitor.
* Two segment rules for [personalization](/umbraco-engage/marketers-and-editors/personalization/creating-a-segment.md):
  * **Commerce - has product(s) in cart**: the visitor has products in their cart right now.
  * **Commerce - existing customer**: the visitor has completed an order, ever or within a chosen number of days.
* [Cockpit](/umbraco-engage/getting-started/for-marketers-and-editors/cockpit.md) support for the Commerce segment rules.

![The Commerce view on a visitor profile, showing the visitor's orders](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-1b8abd9eaff9710c385169af1bf8dd5321818ae3%2Fengage-commerce-profile-orders.png?alt=media)

![The Commerce segment rules in the segment parameter picker](https://2164986937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fds5IoWmsX6a6ooVdYthx%2Fuploads%2Fgit-blob-5cfd6c2a1e406a31d467d516aac65e561240532e%2Fengage-commerce-segment-rules.png?alt=media)

## Prerequisites

* Umbraco Engage is [installed](/umbraco-engage/installation/installation.md) and [licensed](/umbraco-engage/installation/licensing.md).
* Umbraco Commerce is installed with a valid license.

## Install the package

Install the [Umbraco.Engage.Commerce](https://www.nuget.org/packages/Umbraco.Engage.Commerce) package via NuGet or using your preferred approach.

{% tabs %}
{% tab title="Visual Studio Package Manager" %}

```
PM> install-package Umbraco.Engage.Commerce
```

{% endtab %}

{% tab title="Console" %}

```console
dotnet add package Umbraco.Engage.Commerce
```

{% endtab %}
{% endtabs %}

Build or restart your website afterwards.

## Next steps

{% content-ref url="/pages/qzVFgsasq4wuFdDBUQL7" %}
[Creating a Segment](/umbraco-engage/marketers-and-editors/personalization/creating-a-segment.md)
{% endcontent-ref %}

{% content-ref url="/pages/g4FIOHhc51PJR8V87Oqk" %}
[Profile detail](/umbraco-engage/marketers-and-editors/profiling/profile-detail.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-engage/add-ons/commerce.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.