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

# Common issues & solutions

> Quick fixes for frequent tracking problems

## 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

<AccordionGroup>
  <Accordion title="What you're seeing">
    * No events in your dashboard
    * Live Debugger is empty
    * Chrome extension says "No tracking detected"
  </Accordion>

  <Accordion title="Common causes">
    * Wrong project ID entered
    * Ad blockers preventing tracking
    * Tag not published yet
    * Browser security settings
  </Accordion>

  <Accordion title="How to fix it">
    **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
  </Accordion>
</AccordionGroup>

### Wrong project ID issues

<Warning>
  The project ID should be numbers only (like 664), not include "project\_" or any other text.
</Warning>

**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

<AccordionGroup>
  <Accordion title="Quick checks">
    1. Visit your website
    2. Open Tag Insight Live Debugger
    3. Click around your site
    4. Events should appear within seconds
  </Accordion>

  <Accordion title="If nothing appears">
    **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
  </Accordion>
</AccordionGroup>

### Missing information in events

You might see alerts like "Missing required variable" or "Incomplete event data".

<Tabs>
  <Tab title="What it means">
    Your tracking is working but missing important details. Like submitting a form with blank fields.
  </Tab>

  <Tab title="Example">
    A purchase event might have:

    * ✅ Total amount: \$99.99
    * ❌ Order ID: missing
    * ❌ Currency: missing

    This makes reporting incomplete.
  </Tab>

  <Tab title="How to fix">
    **Work with your developer to:**

    1. Add the missing information
    2. Or mark it as optional if not always available
    3. Set default values where appropriate

    **For marketing team:**

    * Document what data you need
    * Explain why each field matters
    * Prioritize critical vs nice-to-have
  </Tab>
</Tabs>

## Data quality problems

### Wrong data types

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

<Steps>
  <Step title="The problem">
    Price shows as "\$29.99" (text) instead of 29.99 (number)
  </Step>

  <Step title="Why it matters">
    * Can't calculate totals
    * Reports show errors
    * Averages don't work
  </Step>

  <Step title="The fix">
    Tell your developer:

    * Remove currency symbols from numbers
    * Send prices as numeric values
    * Put currency in separate field
  </Step>
</Steps>

### Inconsistent formats

Different formats for the same information cause confusion.

<AccordionGroup>
  <Accordion title="Date formats">
    **Problem**: Dates like "01/15/2024" vs "2024-01-15"

    **Solution**: Pick one format and stick to it
  </Accordion>

  <Accordion title="Currency codes">
    **Problem**: Using "\$", "dollars", "USD" randomly

    **Solution**: Always use standard codes (USD, EUR, GBP)
  </Accordion>

  <Accordion title="Product IDs">
    **Problem**: SKU12345 vs sku-12345 vs 12345

    **Solution**: Define one format for all products
  </Accordion>
</AccordionGroup>

## Alert fatigue

### Too many unnecessary alerts

Getting bombarded with alerts that aren't real problems.

<Tabs>
  <Tab title="Common causes">
    * Test traffic triggering alerts
    * Optional data marked as required
    * Development sites being monitored
    * Too sensitive settings
  </Tab>

  <Tab title="Quick fixes">
    **1. Filter test traffic**

    * Exclude your office IP
    * Ignore development sites
    * Filter test user accounts

    **2. Adjust requirements**

    * Make truly optional fields optional
    * Set realistic thresholds
    * Focus on critical events

    **3. Schedule alerts wisely**

    * Group similar alerts
    * Set business hours only
    * Choose daily summaries over instant
  </Tab>
</Tabs>

## Chrome extension issues

### Extension not working

<AccordionGroup>
  <Accordion title="Basic troubleshooting">
    1. Check extension is installed and enabled
    2. Refresh the page
    3. Try incognito mode (with extension allowed)
    4. Update to latest version
  </Accordion>

  <Accordion title="Still not working?">
    * Uninstall and reinstall extension
    * Check for conflicting extensions
    * Try different browser profile
    * Clear browser data
  </Accordion>
</AccordionGroup>

## Performance issues

### Site seems slower

For high-traffic sites, tracking can impact performance.

<Steps>
  <Step title="Symptoms">
    * Pages loading slowly
    * Browser using lots of memory
    * Laggy interactions
  </Step>

  <Step title="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
  </Step>
</Steps>

## 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

<CardGroup cols={2}>
  <Card title="Regular checks" icon="calendar">
    Review tracking weekly, not just when things break
  </Card>

  <Card title="Test changes" icon="flask">
    Always verify tracking after website updates
  </Card>

  <Card title="Document setup" icon="book">
    Keep notes on your configuration
  </Card>

  <Card title="Train your team" icon="users">
    Ensure everyone knows basics
  </Card>
</CardGroup>

## Common questions

<AccordionGroup>
  <Accordion title="Why did tracking suddenly stop?">
    Usually due to:

    * Website updates
    * Tag manager changes
    * Browser updates
    * Security policy changes

    Check when it last worked and what changed.
  </Accordion>

  <Accordion title="Can I fix issues myself?">
    Some things yes:

    * Browser issues (clear cache, try another)
    * Extension problems (reinstall)
    * Alert settings (adjust in dashboard)

    Technical fixes need developer help.
  </Accordion>

  <Accordion title="How long do fixes take?">
    Depends on the issue:

    * Configuration changes: Minutes
    * Simple fixes: Hours
    * Code changes: Days
    * Major updates: Weeks

    Plan accordingly.
  </Accordion>
</AccordionGroup>

## Still need help?

<CardGroup cols={2}>
  <Card title="Email support" icon="envelope" href="mailto:support@taginsight.com">
    Get help from our team
  </Card>

  <Card title="Check FAQ" icon="question" href="/troubleshooting/faq">
    Common questions answered
  </Card>

  <Card title="Book a call" icon="phone" href="https://taginsight.com/demo">
    Schedule expert help
  </Card>

  <Card title="Documentation" icon="book" href="/">
    Browse all guides
  </Card>
</CardGroup>