Verify the pixel and connect your CRM for company resolution
After installing the AI Discovery pixel, verify it is firing correctly and connect your CRM so Revenue Proven can match anonymous AI-referred visits to known company accounts.
Installing the pixel snippet is the first step. This guide covers how to verify the pixel is actually sending data and how connecting your CRM significantly improves company resolution for AI-referred visits.

Verifying the pixel is working
After installing the pixel, open AI Discovery Settings in Revenue Proven. The status section shows whether your pixel token is active and when the last event was received. To trigger a test event, visit your own website from a browser tab where you have first navigated to one of the supported AI platforms (chatgpt.com, claude.ai, gemini.google.com, perplexity.ai, or copilot.microsoft.com) before loading your page. The Settings page will reflect the new event within a minute or two.
- The pixel must be installed on every page you want to track, not just your home page.
- Events from your own IP address will appear in the pixel logs during testing — this is expected.
- If no events appear after 10 minutes, check that the snippet is in the head section and is not blocked by a Content Security Policy header.
- The pixel status section shows the last event timestamp and the 24-hour event count.
Why CRM connection improves company resolution
The pixel captures an anonymised IP signal and attempts to resolve the visiting company automatically using ASN and domain data. Resolution accuracy improves significantly when Revenue Proven can cross-reference those signals against your CRM accounts. When a match is found, the AI-referred visit is soft-linked to the CRM account — letting you see which known accounts are researching you through AI platforms, not just anonymous traffic volumes.
Configuring your origin allowlist
For security, Revenue Proven only accepts pixel events from domains you have registered in the AI Discovery Settings page. Add each domain where you have installed the pixel — for example, your main marketing website and any subdomains where the snippet is present. Events from unlisted domains are rejected to prevent spoofed or third-party data from appearing in your AI Discovery reports.