Product addresses
The addresses used by the tag, the capture script, the dashboard, and TV Mode, and what to allow in the site's firewall and CSP for collection to work.
Updated on
The product uses four addresses, on two domains. A site with a restrictive Content Security Policy or a network with a corporate proxy can block one of them without showing an error, and the symptom is the same as for an unauthorized domain: the tag is installed and no data arrives.
| Address | Who uses it | Where it appears |
|---|---|---|
| tracking.pagesignal.net | The collection tag, on the site | The src attribute of the <script async> in Instalação & Tag (installation and tag) |
| cdn.pagesignal.io | The newsletter capture script, capture.js | The code in Instalar script de captura (install capture script) |
| admin.pagesignal.net | The dashboard, in the operator's browser | The address bar |
| pagesignal.io | The TV Mode link, on the television | The TV Mode dialog |
On the site
The site's CSP must allow tracking.pagesignal.net and cdn.pagesignal.io. Since the tag loads scripts and sends data, the directives involved are script-src and connect-src.
On the newsroom network
The network must reach admin.pagesignal.net, for the dashboard, and pagesignal.io, for the television. A proxy that blocks either address prevents login or the display of the TV screen.
Collection and the dashboard use the pagesignal.net domain; TV Mode and capture use pagesignal.io. The allow rules must cover the 2 domains.