How can we help?

Yes, you are able to. Our SDK identifies the domain it is running on and attributes its data collection and analysis to that domain. Register and verify each domain in the console, and one SDK snippet covers all of them, with data kept separate per domain. See Manage domains for assignments and access boundaries.

Our SDK collects extensive telemetry of your ad stack, your page and app performance, your content, and user interaction. Using our proprietary models, we create a deep contextual and behavioral analysis from it, and the output is audiences and over 50 enrichment signals for your programmatic bidding pipelines. See Set up Prism curation enrichment for how content discovery works.

No. With the SDK connected, Prism discovers your content by itself: as users browse your site, the SDK sees the articles they visit and Prism reads and scans them automatically. Connecting a sitemap is only needed if you run Prism without the SDK, or want guaranteed coverage of low-traffic pages. Both can run together with no duplication.

Signals begin on the first SDK heartbeat after embedding, and the Pipeline Analysis page shows activity immediately. Full AI Ad Ops reports require statistical significance first, which new integrations typically reach within the first days of collection. Check the SDK status panel to see exactly where you are: connected, streaming, significance, and insights ready.

Report metrics describe the analyzed sample, which is shaped by your configuration's collection scope, daily session quota, and sample rate. When comparing against ad server or SSP dashboards, compare rates and ratios such as response rate or win rate rather than absolute volumes. Also note that today's scan is in progress until 00:00 UTC, so compare only closed UTC days.

No. The module sends only the URL path and domain to our API, and enrichment is derived entirely from the content of the current page. No cookies or user identifiers are transmitted, which keeps the integration contextual and consent-friendly by design.

No. The module fetches enrichment in the background on page load and caches it in sessionStorage, so repeat auctions in the same session cost roughly 0 ms. If the API has not responded within the configured timeout (300 ms by default), the auction is released clean. The module never blocks an auction indefinitely.

Each item in a Curation API request costs 1 API calls credit, including items inside batch requests of up to 100 URLs or article IDs. Every item is resolved independently, so one unindexed URL never fails the batch. Track consumption anytime on the Usage & Plan page, where counters reset monthly.

Domains are reserved globally and assigned to exactly one account or subaccount across the platform. If a domain you own appears taken, it may have been registered under another account, for example by a previous partner, or auto-discovered elsewhere. Contact support and we will resolve the assignment.

Invites and role changes require the Admin role. Admins can invite teammates and clients, set their role, grant per-product access such as Pipeline Analysis or Pulse, and deactivate users. See User management for the full flow, including invite expiry and resending.