> For the complete documentation index, see [llms.txt](https://docs.getuntitled.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getuntitled.ai/audience-studio/creating-an-ideal-customer-profile-icp-with-your-shopify-store-data-and-untitled.md).

# Creating an Ideal Customer Profile (ICP) with your Shopify store data and Untitled

Using machine learning, Untitled can find you the website visitors who look most like your best customers, and build you an audience of website who are most likely to become your high value customers.

## Prerequisites

1. You must already have your Shopify store linked to Untitled as a Source. [Click here for the guide to do that.](https://docs.getuntitled.ai/integrations/sources/shopify.md)
2. Your Shopify store should have a minimum of 100 customers over its lifespan before training an ICP model. The more data, the better, but the model will fail to train if the store has below 100 customers.

## Video Walkthrough

{% embed url="<https://youtu.be/dsON9LPy8XY>" %}

Step-by-step text and screenshot walkthrough coming soon! Have extra questions or prefer to walk through this with someone on a video call? Email <support@getuntitled.ai> .&#x20;


---

# 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.getuntitled.ai/audience-studio/creating-an-ideal-customer-profile-icp-with-your-shopify-store-data-and-untitled.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.
