# Adding Trackers
***
### Step 1: Scan URL for Trackers
Quickly check if your site already has tracking scripts installed.
* Enter your site URL in Scan URL (e.g., [`https://example.com`](https://example.com/)).
* Click Scan URL.
* If trackers are found, they appear in the Available Trackers list.
* Select the trackers you want and attach them to your project.
> Use this if you’ve already embedded trackers in your website code and just need to connect them to this project.
Tips
* Scan the public URL that actually serves your pages (avoid staging or password-gated URLs unless accessible).
* Some script managers (e.g., GTM) may require the page to fully load—open the page in a new tab first if a scan returns nothing.
### Step 2:Add New Tracker
If your project needs a tracker that isn’t found by the scan:
* Click Add Tracker.
* Paste the tracker id (e.g., GA, Microsoft Clarity, Hotjar).
* Save. The tracker now appears under Current Trackers.
> Use this to manually install additional analytics or marketing pixels.
### Step 3: Current Trackers
This section lists the trackers currently attached to your project.
* To stop using a tracker, click Remove (you can always re-attach it later from Available Trackers, if applicable).
* If no trackers are attached, you’ll see:
* *“No trackers attached to this project. Scan a URL or add trackers from your organization.”*
### Step 4:Available Organization Trackers
If your organization has pre-approved (shared) trackers, they’ll appear here.
* Click to attach any available organization tracker to your project.
* If you see *“All organization trackers are already attached,”* there’s nothing else to add.
### Best Practices
* Verify detections: After a scan, confirm the trackers listed match what’s actually installed on your site.
* Avoid duplicates: Don’t attach the same tracker twice (e.g., two GA4 tags), which can inflate analytics.
* Align with policy: Use only the trackers your team has approved (e.g., company-wide GA4 or Clarity).
* Respect privacy: Ensure your use of trackers complies with consent/notice requirements (e.g., GDPR/CPRA) and your cookie banner setup.
### Troubleshooting
* Scan found nothing:
* Ensure the URL is publicly accessible and not behind auth.
* Check if an ad-blocker is hiding scripts during scan.
* Single-page apps: make sure the base route serves the script tags.
* Tracker shows attached but no data:
* Verify the correct property/site ID in the snippet.
* Check domain filters and consent settings in the tracker’s dashboard.
* Seeing duplicates:
* Remove one copy via Current Trackers, and confirm only one snippet is present in your site/template or tag manager.
***
