> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/general-settings-app-+-vp-1/registration-and-pre-event-page-settings/using-tracking-scripts-gtm-ga-and-pixels-in-lets-get-digital.md).

# Using Tracking Scripts (GTM, GA & Pixels) in Let’s Get Digital

## Overview

Let’s Get Digital allows you to add tracking scripts such as Google Tag Manager, Google Analytics, and other marketing pixels to your event's registration form.

The registration form uses step-based URLs and a dedicated completion URL, enabling accurate funnel and conversion tracking.

This article explains:

* Where to add tracking code
* How registration form URLs behave

***

### 1. Adding a Tracking Pixel

Tracking scripts can be added in the event settings.

**Location in admin panel:**

<kbd>Settings</kbd> → <kbd>General Settings</kbd> → <kbd>Registration & Pre-Event Page</kbd>

Use the field:

> **“Analytics scripts - For example Google Tag Manager”**

Paste your full tracking snippet here (for example, your Google Tag Manager container code).

After saving and publishing, the script will be loaded on the registration form.

Supported integrations include::

* Google Tag Manager
* Google Analytics
* Facebook Pixel
* Other custom tracking scripts

***

### 2. Registration Form URL Behaviour

The registration form updates the URL as visitors move through the steps.

Example:

```
{registration-url}
{registration-url}/step_2
{registration-url}/step_3
```

When the registration is successfully completed, the user is redirected to:

```
{registration-url}/registered
```

This allows you to measure:

* Funnel progression (step 1 → step 2 → step 3)
* Drop-off between steps
* Completed registrations (conversion tracking)

***

### 3. Responsibility for Configuration

LGD provides the ability to load tracking scripts and exposes step-based URLs for measurement.

Configuration of tracking goals, triggers, and analytics logic is the responsibility of your marketing or analytics team.


---

# 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://knowledge-base.letsgetdigital.com/the-admin-panel/settings/general-settings-app-+-vp-1/registration-and-pre-event-page-settings/using-tracking-scripts-gtm-ga-and-pixels-in-lets-get-digital.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.