Disadvantages of Page Tags
Dependence on Cookies as a Unique Identifier: While client-side solutions profess to provide human visitor information, they actually provide information about web browsers. The following assumptions made in client-side data collection raise the probability of error:
- A single user equals a single browser
- A web browser will not have multiple users
- Cookies are not likely to be turned off
- People allow their browser's cookie cache to accumulate
- People are loyal to a single browser
- People are reluctant to spend money on a new computer
Adding Page Tags to Every Page: Without a built-in header/footer structure for your website, this step will be very time intensive. Those who already have this structure set up can simply insert the page tag in a common header and footer file. For static sites (that don't use server-side includes), this tag will have to be manually inserted on every page to be tracked.
Tag Implementation Complexity: The complexity of your page tags and vendor selection will determine how long the project takes. Tagging can be done in a matter of hours or it can take weeks or months.
Time Limits on Data Storage: Many page tag vendors cannot store collected data indefinitely due to disk space and rising storage costs.
Limits on Type of Data Collected: Page tags have some restrictions in their ability to report on non-HTML views such as Adobe PDF files, error pages, redirects, zipped files and multimedia files.