Integrations
AI Discovery Pixel: CSP and Deployment Details
The AI Discovery pixel sends events to Revenue Proven when AI assistant traffic is detected. This guide covers Content Security Policy directives, single-page app support, and ad-blocker behavior.
AI Discovery Pixel: CSP and Deployment Details is part of the authenticated Revenue Proven workspace. The pixel loads from Revenue Proven, stores the first-party rp_vid visitor identifier and posts to the script origin /api/p/collect. CSP connect-src must allow the Revenue Proven app origin. The page is documented against the current production interface rather than a mockup or an obsolete navigation path.
What this guide covers
Pixel Settings provides the workspace-specific script, token version, allowed origins, and reachability checks needed for AI-referral visitor tracking. The controls and values shown depend on the signed-in workspace, its connected providers, plan entitlements, member role, and any data already synchronized or seeded for demonstration.
Use this article to understand the page’s purpose, where its data comes from, and the safest next action. Revenue Proven separates read-only analysis from explicit mutations so that opening a page never implies that an external write has occurred.
Current product workflow
Pixel Settings provides the workspace-specific script, token version, allowed origins, and reachability checks needed for AI-referral visitor tracking. This screenshot was captured from the current production route while signed in to the populated Shawn Brown demo workspace.

Install the snippet in the site head, register the exact production origin, and use Recheck when the domain changes. Pro can view setup while full configuration requires the applicable entitlement. Interface labels and availability follow the current plan, role, connection, and workspace context.
Unlike Shawn’s other AI Discovery pages, rareplantshop.vercel.app and its Reachable status are real production test configuration. Confirm the active workspace and understand whether a control reads data, changes local configuration, or calls an external system before using it.
Data, access, and permissions
Unlike Shawn’s other AI Discovery pages, rareplantshop.vercel.app and its Reachable status are real production test configuration. Real synchronized values can change after a scheduled sync, while seeded demo rows are deterministic examples and must not be presented as customer benchmarks.
Feature availability is enforced on the server. A button may be hidden or disabled when the workspace lacks the required plan, add-on, OAuth scope, account role, owner permission, or rollout flag. Team membership never bypasses owner-only write guards.
Operational guidance
Before changing anything, verify the active workspace, selected account, date range, provider filters, and saved configuration. If a screen looks incomplete, allow asynchronous charts and grids to finish loading and check Workspace > Connections for sync health.
Use read-only preview, filter, export, and drill-down controls freely. Treat controls labelled Save, Submit, Apply, Resume, Sync, Send, Publish, Delete, Reconnect, or Regenerate as state-changing actions and confirm their effect before continuing.

