> 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/integrations-websites/lightspeed/lightspeed-c-series-their-new-checkout.md).

# Lightspeed C-series: their new checkout

Lightspeed's new checkout runs entirely inside a cross-origin iframe.

Lightspeed's new checkout runs entirely inside a cross-origin iframe. Because of browser security rules, nothing inside that iframe can be read or tracked from your website, so server-side tagging cannot measure the checkout.

In practice this means `begin_checkout`, `add_shipping_info` and `add_payment_info` cannot be measured at all, and `purchase` only server-side via Lightspeed webhooks (without client ID and session ID, so attribution is less accurate). Custom scripts and dataLayer customisation aren't possible either.

We've raised this issue with Lightspeed. There's currently no planned solution comparable to Shopify's Customer Events API, and no workaround on our side: the restriction comes from the browser, not from our implementation.

### What we recommend

Use Lightspeed's regular checkout. It supports the full AdPage DataLayer, all ecommerce events, and server-side tagging. To switch back: log in to your Lightspeed eCom back office, go to **Settings → Checkout**, disable **Use new checkout**, and save.

We're monitoring this and will update the article if Lightspeed changes anything.


---

# 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/integrations-websites/lightspeed/lightspeed-c-series-their-new-checkout.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.
