> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/sales-insights/set-up-and-manage-sales-insights/set-up-the-customer-profile-feature.md).

# Set up the customer profile feature

{% hint style="info" %}
This feature is coming soon.
{% endhint %}

Set up the Customer profile feature by mapping the data used to generate customer profiles and opportunities.

The first time you try to open a customer profile, the **Setup customer profile** page opens automatically.

1. Select the **Product dimension** and **Product property (name)**. The property determines the product name displayed on the customer profile page.
2. (Optional) Select a **Secondary product property** to display additional information about the product.
3. (Optional) Select the **Product group dimension**, then select the **Product group property (name)**.
4. Select the **Sales rep dimension** and **Sales rep property (name)**. The property determines the sales rep name displayed on the customer profile page.
5. Select the **Quantity measure**.
6. (Optional) Select the **Margin measure**.
7. Click **Save**.
8. Review the message, then click **Save and run**.

{% hint style="info" %}
The Sales Insights run typically takes 10–120 minutes, depending on the size of your customer data. Your changes aren't reflected on the **Customer profile** page until the run completes. You can check the status in the top-right corner of the page to see whether opportunities have been generated.
{% endhint %}

You can edit the setup later. On the **Customer profile** page, click the menu button in the top-right corner and select **Edit configuration**. The **Setup customer profile** page opens.


---

# 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.phocassoftware.com/sales-insights/set-up-and-manage-sales-insights/set-up-the-customer-profile-feature.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.