There are two cases in which AT Internet will use a 302 redirection:
New visitors with server-side cookies:
If a visitor sends a hit towards our servers but no cookies are set for them, then the collection server will force a 302 redirect. This initial hit is not taken into account, as it is simply a way of asking for a third-party cookie to be set on the xiti.com collection domain. Once the cookie has been created, a second hit is sent containing the exact same information as well as an &Rdt=On parameter. This second hit has a 200 OK status and is processed.
If you're using a redirection tag (go.url, go.click, gopc.url, go.ad ...) the hit will have a 302 status, but it will be taken into account. Once the event has been measured, the redirect you specified in the tag takes place.