Moz Analytics doesn't work
-
Hello Mozers,
Moz analytics doesn't work already more than a week. I've tried on Mozila Firefox 29.0.1 and Chrome Version 34.0.1847.137 and getting some nasty errors.
Firefox Firebug console:
TypeError: freya.getApp is not a function
...mpaign_owner_id:app.getParam('campaign_user_num'),campaign_id:app.getParam('camp...applic...23b3.js (line 223)
Chrome Firebug console:
-
Uncaught TypeError: undefined is not a function <a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:223">application-c42010fe6b0d425aca7cad19e29223b3.js:223</a>
-
freya.RoutesUtils.applyDefaultParams<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:223">application-c42010fe6b0d425aca7cad19e29223b3.js:223</a>
-
freya.RoutesUtils.make<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:223">application-c42010fe6b0d425aca7cad19e29223b3.js:223</a>
-
freya.Routes.settingsCampaignPath<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:227">application-c42010fe6b0d425aca7cad19e29223b3.js:227</a>
-
freya.views.NavSite.freya.View.extend.renderData<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:713">application-c42010fe6b0d425aca7cad19e29223b3.js:713</a>
-
freya.View.Backbone.View.extend.render<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:231">application-c42010fe6b0d425aca7cad19e29223b3.js:231</a>
-
(anonymous function)<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/pro/home:213">home:213</a>
-
fire<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:60">jquery-b68cd156547e7de90502ecf7becf0beb.js:60</a>
-
self.fireWith<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:66">jquery-b68cd156547e7de90502ecf7becf0beb.js:66</a>
-
jQuery.extend.ready<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:22">jquery-b68cd156547e7de90502ecf7becf0beb.js:22</a>
-
DOMContentLoaded<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:53">jquery-b68cd156547e7de90502ecf7becf0beb.js:53</a>
-
-
Hi Abe,
Using http://proxy.freya.moz.com/ it works but no always. I need to refresh page few time to get it right. Page load time is very slow...
-
Sorry for the outage, I am guessing this was either a part of our site being down when you tested this or your server/firewall not liking our site. Try logging in through http://proxy.freya.moz.com/ and let me know if that helps. Sorry you are unable to access the site, I'm sure we can get this to work for you
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Location Data Batch Updates via the MOZ API
According to the MOZ API documentation, I am able to update multiple Locations in a batch in order to create or update their location data, currently 130 locations. I have successfully created a batch and the API returned the $id, as I expected. Yet, it doesn't make clear how the multiple locations I want to update are supposed to be sent back to the API. I was expecting an upload of a CSV file or JSON data, and not Query Parameter as noted in the docs. When including a JSON file, properly formatted, as a binary upload, the response is still expecting a locations parameter. See error here: { "status":"MISSING_PARAMETER", "message":"locations missing. ", "response": { "locations":"MISSING_PARAMETER" } } https://mza.seotoolninja.com/developers/docs/local/api#_api_batch__id-PATCH
API | | yuca.pro1 -
What is the metric to check link state and link type for MOZ API ?
Kindly do not share the website url related to url and link metrics,instead of mention the correct metric for link state and link type. Thanks!
API | | rogerdavid0 -
I'm only seeing 3 results for DA/PA, is this a limitation?
I'm checking the DA/PA of the top 10 urls on google for a keyword, but I only get the DA/PA results for 3 of the domains, I know the other domains in the list would have results, is this a limitation on the API or should I be able to get DA/PA for more than 3 domains at a time? would it help if I only check one at a time instead of a larger set? 5dpi0h.png
API | | infernodia0 -
Alternatives to Supermetrics to get Moz metrics into Google Sheets?
Hi, Interested in getting Moz API metrics into Google Sheets on an automated scheduled. Supermetrics can do this, but I am curious to know if there are any alternatives, free or paid. Thanks! 🙂
API | | GOODSIR1 -
Domain Authority drop due to Moz update?
Hi guys, I have noticed an unusual Domain Authority (DA) drop in mid November for many different websites here in Sweden. There was a Moz update the 12th of November which I assume has to do with this drop. I have attached the DA history chart to visualize the drop. Does someone have any information about: Did the drop in DA have to do with the update the 12<sup>th</sup>? Did the new update have a new type of metric calculation? Is anyone else experiencing this drop? Any extra details would be helpful. Thanks a lot guys. YLhKVwF.png
API | | OscarSE0 -
September's Mozscape Update Broke; We're Building a New Index
Hey gang, I hate to write to you all again with more bad news, but such is life. Our big data team produced an index this week but, upon analysis, found that our crawlers had encountered a massive number of non-200 URLs, which meant this index was not only smaller, but also weirdly biased. PA and DA scores were way off, coverage of the right URLs went haywire, and our metrics that we use to gauge quality told us this index simply was not good enough to launch. Thus, we're in the process of rebuilding an index as fast as possible, but this takes, at minimum 19-20 days, and may take as long as 30 days. This sucks. There's no excuse. We need to do better and we owe all of you and all of the folks who use Mozscape better, more reliable updates. I'm embarassed and so is the team. We all want to deliver the best product, but continue to find problems we didn't account for, and have to go back and build systems in our software to look for them. In the spirit of transparency (not as an excuse), the problem appears to be a large number of new subdomains that found their way into our crawlers and exposed us to issues fetching robots.txt files that timed out and stalled our crawlers. In addition, some new portions of the link graph we crawled exposed us to websites/pages that we need to find ways to exclude, as these abuse our metrics for prioritizing crawls (aka PageRank, much like Google, but they're obviously much more sophisticated and experienced with this) and bias us to junky stuff which keeps us from getting to the good stuff we need. We have dozens of ideas to fix this, and we've managed to fix problems like this in the past (prior issues like .cn domains overwhelming our index, link wheels and webspam holes, etc plagued us and have been addressed, but every couple indices it seems we face a new challenge like this). Our biggest issue is one of monitoring and processing times. We don't see what's in a web index until it's finished processing, which means we don't know if we're building a good index until it's done. It's a lot of work to re-build the processing system so there can be visibility at checkpoints, but that appears to be necessary right now. Unfortunately, it takes time away from building the new, realtime version of our index (which is what we really want to finish and launch!). Such is the frustration of trying to tweak an old system while simultaneously working on a new, better one. Tradeoffs have to be made. For now, we're prioritizing fixing the old Mozscape system, getting a new index out as soon as possible, and then working to improve visibility and our crawl rules. I'm happy to answer any and all questions, and you have my deep, regretful apologies for once again letting you down. We will continue to do everything in our power to improve and fix these ongoing problems.
API | | randfish11 -
Lost many links and keyword ranks since moz index update
Hi All, I came back from work today from a week off to find my site has gone from 681 external inbound links to 202. With this my domain authority, moz trust and moz rank have all also taken a slip. Compounding this, I am seeing a slip most of my keywords rankings. If i try to use the open site explorer to explore my links and see what going on i get the message It looks like we haven't discovered link data for this site or URL. If i check the just discovered links like it suggests I get It looks like there's no Just-Discovered Links data for this URL yet. I know these features worked before the index as i used them. Is this all attributable to the moz index issues that have been noted or could something have happened to my site? Since i started 2 months ago I have made many changes including... Updating the site map that was 4 years out of date and included 400 broken urls Removed blank pages and other useless webpages on the site that contained no content (from the previous administrator) Edited a few pages content from keyword spammy stuff to nicely written and relevant content Fixed url rewrites that made loops and un-accessible product pages All these changes should be for the better but the latest readings have me a little worried. Thanks.
API | | ATP0 -
Google Analytics connection keeps breaking
Hi, Every time I log back in to Moz my Google analytics connection breaks. I have to reconnect it every time I want to look at something. Thanks, Amelia
API | | CommT0