Rule that redirects and keeps tracking code

I don't fully understand what is happening here, but I will try to explain.

 

 

We have the following information in our external DNS structure:

 

 

Host A: thejettareport.com --> 64.207.133.221

 

Host A: www.thejettareport.com --> 199.5.47.99

 

 

The 199.5.47.99 IP is a VIP on the BigIP that redirects traffic based on uri/url content for thejettareport.com. I'm not sure what the the "www.thejettareport.com --> 199.5.47.99" record is used for. The issue is that the "tracking code" is not included when users hit the redirect to the f5, as shown below:

 

 

http://thejettareport.com --> includes tracking code

 

http://www.thejettareport.com --> DOES NOT include tracking code

 

 

This is expected behavior. My question:

 

 

Is there a way/rule for the f5 to feed the tracking code for the redirects that occur because a user hits "www.thejettareport.com"?

 

 

Hopefully this is clear. I will include below the email that was originally given to me. (I'm a network guy; not WebOps.)

 

 

Thanks,

 

Bryan

 

 

 

We are having what appears to be a domain issue for thejettareport.com domain. When I click through from google or yahoo to thejettareport.com, there appears to be a server-side redirect occurring from http://www.thejettareport.com to http://thejettareport.com

 

 

This is only an issue because the paid keywords from google and yahoo contain a query string tracking code that gets eliminated in this redirect.

 

 

When you click through on this link, the tracking code does not appear in the query string. Beyond Interactive has confirmed that that keyword is definitely associated with an appropriate tracking code.

 

 

In fact, if you load "http://www.thejettareport.com?ic_id=12345" you will see the redirect, and the tracking code eliminated from the query string

 

 

If you load "http://thejettareport.com?ic_id=12345" you will see the tracking code retained in the query string.

 

 

Do you know how to prevent this server side redirect from happening? It is impacting our click-through numbers in Omniture.