=== Tag Scout ===
Contributors: zemraplugins
Tags: Tags: analytics, tracking, scripts, debugging, tag-manager
Requires at least: 5.8
Tested up to: 7.0
Requires PHP: 7.4
Stable tag: 1.0.1
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Find out where your tracking code is installed. Tag Scout scans your front-end HTML and shows where tracking scripts live in your WordPress install.

== Description ==

Tracking scripts can hide in many places — plugins, themes, and custom code.
Tag Scout shows you exactly where each tracking code originates.

It scans any URL on your site and detects:

    Google Analytics 4 (GA4)
    Universal Analytics (legacy)
    Google Tag Manager (GTM)
    Meta Pixel
    Hotjar
    Microsoft Clarity

Tag Scout searches your WordPress installation for matching fragments in:

- wp_options (option values)
- wp_posts (post content across all post types, including Code Snippets CPT)
- wp_postmeta (meta values: page builders, ACF, etc.)
- Legacy Code Snippets table ({prefix}snippets), if present
- Key theme files: header.php, footer.php, functions.php in parent and child themes

   
Results are shown as clean cards with:

    Provider name (GA4, UA, GTM, etc.)
    ID (Measurement ID, UA property, GTM container, etc.)
    Snippet preview
    “Found in…” list (options, posts, postmeta, Code Snippets, theme files)

Tag Scout is read-only. It never changes your database or files — it just helps you find where to fix things.

Tag Scout does not connect to any third-party APIs or services. It only requests your own site’s URL using wp_remote_get() and scans that HTML for known tracking patterns.

== Screenshots ==

1. **Multiple tracking scripts detected**  
   GA4, UA and GTM cards together, each with IDs, snippets, and source locations.

2. **Single tracking script view**  
   GA4 implementation with Measurement ID and matching Code Snippets entry.

3. **No tracking scripts detected**  
   Clean “No known tracking scripts were detected on that URL” state.

== Installation ==

1. Upload the tag-scout folder to /wp-content/plugins/ or install via Plugins → Add New.
2. Activate the plugin.
3. Go to Tools → Tag Scout.
4. Enter a URL from your site and click Scan URL.

== Frequently Asked Questions ==

= Does Tag Scout change anything on my site? =
No. It is completely read-only. It only reads database values and theme files to show matches.

= Will it find tracking code inside themes and plugins? =
If the code is stored in options, posts, postmeta, Code Snippets, or in header.php, footer.php, or functions.php of the active theme (child or parent), Tag Scout can report it as a possible source.

= Why does it sometimes say “No matching locations were found”? =
That means the script is visible in the front-end HTML, but the exact fragment wasn’t found in the places Tag Scout searches. It may be injected dynamically at runtime by a plugin or only load under certain conditions.

= Does it detect disabled Code Snippets? =
Yes. Disabled snippets still exist in the database, so they can show up as locations even if they’re not currently running.

== Changelog ==

= 1.0.1 =
* Improved tracking source detection for Code Snippets, including clearer active/inactive status.
* Restored theme file scanning for header.php, footer.php, and functions.php in parent/child themes.

= 1.0.0 =
* Initial public release.

= 1.0.0 =
* First public release.
* Detection for GA4, UA, GTM, Meta Pixel, Hotjar, Clarity.
* Grouped implementations with IDs and snippet previews.
* Source finder for options, posts, postmeta, Code Snippets CPT + legacy table.
* Theme file checks for header.php, footer.php, functions.php.
* Read-only scan UI under Tools → Tag Scout.

== Upgrade Notice ==

= 1.0.1 =
Improved tracking source detection for Code Snippets and theme files. Recommended update.

= 1.0.0 =
Initial release.