siteline Start free trial Log in

First-party proxy

See your data

Serve the script and the collect endpoint from your own domain so more events survive ad blockers that drop a third-party analytics host. SiteLine does not manage custom CNAMEs in v1. You configure the reverse proxy.

Proxy both the script (/js/script.js) and the collect path (/api/analytics/event, or the js/event route the app also accepts). Point data-endpoint at the absolute URL on your domain. If the endpoint is relative, the browser will post to your site and the proxy must forward that path.

Pass X-Forwarded-For and X-Forwarded-Proto on the collect path so truncation (IPv4 /24, IPv6 /48) hashes the visitor, not the proxy's IP. If every visitor collapses to one office NAT, uniques become one bucket.

The hostname allowlist still applies to the page hostname, not to the proxy host. Register the site you are measuring. The proxy does not turn a public site id into an open collector.

Configure it

  1. Register and add the website. The trial is 7 days, no card, from $4.99/mo. Copy the public site id.
  2. Forward /js/script.js and /api/analytics/event from your host to the SiteLine origin. You can also forward the js/event path the app accepts.
  3. Point data-endpoint at the absolute collect URL on your domain. A relative endpoint posts to your site, and the proxy has to forward that path.
  4. On the collect path, pass X-Forwarded-For and X-Forwarded-Proto. Truncation (IPv4 /24, IPv6 /48) should hash the visitor, not the proxy address. If every visitor collapses to one office NAT, uniques become one bucket.
  5. Load a page on the registered hostname. The install screen clears when the first pageview arrives.

SiteLine does not issue a certificate or a CNAME for this. The proxy is yours. Events from a host you did not register are still rejected.