Why do I have two hits including one with a 302 redirect?

A 302 redirection can appear in the context of a Smarttag implementation when Piano Analytics needs to set server-side cookies.

302 redirect for server-side cookie creation

If a visitor sends a hit to Piano Analytics collection servers and no cookie is set yet for that visitor on the collection domain, the collection server forces a 302 redirect.

• The first hit returns 302. It is not taken into account because it is only used to request that the browser set a cookie on the collection domain.

• After the cookie is created, the browser sends a second hit with the same information, plus an additional parameter &Rdt=On. This second hit returns 200 OK and is processed.

Rdt=On is the indicator that the hit was sent after the redirect/cookie step succeeded.

Why you may not see the 302 hit in Tag Inspector

It’s normal to see the 302 in your browser network tools but not in Tag Inspector: the redirect hit is not processed as a tracked hit, so it may not appear in tools focused on measured events.