---
title: "What is gtm-msr.appspot.com and How to Prevent It from Triggering Tags in GTM"
description: "Learn why gtm-msr.appspot.com appears in Google Tag Manager and how to prevent it from firing tags or polluting your analytics."
canonical_url: "https://docs.sealmetrics.com/reports/insights/gtm-msr-appspot-and-tag-blocking"
lang: "en"
date_generated: "2026-09-14T13:48:10.438Z"
source_hash: "8b4b4efff1597d5dd0f513eaa5b2cb5366219cba577f0337918f53244a3a550f"
content_type: "documentation"
owner: "docs"
llm_priority: "useful"
source_file: "reports/insights/gtm-msr-appspot-and-tag-blocking.mdx"
publisher: "Sealmetrics"
---

# What is gtm-msr.appspot.com and How to Prevent It from Triggering Tags in GTM

Canonical page: https://docs.sealmetrics.com/reports/insights/gtm-msr-appspot-and-tag-blocking

When working with Google Tag Manager (GTM), you may notice traffic coming from **gtm-msr.appspot.com**.
This domain is owned by Google and appears in very specific scenarios.

---

## What is gtm-msr.appspot.com?

This domain appears when:

- You (or your team) enter **Preview Mode** in Google Tag Manager
- Google runs **automated scans** or internal container checks
- A **browser extension** or tool triggers a render for debugging
- GTM loads your container inside an **Appspot sandbox environment**

**Warning:**
This traffic **is NOT from real users** — but it *can* cause your tags to fire, which leads to:

- Fake pageviews
- Phantom conversions
- Polluted campaign attribution
- Incorrect ROAS calculations

---

## Why This Domain Is a Problem

If tags fire when GTM loads from `gtm-msr.appspot.com`, you may experience:

- Inflated events
- Artificial conversions in Meta Ads / Google Ads / TikTok
- Incorrect GTM trigger debugging
- Polluted analytics reports

This is especially harmful for:
- Conversion tracking
- Ads optimization signals
- GTM-based event measurement

---

## How to Prevent Tags From Firing on gtm-msr.appspot.com

You can fully block this domain at the trigger level by using a simple variable.

### Step 1 — Create a blocking variable in GTM

1. Go to **Variables**
2. Click **New → Custom JavaScript Variable**
3. Name it: `IsNotGTMAppspot`
4. Use this code:

   ```js
   function() {
     return location.hostname !== "gtm-msr.appspot.com";
   }
   ```

5. Click **Save**

This variable returns `true` only when the page is **not** GTM's sandbox domain.

### Step 2 — Add the condition to all triggers

For every trigger that launches tags (pageviews, clicks, conversions, etc.):

1. Open the trigger
2. Add this condition:

   ```
   IsNotGTMAppspot  equals  true
   ```

This ensures tags fire everywhere **except** inside GTM's Appspot preview environment.

### Step 3 — Test it

1. Click **Preview** in Google Tag Manager
2. Confirm the debug URL becomes `https://gtm-msr.appspot.com/...`
3. Check the tag panel — no tags should fire

If everything looks correct:

- Publish your container
- Your tags are now protected from false firing

## Related documentation

- [Google Tag Manager Template](/integrations/google-tag-manager) — Install the Sealmetrics pixel through GTM
- [Bot Detection & Traffic Quality](/security-privacy/bot-detection) — How Sealmetrics filters non-human traffic
- [How to Track Google Ads Campaigns](/reports/insights/how-to-track-google-ads-campaigns) — Prevent inflated ad conversions
- [Sources Report](/reports/sources) — Verify campaign attribution stays clean