Skip to main content

​
Overview

When tracking isn’t working properly, it impacts your data and decisions. This guide helps you identify and resolve common issues quickly, without needing deep technical knowledge.

​
Installation problems

​
Tag Insight isn’t showing any data

  • No events in your dashboard
  • Live Debugger is empty
  • Chrome extension says “No tracking detected”
  • Wrong project ID entered
  • Ad blockers preventing tracking
  • Tag not published yet
  • Browser security settings
1. Check your project ID
  • Find it in your Tag Insight dashboard
  • Make sure it’s just numbers (like 664, not “project_664”)
  • Ask your developer to verify it’s correct
2. Disable ad blockers
  • Turn off ad blockers temporarily
  • Add taginsight.com to your allowed list
  • Try in an incognito/private window
3. Verify tag is published
  • In GTM: Check the tag is in the published version
  • In Commander Act: Ensure container is generated
  • Ask your developer to confirm deployment
4. Try a different browser
  • Some corporate browsers have strict settings
  • Test in Chrome, Firefox, or Edge

​
Wrong project ID issues

The project ID should be numbers only (like 664), not include “project_” or any other text.
Tell your developer:
  • Use only the numeric ID
  • Don’t add prefixes or suffixes
  • Check it matches exactly what’s in Tag Insight

​
Data collection issues

​
No events showing up

  1. Visit your website
  2. Open Tag Insight Live Debugger
  3. Click around your site
  4. Events should appear within seconds
Ask your developer to check:
  • Is Tag Insight installed correctly?
  • Is it loading before other tags?
  • Are events being sent to the right place?
Common fixes:
  • Refresh the page
  • Clear browser cache
  • Check different pages
  • Try another browser

​
Missing information in events

You might see alerts like “Missing required variable” or “Incomplete event data”.
Your tracking is working but missing important details. Like submitting a form with blank fields.

​
Data quality problems

​
Wrong data types

A common issue where prices show as text instead of numbers.
1

The problem

Price shows as “$29.99” (text) instead of 29.99 (number)
2

Why it matters

  • Can’t calculate totals
  • Reports show errors
  • Averages don’t work
3

The fix

Tell your developer:
  • Remove currency symbols from numbers
  • Send prices as numeric values
  • Put currency in separate field

​
Inconsistent formats

Different formats for the same information cause confusion.
Problem: Dates like “01/15/2024” vs “2024-01-15”Solution: Pick one format and stick to it
Problem: Using ”$”, “dollars”, “USD” randomlySolution: Always use standard codes (USD, EUR, GBP)
Problem: SKU12345 vs sku-12345 vs 12345Solution: Define one format for all products

​
Alert fatigue

​
Too many unnecessary alerts

Getting bombarded with alerts that aren’t real problems.
  • Test traffic triggering alerts
  • Optional data marked as required
  • Development sites being monitored
  • Too sensitive settings

​
Chrome extension issues

​
Extension not working

  1. Check extension is installed and enabled
  2. Refresh the page
  3. Try incognito mode (with extension allowed)
  4. Update to latest version
  • Uninstall and reinstall extension
  • Check for conflicting extensions
  • Try different browser profile
  • Clear browser data

​
Performance issues

​
Site seems slower

For high-traffic sites, tracking can impact performance.
1

Symptoms

  • Pages loading slowly
  • Browser using lots of memory
  • Laggy interactions
2

Solutions

Ask your developer to:
  • Enable sampling (track portion of users)
  • Limit events on busy pages
  • Optimize high-frequency events
You can help by:
  • Identifying which events are essential
  • Removing unnecessary tracking
  • Prioritizing critical data

​
Common scenarios

​
After website updates

Tracking often breaks when your website changes. Prevention checklist:
  • Tell developers to test tracking after changes
  • Check Live Debugger after deployments
  • Review audit reports weekly
  • Set up alerts for critical events

​
During sales or campaigns

High traffic can reveal tracking issues. Be prepared:
  • Test before launching campaigns
  • Monitor during first hours
  • Have developer on standby
  • Know who to contact for help

​
Cross-browser issues

Different browsers may behave differently. Test regularly in:
  • Chrome (most common)
  • Safari (Mac/iPhone users)
  • Firefox (privacy-conscious users)
  • Edge (corporate users)

​
Getting help

​
What to tell support

When contacting support, provide:
  1. Your project ID
  2. What you expected to see
  3. What actually happened
  4. When it started
  5. What pages are affected
  6. Browser and device used

​
Quick diagnostics

Before contacting support, try:
  • Different browser
  • Different device
  • Incognito/private mode
  • Different network (mobile vs wifi)
  • Clear cache and cookies

​
Prevention tips

Regular checks

Review tracking weekly, not just when things break

Test changes

Always verify tracking after website updates

Document setup

Keep notes on your configuration

Train your team

Ensure everyone knows basics

​
Common questions

Usually due to:
  • Website updates
  • Tag manager changes
  • Browser updates
  • Security policy changes
Check when it last worked and what changed.
Some things yes:
  • Browser issues (clear cache, try another)
  • Extension problems (reinstall)
  • Alert settings (adjust in dashboard)
Technical fixes need developer help.
Depends on the issue:
  • Configuration changes: Minutes
  • Simple fixes: Hours
  • Code changes: Days
  • Major updates: Weeks
Plan accordingly.

​
Still need help?

Email support

Get help from our team

Check FAQ

Common questions answered

Book a call

Schedule expert help

Documentation

Browse all guides