Unusual setups
Your stack page already names its normal forwarder. Use this page only when that choice does not fit how traffic reaches your site.
| What you run | Forwarder | Why it fits |
|---|---|---|
| A Node application where middleware runs on Node with persistent disk | App-hook | Observes the requests your app receives and queues them durably. |
| A web server with readable combined-format access logs | Origin-log | Reads logs outside the request path. |
| A supported CDN where cache-served requests matter | Edge-worker | Observes requests before cache responses leave the edge. |
| WordPress | WordPress | Observes after WordPress sends its response. |
Install exactly one primary forwarder per site: the one that sees traffic where it is best observed. A second forwarder is harmless for cross-validation because overlapping observations stay as separate raw records; it does not double-count the primary view.
If no forwarder can run on your site, the install line can still measure browser pageviews. Tell us about the limitation so we can disclose the missing crawler and ad-blocker coverage honestly.