> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/product-finders/launch-your-first-product-advisor.md).

# Launch Your First Product Finder

Get your Product Finder live with these quick and essential steps. Make sure your technical setup is complete before diving in.

{% stepper %}
{% step %}

#### Connect Your Data Feed

Make sure your [product feed is integrated](/how-to-guides/product-data/setting-up-a-product-feed.md) so the Product Finder has the latest product information to work with.
{% endstep %}

{% step %}

#### Generate a Finder for Your Category

Use our AI-powered in app tool to create a Finder—just enter your product category, and we’ll do the rest.
{% endstep %}

{% step %}

#### Customize Content & Styling

Adjust the look and feel to match your brand and provide a seamless experience.
{% endstep %}

{% step %}

#### Set Up Filtering, Ranking & Benefits

Link your product data to fine-tune recommendations, add benefits to highlight why a product is a great fit for your user.
{% endstep %}

{% step %}

#### Generate Translations

Easily generate translations with AI so your Finder works in all your key markets.
{% endstep %}

{% step %}

#### Activate & Place Your Finder

Decide where users can access the Finder on your site for maximum impact.
{% endstep %}

{% step %}

### Publish & Go Live

You’re ready! Launch your Product Finder and start helping customers find the perfect products. 🚀
{% endstep %}
{% endstepper %}


---

# 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.crobox.com/how-to-guides/product-finders/launch-your-first-product-advisor.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.