---
title: "Basic Implementation"
slug: "gtm-basic-implementation"
updated: 2026-07-07T09:59:32Z
published: 2026-07-07T09:59:32Z
canonical: "docs.mapp.com/gtm-basic-implementation"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Basic Implementation

This guide explains how to implement Mapp Intelligence via Google Tag Manager (GTM) using the official Mapp Cloud Tracking Template.

The setup uses a Web container and consists of two steps:

1. Add the GTM Template to define tracking behavior
2. Configure your data mapping in the Template UI

---

## Implementation

### A) Add the Mapp Intelligence Configuration as GTM Template

Use this tag to define basic tracking settings, such as:

- In which Mapp account(s) the data should be tracked
- How pages should be named
- Whether automatic link tracking is enabled

**Steps:**

1. In your GTM container, go to *Tags > New* > *Tag Configuration*
2. Click **Discover more tag types in the Community Template Gallery** ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/51775331-b19b-4ed4-adce-930c1fdfd95e.png)
3. Search for the **Mapp Cloud Tracking** tag
4. Click **Choose as Template** to add it to your container
5. In the template settings, enable **Load Smart Pixel from Mapp CDN**
6. Name the tag (e.g., Mapp Intelligence Tracking Configuration)
7. Save the tag:
  - without a trigger (if you want to activate it later), or
  - with a trigger of your choice (e.g., *All Pages*)

### B) Configure and Map Data in the Template

**Steps:**

1. Open the saved tracking tag in GTM and click **Edit**.
2. Set **Request Type** to Page

This defines the type of interaction the tag tracks.
  - Use **Page** to track full page loads (recommended for most websites).
  - Use **Event** only for tracking user actions that don’t trigger a page reload (e.g., in SPAs).

[Learn more about request types and their supported parameters](/v1/docs/request-type-page-and-event)
3. Provide the following information:

| **Setting** | **Description** |
| --- | --- |
| Track ID(s) | Unique identifier(s) for your Mapp Intelligence account. Use comma-separated values for multiple accounts. |
| Track Domain | Provided by your account manager. This is the domain where tracking data is sent. |
| Manual exclusion of referrers | By default, the domain from which tracking is executed is not counted as a referrer. Use this setting to override that behavior and define additional domains to exclude from referrer and campaign analyses. Enter a comma-separated list of domains and subdomains (without http/https). You can use wildcards (*) to include subdomains. Example: example.com, *.paymentprovider.com. |
4. Optional but recommended settings:

> [!NOTE]
> Note on Supported Input
> 
> Mapp Intelligence supports UTF-8. Each parameter should not exceed 255 characters.
> 
> The system trims inputs automatically and may filter unsupported characters. Avoid unnecessary whitespace or special characters.
  1. Enable Automatic **Link Tracking**

Tracks clicks on all HTML links using the default link type “Link”.
  2. Enable **Page Naming**

The system will use the page URL as the default page name.
  3. Add **Page Categorization** using Content Groups (optional but recommended):
    - Go to the Page section in the template
    - Enter the ID of the content group
    - Set the value based on your GTM configuration
    - Learn more about content groups in this [How-To](/v1/docs/build-content-groups-to-dissect-the-usage-of-the-website). ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/78625e30-0069-4a69-8890-2d61668e36ff.png)

---

## Testing your GTM Implementation

After configuring tracking in Google Tag Manager, it’s essential to verify that the setup works as intended – both technically and analytically.

We recommend a three-step approach:

### 1. Check outgoing tracking requests (via Mapp Cloud Debugger)

Use the [Mapp Cloud Debugger](/v1/docs/mapp-cloud-debugger) browser extension to check which tracking requests are sent from your website. This step helps you confirm that:

- Tracking requests are fired as expected
- The correct Track ID is used
- Key parameters such as page name, campaign data, or content groups are included
- Optional extensions (e.g., link tracking) are configured properly

---

### 2. Check incoming data (in Mapp Intelligence)

Once the tracking requests are confirmed, check whether the data actually appears in Mapp Intelligence. This ensures that:

- Data is being received by the correct account
- Values are mapped correctly in the user interface
- No filtering or configuration issues prevent data from being displayed

You can start with basic reports such as:

- *Visitors > Traffic*
- *Navigation > Pages*
- *Navigation > Events*

> [!NOTE]
> Note
> 
> Data in standard Mapp Intelligence reports is updated hourly. You may need to wait up to 60 minutes to see newly tracked data.

---

### 3. Explore deeper testing and validation options

For more advanced validation, Mapp provides additional tools and strategies to assess data quality and implementation accuracy. These include:

- verifying content group assignments
- checking event accuracy and scope
- analyzing session behavior and entry pages
- filtering test traffic by device ID, order ID, or campaign

For a detailed walkthrough of these options, refer to [Mapp Cloud Debugger](/v1/docs/mapp-cloud-debugger)

---

> [!NOTE]
> Optional: Using Extensions
> 
> If you want to extend your tracking setup with features like Teaser Tracking or Scroll Depth, refer to the separate [GTM Extensions guide](/v1/docs/gtm-extensions). These extensions build on the configuration you implemented here.

Track IDs are used to assign requests to an account. You find the track ID under *Mapp Q3 >**Configuration > System Configuration > Data Collection.* If the same information is to be recorded for multiple accounts, you can enter the corresponding Track IDs of the accounts comma-separated.

Specify your Mapp Intelligence track domain. This information is provided by your account manager.

Content groups categorize pages for simplified, higher-level analysis and reporting. Each page can be assigned exactly one unique value per content group, such as language or main menu category. Content group assignments can also be imported retroactively. For more information, see Build content groups to dissect the usage of the website.