> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/data-and-insights/marketing-integrations/lightspeed.md).

# Lightspeed

Connect one or more Lightspeed eCom (C-series) shops for orders and revenue.

Connect Lightspeed eCom so AdPage reads your orders and revenue from the shop itself. Lightspeed uses an API key and secret, so this is a credential connection.

{% hint style="warning" %}
**This is Lightspeed eCom, the C-series** — the webshop platform formerly known as SEOshop. Lightspeed Retail (R-series), Restaurant (K-series) and the newer X-series are different products with different APIs and are not supported here. If your admin does not look like the eCom back office, check which product you have before creating keys.
{% endhint %}

### Before you start

You need access to the Lightspeed eCom back office with rights to create an API key.

You also need to know your **cluster** — `eu1` for European shops, `us1` for American ones. European shops are the common case and `eu1` is the default. Getting this wrong produces an authentication failure rather than a helpful message, because you are simply calling the wrong data centre.

### Create the API key in Lightspeed

{% stepper %}
{% step %}

#### Open the API settings

In the Lightspeed eCom back office, go to **Settings → API** (under Integrations in some versions) and create a new API key.
{% endstep %}

{% step %}

#### Copy the key and secret

Lightspeed shows an **API key** and an **API secret**. Copy both.
{% endstep %}
{% endstepper %}

### Connect Lightspeed in AdPage

{% stepper %}
{% step %}

#### Open the tile

Go to **Integrations**, select the container, and open the **Lightspeed** tile.
{% endstep %}

{% step %}

#### Fill in the key, secret and cluster

Paste the API key and secret, choose the cluster, and set the language if your shop is not Dutch.

Give the shop a **label** if you plan to connect more than one — it is what distinguishes them in the list afterwards.
{% endstep %}

{% step %}

#### Save

AdPage calls Lightspeed before storing anything and reads your shop details to prove the credentials work. Credentials that fail are never saved.

On success the tile shows the shop name read from Lightspeed.
{% endstep %}
{% endstepper %}

### More than one shop per container

Lightspeed is the one integration that holds **several shops in a single container**. Many Lightspeed merchants run a separate shop per country or per domain while operating one business, and reporting them as one is usually what they want.

Add each shop with its own key, secret and label. Each appears in the list with its own status, and each can be reconnected or removed without touching the others.

### What you get

Orders and revenue in **Business & Revenue**, with order revenue feeding the **Marketing Mix Model**.

Where several shops are connected to one container, their revenue is combined — which is the point of connecting them together.

### Reading the numbers

**Combined shops mean combined revenue.** If you need per-shop figures, connect each shop to its own container instead. Decide this early: changing it later means re-running history.

**Currency is not converted.** Shops in different currencies in one container produce a total that adds different units together. Split them by container.

**Order status matters.** Cancelled orders are in the same API as completed ones.

### Troubleshooting

**Authentication fails but the key looks right.** Check the cluster first. A `eu1` key called against `us1` fails exactly like a wrong key.

**"Invalid credentials".** The key or secret is wrong, or was revoked in the back office. Create a new key.

**You have an R-series or X-series account.** Those are different products — see the warning above. Contact support to discuss options.

**One shop works and another does not.** Each has its own key. Check the failing one's status in the list, and re-enter its credentials.

Still stuck? Contact <support@adpage.io> with the container, the shop label and the cluster — never the secret.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adpage.io/data-and-insights/marketing-integrations/lightspeed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.