Dilate

a tracking and tagging

Tag scout

Inspect tracking and tagging implementation across any domain — built for the Dilate team.

Static HTML scan only — detects tags present in page source. JS-injected or async-loaded tags may require browser-side inspection.

scanning page source…
Fetching via CORS proxy · analysing scripts · detecting tag IDs

Paste page source instead

Open the target site in Chrome, press ⌘U (Mac) or Ctrl+U (Windows) to view source, select all with ⌘A / Ctrl+A, copy, then paste below.


on-site

Tag summary dashboard

Platform On-site status ID / details

Google tag gateway

Cloudflare tag gateway status
Detection via page source: —

The Google Tag Gateway (GTG) routes measurement traffic through your own domain via Cloudflare, bypassing ad blockers and protecting conversion data. Validate a live GTG deployment by entering the measurement path below (e.g. /sgtm or /g).

audit

Findings and issues

raw

Detected script sources

View all external scripts found on page
our approach

Implementation recommendations

recommended track
Google tag gateway via Cloudflare
GTG
  1. 01. Confirm domain is Cloudflare-managed — Log into Cloudflare and check Overview. The target domain must appear in the domain list. If it is not listed, update the domain's nameservers at the registrar (e.g. GoDaddy) to the two Cloudflare-issued NS records. Allow time for propagation before proceeding — this can take a few hours to a few days.
  2. 02. Consolidate to a single tag source — Audit the site for both gtag.js snippets and GTM container snippets. Choose one source of truth — either all tracking via GTM, or all via direct Google Tag — and remove the other entirely. GTG accepts only one Tag ID and cannot de-duplicate events fired by two separate tagging systems.
  3. 03. Initiate the gateway from Google's side — In GTM go to Admin → Google Tag Gateway and click Continue. Alternatively use Google Ads → Tools → Data Manager → Google Tag → Manage → Admin. When prompted to choose a CDN, select Cloudflare and authenticate with the Cloudflare account.
  4. 04. Configure in Cloudflare — Navigate to Domains and Performance → Web Pack Management → Gateway. Select the target domain and toggle the gateway On. Fill in three fields: (1) Tag ID — enter the GTM container ID (GTM-XXXXXXX) if using GTM, or the Google Ads/Analytics ID if using direct gtag — one ID only; (2) Measurement Path — use a readable name such as metric or analytics, not a random string, and ensure it does not conflict with any existing page; (3) Set Up Tag — turn ON to let Cloudflare automatically rewrite tag URLs at the edge. Click Save.
  5. 05. Remove legacy scripts from source code — Find and remove every <script> block referencing googletagmanager.com (both gtm.js and gtag/js variants). Deploy the change. After deployment, only the Cloudflare-injected gateway script — which uses your own domain — should remain in the source.
  6. 06. Validate — healthy endpoint — Navigate to https://yourdomain.com/[measurement-path]/healthy. A blank page returning exactly OK confirms the gateway is live. An error response indicates a misconfigured Tag ID or measurement path. Use the checker above.
  7. 07. Validate — Tag Assistant — Open tagassistant.google.com, add the domain, and trigger tracked events on the live site. In the History view, confirm a Cloudflare icon appears against recorded events and that destination URLs use your own domain rather than googletagmanager.com. A small number of direct-to-Google ping requests is normal — the majority of hits should route through your own domain.
baseline track
Standard GTM setup
Baseline
  1. 01. Install GTM container — Add the GTM snippet to <head> and <body> of every page. Use one container per domain — avoid multiple containers.
  2. 02. CMP and Consent Mode V2 — Install a CMP (CookieBot, OneTrust, or CookieYes) and configure Google Consent Mode V2 in GTM. Required for EU compliance and modelled conversions.
  3. 03. GA4 tag via GTM — Set up a GA4 Configuration tag using the measurement ID (G-XXXXXXXXXX). Enable Enhanced Measurement. Configure key conversion events.
  4. 04. Google Ads conversion tracking — Add a Google Ads Conversion Tracking tag in GTM using the AW-XXXXXXXXX/conversion_label format. Match triggers to actual conversion actions.
  5. 05. Meta Pixel via GTM — Add Meta Pixel tag using the pixel ID. Fire PageView and key events (Lead, Purchase). Implement CAPI (Conversions API) server-side for deduplication.
  6. 06. Additional platforms — Add LinkedIn Insight Tag, TikTok Pixel, Microsoft UET via GTM as needed. All in one container, all governed by consent triggers.
  7. 07. Validate in GTM Preview — Use GTM's Preview and Debug mode to confirm all tags fire on the correct triggers. Cross-check in each ad platform's conversion dashboard.

Tag scout · Dilate · Internal tool · Static HTML scan only