Ana içeriğe geç

Report a batch of page views from a connected web site (browser key)

POST 
/api/public/attribution/pageviews

The visitor's page journey: what the chat widget's loader sends when a page is hidden or left. Up to 20 views, each with the browser's own id, so a retry or a second report of the same view only lengthens its time on page. Same keys, domain check, CORS and text/plain JSON body as recordWebsiteTouch; its own rate limit per key + client IP.

Stored per view: the address WITHOUT ad click ids, its path, the document title, the referring host (another site's only), when, how long it was visible, and whether the page reported analytics/ads consent. Never the IP or the user agent. Views from a host the site does not own, or timed more than a day ago, are dropped. With the site's "track visits" switch off nothing is stored (outcome: ignored).

CONSENT: the visitor_key is the attribution runtime's (the 90-day _cw_at id with ads consent, a per-tab-session id without). A key reported without consent is its own in-session visitor; it is joined to the chat's visitor only when the person identifies themselves in that session (writes in the chat, submits a form carrying the key, sends the WhatsApp ref code issued to it).

Request​

Responses​

The site's "track visits" switch is off (outcome ignored).