> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/setup-wizard-connection.md).

# Setup wizard: connection

In the first part of the setup wizard you connect your shop to InsightSearch and create one installation per environment.

In the first part of the setup wizard you connect your shop to InsightSearch. To do so, you create a separate InsightSearch installation for this shop. After a fresh installation, go through this part once completely; then you continue with the product data.

## Where to find the wizard

Open **Content → InsightSearch**. As long as the setup is not finished, the setup wizard with the title "Initial setup" appears instead of the normal dashboard. The plugin's sidebar is hidden during this time.

At the very top there is a note: if you like, InsightSearch handles the initial setup for a one-time setup fee (contact via the Shopware ticket system). Next to it, "Open documentation" leads to this documentation.

## The five steps at a glance

At the top of the wizard you see a timeline with five steps. This page covers the first three; steps 4 and 5 are described in [Setup wizard: product feed](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/setup-wizard-product-feed.md).

| No. | Step               | What happens                          |
| --- | ------------------ | ------------------------------------- |
| 1   | "Connection type"  | You start a new installation.         |
| 2   | "Connect"          | You enter shop name, usage and email. |
| 3   | "Validation"       | The wizard checks the connection.     |
| 4   | "Connect products" | You set up the product feed or push.  |
| 5   | "Index products"   | InsightSearch reads in your products. |

## Step by step

{% stepper %}
{% step %}

### Step 1: "Connection type"

The wizard explains that you create a separate InsightSearch installation for each environment (Prod, Staging or DEV). This keeps the recommendations and data of the environments separate.

Click **"Create new installation"**.
{% endstep %}

{% step %}

### Step 2: "Connect"

Fill in the three required fields:

| Field                    | Meaning                                                                                                        | Default       |
| ------------------------ | -------------------------------------------------------------------------------------------------------------- | ------------- |
| "Shop name"              | A name to recognise the installation, for example "Main shop production", "Staging shop" or "DEV environment". | empty         |
| "Usage (dev/stage/live)" | What this installation is used for: "Development", "Staging" or "Production".                                  | "Development" |
| "Email"                  | Address for notifications about critical problems with the recommendations.                                    | empty         |

{% hint style="warning" %}
The "Usage" field starts with "Development". If you set up the plugin in your live shop, deliberately choose "Production" here.
{% endhint %}

InsightSearch uses the email address only to inform you about critical problems. You can later change in the InsightSearch settings whether and to which address these notifications are sent.

The **"Continue"** button becomes active as soon as all three fields are filled. "Back" returns you to step 1.
{% endstep %}

{% step %}

### Step 3: "Validation"

The wizard shows "We're briefly checking the connection. This will only take a moment." and a loading indicator. If the connection works, it automatically continues with step 4 "Connect products".
{% endstep %}
{% endstepper %}

## If the wizard is locked: installation not registered

During installation, the plugin registers with InsightSearch and receives an installation key. If this key is missing (for example because the shop had no connection during installation), the wizard only shows this warning:

> "This plugin installation is not fully registered with InsightSearch yet. As long as the installation secret is missing, the setup wizard stays locked. Please retry the registration."

What to do:

1. Click **"Retry installation"**.
2. If it works, "The installation was registered successfully." appears and the wizard starts.
3. If "The installation could not be registered." appears, check whether your shop server is allowed to connect to the internet (firewall, proxy). If that does not help, contact support.

## If the shop was connected before

A copy of a shop that is already connected (for example a stage built from the live database) carries the same identifying features as the original. If InsightSearch refuses the registration for that reason, the Administration tells you. In that case, allow the re-registration in your InsightSearch account under installations and try again.

## Credentials in the plugin configuration

The wizard stores the credentials itself. They are in the plugin configuration in the card "Global configuration" as "Account Secret" and "Installation Secret". Only change these fields if support asks you to.

With "Test connection" at the top of the plugin configuration you can check at any time whether the connection works. The answer is "Connection successful" or "Connection failed".

{% hint style="info" %}
The connection is done when the wizard shows step 4 "Connect products". Continue with [Setup wizard: product feed](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/setup-wizard-product-feed.md).
{% endhint %}

## Read more

{% content-ref url="/pages/CfBdonqbr8uY5kTUtqq2" %}
[Setup wizard: product feed](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/setup-wizard-product-feed.md)
{% endcontent-ref %}

{% content-ref url="/pages/cBKy95w4S0o2CevRDTsz" %}
[Installation](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/installation.md)
{% endcontent-ref %}

{% content-ref url="/pages/R4ryPjO5ox01iI39KIJG" %}
[Troubleshooting and FAQ](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/troubleshooting-and-faq.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.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/setup-wizard-connection.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.
