Facebook Tracking Alternatives: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Michael= HTTP includes a referrer header that is used to tell you where your traffic comes from. So all the data is already there in our nginx web server logs for tracking t...") |
No edit summary |
||
| Line 1: | Line 1: | ||
= | =Q= | ||
Right. If that is the case, is there an effective alternative? And how do we quantify how effective a possible solution is compared to FB/Google tracking? I wonder who has looked into this issue in detail. | |||
=A= | |||
HTTP includes a referrer header that is used to tell you where your | HTTP includes a referrer header that is used to tell you where your | ||
traffic comes from. | traffic comes from. | ||
Latest revision as of 19:59, 12 March 2020
Q
Right. If that is the case, is there an effective alternative? And how do we quantify how effective a possible solution is compared to FB/Google tracking? I wonder who has looked into this issue in detail.
A
HTTP includes a referrer header that is used to tell you where your traffic comes from.
So all the data is already there in our nginx web server logs for tracking the number of hits we get that originate from facebook.com (or any other domain). Awstats currently will show us this, but I don't think it breaks it down easily for reporting over time. We may need a plugin/config for Awstats. Or use another log analysis tool.