> 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.md).

# Lightspeed

How to set up server-side tagging for a Lightspeed webshop

***

## Setting up server-side tagging for Lightspeed

This article walks you through the full setup of server-side tagging on a Lightspeed store: generating your Google Tag Manager templates, importing them, filling in your IDs, testing them, and finally removing the old tracking connections within the Lightspeed webshop.

### Before you start

This article picks up where **Getting Started** leaves off. Make sure all of the steps in the [Setup AdPage container](/getting-started/setup-adpage-container.md) article have been followed. Which means that:

* [ ] Your **AdPage container** is created.
* [ ] Your AdPage container is **connected to your GTM server container**.
* [ ] The **CNAME record** is added in your DNS settings, so tagging runs on your own (sub)domain.
* [ ] The **AdPage dataLayer scripts** are installed in your store.

{% hint style="warning" %}
If one of these steps is still open, finish it first. Everything below assumes your server container is reachable on your own domain and that the AdPage dataLayer is present on the webshop's frontend.
{% endhint %}

***

### Step 1: Generate your templates in the Template Library

You do not have to build your tags, triggers and variables by hand. AdPage's Template Library generates a complete, tested Google Tag Manager setup for Lightspeed for you.

1. Go to [data.adpage.io/template-library](https://data.adpage.io/template-library).
2. Select the marketing platforms you want to send data to, for example Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads or Pinterest Ads.
3. Select the Consent Management Platform you use on your Lightspeed webshop.
4. Generate the templates. You get **two JSON files**: one for your GTM **web** container and one for your GTM **server** container.
5. Download both files and keep them handy.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2Fo4nPmZrjh5NFMGAYOnPp%2Fimage.png?alt=media&amp;token=a8b98f2d-df97-4c6a-9a20-c91350247029" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Only select the platforms you actually use. Every platform you add creates extra tags and constant variables that you will need to fill in later.
{% endhint %}

***

### Step 2: Import the web container template

1. Open your **GTM web container**.
2. Go to **Admin** and click **Import Container**.
3. Select the **web** JSON file you downloaded.
4. Choose a workspace.&#x20;
   * If you have unpublished changes in your default workspace, we recommend importing into a **new workspace** so your import stays separate from any other work in progress.
5. Choose the import option:
   * **Merge and rename conflicting tags, triggers and variables** for a container that already contains a setup. Nothing existing gets removed.
   * **Overwrite** only for a brand new, empty container.
6. Check the preview of the changes that GTM shows you, then click **Confirm**.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2F3CKvxX1mSb1O2JBpcE4Q%2Fimage.png?alt=media&amp;token=ee12042d-41d9-4406-95f9-9e2eaf8d3bc1" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
Do not publish your GTM web container yet. The tags in the import are still missing your IDs, which you fill in at step 4.
{% endhint %}

***

### Step 3: Import the server container template

Repeat the same steps in your **GTM server container** with the **server** JSON file.

1. Open your **GTM server container**.
2. Go to **Admin** and click **Import Container**.
3. Select the **server** JSON file.
4. Import into a new workspace and choose **Merge and rename conflicting tags, triggers and variables**.
5. Check the preview and click **Confirm**.
6. Go to **Clients** and check if an extra GA4 client has been set up. If so, delete the imported GA4 client.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2FyhuHijhZUYGKSi2cG86j%2Fimage.png?alt=media&amp;token=fbe37ee9-0cec-4291-8c7d-b9f5569cb1d6" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
Do not publish your GTM server container yet. The tags in the import are still missing your IDs and tokens, which you fill in at step 4.
{% endhint %}

***

### Step 4: Fill in the constant variables

Both templates are built around **constant variables**. All IDs, tokens and settings live in one place, so you never have to open individual tags to change something.

1. In your GTM web container, go to **Variables**.
2. Open every constant variable, which you can recognize by the "@" in the name. Fill in the correct value per variable. See the table below to know what ID or Token you have to fill in.
3. Save each variable.
4. In your GTM server container, go to **Variables**.
5. Open every constant variable, which you can recognize by the "@" in the name. Fill in the correct value per variable. See the table below to know what ID or Token you have to fill in.
6. Save each variable.

Depending on the platforms you selected, you will typically fill in:

<table><thead><tr><th width="118">Container</th><th width="240">Variable</th><th>Value</th></tr></thead><tbody><tr><td>Web</td><td>Server Container URL</td><td>The tagging domain from your CNAME record, for example: <code>https://tagging.domain.com</code></td></tr><tr><td>Web</td><td>GA4 Measurement ID</td><td>Your GA4 property's Measurement ID: <br><code>G-XXXXXXXXXX</code></td></tr><tr><td>Web</td><td><a href="/integrations-marketingtools/meta-ads/where-to-find-the-meta-pixel-id-and-the-meta-api-token.md">Meta Pixel ID</a></td><td>Your Pixel ID from Meta Events Manager</td></tr><tr><td>Web</td><td><a href="/integrations-marketingtools/tiktok-ads/where-to-find-the-tiktok-pixel-id-and-the-tiktok-api-token.md">TikTok Pixel ID</a></td><td>Your Pixel ID from TikTok Events Manager</td></tr><tr><td>Web</td><td><a href="/integrations-marketingtools/pinterest-ads/where-to-find-the-pinterest-tag-id-advertiser-id-and-api-token.md">Pinterest Tag ID</a></td><td>Your Pinterest Tag ID, found in the Tag Manager of your Pinterest Ads Account</td></tr><tr><td>Web</td><td><a href="/integrations-marketingtools/linkedin-ads/where-to-find-the-linkedin-partner-id-conversion-ids-and-api-token.md">LinkedIn Partner ID</a></td><td>Your LinkedIn Partner ID, found in the Signals Manager of your LinkedIn Ads Account</td></tr><tr><td>Web</td><td>Cookiebot Domain Group ID</td><td>The Domain Group ID from your Cookiebot account</td></tr><tr><td>Server</td><td>GA4 Measurement ID</td><td>Your GA4 property's Measurement ID: <br><code>G-XXXXXXXXXX</code></td></tr><tr><td>Server</td><td><a href="/integrations-marketingtools/meta-ads/where-to-find-the-meta-pixel-id-and-the-meta-api-token.md">Meta Pixel ID</a></td><td>Your Pixel ID from Meta Events Manager</td></tr><tr><td>Server</td><td><a href="/integrations-marketingtools/meta-ads/where-to-find-the-meta-pixel-id-and-the-meta-api-token.md">Meta API Ttoken</a></td><td>The API Token of your Pixel from Meta Events Manager</td></tr><tr><td>Server</td><td><a href="/integrations-marketingtools/tiktok-ads/where-to-find-the-tiktok-pixel-id-and-the-tiktok-api-token.md">TikTok Pixel ID</a></td><td>Your Pixel ID from TikTok Events Manager</td></tr><tr><td>Server</td><td><a href="/integrations-marketingtools/tiktok-ads/where-to-find-the-tiktok-pixel-id-and-the-tiktok-api-token.md">TikTok API Token</a></td><td>The API Token of your Pixel from TikTok Events Manager</td></tr><tr><td>Server</td><td><a href="/integrations-marketingtools/google-ads/where-to-find-the-google-ads-conversion-id-and-conversion-labels.md">Google Ads Conversion ID</a></td><td>Your Google Ads Conversion ID: <br><code>AW-XXXXXXXXXX</code> minus the <code>AW-</code> part</td></tr><tr><td>Server</td><td><a href="/integrations-marketingtools/google-ads/where-to-find-the-google-ads-conversion-id-and-conversion-labels.md">Google Ads Conversion Labels</a></td><td>Create new <code>purchase</code>, <code>add_to_cart</code>, and <code>begin_checkout</code> conversions in Google Ads. Once set up, you can find their Conversion Labels.</td></tr><tr><td>Server</td><td><a href="/integrations-marketingtools/pinterest-ads/where-to-find-the-pinterest-tag-id-advertiser-id-and-api-token.md">Pinterest Advertiser ID</a></td><td>The Advertiser ID from your Ad Account. This ID usually starts with 549.</td></tr><tr><td>Server</td><td><a href="/integrations-marketingtools/pinterest-ads/where-to-find-the-pinterest-tag-id-advertiser-id-and-api-token.md">Pinterest API Token</a></td><td>The API Token found in your Conversions API settings of your Pinterest Business Account.</td></tr><tr><td>Server</td><td><a href="/integrations-marketingtools/linkedin-ads/where-to-find-the-linkedin-partner-id-conversion-ids-and-api-token.md">LinkedIn API Token</a></td><td>The API Token which you can generate in your LinkedIn Campaign Manager in the Sources.</td></tr><tr><td>Server</td><td><a href="/integrations-marketingtools/linkedin-ads/where-to-find-the-linkedin-partner-id-conversion-ids-and-api-token.md">LinkedIn Conversion IDs</a></td><td>Create new <code>purchase</code>, <code>add_to_cart</code>, and <code>begin_checkout</code> conversions in LinkedIn Ads. Once set up, you can find their Conversion IDs in the URL of the conversion.</td></tr></tbody></table>

{% hint style="info" %}
Never leave a constant variable empty. An empty ID means tags fire without a destination, which shows up as missing conversions or failed outgoing requests later on.
{% endhint %}

***

### Step 5: Test in preview mode

You have just imported container templates with complete tracking for GA4 and the marketing platforms you selected. That means everything you need is now present in your GTM containers, and anything that was already there for the same purpose is a duplicate.

#### **Disable your old tags first**

Go through the tags in your web container and pause or delete every tag that measures something your new setup now handles. In practice this is your old GA4 configuration tag, all GA4 event tags for e-commerce steps such as `add_to_cart` and `purchase`, your Meta Pixel tags, your Google Ads remarketing tags, and any custom HTML tags that send data to a platform directly.&#x20;

If you are not sure whether you will need an old tag later, pause it instead of deleting it. You can always remove it in a later version once the new setup has proven itself. Old triggers and variables can stay, they do nothing on their own.

Skip this and preview mode will show two of everything, and after publishing your conversions will be counted twice.

#### Test both containers

1. Open the **Preview mode** in your GTM web container and fill in the URL of your webshop.
2. Open the **Preview mode** in your GTM server container as well, so you can follow the same hits arriving server-side.
3. Walk through the complete customer journey and check that each step fires once, with the right e-commerce parameters:
   * `page_view`
   * `view_item_list`
   * `view_item`
   * `add_to_cart`
   * `view_cart`
   * `remove_from_cart`
   * `begin_checkout`
   * `add_shipping_info`
   * `add_payment_info`
   * `purchase`
4. For every event, check in the **server** container that the GA4 event request arrives and that your platform tags fire and return a successful response.

***

### Step 6: Clean up and publish

Before you publish, make sure your Lightspeed shop no longer sends anything directly to the platforms that now run through your server container. Otherwise the same conversions are measured twice, once client-side from Lightspeed and once server-side from your server container, which inflates your conversion counts, breaks your ROAS calculations and feeds advertising platforms the wrong optimisation signals.

#### **Check your Web Extras**

Earlier in this setup you added the AdPage tagging pixel to your Web Extras through three separate scripts. Those scripts should not be present alongside a standard Google Tag Manager snippet, so go through your Web Extras and check whether the regular GTM code is still there. It looks like this:

```
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-XXXXXXXX');</script>
<!-- End Google Tag Manager -->
```

Remove it, including the accompanying noscript block. While you are in the Web Extras, also remove any other tracking script that is now handled server-side, such as a Meta Pixel base code, a gtag.js snippet for GA4, a TikTok pixel or a Pinterest tag.

#### **Disconnect Google Analytics and Meta Ads**

In your Lightspeed backend, go to your settings and open Web Statistics. Here you can see whether an old connection with Google Analytics or Facebook Ads is still active. Click on the platform in question and switch the connection off.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2FMNAdwwW0UVlXXbwMfCEa%2Fimage.png?alt=media&amp;token=c828dd42-7bce-4b1c-afef-0b30818a62ea" alt=""><figcaption></figcaption></figure>

#### **Publish both GTM containers**

Once your Lightspeed environment is clean, publish your web and server container. Use a version name and description you will recognise later, for example "AdPage server-side tagging", so you can roll back to the previous version if something turns out to be wrong.

Finish with a test purchase on your live shop and check in the AdPage interface whether the events arrive and the conversions are registered once. Any connection that Lightspeed still maintains directly with an advertising platform will send the same event a second time.

***

### Need help?

Still seeing missing events, duplicated conversions or unassigned traffic after following these steps? Reach out to our support team and we will take a look with you.


---

# 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.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.