in.cgi versus te_redirect.php

[peterjones]

Three things:
1. What is the difference between using in.cgi - and te_redirect.php - and how many times should redirect.php be included on a site.

2. Because there's no knowing what page a visitor is going to arrive on - surely, in.cgi has to go on every site page.

3. I can get the cookie correctly laid down on my php pages, but on my html warning page - the following just seems to be being rendered as a comment and not as an include:
<!--#include virtual="/cgi-bin/te/in.cgi?p=default&$QUERY_STRING" -->

[peterjones]

point 3 fixed - html page had to be set shtml. Still looking for clarification re points 1 & 2.

[texpert]

Hi there,

1. By using te_redirect.php you can display different index pages, based on where surfers are being referrered from (trade or country), while in.cgi simply tracks incoming, but "options / index pages" doesn't function with it.

"te_redirect.php" should only be included on the page where u're accepting incoming traffic from your trades.

2. in.cgi can be placed on the rest of the pages, yes. And prevent double tracking shall be enabled in the "options / general / main" menu.

3. You solved it already

best regards.
Jim