Find your pixel snippet
Each brand has a unique pixel tied to its brand ID. To get yours:Select your brand
Make sure the correct brand is selected in the sidebar brand switcher. The snippet is personalized to the selected brand — using a snippet from the wrong brand will attribute traffic incorrectly.
Install the pixel on your website
Paste the snippet into the<head> section of every page on your site. Place it before the closing </head> tag, ideally as early as possible so it loads before other scripts.
The snippet you copy from Settings → Pixel has your actual project URL and brand ID already filled in. Do not use the placeholder values shown above.
<noscript> beacon at the end of the snippet is an image-based fallback that captures AI bot crawls even when JavaScript is disabled. Keep both the <script> and <noscript> tags together.
Install via Google Tag Manager
If your site uses Google Tag Manager instead of direct<head> edits:
Paste the snippet
Paste the full Pharos snippet (including the
<noscript> block) into the HTML field.Set the trigger
Add a trigger and select All Pages. This ensures the pixel fires on every page view.
Advanced tracking
Beyond passive attribution, the pixel exposes apharos() function you can call from your own JavaScript for conversions, user identity, and cross-domain tracking.
- Conversion tracking
- User identity
- Cross-domain tracking
Call Conversion events are associated with the session’s original referral source, so you can see which AI platforms drive not just visits but actual outcomes.
pharos('trackConversion', ...) when a user completes an important action. Pass the event name and an optional numeric value (for revenue tracking).Verify your installation
After installing the pixel, confirm that it is working correctly before relying on the data.Click Verify
Click the Verify button. Pharos checks for tracking events received from your brand in the last 24 hours.
Review the result
The result panel shows one of four states:
If the status is partial or not detected, the panel lists specific troubleshooting steps.
| Status | Meaning |
|---|---|
| Pixel verified | 5 or more events in the last 24 hours — the pixel is working correctly. |
| Partial detection | Fewer than 5 events, or only bot traffic — the pixel may not be on all pages. |
| Pixel not detected | No events in the last 24 hours — check the installation steps below. |
| Verification error | Pharos couldn’t reach its database — try again in a moment. |
Common installation issues
- No events detected: Confirm the snippet is in the
<head>section of every page, not just the homepage. Open your browser’s developer console and check for JavaScript errors on load. - Partial detection: The pixel may be missing from some page templates. Check that your
<head>snippet is in a shared layout component rather than individual pages. - CSP blocked: If your site has a Content Security Policy, add the Pharos SDK domain to your
script-srcandconnect-srcdirectives. - Tag Manager not firing: Verify the trigger is set to All Pages and that the container has been published, not just saved.
What data the pixel collects
The pixel records the following for each visit:- Referrer source — the domain or platform that sent the visitor (e.g.,
chatgpt.com,perplexity.ai) - Referrer type — categorized as AI, organic, direct, or other
- Page visited — the URL of the page the visitor landed on
- Timestamp — when the visit occurred
- User agent — used for bot vs. human visitor classification
pharos('identify', ...) explicitly.
To see AI traffic data after the pixel is installed, go to the AI Traffic page in the sidebar.
