Hey Xavier!

This was the reason we weren't seeing it, but as you can see, Google's crawler is a clever little thing. It can pick up a lot of cool stuff that Roger can't. Fortunately, this is exactly the type of error we want Roger to show you, so we probably wouldn't change it so Roger could figure out these things anyways. It's great that Google figured it out, but it would have been understandable if they hadn't been able to.

Hope this helps!

@sk That is definitely one of the solutions! There are a few reasons this might be happening. Usually, if you have the correct account and profile already selected, the only fix is to disconnect the GA account and then reconnect it. While it does say that you'll lose some data by doing this, the data loss is temporary because we'll repopulate it all when you reconnect from historical data in GA the entire re-population could take a few days though since we won't have it cached anymore). Also, make sure that you have selected the correct account and profile in GA.

You can verify this by going to your GA account, going to the profile that corresponds with your campaign, finding the number of that profile, and checking it against the profile number embedded in your homepage you're tracking. If they match up, you're gold! GA accounts and profiles can sometimes get mixed up so if you have more than one of either, try changing it to another profile. It might work that way.

You may have to wait for traffic data to repopulate but the current data in the Traffic Data tab will repopulate pretty quickly (immediately most of the time). Hope that helps! If you're still not able to get it to work, send us an email at help@seomoz.org with your PRO email address, the campaign that's having issues, and examples/screenshots of your GA account if you can! We'll try to get you running ASAP.

Hey Kalen! Rogerbot is the crawler we use to gather data on websites for Moz Analytics and the Mozscape link index. Here's his info: http://moz.com/help/pro/what-is-rogerbot-.

I wish I could give you IP addresses, but they change all the time since we host Roger in the cloud. There's not even a reliable range of IPs to give you. You can totally whitelist the useragent rogerbot, but that's the only reliable information about the crawler you can go off of. I hope that helps but let me know if there's any other solution you can think of. Thank you!