You are using a CDN. You logs are altered. The distributed file servers may be using 302s to redirect traffic.
On a normal server set-up, a 302 response code is a temporary redirect. If you are using "www" and visitors, bots & scrapers are requesting files without the "www" then you'll see a lot of 301s & 302s. That's the most common occurrence. There are many other reasons for seeing 302s in your logs.
A redirect--whether 301 or 302--should be followed immediately by a fresh request. For example, if they ask for with-www and you tell them to go to without-www, the logs will show two requests for the same filename. (http vs https is similar, only the information will be in two separate log files.) That's assuming the visitor is human. Robots can behave differently.
If you're seeing any kind of redirect not followed by a fresh request, then they're getting redirected to some place other than your site. Take a closer look at your htaccess-or-equivalent and see if there's anything that doesn't belong. In fact, just ftp into your site and look at the timestamp on your htaccess. If it says yesterday, and you know you haven't changed anything in weeks, there's a problem.
In all likelihood, the 302s are normal and are having no effect on earnings.
If you analyze the ad paths, you'll find that quite a few redirect from the displayed address to another address. AFAIK they do this to control where the user goes which is different from the address they often use in their Adwords account.