Verify the pixel and connect your CRM for company resolution

Installing the pixel snippet is only the first step. This guide covers how to verify the pixel is sending data correctly and how connecting your CRM improves company resolution for AI-referred visits.

Verifying the pixel is working

After installing the pixel, open the AI Discovery Settings page in Revenue Proven. You should see a status indicator for your pixel token. To trigger a test event, visit your own website from a browser where you have manually navigated from chatgpt.com or another supported AI platform before loading your page. The Settings page will show when the last event was received, usually within a minute or two of the visit.

• The pixel must be installed on every page you want to track, not just the home page.
• Events from your own IP address will appear in the pixel logs, which is expected during testing.
• If no events appear after 10 minutes, check that the snippet is in the head section and not blocked by a content security policy.
• The pixel status page shows the last received event timestamp and the number of events in the past 24 hours.

Why CRM connection improves resolution

The pixel captures an anonymised IP signal and attempts to resolve the visiting company automatically using ASN and domain data. However, resolution accuracy improves significantly when Revenue Proven can cross-reference 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.

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 subdomain where the snippet is present. Events from unlisted domains are rejected to prevent spoofed data.