RP
RevenueProven
All Docs
AI Discovery Pixel Settings

AI Discovery Pixel Settings

Generate your tracking snippet, manage allowed origins, verify installation, and rotate your secure token for AI-referrer tracking.

The Pixel Settings page is where you generate the AI Discovery tracking snippet, manage the domains authorized to send events, verify that your pixel is reachable, and rotate your HMAC-signed token. The pixel detects visits from AI assistants and sends them directly to the Revenue Proven event ingestion endpoint; you authorize your site by adding its domain to the Allowed Origins list below. Full pixel configuration is available on the Pro plus AI Discovery add-on, Growth, Scale, Agency, and Enterprise plans.

AI Discovery pixel settings showing the snippet and verification status
The Pixel Settings page with the generated snippet, allowed origins management, and per-domain verification status.

AI assistants detected by the pixel

  • ChatGPT (chatgpt.com)
  • Claude (claude.ai)
  • Google Gemini (gemini.google.com)
  • Perplexity (perplexity.ai)
  • Microsoft Copilot (copilot.microsoft.com)
  • OpenAI ChatGPT Android app

How to set up the pixel

  • In the left sidebar, open AI Discovery and go to Settings
  • Copy the snippet from the installation panel. The snippet has the form: <script src="...p.js" data-tenant="..." data-token="..." async></script>
  • Paste the snippet into the <head> section of every page on your website, or add it via a tag manager on an All Pages trigger
  • Add your website's origin as an allowed origin in the Allowed Origins section. Use origin-only format (scheme and hostname only, with no path or query string).
  • Click Verify to probe the origin and confirm Revenue Proven can reach it
  • To rotate your HMAC token, click Rotate Token and update the snippet on your site with the new token value

How the pixel sends data

The pixel sets a first-party cookie named rp_vid with a one-year expiry to identify returning visitors. By default, the snippet posts events directly to the Revenue Proven event ingestion endpoint at the origin the script is served from, so no proxy or extra setup is required. Add your site's domain to the Allowed Origins list so the cross-origin requests are accepted. Bot requests and empty user-agents are filtered out before any event is processed.

Plan availability: the pixel is fully disabled on Free plans and shows no data. Pro plan users can copy the snippet but cannot add or edit allowed origins or rotate the token. Full configuration, including origin management and token rotation, is available on the Pro plus AI Discovery add-on, Growth, Scale, Agency, and Enterprise plans.