My AI Discovery pixel is installed but not recording any visits
You installed the Revenue Proven pixel snippet on your website but the AI Discovery Visitors dashboard shows zero visits. A script loading issue or incorrect data-tenant attribute is the most common cause.
You copied the pixel snippet from Settings > AI Discovery > Pixel and added it to your website, but after 24-48 hours the Visitors section of the AI Discovery dashboard shows no data and no AI-referred visits.
Why this happens
The pixel snippet must load on every page that you want to track, and the data-tenant attribute must contain your exact tenant token from the Settings page. If the script tag is missing the data-tenant value, is placed after a Content Security Policy that blocks external scripts, or is only added to one page while visitors come via AI links to other pages, visits will not be recorded.
How to fix it
- Go to Settings > AI Discovery > Pixel Setup and copy the snippet again. Confirm the data-tenant attribute contains a long token string, not a placeholder.
- Open your website in a browser, right-click and view page source, then search for revenueproven to confirm the script tag is present on the page.
- Open browser developer tools > Network tab, reload the page, and filter for /p.js. Confirm the script loads with HTTP 200. A 404 means the script URL is wrong; a blocked request means a CSP or ad blocker is preventing it.
- If you use a Content Security Policy, add revenueproven.com to your script-src directive.
- Ensure the pixel is placed on all pages you expect AI traffic to land on, not just the homepage. AI assistants often deep-link to blog posts or product pages.
- Wait 24 hours after correcting the installation. The visitor data pipeline has a processing delay and visits appear in the dashboard the following day.
- Send yourself a test visit by clicking a link to your site from an AI assistant conversation and confirm the referrer is chatgpt.com or similar.
Still stuck?
Contact support with your website URL and a note about which pages the pixel is installed on. Our team can verify the pixel is firing correctly from our ingestion endpoint logs.