Chris Santerre wrote:
My point is whatever code/script the redir is running to generate tracking
IDs in a URL can ALWAYS be run from a company's own server. Regardless of
the method, the sender could always do it.
You're still making an assumption that what they're tracking is ad *views*.
What about tracking clicks? Suppose you have a website with ads -- or
search results -- on it, and you want to keep track of which links to
third party sites get followed. You can't do that with a web bug. You
can only do that by setting up a redirect script so that you log the
click, then send the browser off to the other site.
At that point it's a matter of locking it down so that only specific
targets are allowed, etc., or else you end up setting up a script that
can be abused by spammers. Which brings us to where this thread started.
--
Kelson Vibber
SpeedGate Communications <www.speed.net>
