Profound Pixel and Ad Manager are beta features. We’re gradually rolling them out to customers. Follow the Profound blog for updates.
Key facts
- The tag follows the standard pixel pattern. The install shape matches other major pixel providers’, and the events use the same names as OpenAI’s.
- The async loader never blocks rendering. If the Profound content delivery network is unreachable or the browser version is too old, the pixel goes inert and doesn’t throw errors on your page.
- The pixel doesn’t ship a cookie banner. It reads the consent signal your existing consent management platform emits and only fires events when consent is granted. See Consent and privacy.
- No package to install, no code to bundle. Profound pre-builds the script in its continuous integration pipeline and hosts it on its own domain,
pixel.profound.click.
How the pixel script works
To use the pixel, you paste a code snippet into your site and add function calls that record events. Learn more in the installation guide. Profound hosts the pixel script on its own domain. When a page loads, the snippet fetches the pixel script (p.js) from https://pixel.profound.click/sdk/v1/.
Profound’s build process enforces the script’s size limit: under 8KB compressed.
https://events.profound.click/api/v1/events. Profound records the event there and attributes it to the AI ad or AI answer that brought the visitor.
Your pixel ID
Get your pixel ID from the Ad Manager page in the Profound platform. Each pixel ID covers one site or environment, and your account can hold more than one. The ID is safe to expose in page source: it identifies you, it isn’t a secret or an auth token, and it never needs rotating. Profound enforces integrity on its side. Each pixel ID has an allowlist of origins that should include every hostname you’ll install the pixel on: the root domain (example.com), the www variant (www.example.com), and any checkout, landing-page, or regional subdomain.